...

On this page:

Installation errors

Installation errors are listed as follows:

...

• Install the program on a vanilla test computer. Then copy the Computers and Structures folder from that computer over to the production computer that it needs to be installed on. Then run the installer on the production computer.
• Try logging in as Administrator or Domain Administrator and then run the installation with the Administrator or Domain Administrator's rights.

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.

Windows errors and errors with error codes

...

Overview of Windows-related errors

• System Error Codes - This article describes negative error codes for file operations which indicate the negative of a Windows code.

• Windows XP SP3 Sows Havoc, Users Complain - This InformationWeek article describes spontaneous reboots and system crashes which occur with XP SP3.

...

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 # 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.

Error # 6

See Overflow Error below.

...

• SAP2000 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 System Error Codespage webpage.

Error # 41

Error Message: Error 41: Allocate Error # 41

...

• 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.

Error # 112

Error Message:

...

1. 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"
2. 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"

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.

...

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

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 element may be avoided.

Error auto meshing area object

• Resolve this error by dividing area objects which have many nodes into areas with 3 or 4 nodes. Also, divide any large areas into more meshable areas of regular geometry. Because of elaborate geometries and tolerance issues, complicated areas may not mesh successfully. This is the case even when the No Auto-Meshing option is selected.

• A whole-to-part approach is also useful for troubleshooting this error. 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.

...

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

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 the model as an *.e2k file, then import the model back. A series of line-load warnings may occur. Ignore these warnings for the time being. Section cuts and groups will need to be redefined, then the model will run correctly.

No unrestrained mass

Error Message: The structure has no (unrestrained) mass; no Eigen modes can be found.

This error message occurs when zero weight and mass are assigned to the material definition. The assignment of nonzero values should resolve the issue.

Other errors

Additional errors which may occur are listed as follows:

...

• 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.

Overflow error

Overflow error means that a calculation occurred that generated a number larger than can be handled by the CPU, such as division by near zero or some other math function. Usually this occurs in the graphics and is of no concern. This error may be reported with Error Code 6 as Error 6. Some additional information about this error is provided in the Overflow (Error 6) article in Microsoft Documentation.

Installation Wizard errors

...

See also

• ETABS Error section

...