ekalpakoff

Created a project, created a visio file, made a plan view page that included about 16 hi-res photos in it. Saved. Tried to check in the project... see attachment. Checked the size of the visio file 211mb. sooooooooo......

How big is too big? Any Thoughts?

ChristianB

I've had the same problem on three occasions when the project folder exceeded 150 mb. Last time I lost 4 days of work because the project was listed as checked in when in fact it was not. So all files in my local project folder was overwritten when I checked the project out again. Veeeeeery funny.... SO, I now create a locally stored zip-file of my local project folder before I try to check in the project.

__________________
Project manager/project director

[SIGPIC][/SIGPIC]
Trondheim
Norway
www.fotophono.no

fryeguy

First, I'm guessing the photo resolution exceeds your needs (but maybe not). If so, it is definitely worth compressing the images prior to usinf in Visio. Visio files tend to easily get very bloated in my experience.

Next, I assume you were working on this in a location local to your server and not over VPN. I often work on large project files via VPN and this can be very combersome. Not only because transferring files over VPN is generally pretty slow but because D-Tools tends to get agitated when anything takes a long period of time and chokes.

There is a file worth taking a look at. Depending on your OS it may be something like this: C:\Program Files\D-Tools\SI 5\DTools.SystemIntegrator.Navigator.exe.config.

Take a look at the section labelled "FileManagerService" and the CloseTimeout as well as reveiveTimeout values. Depending on circumstances, these values effectively stop a project check-in or check-out if it surpasses the threshold. Sometimes the result is the project says it is checked in but the project files like drawings may be left behind. This results in overwritten files when you attempt to check out the project again. By "adjusting" some values in the above mentioned file I was able to get around this problem. Of course this is all in SI5.5.378.0 not SP2. It is possible that my issue was fixed in SP2 but I am currently planning to wait for SI6 to upgrade .

NareshN

What freguy says is correct - the config files define the timeouts.
SP2 does increase the default service timeouts. However we cannot set a very high default as if there was really a service problem we would never know for a while.
If you have a problem in your environment then I suggest you contact support on how to increase timeouts.

grichards

if the check in aborts because of a timeout shouldn't the status stay checked out? at least users wouldn't be losing data this way.

__________________
Systems Technician/Crestron Certified Programmer
www.ccisolutions.com
[SIGPIC][/SIGPIC]

NareshN

There is a check in SP2 that the project is marked as checked in only if the check in succeeds.

ekalpakoff

hmmmm. What I was experiencing was the check-in would time out but still mark it as checked in.

fryeguy

are you running SP2? It is nice to know this was addressed. I also ran into some problems from the timeout...
for 99.9% of the scenarios I come across SP1 works just great!!
I will not be upgrading our environment until SI6.
Looking forward to the abandonment of legacy code.

ekalpakoff

SP2, Windows 7, 32-bit

fryeguy

Sounds like the update addresses this issue. It also sounds like some mechanism that can determine if the file is still checking in would be valuable.