Page Comparison

This page describes some common errors and suggestions how to resolve them.

*On this page:*

{toc}

h1. Windows Errors

h2. Overview of Windows Related Errors

* [Windows XP SP3 Sows Havoc, Users Complain|http://www.informationweek.com/news/windows/operatingsystems/showArticle.jhtml?articleID=207600950] - The problems with XP SP3 range from spontaneous reboots to outright system crashes. At [InformationWeek.com|http://www.informationweek.com]

* Negative error codes for file operations indicate the negative of a Windows code: http://msdn.microsoft.com/en-us/library/ms681381%28VS.85%29.aspx.

h2. Error -32

SAP2000 error # -32 corresponds to Windows error code # 32, which is a sharing violation as described at http://msdn.microsoft.com/en-us/library/ms681381%28VS.85%29.aspx

The error is most likely due the the file in question being used by another process. You should be able to resolve this error by closing all other programs that may be potentially using the file or by restarting your computer.

h2. Error 112

{code}
ERROR_DISK_FULL
112 (0x70)
There is not enough space on the disk.
{code}


h2. Error 430 when exporting to Excel

To resolve this error, please try the following on the machine that is giving the Error 430:
 
(1) Unregister DAO by clicking "Start, Run", copy and paste the following, and click OK

  regsvr32 /U "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"

(2) Re-register the DAO by clicking "Start, Run", copy and paste the following, and click OK

  regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"

{hidden-content}
Related emails:

* {email:from=rs|to=ok|date=10/8/2010|subject=Unable to export to Excel|comment=Suggests to re-register DAO to prevent Error 430.|id=6357124}
{hidden-content}

 

h2. Error 480

Error 480 is related to insufficient graphics memory. The best way to handle it is to use a lower resolution and/or fewer colors. If you have a graphics accelerator, you can also try changing the amount of acceleration to something less than the full value and see if that helps.

h1. Analysis Errors

h2. Error Auto Meshing Area Object

*Troubleshooting tips:* We usually use whole-to-part approach to troubleshoot such issues. Basically, you go on deleting the model incrementally till the problem areas are isolated.

If the area has more than 4 nodes and the program is unable to mesh it then it is likely that this area (and assignments associated with it) do not go to the analysis model at all. Given that, it is recommended that this issue be resolved.

h2. Error in computing frame section locations

* You should verify that the auto meshing tolerance is smaller than the anticipated auto meshed member length. {verify}

{hidden-content}
See also [t:Error|t:Error]
{hidden-content}