LIBGWT_CAT:1073,LIBGWT_CAT:1509

Hi All,
I am getting below errors in my ulog:
GWTDOMAIN.27232.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
GWTDOMAIN.27232.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
I am wondering why?
I am using this dmconfig,
while executing dmloadcf -y dmconfig.new
The current dmconfig file is:
# TUXEDO DOMAIN CONFIGURATION FILE
*DM_LOCAL_DOMAINS
QFISWTC01_TST GWGRP=TDOM
TYPE=TDOMAIN
DOMAINID=QFISWTC01_TST
CONNECTION_POLICY=ON_STARTUP
SECURITY=NONE
*DM_REMOTE_DOMAINS
EI_WTC_NGL_TEST TYPE = TDOMAIN
DOMAINID=EI_WTC_NGL_TEST
MTYPE="WINOS"
*DM_TDOMAIN
QFISWTC01_TST NWADDR="//abc:61601"
EI_WTC_NGL_TEST NWADDR="//ei-t-alsb-adm.xyz.com.in:41895"
in dmadmin,
I can see :
pd -d QFISWTC01_TST
Local domain :QFISWTC01_TST
Connected domains:
Domainid: EI_WTC_NGL_TEST
and in ulog:
GWTDOMAIN.25741.1.0: LIBGWT_CAT:1129: INFO: Connection established with domain (domainid=<EI_WTC_NGL_TEST>)
There is no retries for this domain.
However I am wondering why this :
GWTDOMAIN.27232.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
GWTDOMAIN.27232.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
is happening.
However,my old dmconfig file(dmconfig.old) is :
*DM_LOCAL_DOMAINS
QFISWTC01_TST GWGRP=TDOM
TYPE=TDOMAIN
DOMAINID=QFISWTC01_TST
CONNECTION_POLICY=ON_STARTUP
SECURITY=NONE
*DM_REMOTE_DOMAINS
EI_WTC_03_TST TYPE = TDOMAIN
DOMAINID=EI_WTC_03_TST
MTYPE="WINOS"
*DM_TDOMAIN
QFISWTC01_TST NWADDR="//abc:61601"
EI_WTC_03_TST NWADDR="//ei-t-alsb-adm.xyz.com.in:41895"
but I am not using it.
Could you please suggest why it is happening?
Why I am receiving these errors when I am no longer using this old dmconfig file?
I have tried doing bbclean,ipcrm
but no fruitful result I got.
Please help me.

Hi Todd,
Here is some lines from my ULOG:
**yesterday*18:27:28* we booted up the whole environment
182728.BBL.4607.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit, Patch Level 405
182728.BBL.4607.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182728.TMS_MQ.4611.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182728.TMS_MQ.4611.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182729.TMS_MQ.4612.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182729.TMS_MQ.4612.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182729.TMS_MQ.4613.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182744.MQREPORT_0002_00.4703.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182744.MQREPORT_0002_00.4703.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182744.MQREPORT_0002_00.4703.1.0: INFO TuxServer::addService() Service Name "MQREPORT_TRANS" OK
182744.TMS_MQ.4704.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182744.TMS_MQ.4704.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182744.TMS_MQ.4705.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182744.TMS_MQ.4705.1.0: LIBTUX_CAT:262: INFO: Standard main starting
*182744.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory*
*182744.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection*182744.MQWRITE_0002_00.4706.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182744.MQWRITE_0002_00.4706.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182744.MQWRITE_0002_00.4706.1.0: QueueManager is QMT102
182744.MQWRITE_0002_00.4706.1.0: QueueName is I5.AE.CARGO.CUS.REQUEST
182744.MQWRITE_0002_00.4706.1.0: Local Queue Manager is QMT102
182744.MQWRITE_0002_00.4706.1.0: Reply Queue Name is I5.1B.CSXERROR.QF.REPLY
182744.MQWRITE_0002_00.4706.1.0: MQFMT_STRING is MQSTR
182744.MQWRITE_0002_00.4706.1.0: INFO TuxServer::addService() Service Name "MQWRITE_0002_00" OK
182822.I5_TRNS_0002_01.5022.1.0: 08-31-2011: Tuxedo Version 8.0, 32-bit
182822.I5_TRNS_0002_01.5022.1.0: LIBTUX_CAT:262: INFO: Standard main starting
182822.I5_TRNS_0002_01.5022.1.0: Welcome to the I5_TRNS_0002_01 Request Manager server
182822.I5_TRNS_0002_01.5022.1.0: ORBIT ADDRESS = 194.333.222.78, PORT = 20002
182822.I5_TRNS_0002_01.5022.1.0: INFO TuxServer::addService() Service Name "I5_TRNS_0002_01" OK
*182844.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory*
*182844.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection*
*182944.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory*
*182944.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection*183029.SABackEnd.4674.1.0: Service CVQFCC01 has been called
183030.SABackEnd.4674.1.0: Service CVQFCC01 has been called
*183044.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory*
*183044.GWTDOMAIN.4653.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection*183105.I5_PC_0002_00.4683.1.0: CHECK ::: INTO run() of ProxyClient
I tried : grep EI_WTC_03_TST ULOG.083111 |less
and I can see that it was these errors were continuous.
165444.!GWTDOMAIN.23835.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
165544.!GWTDOMAIN.23835.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
165644.!GWTDOMAIN.23835.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
In this interval we booted up the server
182744.!GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
182844.!GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
182944.!GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
183044.!GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
183144.!GWTDOMAIN.4653.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
Today I shutted down the whole environment.
I changed the IPCKEY .
loaded the ubbconfig and dmconfig.
Then booted up.
The time i booted up was 13:01:08
but still I can see the statements in ULOG like
131344.GWTDOMAIN.7907.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
131344.GWTDOMAIN.7907.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
131444.GWTDOMAIN.7907.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
131444.GWTDOMAIN.7907.1.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
131544.GWTDOMAIN.7907.1.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (EI_WTC_03_TST) information from shared memory
I am astonished to see the time stamps.Are these processes Independant of Environment restarts.
Every 44 th Second of a minute its generating these error.But the Process Id is different.
Yesterday also this was same.
I am not able to figure it out.
Can you please advice?
Thanks in advance.
Regards,
Deb
Edited by: 835542 on Sep 1, 2011 9:00 AM

Similar Messages

Remote tuxedo domain rejects connection from client only Tuxedo JCA Adapter

I am trying to use a client only configured Oracle Tuxedo JCA Adapter 11.1.1.2.1 to connect to a remote tuxedo 10.3 domain. The connector is deployed to a JDeveloper 10.1.3.4 embedded OC4J container. The connector is failing silently when attempting to establish a connection with the remote domain. Locally, the JCA Adapter ntrace logs the following:
1/20/11:9:41:49 PM:10:TRACE[DMLocalAccessPoint,DMLocalAccessPoint]> (ypjspNQ5QIPKmOyk1DlAgw==)
1/20/11:9:41:49 PM:10:DBG[DMLocalAccessPoint,DMLocalAccessPoint]_useSSL = false
1/20/11:9:41:49 PM:10:TRACE[DMLocalAccessPoint,DMLocalAccessPoint]< return(10)
1/20/11:9:41:49 PM:10:INFO[TuxedoAdapterSupervisor,createLocalAccessPoint]TJA_0233:Info: Default local access point for factory null created, access point id ypjspNQ5QIPKmOyk1DlAgw==.
1/20/11:9:41:49 PM:10:DBG[TuxedoAdapterSupervisor,createLocalAccessPoint]features = 159
1/20/11:9:41:49 PM:10:TRACE[TuxedoAdapterSupervisor,startListeners]> ()
1/20/11:9:41:49 PM:10:TRACE[TuxedoAdapterSupervisor,startListeners]< (20) return
1/20/11:9:41:49 PM:10:TRACE[DMSession,DMSession]> (__sess_0_0)
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_lap_name:ypjspNQ5QIPKmOyk1DlAgw==
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_rap_name:e1tst_tdtux02
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_pro_name:__default_session_profile__
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _lap: com.oracle.tuxedo.adapter.config.DMLocalAccessPoint@1f6bc1a
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _rap: com.oracle.tuxedo.adapter.config.DMRemoteAccessPoint@1b75e54
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _pro: com.oracle.tuxedo.adapter.config.DMSessionProfile@191f64b
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]sec = NONE
1/20/11:9:41:49 PM:10:TRACE[DMSession,DMSession]< return(60)
1/20/11:9:41:49 PM:10:INFO[TuxedoAdapterSupervisor,createDefaultSession]TJA_0193:INFO: Default session created between LocalAccessPoint ypjspNQ5QIPKmOyk1DlAgw== and RemoteAccessPoint e1tst_tdtux02.
1/20/11:9:41:49 PM:10:TRACE[DMSession,DMSession]> (__sess_0_1)
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_lap_name:ypjspNQ5QIPKmOyk1DlAgw==
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_rap_name:e1tst_tdtux01
1/20/11:9:41:49 PM:10:DBG[DMSession,myInit]_pro_name:__default_session_profile__
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _lap: com.oracle.tuxedo.adapter.config.DMLocalAccessPoint@1f6bc1a
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _rap: com.oracle.tuxedo.adapter.config.DMRemoteAccessPoint@1c0f654
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]got _pro: com.oracle.tuxedo.adapter.config.DMSessionProfile@191f64b
1/20/11:9:41:49 PM:10:DBG[DMSession,DMSession]sec = NONE
1/20/11:9:41:49 PM:10:TRACE[DMSession,DMSession]< return(60)
1/20/11:9:41:49 PM:10:INFO[TuxedoAdapterSupervisor,createDefaultSession]TJA_0193:INFO: Default session created between LocalAccessPoint ypjspNQ5QIPKmOyk1DlAgw== and RemoteAccessPoint e1tst_tdtux01.
1/20/11:9:41:49 PM:10:TRACE[TuxedoAdapterSupervisor,registerClientSideResourceAdapter]create default import
1/20/11:9:41:49 PM:10:TRACE[ServiceManager,registerImportedService]> (*)
1/20/11:9:41:49 PM:10:INFO[,]factory = null
1/20/11:9:41:49 PM:10:INFO[,]name = *
1/20/11:9:41:49 PM:10:INFO[,]iname = *
1/20/11:9:41:49 PM:10:TRACE[ServiceManager,registerImportedService]register Default Import
1/20/11:9:41:49 PM:10:TRACE[Route,Route]> (*)
I can't determine if there are any problems from these log entries, but the remote tuxedo domain logs the following in the ULOG:
155138.tdtux01!GWTDOMAIN.3495.4.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (ypjspNQ5QIPKmOyk1DlAgw==) information from shared memory
155138.tdtux01!GWTDOMAIN.3495.4.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
My understanding is that the client only configuration should connect to a remote tuxedo domain as an anonymous client instead of a peer tuxedo domain, but the remote tuxedo gateway domain listener is acting like the client has to be configured in its dmconfig file before it will allow the connection request. Is there a different kind of listener the client only configuration should connect to instead of the tuxedo gateway domain listener? How can a remote tuxedo domain accept a connection from an anonymous client if the client must first be specified in the remote domain's dmconfig file? Is this a tuxedo 11g only feature? I'm trying to connect to a tuxedo 10.3 server.
The local ra.xml is reproduced here:
<?xml version="1.0" encoding="UTF-8"?>
<connector xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
version="1.5">
<display-name>Tuxedo JCA Adapter</display-name>
<vendor-name>Oracle</vendor-name>
<eis-type>Tuxedo</eis-type>
<resourceadapter-version>11gR1(11.1.1.2.1)</resourceadapter-version>
<license>
<description>Tuxedo SALT license</description>
<license-required>false</license-required>
</license>
<resourceadapter>
<resourceadapter-class>com.oracle.tuxedo.adapter.TuxedoClientSideResourceAdapter</resourceadapter-class>
<config-property>
<config-property-name>debugConfig</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<config-property-name>traceLevel</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>100000</config-property-value>
</config-property>
<config-property>
<config-property-name>xaAffinity</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<config-property-name>remoteAccessPointSpec</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>//tdtux01:9601/domainId=e1tst_tdtux01,//tdtux02:9601/domainId=e1tst_tdtux02</config-property-value>
</config-property>
<outbound-resourceadapter>
<connection-definition>
<managedconnectionfactory-class>com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory</managedconnectionfactory-class>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.oracle.tuxedo.adapter.cci.TuxedoConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.oracle.tuxedo.adapter.cci.TuxedoJCAConnection</connection-impl-class>
</connection-definition>
<transaction-support>NoTransaction</transaction-support>
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
</authentication-mechanism>
<reauthentication-support>false</reauthentication-support>
</outbound-resourceadapter>
</resourceadapter>
</connector>
Thanks for any help.
Steve

Looks like this is an RTFM question. From:
[http://download.oracle.com/docs/cd/E18050_01/jca/docs11gr1/users/jca_usersguide.html]
Is the following:
Dynamic RemoteAccessPoint (RAP) Insertion
In order to make default LocalAccessPoint to work, Oracle Tuxedo GWTDOMAIN gateway configuration is required in order to make this simplified /Domain configuration to work.
GWTDOMAIN gateway must be modified to allow Dynamic RemoteAccessPoint (RAP) Registration. If DYNAMIC_RAP is set to YES, it will also update the in-memory database of the status of the connection from those dynamically registered RAP. If the connection from those dynamically registered RAP lost then the information about that RAP will be removed from the SHM database.
GWADM must be modified to process the DM MIB correctly to reflect the connection status of those dynamically registered RAP. When the connection from those dynamically registered RAP lost their entries in the SHM database will also be removed so that the DM MIB query can return the connection status correctly.
The dynamically registered RAP will be added to /DOMAIN configuration permanently. Their existence will only be known when the Session is established. Their existence will be lost when the connection is lost.
The DM_CONNECTION Oracle Tuxedo /Domain DMIB call returns all the connected dynamically registered RemoteAccessPoint. All other dynamically registered RemoteAccessPoint that are not connected will not be shown.
The OPENCONNECTION DMIB request will not be supported to connect to those dynamically registered RAP.
The CLOSECONNECTION Oracle Tuxedo /DMIB request closes the connection and remove the session from those dynamically registered RemoteAccessPoint, and returns its connection status as 'UNKNOWN.
The PERSISTENT_DISCONNECT type of CONNECTION_POLICY will be honored that means when PERSISTENT_DISCONNECT is in effect all connections request from any RAP, whether they are dynamically or non-dynamically registered, will be rejected.
I must have overlooked this section when reading it. Looks like I've got more configuration to do.
Thanks,
Steve

Information regarding how to overcome LIBGWT_CAT:1267 error is required

Hi,
We are using WLE5.0.1 along with Tuxedo6.5 .Sometimes the call from a CORBA Server
to a remote BEA tuxedo service is failing .Error in ULOG is :
132855.GWTDOMAIN.8237: LIBGWT_CAT:1267: ERROR: Unable to convert old stlye network
buffer. Error code 90.
At Times,The GWTDOMAIN server dumps core(Segmentation fault 11).
On restarting this GWTDOMAIN server the same call(ie sameinput data) to the remote
TUXEDO service passes.
As the clarification given for this error,we have checked up Product versions
and they are fine(ie TUXEDO Version 6.5forWLE5.0.1 on both domains ie where the
remote Tux service is running tux6.5and the local wledomain5.0.1 for tux6.5).
Does anybody have any info in overcoming this error?

Hello,
Can you provide some source code so that I can better understand what you are trying to do? Also, can you provide the complete error message from the log file that you are getting?

LIBGWT_CAT:1313: ERROR: Bad message

I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic 7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let me know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection established
with domain (domainid=<BEA001
)150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain (domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
 VERSION="U22"
*DM_LOCAL
CLAR115 GWGRP=GWDOM
 TYPE="TDOMAIN"
 DOMAINID="CLAR115"
 AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
 BLOCKTIME=10
 CONNECTION_POLICY="ON_DEMAND"
 DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
 DMTLOGNAME="DMTLOG_TDOM"
 MAXDATALEN=56
 MAXRACCESSPOINT=89
 MAXTRAN=100
 BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001 TYPE=TDOMAIN
 DOMAINID="BEA001"
*DM_TDOMAIN
BEA001 NWADDR="//172.24.3.208:7001"
# NWDEVICE="/dev/tcp"
CLAR115 NWADDR="//jupiter:53401"
# NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================

Bhaskar,
The ULOG message about "Retrying" does not go with a configuration
of "ON_DEMAND". The best guess is that BEA001 is not really communicating
with whom you think. Two things to look at:
1)Check that "jupiter"=="10.3.0.14"
2) Do a dmunloadcf on the CLAR115 domain and see if the domain that is
booted
is what you expected from your configuration.
Bob Finan
Bhaskar wrote:
Bob,
No success by changing port numbers.
However after some more experimentation I am getting the following:
I installed tuxedo on another Windows 2000 m/c. (say TUX001). If I call the Clarify
domain as CLAR115 and BEA domain as BEA001 then
a) I am able to communicate between CLAR115 and TUX001
b) I am able to communicate between TUX001 and BEA001 by using WTC in BEA001
c) But, I am still not able to communicate between BEA001 and CLAR115. I still
obtain a BAD Message error on the CLAR115 side
Quite puzzled with this.
Regards
Bhaskar
"Bhaskar" <[email protected]> wrote:
Thanks Bob,
I would surely try with using another port.
Currently,I am using a different port for the WLS admin server. Secondly,
in case
I was using a port that was already being used by some other server,
one of the
two servers would not have come up.
Is there any method to read the ULogs for the Local tuxedo domain on
WLS end.
thanks and regards
Bhaskar
Bob Finan <[email protected]> wrote:
Bhaskar,
You are probably using the //172.24.3.208:7001 port for other purposes
and this is
causing the problem(e.g. 7001 is the default WLS admin port).Try
changing the
NWAddr port number for the WTCLocalTuxDom..
Bob Finan
Bhaskar wrote:
I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic
7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let
me
know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
established
with domain (domainid=<BEA001
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message
from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying
domain
(domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB"
ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
 VERSION="U22"
*DM_LOCAL
CLAR115 GWGRP=GWDOM
 TYPE="TDOMAIN"
 DOMAINID="CLAR115"
 AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
 BLOCKTIME=10
 CONNECTION_POLICY="ON_DEMAND"
 DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
 DMTLOGNAME="DMTLOG_TDOM"
 MAXDATALEN=56
 MAXRACCESSPOINT=89
 MAXTRAN=100
 BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001 TYPE=TDOMAIN
 DOMAINID="BEA001"
*DM_TDOMAIN
BEA001 NWADDR="//172.24.3.208:7001"
# NWDEVICE="/dev/tcp"
CLAR115 NWADDR="//jupiter:53401"
# NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Bhaskar, 
You are probably using the //172.24.3.208:7001 port for other purposes
and
this is 
causing the problem(e.g. 7001 is the default WLS admin port).Try changing
the 
NWAddr port number for the WTCLocalTuxDom.. 
Bob Finan 
 
Bhaskar wrote: 
<blockquote type="cite" cite="[email protected]">
<pre wrap="">I am trying to connect a clarifyCRM 11.5 based system
from BEA WebLogic 7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let me
know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
established
with domain (domainid=<BEA001
</pre>
<blockquote type="cite">
<pre wrap="">)
</pre>
</blockquote>
<pre wrap="">150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313:
ERROR: Bad message from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain
(domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
 VERSION="U22"
*DM_LOCAL
CLAR115 GWGRP=GWDOM
 TYPE="TDOMAIN"
 DOMAINID="CLAR115"
 AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
 BLOCKTIME=10
 CONNECTION_POLICY="ON_DEMAND"
 DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
 DMTLOGNAME="DMTLOG_TDOM"
 MAXDATALEN=56
 MAXRACCESSPOINT=89
 MAXTRAN=100
 BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001 TYPE=TDOMAIN
 DOMAINID="BEA001"
*DM_TDOMAIN
BEA001 NWADDR="//172.24.3.208:7001"
# NWDEVICE="/dev/tcp"
CLAR115 NWADDR="//jupiter:53401"
# NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================
</pre>
</blockquote>
 
</body>
</html>
[att1.html]

LIBGWT_CAT:1070:

Hi!
I obtain errors :
105630.sunz08!GWTDOMAIN.2074.1.0: LIBGWT_CAT:1070: ERROR: Unable to obtain local
service information from shared memory
105630.sunz08!GWTDOMAIN.2074.1.0: LIBGWT_CAT:1043: ERROR: Unrecoverable error
occurred on receipt of data - sending failure reply over network
It ocurrs only with remote invocations. When i do a local request at the same
service, there are no error. What is happen??? ipcs assigment is valid to the
local invocation, but not to remote request?
Thanks

Peter Holditch <[email protected]> wrote:
Lucia,
Is the service you are exporting referenced in the DM_LOCAL_SERVICES
section of
the dmconfig?
Although the manual states that this is not necessary, I vaguely remember
seeing
this error in the past and solving it with local_services entries.
I hope that helps...
Regards,
Peter.
Lucia wrote:
Hi!
I obtain errors :
105630.sunz08!GWTDOMAIN.2074.1.0: LIBGWT_CAT:1070: ERROR: Unable toobtain local
service information from shared memory
105630.sunz08!GWTDOMAIN.2074.1.0: LIBGWT_CAT:1043: ERROR: Unrecoverableerror
occurred on receipt of data - sending failure reply over network
It ocurrs only with remote invocations. When i do a local request atthe same
service, there are no error. What is happen??? ipcs assigment is validto the
local invocation, but not to remote request?
Thanks
You solved my proble. Your solution is worked. Thanks a lot
Lucia

Error 1073 (on Clear Errors.vi) When Building Application in LV 8.2

I have seen numerous posts about this problem when building an application without a block diagram in LV 7.x, however, I am recieving this error on LV 8.2. Whats most disturbing about it, is that it always hangs when processing Clear Errors.vi. I have tried my source on two different machines, to no avail. Also I tried to do a mass recompile of the entire vi.lib again no help. It is very important that this program compiles, however I cannot get past this error. Any suggestions?
My specific error message is here:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1073 occurred at ABAPI Dist disconnect td-poly.vi -> ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.
-Paul

Hello Paul,
I am sorry for not elaborating previously. This issue has been documented previously for further investigation to our R&D group (# 3ZK9LGP2). In the report I found that this error, though vague in the description, is fixed by enabling MathScript Support.
To enable MathScript support, check the checkbox in the application properties for the 'Enable MathScript support' option.
-Bob
-Bob

Can i use PXIe-1073 with an embedded PXIe controller PXIe-8108

I have a PXI express chassis PXIe-1073 with an integrated controller MXI-Express controller PCIe-8361. I now want to use the chassis as a standalone system with an embedded controller.
(a)Can i use PXIe-1073 chassis with PXIe-8108 embedded controller
(b)Can i use a windows based laptop to control the PXIe-1073 via the PCIe-8361 integrated controller.

Hello kanad,
The PXIe-1073 is a MXI-integrate chassis. This means that the MXI card that would normally go into the controller slot (slot 1) is built into the chassis. The PCIe-8361 or Expresscard8360 are placed into the desktop or laptop, respectively, and connect to the chassis. The cards in the PXIe-1073 then appear as if they are part of the desktop of laptop.
Since the controller is built into the chassis, the PXIe-1073 does not have a slot 1. Controllers, such as the 8108 can only be plugged into slot 1. Therefore, the PXIe-1073 can only be controlled by the desktop or laptop MXI link. It cannot run standalone with an embedded controller.
Consider reading page 1-3 and 1-6 in the manual below:
NI PXIe-1073 User Manual and Specifications
Regards,
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

How to determine what card is in what slot of a PXIe-1073 unit programmable

How can i programmable determine what card is in what slot of a PXIe-1073 unit I have a PXI-4063 and a PXI-2503 in a 1073 chassis. I use the DAQmx Device Product Type to to find the 2503 matrix card but it woun't return the 4065 product type.

Hi cjp1,
The KnowledgeBase article Programmtic PXI Slot Detection walks you through the steps to do this. There is also a community example called Read PXI an PXIe Card Serial Numbers Programatically that demonstrates the type of LabVIEW architecture you can use to do it.
You should first ensure that all of your modules can be identified and self-test in MAX.
In case the above hyperlinks don't work, you can copy-paste the addresses below:
http://digital.ni.com/public.nsf/allkb/2342900AED02975A86256BD800764C8B
https://decibel.ni.com/content/docs/DOC-20207
Jeff Munn
Applications Engineer
National Instruments

2012 R2 RDS - Your roaming profile was not completely synchronized - Event ID 1509 1504 - After installing Update 1

In my deployment I have 2 brokers, and 3 session hosts. I finally installed Update 1 and all following updates available (the ones that were available about two weeks before). Also updated Forefront to v4.3 (SCCM managed).
I have roaming TS profiles enabled with folder redirection and also policy set to "delete local copy of roaming profiles" after logout. Profile folders are on a network share (Server 2003). Things were working ok until Update 1 and rest of updates
got installed.
I started getting events 1509 and 1504 when users logoff and the screen displays "Your roaming profile was not completely synchronized" message briefly. The only file affected so far is ntuser.pol.
There are two variations of the event, one claiming it cannot write the local server copy to fileshare, and the opposite, from file share to c:\users\username.
====
Windows cannot copy file \\server\profileshare\username.V2\ntuser.pol to location C:\Users\username\ntuser.pol. This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
=====
Windows cannot copy file C:\Users\username\ntuser.pol to location \\server\profileshare\username.V2\ntuser.pol. This error may be caused by network problems or insufficient security rights.
DETAIL - Cannot create a file when that file already exists.
==========
Permissions have not changed. The only thing changing is the Updates installed on the servers. I tried running with AV realtime protection off, no change. Ntuser.pol is already on the exclude list in Forefront.
This is happening on my test server and 2 prd servers. Any ideas. I looked for related hotfixes but not coming up with anything.
The whole reason for installing Update 1 was so that we can continue to receive security updates...

Hi,
Thanks for your comment.
When a roaming profile user logs off, the NTuser.dat file is always updated on the roaming profile share. The corresponding NTuser.pol file is only updated if the timestamp of the local copy that was created at logon is newer than the copy found in the roaming
profile share. A synchronization problem may occur if a user with a roaming profile logs on to multiple client computers at the same time. This can eventually cause policy settings to be applied incorrectly.
For example, if the Group Policy loopback feature is applied on one of the client computers, the NTuser.dat file on the roaming profile share may contain loopback policy settings that are not present in the NTuser.pol file. If this problem occurs, the loopback
policy settings that are targeted at one client computer may be unexpectedly applied to a user who logs on to a different client computer.
So please check the permission or group policy which you have applied and also whether you are performing multiple connection at a time.
Note: This KBhere providing only for reference as it’s for previous version.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

PRKC-1073 while installing the crs on solaris 10

when I install the crs 10201 on solaris 10, at the last step the setup failed and in the log I see:WARNING: Error while copying directory /u01/crs/oracle/product/10.2.0.1/crs with exclude file list 'null' to nodes 'RAC2'. [PRKC-1073 : Failed to transfer directory "/u01/crs/oracle/product/10.2.0.1/crs" to any of the given nodes "RAC2 ".
Error on node RAC2:RAC2: unknown host :failed]
and
PRKC-1031 : Error checking free space for / on RAC2
I am sure I have configured the network properly and the authority is right,I search in the metalink but got nothing,could anyone give some advice? thanks in advance

So let me get this right , you have a Sun box with a hostname RAC2 ? is that correct EXACTLY
from the first node can you do
sftp /etc/hosts RAC2:/tmp/foofoo
with NO passwords etc ?
RAC2 seems a poor hostname for a unix box.

Datacopy command copied [0] source data blocks to [1073] target data blocks

Hi,
When I ran this particular script, datacopy command executed successfully but the values did not copied (Plan1 has values). Can you please suggest.
Datacopy command copied [0] source data blocks to [10736] target data blocks
SET UPDATECALC OFF;
SET CREATEBLOCKONEQ ON;
FIX("")
DATACOPY "Plan1" TO "Plan2";
EndFIX
Thanks, UB

FIX("")
DATACOPY "Plan1" TO "Plan2";
EndFIX^^^Did you mean to have your FIX statement blank?
FWIW, you don't need the CREATEBLOCKONEQ setting at all for the purposes of the DATACOPY.
I'm a little puzzled by the log file message -- 0 blocks to 1073 (or is it 10736?). That seems somewhat unlikely -- how could you copy nothing to something. Unless it is somehow triggered by the CREATEBLOCKONEQ setting but I don't believe that has any impact beyond block creation in formulas.
Do you see an actual increase in the number of blocks in database statistics?
Regards,
Cameron Lackpour

Error 1073 When trying to build app.

"Error 1073 occurred at... Possible reasons: This property is writable only when the VI is in the edit mode.
Application builder: The source VI must have its diagram in order to be included in an application."
When I save my vi as an app. distrib. without diagram I get this message when I try to build app. No problem if the diagram is included. Didn't have this problem in 6.1... any suggestions? Would like to build without diagrams.
Attachments:
open_dialog.vi ‏33 KB

That's exactly the same problem I am having. I have purchased some third party VIs that do not have diagrams. Previously in LV6.1, I could build them into an executable, but now with LV7.0 I can't (even though I now have the LV7.0 versions of these VIs). It seems that NI have changed the rules without telling anyone.
A work-around that I have tried successfully is to get DLL versions of the VIs.

PXIe-1073 sytem not detected

I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
Any ideas on how to fix this issue ?
Thanks
Jeet

Hi Matt
Sorry for delay in replying.
After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
In the picture, you can see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
The attached pic shows NI-MAX and device manager snap shot.
Please advise.
Thanks
Jeet
Attachments:
nimax dev man.jpg ‏316 KB

NI 1073 PXI chassis

HI
I have a new chassis 1073
If in MAX I try to open a Visa Test panel I receive this warning message( cf the attached capture file) it isa usual?
We develop a PXIe card( arb wavefor generator) with PLX8311 PXIe-local bus bridge. When we plug this card in the chassi the computer don't success to "see" it. When we test we know that there is no activity on receive line (A5 B5 line3 on connector) ( when check on pcie connector on the computer mother board we see activity on this lines) why?
the pin A2 (PRSNT#) will be pulled down?( or connect directly to GND?)
The signal level PXIe and PCIe are the same? ( we work with an evaluation bord with the same bridge on PCIe and it work fine)
Thanks for help
Dina
Attachments:
PXIeChassis1073.nitrace ‏6 KB

Dina,
Here are a few things to check.
- A5/B5 should be connected to the PLX 8311's TX lines through capacitors (standard PCIe levels). TX --> cap --> A5/B5
- C5/D5 should be connected to the PLX 8311's RX lines (standard PCIe levels). RX <-- C5/D5
- Refclk is not a standard PCIe level. It's LVPECL instead. So it should should be AC-coupled and rebiased/terminated. As I recall, this suggested bias is a 56 ohm resistor to GND and a 475 ohm resistor to 3.3V (50 ohm Thevenin equivalent, center point of voltage around half the normal swing of PCIe's HCSL clock lines). The PLX bridge may have different requirements. RefClk <-- [bias resistors] <-- cap <-- E4/F4
- PRSNT# (A2) should be pulled down or connected directly to GND, though it's not used in a 1073.
Robert

Where can I find 3D model step files for PXIe-1073 chassis?

I need 3D model step files for the PXIe-1073 chassis. Does anyone know where I can get them?

Eduardo,
I again apologize for the extremely long delay. Our R&D department has completed your request, and it can be found online, here: http://digital.ni.com/hardref.nsf/websearch/99B2D43123FBABE1862578B60077848F?OpenDocument&node=20053...
Paul Davidson
Sound and Vibration Software Staff Product Support Engineer
National Instruments

LIBGWT_CAT:1073,LIBGWT_CAT:1509

Similar Messages

Maybe you are looking for