A user has a problem with Geopak cogo crashing when he tries to list points or store curves. He has a survey project created, and opens classic cogo from the survey manager. He is able to store points, but can't list them without crashing. Also, if he tries to store a curve, cogo also crashes. I had him perform a clean and compress on the database, but the problem persisted. He was working from the network file server, so I had him copy all his files to his local drive, but the same thing happened. I had him create a new survey project locally and try it again, but same problem.
I copied his files to my computer, set up a survey project, opened cogo and was able to do everything he was trying to do with no problems. I am in a different office, so I don't have quick access to his computer other that remote desktop, but does anyone have any suggestions? I have check his preferences, and nothing looks wrong.
He is running Win XP Pro, MS V8i SS2 and the most recent versions of Geopak Survey. As a side note, we tried on a different computer in his office running Microstation V8 2004 and Geopak Survey 2004, and that crashed also.
You might have him try deleting the Geopak .rsc files on his machine. Might also check to see if any .rsc files have ended up out on the network where the files and gpk are located. I can't say that we have seen many problems with them corrupting with cogo, but we see this happen often in other processes so this has become one of our first trouble shooting tips when these type of issues pop up.
Sounds more like there are multiple GEOPAKexe running... be sure to check following a crash if any remaining GEOPAK process are running (ctrl - alt- delete > process tab... sort to look for GEOPAK.exe) end any GEOPAK.exe processes running and re open...
A batch process can be completed to complete this simply create a txt file and copy the text below... rename the fil.bat
@echo off
for %%i in (powergeopak.exe geopak.exe powercivil.exe iplotorg.exe ustation.exe draft.exe xs.exe InRoads.exe PowerInRoads.exe) Do TaskKill /F /T /IM %%i
Good luck
Michael Barkasi
Application Engineer
Reality Modeling
Sorry for taking so long to reply to this thread, but thanks guys for the tips to keep in mind. Turned out to be a dns problem on the network. Rebooting the file server fixed it, and it hasn't recurred.
Can you further explain why dns issue would have anything to do with the crash? As you already mentioned you've tried working locally that still yielded a crash.