Step #1:

Review the *.log files

AutoPIPE provides a number of translators to import files from other programs (PCF Translator, ADL Pipe Translator, etc..). While using these programs they will usually generate a filename.log file for the user to review. There is valuable information in the log file:

1. Detailed information about what a what a component was mapped to
2. Default values used if information was missing from imported files
3. etc..

Step #2:

Review the *.msg files

There are multiple files created when importing a file into AutoPIPE (DAT, BAK, LCK, PRV, MSG, etc..). The *.MSG file contains valuable information about the imported file. The user can review warnings and errors that occurred during the import process. These *.MSG files can be opened by any text editor (i.e Notepad++, Ultra Edit, MS Word, etc..). See WIKI here for additional information about the messages. 

Example

In this example, at node point 104 a new pipe size was defined (PIPE 0.1-10). However the translator could not understand what wall thickness or pipe schedule to use. Therefor it assumed a default wall thickness = outside dia / 4. The user is warned about this via the warning message in the *.MSG file and should immediately review the pipe properties and update them as needed. 

Avoidance, the PCF file is either missing wall thickness information or the information is not formatted correctly. After determining which is the primary reason, work with technical support of the application used to create the PCF file to correct the problem. 

After pressing Convert button in the PCF translator, the following happens behind the scene:

1. The translator generates an AutoPIPE Batch *.NTL file.
2. AutoPIPE automatically starts
3. AutoPIPE automatically reads in the newly generated *.NTL file 

If successful, the user can then start using AutoPIPE as required to complete the stress analysis.

However, if there is a problem the program will either:

• Generate an Abort report

or

• The application will close

Review the Abort report, if available, for more information on why the imported *.NTL file aborted. Otherwise continue to step #3.

Step #3:

1. Open the *.NTL file (located in the same folder as the imported file) using any text editor (i.e Notepad++, Ultra Edit, MS Word, etc..)
2. Go to the end of the file to see how many line numbers there are in the file (ex 8480 lines)
3. Divide the total line numbers in half, and go to that line number (ex. go to line 4240)
4. Go to the next Batch Input Command (ex. line #4250) see AutoPIPE help section: Help > Contents> Contents Tab> Bentley AutoPIPE> Batch NTL Input Reference> Command Card Reference)
5. Delete from this line and all lines to the bottom of the file (ex. delete lines 4250 to 8480)
6. Save the file with a new name (ex. Test1), make sure the file extension is .NTL
7. Start AutoPIPE
8. Inside of AutoPIPE select File > Open> select AutoPIPE Batch *.NTL
9. Search for and try to open the last *.NTL file just saved. 

The newly created file will either open or it will not open and crash again. 

If the file opens:

Great, but half the file is still missing and there is no indication on why the imported file crashes.

1. Open the original file again in a text editor
2. Divide the total delete line in half again, add this value to the starting line number and go to that line number (ex. 4249 + (8480 - 4250) / 2] = 4249 + 2125 = 6374, go to line #6374)
3. Again, go to the next Batch Input Command (ex. line #6380)
4. Delete from this line and all lines to the bottom of the file (ex. delete lines 6380 to 8480)
5. Save the file with a new name (ex. Test2), make sure the file extension is .NTL
6. Start AutoPIPE
7. Inside of AutoPIPE select File > Open> select AutoPIPE Batch *.NTL
8. Search for and try to open the last *.NTL file just saved. 
9. The newly created file will either open or it will not open and crash again. 

Repeat the process as needed to delete more lines or add lines back into the file. At one point there will be a single command card between the file that imports and the file that does not import. Use AutoPIPE help to determine exactly what part of the command card is not configured or missing, open the original file make the necessary change and try to import the complete newly fixed file. 

Note there may be more than one error in a file. Again, repeat the process as need until the complete file is imported. 

If the file Does Not open:

Well at least we know that the problem is in the first half of the file.

1. Open the last saved file again in a text editor
2. Perform the same steps again:
3. Divide the total line numbers in half, and go to that line number (ex. go to line 4250 / 2 = 2125)
4. Go to the next Batch Input Command (ex. line #2130) 
5. Delete from this line and all lines to the bottom of the file (ex. delete lines 2130 to 4250)
6. Save the file with a new name (ex. Test2), make sure the file extension is .NTL
7. Start AutoPIPE
8. Inside of AutoPIPE select File > Open> select AutoPIPE Batch *.NTL
9. Search for and try to open the last *.NTL file just saved. 

The newly created file will either open or it will not open and crash again.

Repeat the process above until the file opens in AutoPIPE and follow those instructions above to resolve the issue.