Page Comparison

{info}
This page describes errors and suggestions for their resolution.
{info}

\\

{on-this-page}

h1. Installation errors

h2. Error 1722

"Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected." error message sometimes occurs during the part of the installation that is installing DirectX. It usually means that DirectX is in use. We would recommend re-booting the system and re-installing, choosing Repair. Or better yet, uninstall, reboot, and re-install.

{hidden-content}
Related Incidents:

* {incident:no=36586|comment=Installation error 1722.}
{hidden-content}

h1. Windows Errors and Errors with Error Codes

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. File Write Error #4

File Write Error #4 occurs when nonlinear modal time-history results exceed the 2GB file size allocated for data. Please see the [time-history results exceeding 2GB|kb:Nonlinear modal time-history results exceeding 2GB] page for additional details and suggestions for resolution.

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 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 41: Allocate Error #41

Error 41 is due to insufficient virtual memory. If the model is large and is reaching memory limits, there may not be any fix for this error other than reducing the size of the model.

On an XP system you may be able to get a little more virtual memory by changing the c:\boot.ini file to allow 3GB per process. This should be done by a technician who understands the implications of making this change. A 64-bit machine may not have this problem, but a slightly larger model may yet run into memory limits.

Another approach to try is to close program and re-open it, and try to extract results, perhaps for a subset of the model and/or a subset of the tables. Using the [OAPI|kb:API] may also help.

{hidden-content}
Related Incidents and Emails:

* {incident:no=31943|comment=Explanation of error 41 by bm}
** {email:date=1/28/2011|from=bm|to=mnk|subject=Memory allocate error 41|comment=|id=6881465}
* {incident:no=42148|comment=Strategies to mitigate error 41.}
{hidden-content}

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. Cannot run analysis\!

This error is triggered by a model having no joints, or having elements of a particular type but without any of the corresponding properties.

{hidden-content}
Related incidents:

* {incident:no=33808|comment=Explanation of the "Cannot run analysis!" error}
** {email:date=4/4/2011|from=bm|to=ok|subject=Cannot run analysis error|comment=Explanation of the error|id=7635147}
{hidden-content}

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}

h1. Other errors

h2. Database formatting data is corrupt and has been refilled by the program. Please check the Options menu > Set Program Default Display Units command.

This error may be related to the fact that the file is saved where the program does not have full read/write access. If this is the case, the issue can be resolved by saving the file locally and re-opening it.

{hidden-content}
Related Incidents:

* {incident:no=32261|comment=Possible explanation of the error.}

Other errors:

* {incident:no=32644|comment=FILE WRITE ERROR # 4. THE DISK MAY BE FULL, THERE MAY BE A SHARING CONFLICT, YOU MAY HAVE INSUFFICIENT RIGHTS, OR SOME OTHER ERROR MAY HAVE OCCURRED. (This error could be also caused by a 2GB size limit on the file size created during modal time history analysis.}
{hidden-content}