[CONNECT] Cant open or export DWG

I cant open or export a DWG file in CONNECT. I get the following error with open:

[test.dwg] is not in a  recognized file format

And and invalid dwg seed file when trying to export.

Cant even open the DWG seed files provided with SELECT. I have reproduced this on three different systems.

Parents
  • 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?

     

    René R. van den Brink
    Technical Support
    Bentley Systems Incorporated

  • 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

  • Does terrasolid happen to deliver Intel's Thread Building Block module? Check all of the folders under MS_LIBRARY_PATH, including your OS's $(PATH) environment variable, and see if you can find a file called tbb.dll. I expect only one turned up from RealDWG folder. If you find more than one, check its version number.



  •  think you may have hit this one on the head. A search for tbb.dll (I'm assuming you made a type with .ddl) reveals 13 different instances of that file and 6 different versions. 4 installed by Bentley, two by autodesk and 7 others installed by various software throughout the system. 

    3.0.2011.0427 C:\Program Files\Autodesk\AutoCAD Civil 3D 2013\tbb.dll 180.00 KB 25-06-2011 6:06
    3.0.2011.0427 C:\Program Files\Autodesk\DWG TrueView 2013\tbb.dll 180.00 KB 23-05-2012 10:46
    4.2.2014.0601 C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\MdlSys\Filehandler\RealDwg2016\tbb.dll 236.00 KB 17-07-2014 2:09
    4.1.0.0 C:\Program Files\Blue Marble Geo\Geographic Calculator\tbb.dll 316.00 KB 12-06-2015 11:57
    2.2.2009.1011 C:\Program Files\ERDAS\Image Web Server Utilities 2011\bin\tbb.dll 275.00 KB 20-08-2012 6:31
    4.2.2014.0601 C:\Program Files (x86)\Bentley\DGNIndexer\RealDwg2016\tbb.dll 187.00 KB 03-07-2014 0:35
    4.0.2012.0408 C:\Program Files (x86)\Common Files\Bentley Shared\RealDWG2014\tbb.dll 151.00 KB 23-10-2012 9:03
    4.2.2014.0601 C:\Program Files (x86)\Common Files\Bentley Shared\RealDWG2016\tbb.dll 187.00 KB 05-02-2015 13:10
    2.2.2009.1011 C:\Program Files (x86)\ERDAS\ER Viewer 11.0\bin\tbb.dll 231.00 KB 23-06-2011 6:18
    2.2.2009.1011 C:\Program Files (x86)\GlobalMapper14\tbb.dll 216.00 KB 17-01-2013 15:58
    2.2.2009.1011 C:\Program Files (x86)\Quantum GIS Lisboa\bin\tbb.dll 216.00 KB 19-11-2010 14:18
    2.1.2009.0325 C:\Windows\Installer\tbb.dll 176.00 KB 25-07-2012 11:06
    4.1.0.0 C:\Windows\System32\tbb.dll 287.00 KB 20-10-2014 17:52

  • Try to rename C:\Windows\System32\tbb.dll to a temporary name and see if it fixes your problem.

    Are you able to track down which product that has installed TBB on your c:\Windows\System32\ folder?



    Answer Verified By: Loren 

  • Thanks Don - renaming tbb.dll did the trick!
    I will see if I can identify the culprit software and update this forum if I find it.

    Answer Verified By: Loren 

  • I would start with C:\Program Files\Blue Marble Geo\, as it shows the same version of TBB that is found in your system's folder.

    If you can post back with whatever you will find, that will be much appreciated, as it may benefit other folks reading this forum.

    TBB is a parallel process utility developed by Intel and made as an open source code a few years ago. Some programmers who develop software for large data processing use this utility to improve their application's performance. Unfortunately, while it is an open source SDK, Intel recommends against creating versioned modules from this utility. As a result, different software vendors that use this utility would install different versions of TBB on the same user's computer. Since everyone thinks his/her program is the most important of all, he/she may insert his/her program's folder at the top of the search path, or worse yet directly place his modules into system's folder, potentially causing other programs that share the same dependency to fail. I'm not holding my breath that Intel may one day change their SDK and/or their recommendation of single module, but I sure hope that application developers who use TBB to avoid inserting their application folders into system's search path. And no one should install their modules on system's folders other than Microsoft's own runtime dependencies.



Reply
  • I would start with C:\Program Files\Blue Marble Geo\, as it shows the same version of TBB that is found in your system's folder.

    If you can post back with whatever you will find, that will be much appreciated, as it may benefit other folks reading this forum.

    TBB is a parallel process utility developed by Intel and made as an open source code a few years ago. Some programmers who develop software for large data processing use this utility to improve their application's performance. Unfortunately, while it is an open source SDK, Intel recommends against creating versioned modules from this utility. As a result, different software vendors that use this utility would install different versions of TBB on the same user's computer. Since everyone thinks his/her program is the most important of all, he/she may insert his/her program's folder at the top of the search path, or worse yet directly place his modules into system's folder, potentially causing other programs that share the same dependency to fail. I'm not holding my breath that Intel may one day change their SDK and/or their recommendation of single module, but I sure hope that application developers who use TBB to avoid inserting their application folders into system's search path. And no one should install their modules on system's folders other than Microsoft's own runtime dependencies.



Children
No Data