[CONNECT] Cant open or export DWG

Hello Loren,

Can you have a look where the MicroStation seed files are located. You can do this with the key-in:
$ % explorer $(MS_SEEDFILES)
If you can find seed files in that location, please check using the Open/Save options for DWG to see if that location is the same as for the MS_SEEDFILES variable
Also please check the accessibility to the TMP location and make sure you have also write access to that location.

If these suggestions don't help solving the issue, can you send us a debug file. You can create one by adding the swithc -debugfileopen to the command prompt
Have you done a 'standard' installation?

 

Hi Rene,

1. TMP, TEMP, and MS_TMP all set to folders with R/W access and over 500gb free space
2. Standard installation using defaults
3. The seedfile variables are left at the uStn defaults. Each folder exists with R/W access:
4. Please note that we are experiencing the same thing on all (5) CONNECT installations.
5. I have inserted msdebug.txt below, if this didnt work please provide a link
6. msdebug.txt

P.S - We work exclusively with 3D files

Just an update:
1) I created a new workset and workspace today to see if that would fix this problem. No Joy
2) I un-installed RealDWG 2014, tried to export/open DWG - No Joy
3) I re-installed RealDWG 2014, tried to export/open DWG - No Joy
4) I un-installed RealDWG 2014 and installed ReadDWG 2016 - No Joy
5) I finished work and am going home - will try more tomorrow

Another update:
1) Installed CONNECT on brand new system - DWG opens fine
2) Installed PowerView on same system - DWG wont open in PowerView
3) All our other systems having the CONNECT DWG problem have either MicroStation and/or PowerView (or at least PowerView) v8i installed on them as well.
4) Thinking that the first installation of a Bentley product "steals" the DWG handling, uninstalled all Bentley products from one of the problem systems, rebooted and installed CONNECT only. Still cant open DWG. Installed PowerView on same system - PowerView opens DWG fine.

Possible Conclusion: CONNECT does not play nice with other installations of 32bit Bentley products. This should be enough for Bentley staff to reproduce this bug.