Usage Note 8179: Errors occur when running the TIB/Rendezvous coding example with SAS® Integration Technologies Common Messaging Interface
When running the TIB/Rendezvous coding example at the following
location:
http://corptest.unx.sas.com/apps/demosdownloads/inttechdoc_PROD__sysdep.jsp?packageID=000436&jmpflag=N
with the SAS Integration Technologies Common Messaging Interface, the
following errors might display:
----
Call INIT
INIT: failed
ERROR: Unable to load auxiliary transport image.
----
Call OPENQUEUE for queue1 to listen for and receive messages
NOTE: LDAP Server opened.
NOTE: LDAP Server closed.
OPENQUEUE: failed
ERROR: Queue alias does not exist.
----
Call OPENQUEUE for queue2 to send messages
NOTE: LDAP Server opened.
NOTE: LDAP Server closed.
OPENQUEUE: failed
ERROR: Queue alias does not exist.
----
Call SETMAP
NOTE: LDAP Server opened.
NOTE: LDAP Server closed.
SETMAP: failed
ERROR: LDAP server reports no such object.
----
Call SENDMESSAGE
send message failed:
ERROR: Invalid queue identifier.
----
Call RECEIVEMESSAGE
qid =0
event = ERROR
attchflg =.
receive message failed:
ERROR: Invalid queue identifier.
----
Call CLOSEQUEUE for queue2
CLOSEQUEUE: failed
ERROR: Invalid queue identifier.
----
Call CLOSEQUEUE for queue1
CLOSEQUEUE: failed
ERROR: Invalid queue identifier.
----
Call TERM
TERM: failed
ERROR: Invalid transport handle.
NOTE: DATA statement used:
real time 0.28 seconds
cpu time 0.27 seconds
----
Possible reasons that the errors occur are:
* The module sasrend.dll that is required to run with Rendezvous is
missing.
* The module sasrend.dll is not found in !sasroot\inttech\sasexe.
* SAS Integration Technologies is not licensed or installed.
* The path to the Tibco Rendezvous bin directory is missing.
One user resolved the problem by reinstalling Tibco Rendezvous and
setting the path to include c:\tibco\tibrv\bin.
Operating System and Release Information
| SAS System | SAS Integration Technologies | Microsoft Windows 95/98 | 8.2 TS2M0 | |
| Microsoft Windows XP Professional | 8.2 TS2M0 | |
| Microsoft Windows NT Workstation | 8.2 TS2M0 | |
| Windows Millennium Edition (Me) | 8.2 TS2M0 | |
| Microsoft Windows 2000 Server | 8.2 TS2M0 | |
| Microsoft Windows 2000 Advanced Server | 8.2 TS2M0 | |
| Microsoft Windows 2000 Datacenter Server | 8.2 TS2M0 | |
| Microsoft Windows 2000 Professional | 8.2 TS2M0 | |
| OpenVMS VAX | 8.2 TS2M0 | |
| Solaris | 8.2 TS2M0 | |
| IRIX | 8.2 TS2M0 | |
| 64-bit Enabled Solaris | 8.2 TS2M0 | |
| OS/2 | 8.2 TS2M0 | |
| z/OS | 8.2 TS2M0 | |
| Linux | 8.2 TS2M0 | |
| 64-bit Enabled HP-UX | 8.2 TS2M0 | |
| ABI+ for Intel Architecture | 8.2 TS2M0 | |
| HP-UX | 8.2 TS2M0 | |
| CMS | 8.2 TS2M0 | |
| OpenVMS Alpha | 8.2 TS2M0 | |
| 64-bit Enabled AIX | 8.2 TS2M0 | |
| Tru64 UNIX | 8.2 TS2M0 | |
| AIX | 8.2 TS2M0 | |
*
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.
| Type: | Usage Note |
| Priority: | |
| Topic: | Third Party ==> Products ==> Message Queuing
|
| Date Modified: | 2008-04-09 15:23:57 |
| Date Created: | 2002-08-05 14:04:18 |
