| Applies To | |||
| Product(s): | AutoPIPE, | ||
| Version(s): | ALL | ||
| Area: | Open | ||
| Original Author: | Bentley Technical Support Group |
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: Rename Undo files
a. Open folder location where model was stored
b. All Undo files are saved as a U01...U**.
c. Rename one of these files to *.DAT
d. Open with AutoPIPE.
Option #3: Recover files from Temp folder
a. Select Start button
b. In the field just above the button type in "%temp%", and press keyboard enter / return key.
c. This will display your user profile temp folders, scan down for a folder with the format "AP_..." (ex. AP_11, AP_09, etc..) and open this folder to view the files within.
Note: This folder contains temp files used by the program. When a file is closed by the program, it will automatically remove these temp files. If AutoPIPE is currently closed, no model is open on your system, these represents instances where AutoPIPE may have been closed incorrectly or system crashed where these files could not have been automatically removed.
d. Search for a folder with the correct system name that was being worked on, and open that folder.
e. If there are files within it, move the entire folder to a safe location (ex. desktop), and try to open the AutoPIPE DAT model from this new folder location. Otherwise use the steps above to rename any BAK or Uxx files and open them for review.
f. If successful in recovering a file, with it still open in AutoPIPE, save the file to the correct working directory location typically used for your AutoPIPE models.
Note: If AutoPIPE is closed, no model is currently opened, you may delete the AP_xxxx folders from the %temp% location with out concern.
Option #4: Recover NTL file (if available)
Open the affected model's folder location and search for an filename.NTL file. If available use the following procedure:
a. Start AutoPIPE
b. Select File> Open> AutoPIPE Batch (*.NTL).
The model should now open in the same state when the file was originally created.
Option #5: 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 #6: 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 #7: 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 #8: 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.
Option #9: Create a Bentley case and send Zip file of folder for review
Please create a case that references this WIKI page, send all files in the folder into a single ZIP file, and attach it to the case for review. It is important to include as much historical information about the model as possible, such as its storage location (local or server) and any edit commands utilized, such as copy and paste. Any additional details that could assist the development team in their investigation would be greatly appreciated.
When and IF a model is returned, refrain from using it in a production environment until you have thoroughly reviewed it and confirmed its accuracy.