• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 6289 views
  • Users 0 members are here

ProjectWise Error 222 - User Can't Open DGN

jcallicott
Offline

Two users in ProjectWise cannot open DGN files. They receive Error 222:

When I look at the pwc.log file, it has this entry:

2019-11-18 10:55:24,206 FATAL [0x00001d0c] pwise.dms.workspace - processConfigurationFiles(): Runtime error occured. CsbFileIncluder has failed to get CSB file names for a level.

2019-11-18 10:55:24,206 ERROR [0x00001d0c] pwise.dms.workspace - Failed to compile configuration files. Compilation failed with aaApi error [50164] and error message [(null)].

2019-11-18 10:55:24,207 ERROR [0x00001d0c] pwise.dms.workspace - Failed to create final configuration file.

2019-11-18 10:55:24,207 ERROR [0x00001d0c] pwise.dms.workspace - Configuration file generation for the document [91637, 8] failed.

2019-11-18 10:55:25,324 ERROR [0x00001d0c] pwise.dms - Error 222 "Cannot start application for the specified document. Check your program associations.

Failed to generate managed workspace configuration file.

An exception raised."

I tried logging in with my credentials on the affected PC, but I too received the same error on that PC. I'm wondering what (if anything) on a particular PC would prevent the Configuration Settings Blocks' names from being delivered. The problem sure feels PC specific. 

Of note: this is not on our own PW system, but rather that of another company hosting files for our use.

Any ideas are appreciated!

Parents
  • 0 Offline

    I ran into this a while back. After a server upgrade, this started happening to some (but not all) MicroStation V8i clients. In this case, it was the use of %level directive in a cfg file that was being loaded as part of the managed workspace. The same might happen if you are using the %level directive in a CSB. Removal of the %level directive fixed the issue. It was very difficult to track down, as the log messages were very cryptic, and only one made mention of level, but didn't state that was the problem. Level is mentioned in your first error message, so it might be a similar issue.

    Please note that I post here on a voluntary basis and am not a Bentley employee. 

Reply
  • 0 Offline

    I ran into this a while back. After a server upgrade, this started happening to some (but not all) MicroStation V8i clients. In this case, it was the use of %level directive in a cfg file that was being loaded as part of the managed workspace. The same might happen if you are using the %level directive in a CSB. Removal of the %level directive fixed the issue. It was very difficult to track down, as the log messages were very cryptic, and only one made mention of level, but didn't state that was the problem. Level is mentioned in your first error message, so it might be a similar issue.

    Please note that I post here on a voluntary basis and am not a Bentley employee. 

Children
No Data

Communities
Support and Services
Training and Learning
Social Media