Problem:

When opening a model in AutoPIPE the program crashes. How to fix the model so it can be opened by AutoPIPE?

Solution:

Apply one or more of the following options as needed:

Option #1: Try to open the *.BAK file:

a. Create a new folder on the host desktop

b. Locate the folder where the model is stored, look for a *.BAK file.

c. Copy this file to the new folder location above. 

d. Start AutoPIPE and open the *.BAK file from the new folder location.

e. If the file opens, immediately save the model back to the original folder location.

f. If the file does not open, continue to next option.

Option #2: Insert the model into a different model.

a. Open AutoPIPE and create a new file, be sure to mimic the exact same settings on the "General Model Options" dialog when creating this new file (ex. piping code, edition, number of thermal cases, etc..) and press the OK button.

b. When the model prompts for the first node point, press the "Cancel" button to close the Segment dialog. 

c. Use the File> Insert Model> AutoPIPE Model (*.DAT).

d.  The Insert Model dialog is displayed. Select the drive and directory containing the model to be inserted, highlight it in the file list, then press OK.

e. The model which will be inserted is opened, and the prompt to "Select base point" is displayed. Specify the base point by selecting it with your mouse, or input the point name in the panel which appears near the command line (bottom left corner of the application screen) and press OK button to continue.

f. A Consistency check is performed, then the Paste dialog is displayed. Select the first option "Use Actual Coordinates:" and press OK button.

g. Wait a moment for the entire model to be imported and then use the Zoom Extents toolbar icon to see the entire model that was imported. 

h. Review the entire model and settings to be correct. 

i. Save file and continue working.

If this option did not work, continue to next option.

Option #3: Check the file name

E512-149: Model name must not contain space character... error message in AutoPIPE

If this option did not work, continue to next option.

Option #4: Model opens in older version but not in newer version:

The problem is created by model consistency check because of buried pipe result options. Consistency check creates new extra data records. As a result all arrays, after extra data, are moved forward and any pointer to these arrays calculated before that become invalid. Consistency check deals with arrays directly only when an update to some data is required.

Avoidance: Open Model in previous version First, use File> Save As> AutoPIPE Batch (*.ntl). Open newer version of AutoPIPE and use File> Open> AutoPIPE Batch (*.NTL) select the file created by the previous step. Model should now open. 

Option #5: Projectwise was not installed correctly, problem 2738, may need to reset the Registry

It seems the whole problem is caused by the location of where the Windows registry vbscript dll library is registered. If it is registered in HKEY_CURRENT_USER (wrong) instead of HKEY_CURRENT_MACHINE (correct), from security reasons the installation script has no access to VBscript engine. The solution is to remove the library registration from HKEY_CURRENT_USER tree.

In regedit application:

Find {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key in HKCU (HKEY_CURRENT_MACHINE) tree and delete it. There should be only one such key.

From command prompt:

Start command prompt (cmd) as administrator. Key in:
•(32bit OS) reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
•(64bit OS) reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

Now the installation should be OK, I am not quite sure if under some circumstances the new reregistration of vbscript.dll isn't required.

Reference WIKI here

Option #6: Create a Bentley SR and send Zip file of folder for review:

Please log a service request referencing this WIKI page,  save all the file in the folder to a single ZIP file and attach to the service request for review. Try to provide as much model history about the file as possible, i.e. where the model is stored (local / Server), using edit commands like copy/paste, etc... basically anything that might help point a direction for the development team to investigate would be a help.

The development team has a special filter process that may fix a model. However, after you receive the fixed model back from the development team, Do Not use this fixed model in production unless you have completely reviewed and found it to be correct.

See Also

Bentley AutoPIPE has crashed

Bentley AutoPIPE