Geopak's exception.log file is missing and unable to set .prj file

RE: Geopak's exception.log file is missing and unable to set .prj file

Michael VerHoef — Wed, 15 Dec 2021 13:39:53 GMT

Erin, just in case you're still dealing with this problem a year later, there's a draft green book out from 10 years ago that says GPK files are the only ones not integrated into the projectwise environment. The best guidance is to store the GPK on a local server or machine.

You can read the full article here. GreenBook - GEOPAK in a ProjectWise Environment - Content Management Files - Content Management - Bentley Communities

This was a severe oversight on Bentley's part when creating ProjectWise. I'm personally stumped as to why they were able to make .alg files in InRoads work perfectly for multiple users on ProjectWise but they couldn't make GPK files work on ProjectWise.

RE: Geopak's exception.log file is missing and unable to set .prj file

Erin Owens — Wed, 30 Dec 2020 19:16:13 GMT

Luckily, an experience colleague warned me about trying to open any CAD program from the desktop, so I am not making that particular mistake!

As for your second question, perhaps I'm a bit lost. It is my understanding that I am trying to set a new local .prj file for my own Geopak to help it point to the proper working directory and job number that are set up already in the prime's projectwise environment. I do not know of any other existing .prj files I could import and try to open.

Another piece of information that might be useful is that if I try to just work in the .dgn file itself, I don't seem to get any crashes. So far the error only occurs when trying to set the working directory and job number in project manager.

RE: Geopak's exception.log file is missing and unable to set .prj file

MaryB — Tue, 29 Dec 2020 19:41:37 GMT

This may not be related, but it came up with a coworker today...Are you starting Geopak from your desk shortcut, or are you going through the ProjectWise Client, and opening your file with Power Geopak from there? I have seen unpredicatable behavior when files in a ProjectWise environment are opened from the regular desktop shortcut. Certain permissions and environment variables don't get set correctly if not set by the ProjectWise Client app.

This may have nothing to do with it, but it's worth checking.

Can you open project files that already exist? Is it just trying to create the new project?

RE: Geopak's exception.log file is missing and unable to set .prj file

Erin Owens — Tue, 29 Dec 2020 19:09:32 GMT

Thank you for the response, Mary!

I did verify that I have the rights to create a file in that location.

And I did then proceed to follow those instructions for deleting the .rsc files in the specified location. I also verified that there were no .rsc files anywhere else other than the proper folder they should be in. But after deleting those files, then closing and reopening PowerGeopak, the same behavior persisted.

I also checked again in the folder the exception.log should be placed - and it remains missing.

Do you happen to have any other thoughts on the matter? And, is there value to the tactic of just uninstalling and reinstalling this whole program?

RE: Geopak's exception.log file is missing and unable to set .prj file

MaryB — Mon, 28 Dec 2020 19:09:49 GMT

There could be a few things going on. Do you have the ProjectWise permissions to create a file in the location you want to place it?

It's always worth deleting the Geopak Resource files, per this Wiki article. over time, those can cause all sorts of weirdness.