Page Comparison

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

\\

{on-this-page}


h1. Installation errors

Installation errors are listed as follows:

h2. Error # 1722

*Error Message:* Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.

* This error message is linked to the phase of installation associated with DirectX. The error usually indicates that DirectX is in use at the time of installation. In the event of its occurrence, it is recommended that users re-boot the system and re-install, choosing Repair. An even better option is to uninstall first, then reboot and re-install.

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


h1. Windows errors and errors with error codes

Windows and code-based errors are listed as follows:

h2. Overview of Windows-related errors

* {new-tab-link:http://msdn.microsoft.com/en-us/library/ms681381%28VS.85%29.aspx}System Error Codes{new-tab-link} \- This article describes negative error codes for file operations which indicate the negative of a Windows code.

* {new-tab-link:http://www.informationweek.com/news/windows/operatingsystems/207600950}Windows XP SP3 Sows Havoc, Users Complain{new-tab-link} \- This {new-tab-link:http://www.informationweek.com}InformationWeek{new-tab-link} article describes spontaneous reboots and system crashes which occur with XP SP3.


h2. Error # 0

* This error is associated with the array pointers, which may become corrupted while editing the model. To resolve, recreate the data arrays by selecting Edit > Auto Relabel All > OK.


h2. File Write Error # 4

*Error Message:* 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.

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

{hidden-content}
*Related Incident:*
* {incident:no=32644|comment=File Write Error # 4}
{hidden-content}


h2. File Write Error # 5

*Error Message:* File Write Error # 5. The disk may be full, there may be a sharing conflict, you may have insufficient rights, or some other error may have occurred.

* Models should not be run from servers as this may corrupt the files. Copy the \*.edb file to your desktop, then run it on the local hard drive. Ensure that large models have sufficient disk space.

{hidden-content}
*Related Incident:*
* {incident:no=46476|comment=ETABS file write error}
{hidden-content}


h2. Error # 10

* This error occurs onceeither when another user is running the software, or when the software [license|kb:Licensing] has expired. To resolve expiration, submit a new license request with {new-tab-link:http://www.csiberkeley.com/licensing/license-request}CSI Licensing{new-tab-link}.


h2. Error # \-32

* [SAP2000|sap2000:home] error # \-32 corresponds to Windows error code # 32. This is a sharing violation most likely due to the file in question being used by another process. This error should be resolved by closing all other programs that may be using the file, or by restarting the computer. Additional details may be found on the Windows {new-tab-link:http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx}System Error Codes{new-tab-link} page.


h2. Error # 41

*Error Message:* Error 41: Allocate Error # 41

* Error # 41 is due to insufficient virtual memory. If the model is large and reaches memory limits, there may not be any resolution other than reducing the size of the model.

* Those using an XP system may be able to increase 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. Under similar circumstances, a 64-bit machine may not experience this problem, though a slightly larger model may then approach memory limits.

* Another approach may be to close the program, re-open, then try to extract results for a subset of the model and/or a subset of tables. It may also be useful to implement the [OAPI|kb:API].

{hidden-content}
*Related Incidents and Email:*

* {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

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

* As described in the error message, Error # 112 is associated with there not being enough disk space to perform a process.


h2. Error # 430 when exporting to Excel

To resolve error # 430, on the machine producing the error, please complete the following process:

# Unregister DAO by selecting Start > Run, copy and paste the line below, then select OK
\\
\\
regsvr32 /U "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"
\\
\\
# Re-register DAO by selecting Start > Run, copy and paste the line below, then select OK
\\
\\
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"

{hidden-content}
*Related Email:*

* {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 this error is to use a lower resolution and/or fewer colors. User who have a graphics accelerator may also try changing the amount of acceleration to something less than the full value.


h1. Analysis errors

Analysis errors are listed as follows:


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 Incident:*

* {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. Negative Jacobian error

* A negative Jacobian occurs when one side of an area element is smaller than the auto-merge tolerance. To correct this error, auto-merge tolerance should be reduced through Options > Dimensions and tolerances. As an alternative, this type of [mesh|kb:Meshing] element may be avoided.

{hidden-content}
*Related Incident:*
* {incident:no=46574|comment=Jacobian error message}
{hidden-content}


h2. Error auto meshing area object

* A whole-to-part approach is best for troubleshooting this type of issue. Users should incrementally delete the model to isolate problem areas. If the problem area has more than four nodes, and the software is unable to mesh the region, it is likely that the area and the associated assignments do not go to the analysis model at all. This is most likely the source of the issue.


h2. Error in computing frame section locations

* When this error triggers, users should verify that the auto-meshing tolerance is smaller than the anticipated auto-mesh member length.

{hidden-content}
{verify}
{hidden-content}

{hidden-content}
*See Also:* [Error (internal)|t:Error]
{hidden-content}


h2. Members are too close

*Error Message:* Members are too close.

* This error occurs when models are run with very high accuracy. Tolerance should be 0.001mm at the smallest. To resolve, reset the tolerance, [export|kb:Export] the model as an \*.e2k file, then [import|kb:Import] the model back. A series of line-load warnings may occur. Ignore these warnings for the time being. [Section cuts|kb:Section cut] and groups will need to be redefined, then the model will run correctly.

{hidden-content}
*Related Incident:*
* {incident:no=46451|comment=STEEL STRUCTURE MODEL}
{hidden-content}


h1. Other errors

Additional errors which may occur are listed as follows:

h2. Database formatting data is corrupt

*Error Message:* Database formatting data is corrupt and has been refilled by the program. Please check the Options > Set Program Default Display Units command.

* This error may be associated with the file being saved to a location where the software does not have full read / write access. If this is the case, the issue may be resolved by saving the file locally and re-opening.

{hidden-content}
*Related Incident:*
* {incident:no=32261|comment=Possible explanation of the error.}
{hidden-content}


h1. See Also

* [ETABS Error|etabs:Error] section

* [SAFE Error|safe:Error] section