I just installed SAS Enterprise Guide 64bits. Something weird is even I ran any pretty simple program, ex. just defined the library, this is a error window popped out with " The server is disconnected". The error in log is below.
ERROR: BRIDGE FAILURE - ERROR LOADING IMAGE
MODULE: sasxgopt SUBSYSTEM: 184 SLOT: 2
The server is just the local server and it is connected shown in enterprise guide. The error is shown below
Thanks, hope someone can help with that. I can't do anything with SAS now...
Lu
That is a strange message. Try turning off the Graph Options statement in generated code (see this topic for how to do that).
Still, your symptom is very severe. It might be something to do with your SAS install -- not sure if your install of EG also included/touched your installation of SAS. The EG install by itself does not touch SAS, but if you used the SAS Deployment Wizard with more components selection, it might have.
That is a strange message. Try turning off the Graph Options statement in generated code (see this topic for how to do that).
Still, your symptom is very severe. It might be something to do with your SAS install -- not sure if your install of EG also included/touched your installation of SAS. The EG install by itself does not touch SAS, but if you used the SAS Deployment Wizard with more components selection, it might have.
Thanks for you help, Chris! I just turned it off and now it is working. My SAS EG is installed with SAS 9.4. But is there any limitations with running SAS program in the future if I turn off the generation mode ?
No, it just means that you don't have SAS/GRAPH installed. Usually the symptom is an error in the log, not a crash like you saw. So I'm suspicious that something is partially installed on your machine, and this might not be the end of the trouble. So...keep vigilant!
Got it, Chris! I will keep eyes on that.
Setting this option did not solve this problem for me. This information is in the log summary:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
13 The SAS System 09:10 Sunday, August 28, 2016
The SAS task name is [OBJECT_EXECUTIVE]
ERROR: Write Access Violation OBJECT_EXECUTIVE
Exception occurred at (0AA6472C)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
000000000AA6472C 000000000665CBB0 tkjni:tkjni+0x1372C
00000000071DAFDA 000000000665CBB8 sasods:tkvercn1+0x129F9A
00000000073D539C 000000000665D058 sasodst:tkvercn1+0x435C
00000000072C3FDA 000000000665E3F0 sasods:tkvercn1+0x212F9A
00000000071CA8B0 000000000665E4C0 sasods:tkvercn1+0x119870
00000000048DAFE3 000000000665E4C8 sasxshel:tkvercn1+0x49FA3
00000000071CAFA2 000000000665F010 sasods:tkvercn1+0x119F62
00000000073D11D8 000000000665F0B0 sasodst:tkvercn1+0x198
00000000076158EA 000000000665F0B8 sasxany:tkvercn1+0x48AA
00000000076120D2 000000000665F1A0 sasxany:tkvercn1+0x1092
000000000489266D 000000000665F2D0 sasxshel:tkvercn1+0x162D
00000000048919D5 000000000665F360 sasxshel:tkvercn1+0x995
00000000048BAF63 000000000665F4B0 sasxshel:tkvercn1+0x29F23
00000000048E43A1 000000000665F810 sasxshel:tkvercn1+0x53361
00000000048E7C0C 000000000665F900 sasxshel:tkvercn1+0x56BCC
00000000048E13F8 000000000665F9A0 sasxshel:tkvercn1+0x503B8
00000000058B144A 000000000665F9A8 sasxobj:tkvercn1+0x40A
00000000033089DB 000000000665FBF8 sashost:Main+0x10EBB
000000000330E62D 000000000665FF50 sashost:Main+0x16B0D
00000000775759BD 000000000665FF58 kernel32:BaseThreadInitThunk+0xD
00000000777AA2E1 000000000665FF88 ntdll:RtlUserThreadStart+0x21
69 ODS GRAPHICS OFF;
@mcperew, your traceback is a crash in SAS. You'll need to work with SAS Technical Support on possible causes -- be sure to include your program, full log, and the version of SAS you're using (including applied hot fixes). The crash appears to happen when SAS is calling into some Java-based routines, so you should also include the output of proc javainfo; run; in your track.
hi ,
i have come across the same situation in my batch job exection. as the same job was execting sucessfully all of sudden i see the
BRIGE FAILURE -ERROR LOADING IAGE
error: could not load /sas/SASHome/SASFoundation/9.4/sasexe/sassqlt : open failed: No such file or directory
2)any idea of XOB failure detected.. in the same job another exectuion the error occurred. never seen before job was running successfully every day ..how come this eror trigger ? any expert idea :0
thanks
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.