Trouble-shooting
This section describes typical problems that can be encountered on a PowerShape network and the solutions to those problems.
There are three classes of symptom that indicate problems with your software:
| Class | Symptom |
|---|---|
| Crashing | Returns unexpectedly to the operating system. |
| Hanging | Being left in the program, but unable to do anything. |
| Error conditions | Shown by error messages. These may lead to crashing or hanging. |
Note: When you start PowerShape, the powershape_startup_log file is added to the tmp folder. This file contains details of the checks performed when starting PowerShape. It also contains any warnings and errors. Errors or warnings are also displayed in a dialog on the screen when you start PowerShape.
Crashing
For PowerShape crashing, a list of symptoms, their possible causes and solutions are given in the table below:
| Symptom | Possible cause | Solution |
|---|---|---|
| Crash when trying to start PowerShape. | Incorrect installation. | See Installation problems |
| Crashing when trying to create a new graphics window. Crashing when trying to enter a "!" to issue an operating system command within the PowerShape Command window. |
Insufficient virtual memory. | See Virtual memory problems. |
| Program crashes when performing an action on a particular model, but other models behave normally. | Damaged models | See Corrupt databases. |
| Program crashes for no particular reason. | Software error. | If possible, capture any error messages displayed in the operating system's Command window and pass on to Software Support. See Software errors. |
Hanging
If PowerShape hangs, use the following list of symptoms, their possible causes to identify a solution to the problem:
| Symptom | Possible cause | Solution |
|---|---|---|
| Hangs on start up. | Incorrect dates in C:\Program Files\Autodesk\PowerShapexxxxx\sys\hci where xxxxx is the version number of the software. Incorrect installation. Insufficient virtual memory. |
While access rights are not the cause of the problem, the solution involves changing them. See Operating system access rights. See Installation problems. See Virtual memory problems. |
| Hangs when trying to create a new graphics window. Hangs when trying to enter a "!" to issue an operating system command within the Command window. |
Insufficient virtual memory. | See Virtual memory problems. |
| Hangs, usually with a message in the terminal window about semaphore files. | Locked shared database tables. | See Locked shared database tables. |
| Hangs when trying to create or save a model and you do not get an error message. | Possible causes are insufficient disk space or a problem with the network. | See Network breakdowns. |
| Hangs when performing an action on a particular model, but other models behave normally. | The model is damaged. | See Corrupt databases. |
| Hangs for no particular reason. | Software error. | If possible, capture any error messages displayed in the operating system Command window and send to Software Support. See Software errors. |