If you install SAS^® 9.1.3 with SAS Service Pack 4 on a Windows 2003 Server with Service Pack Pack 1 and then use pre-assigned libraries in SAS^® Management Console, the SAS OLAP Server might fail to start.

ERROR:  IOM call failed

ERROR:  Read Access Violation in Task [ DOSPEIN )
ERROR:  Read Access Violation in Task [ DOSPEIN )
ERROR:  Read Access Violation in Task [ DOSPEIN )
Exception occurred at (536B58E4)
Exception occurred at (536B58E4)
Exception occurred at (536B58E4)
Task Traceback
Task Traceback
Task Traceback
Address   Frame      (DBGHELP API Version 4.0 rev 5)
Address   Frame      (DBGHELP API Version 4.0 rev 5)
Address   Frame      (DBGHELP API Version 4.0 rev 5)


ERROR: Generic critical error.

Workarounds

To circumvent the "Read Access Violation" error, try using a metadata LIBNAME engine (MLE) in the autoexec.sas file of the SAS OLAP Server. If the metadata LIBNAME statement does not work, contact SAS Technical Support.

To circumvent the "IOM call failed" error message, verify that there are no special characters used in the password of the "sastrust" account or other accounts required by SAS. If there are special characters in the password, you might need to remove these special characters in order for the SAS OLAP Server to start.

In some cases, creating a second account (for example, OLAPtrust) and assigning a password without special characters enables you to start the SAS OLAP Server.

To do this, follow these instructions:

1. Edit the trustedUsers.txt file in the \Lev1\SASMain\MetadataServer directory, and add the second account, so that it is registered as a trusted user.
2. Modify the SAS OLAP Server start up to specify OLAPtrust and the new password.
3. Restart the metadata server to pick up the new trusted user, and then restart the SAS OLAP Server.

If this does not resolve the "IOM call failed" error message, contact SAS Technical Support.

Operating System and Release Information