	Product(s):	ProjectWise Explorer Client
	Version(s):	08.11.11.111
	Area:	MISC
	Original Author:	Dana Guthrie, Bentley Technical Support Group

Error or Warning Message

Last Error [319] Cannot start application for the specified document. Check your program associations. Failed to generate managed workspace configuration file. Dynamic library loading failed.

Explanation

User has MIcroSation SS2 and 2004 edition on the system
The global association seems to pick up the 2004 edition
User created a user association to open SS2

When opening file via ProjectWise with MIcroSation 2004 it works fine
When opening file via ProjectWise with MIcroSation SS2 user gets error
Last Error [319] Cannot start application for the specified document. Check your program associations. Failed to generate managed workspace configuration file. Dynamic library loading failed.

How to Avoid

Option 1:

Found that the ProjectWise global association was set for MS 2004
On the client had user remove the user association and then recreate it

Go to tools \ associations \ programs
Change the "select an association view' to User associations
Scroll down in the list to MicroStation, expand Microstation, Expand open, then if an association exists, right mouse click on it and choose unassociate. Click Okay

To create a user association, Right click a dgn file, choose open with, browse, if the correct program shows up in the programs page then choose and click okay, if it does not, click the browse button and navigate to the executable in this case ustation.exe then click open, then okay. If you will always use this program for dgn's, then check the box for always use this program, then click okay

Had user open local document organizer and purge the workspace files.

Go to tools local document organizer, click view then choose 'workspace copies'
Highlight all the workspace files that appear and then right click and choose purge
You may need to do this for copies as well.

Then had user open the file via ProjectWise using his user association with MS SS2 and the workspace reloaded and opened the file with no errors

Option 2:

Another problem might be that one of the files associated with the workspace, the master file or its references, may be corrupt.

To test, Export \ Send to folder the master file. The Master and References should be exported. In some cases you may get the error while doing the export that points to the offending file.

If the export succeeds try opening the file locally to see if it opens properly.

Option 3:

The ProjectWise Explorer logs (pwc.log) can help narrow down what files that are part of the workspace that are inaccessible. Contact support for help turning up and reading logs, if needed.