Skip to main content

sas.exe has stopped working

Issue:
When I try to run a code to connect to Oracle DB I get message saying sas.exe has stopped working.

Full Error Details:
ERROR:  An exception has been encountered.

 Please contact technical support and provide them with
the following traceback information:

 The SAS task name is [OBJECT_EXECUTIVE]
Exception occurred at (3F350BF5)
Task Traceback
Address  Frame     (DBGHELP API Version 4.0 rev 5)  3F350BF5 0351F35C  sasioora:tkvercn1+0xFBB5  62A2FB57 
0351F398  sasxdbi:tkvercn1+0xEB17  675611A0 0351F5EC  sasyhl:tkvercn1+0x160  6778D6C2  0351F758  sasyh:tkvercn1+0x2C682  6778C976 
0351F8F8  sasyh:tkvercn1+0x2B936028CB91C  0351FAA8  sasxshel:tkvercn1+0x1A8DC 028B26EA  0351FB34 
sasxshel:tkvercn1+0x16AA  028B15E2 0351FB74  sasxshel:tkvercn1+0x5A2028CF04D  0351FC2C  sasxshel:tkvercn1+0x1E00D  028F5C10 0351FDF0 sasxshel:tkvercn1+0x44BD0 028F990D 0351FE74 sasxshel:tkvercn1+0x488CD 028F3D0F 0351FEAC sasxshel:tkvercn1+0x42CCF  5861351 0351FF28  sasxobj:tkvercn1+0x311  01C53254 0351FF74  sashost:Main+0xD424  01D47038 0351FF88  sashost:Main+0x1012087546ED6C  351FF94  Kernel32:BaseThreadInitThunk+0x12 76FF377B  0351FFD4 ntdll:RtlInitializeExceptionChain+0xEF  2 
The SAS System                  14:50 Tuesday, November 6,2012
76FF374E 

0351FFEC  ntdll:RtlInitializeExceptionChain+0xC2

 Solution:
Check whether your license have following line - SAS/ACCESS ORACLE. Without this license you won't be able to access Oracle DB.

In your software depot you need to have the following file:
C:\SAS Software Depot\products\oraclebndl__93210__win__xx__sp0__1

Comments

Post a Comment

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.
1 comment
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
3 comments
Read more