After you submit code in SAS Studio, you might receive one or more of the following errors:
ERROR: BRIDGE FAILURE - ERROR LOADING IMAGE MODULE: sasxgopt SUBSYSTEM: 193 SLOT: 2
Error: Unable to load transient module (Bridge failure).
Error: Invalid object specified to bridge protocol engine
The problem occurs when SAS/GRAPH® software is licensed but it is not installed. This problem affects SAS® Studio 3.7x and SAS® Studio 4.x (SAS® Viya® 3.x) releases.
You can compare what you have licensed with what you have installed by running the following procedures. Their output is written to the log file.
Use the SETINIT procedure as shown below to see which products are licensed:
proc setinit;
run;
Use the PRODUCT_STATUS procedure as shown below to see which products are installed:
proc product_status;
run;
For SAS Studio Enterprise (Mid-Tier) or Basic edition:
Click the Hot Fix tab in this note to access the hot fix for this issue.
For SAS Studio Single-User edition:
You can determine whether you are running SAS Studio Single-User from the edition displayed in the About SAS Studio page, or by the fact that you launch SAS Studio from a shortcut on the Windows Start menu.
You can download the updated version of SAS Studio Single-User from our Downloads page.
For SAS Studio 4.3 (SAS® Viya®) in Linux operating environments only:
Update Your Software to Fix This Issue
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Verify That the Update Has Been Installed
To verify that the fix is installed, run the following rpm command:
rpm -q sas-sasstudio
To complete this process, make sure that the package versions shown in the rpm output either match or are newer than the following:
sas-sasstudio-4.3.1-20180628.121938969496.x86_64
If you need additional assistance, contact SAS Technical Support.
Operating System and Release Information
SAS System | SAS Studio | Windows 7 Home Premium x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 R2 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 for x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Datacenter | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Datacenter | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Std | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Std | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2016 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Enterprise 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Home Premium 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Ultimate 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Professional 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Professional x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Ultimate x64 | 3.7 | | 9.4 TS1M5 | |
64-bit Enabled AIX | 3.7 | | 9.4 TS1M5 | |
64-bit Enabled Solaris | 3.7 | | 9.4 TS1M5 | |
HP-UX IPF | 3.7 | | 9.4 TS1M5 | |
Linux for x64 | 3.7 | | 9.4 TS1M5 | |
Solaris for x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 10 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft® Windows® for x64 | 3.7 | | 9.4 TS1M5 | |
SAS System | SAS Viya | Linux for x64 | 3.3 | 3.4 | | |
*
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.