Usage Note 17977: The SAS® OLAP Server does not start and might receive critical, violation, or failure errors
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.
The SAS OLAP Server log might show the following error messages:
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:
- 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.
- Modify the SAS OLAP Server start up to specify
OLAPtrust and the new password.
- 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
| SAS System | SAS OLAP Server | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | |
| Windows Vista for x64 | 9.1 TS1M3 SP4 | |
| Windows Vista | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
SAS OLAP Server is not starting and is receiving errors like: ERROR: Read Access Violation in Task [ DOSPEIN ), ERROR: IOM call failed, and ERROR: Generic critical error under Windows 2003.
| Type: | Usage Note |
| Priority: | high |
| Topic: | System Administration ==> Servers ==> OLAP Query and Reporting ==> OLAP (Online Analytical Processing)
|
| Date Modified: | 2009-04-23 16:08:35 |
| Date Created: | 2006-06-30 09:37:37 |