We are running InRoads SS2 v08.11.07.615. We have Alternate Workflow checked on. We are using Project Wise Connect Version 10.00.01.25. The .alg file is set to Read-Only. The user will check-out the file in InRoads and check back in after changes are made. Our .xin file is set to Read-Only for the Geometry.
From time to time without warning our .alg gets corrupted and empties out all alignments. We cannot figure out why this is happening. We scramble to find the latest .alg file on our hard drives and restore it as best we can.
Users open the .alg file as a single open while others use a .rwk file.
I have seen something similar once before, but it was a user's error that was using the Save As dialog to save their project (RWK) and manually changing it to ALG and overwriting the existing ALG. If this were the case, you could open the file in notepad and tell immediately see if this is happening.
Beyond that, I would make sure everyone is on the same version of InRoads, and make sure again that everyone has the Alternate Workflow variable checked.
Thanks Kevin..........I don't think we have the problem of overwriting the ALG file with a RWK file. I sort of got a good chuckle with that one. We did find that one user was running .536 instead of .615. He has that version for a specific client. Can he run two versions? or is that complicated?
This still does not explain the corruption I went thru yesterday. The user has the correct version of InRoads and the settings set for the "Use Alternate Workflow Method". He was working on the .ALG in the morning. He loads the .ALG from PW Connect not thru a RWK file. He made some vertical changes, saved it and later in the day he opened the .ALG again to print a report and the file was corrupted.
Would you suggest loading thru an RWK file or just a regular open of the .ALG file? Our RWK file has many DTM's to load for modeling purposes. This user does not do a lot of modeling therefore he just loads the ALG file.
User Since TDP in the 80's,
Vax based Unix Workstations - Interpro32,
from the Intergraph Corp.
We got a chuckle as well when we finally opened the "corrupted" ALGs in notepad and saw "RWK" at the top. Since that is not the case with you, I do not recall any other reports of corrupted ALGs back in SS2, so we might just have to try to see if you can get it to where you can reproduce a specific workflow to something we can test here. I did try to open and ALG in .615 this morning and make vertical changes to a couple of different profiles and did not see any corruption.
No you can not run .536 and .615 on the same machine, and there is not difference in opening the ALG in a dialog vs an RWK file.
Thanks Kevin, We are going to try to narrow down the issue by creating RWK files for the users. Whereas if someone only needs the .ALG and existing surface vs someone like me who does most the modeling has a RWK with all of the templates and corridors and DTM's loaded.
Additionally, I have created a couple of new RWK files and I noticed that the .ALG file is opened from my hard drive but unchecked in PW. When I do a SAVE on the .alg file the .alg on PW appears to be saving. Is this part of the "Alternate Workflow"???? I was reading the article on ProjectWise and Plotting Integration with Bentley InRoads and it indicated to me that the .ALG is loaded in memory rather than checked out?
The alternate workflow checks out the alg to open it in memory and then checks it back in. in that process, it determines who has read-write and read only access to various alignments and the cogo buffer. If everyone has read only on everything, once someone checks out an alignment, it repeats the check out check in process, to update the access properties. If someone keeps read-write access to an alignment or the cogo buffer, no one else can get read-write access until that person checks them back in.
The check in check out process for alg data is handled by InRoads, using a similar interface to the way it might have been done when the alg was on a network share. But there is no lck file. As for what it uses instead, is beyond my pay grade.
We only recently started trying to share alg files in projectwise and mostly for Ss4
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration