MDM port not found

Hi Friends,
I'm doing currently MDM-PI-Idoc scenario. When I start the mdm adapter I get this error.
MDM Adapter listener could not start due to: MDM port not found
However I have checked PI sp level i.e 05 and MDM sp level i.e 04, will this really be a problem for happening this issue?
How can I solve this?
Regards
Nag

Hi.
Pls now on search before on SDN. We have multiple threads about this.
MDM Port not found error in MDM adapter for PI 7.0
SAP PI 7.1 MDM Adapter
PI MDM Adapter Error - MDM port not found
MDM Adapter 7.1
Regards.

Similar Messages

PI MDM Adapter Error - MDM port not found

We are working on an R/3 - PI - MDM scenario using the PI MDM Adapter. We are currently encountering the following errors.
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-08 15:31:22 Error Message could not be forwarded permantely to the JCA adapter. Reason: System error: MDM port not found
2009-09-08 15:31:22 Error Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found
2009-09-08 15:31:22 Error Adapter Framework caught exception: System error: MDM port not found
2009-09-08 15:31:22 Error Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found.
Is there an issue with our receiver communication channel and the MDM Access Parameters? We are using the Port code and Remote System code provided by the MDM team.
Anyone experience this same issue?

We are no longer seeing the MDM Port Not found error, but we are still seeing the UnknownServer error. Looking at RWB Message Monitoring it appears that the message is successfully sent to the MDM server, but nothing is coming into the Ready folder. Any ideas on where the message is going, and why it is not showing up in the Ready folder?
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-11 14:04:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http: //XXXXXXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-11 14:04:15 Information Using connection MDM_http ://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.
2009-09-11 14:04:15 Information Message successfully put into the queue.
2009-09-11 14:04:15 Information The message was successfully retrieved from the receive queue.
2009-09-11 14:04:15 Information The message status was set to DLNG.
2009-09-11 14:04:15 Information Delivering to channel: MDS_TEST_CC
2009-09-11 14:04:15 Information The message was successfully delivered to the application using connection MDM_http ://sap.com/xi/MDMAdapter.
2009-09-11 14:04:15 Information The message status was set to DLVD.
I thought the implementation of the MDM Adapter was suppose to be straightforward and simple
Edited by: Chris Williar on Sep 11, 2009 9:56 PM

PI-MDM Port Not Found Issue

Dear Experts,
We are posting a message from MDM to ECC via PI. Idoc was successfully created in ECC.
Our requirement is : getting a response message from ECC to MDM via PI. Message reached PI but not posting to MDM Port folder and in CC Monitoring error is as below::
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found"**
Could you please provide your inputs.
Thaking you.
Hemanth

Hi Hemanth,
Please check the Setting for Inbound Messaging (communication channel) of PI
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm
Make sure here you fill all parameters correctly along with <serverName>:<portNumber>, Port Code and Remote System Code etc of the inbound MDM port.
Also, check that there is no more than one MDM receiver configured per MDM inbound port in your system landscape. Deviating from this guideline can lead to a race condition state where different MDM receiver communication channels are monitoring the same MDM inbound port, and only the first one receives the import acknowledgment of the message.
Just check and revert with result.
Regards,
Mandeep Saini

Servermgrd: cupsd's bootstrap server port not found

This issue was posted last fall, but no one had ever posted with a solution to it. About every 2 minutes in /var/log/system.log, I get the following message:
servermgrd: cupsd's bootstrap server port not found
This is on an Xserve running 10.4.5. No printers are attached or will be. I'm not sharing any printers either.
Again, its just an annoyance, but why is something logging to system.log if its not actually a problem?

same prob here. really annoying. ever find the cure?
-ed

Cupsd's bootstrap server port not found

I've got both Samba and CUPS turned off at startup, yet I get this recurring error in the system log:
Dec 12 19:07:12 /usr/sbin/smbd: cupsd's bootstrap server port not found
Dec 12 19:07:13 /usr/sbin/smbd: cupsd's bootstrap server port not found
Dec 12 19:07:13 /usr/sbin/smbd: cupsd's bootstrap server port not found
Dec 12 19:07:14 /usr/sbin/smbd: cupsd's bootstrap server port not found
I kill smbd but it starts up again, apparently thanks to /usr/libexec/launchproxy
I'm using the default configuration files for Samba and CUPS and there is no printer set up. Using OS X 10.4.3 (not Server). repaired permissions.
this is driving me nuts...any suggestions welcome.

I get that response all the time, it doesn't seem to have any relevance to anything and as far as I can tell, doesn't impair the functioning of my machine.
sometimes, too much information is too much information...
Miriam

I am trying to upload dives from my dive computer onto my macbook pro but program says serial port not found - dive computer is listed on macdive

I have a dive program called Macdive and am trying to upload my dives from my Sherwood Wisdom dive computer via usb lead. The dives will not upload and program says that serial port not found. does anyone know how I can activate?

Try a new post in the appropriate iPhoto forum.
DALE

XI Idoc Receiver Port Not Found

Hi there
I have a Idoc Scenario where the Idoc is a receiver adapter going into some Sap System. I have setup the scenario and it gets processed correctly but the Idoc has got a status 56. Everything seems fine but in WE02, if I view the idoc under Technical Info, the Port there is different from what I have specified in the message mapping. Where does that port get specify if not in XI?
Thanx,
Jan

Hi Jan,
have a look at my blog
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
to understand which values from the control record you can control
and how
Regards,
Michal Krawczyk

Port not found for em

1st problem : hi i have created a new database.. so oracle by default is also creating a repository and one directory in in oracle home "hostname_sid"
this directory contains a file emd.properties where we can find the port for em to connect oracle enterprise manager 10g database control. but in my case i am not able to find the port no in emd.properties file below is th portion of emd.properties file.
======================================================================
# OMS Upload URL
# if there is no receiving OMS or if you wish to disable the UploadManager
# please set this value to empty or comment out below line
REPOSITORY_URL=http://hpux1570:%EM_UPLOAD_PORT%/em/upload/
# Proxy settings used for fetchlets. not applicable for uploader.
#proxyHost=www-proxy.us.oracle.com
#proxyPort=80
#dontProxyFor=.us.oracle.com
======================================================================
2nd problem : I have installed oracle EM Grid Control 10.2.0.2.0 on my windows xp system
database version is 10.2.0.1.0 and agent on hpux server.
but i check the status of " emctl status emagent "
it is giving me error
/home/oracle>emctl status agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Date: Fri, 01 Aug 2008 06:11:20 GMT
Server: Apache/2.0.53 HP-UX_Apache-based_Web_Server (Unix) DAV/2
Allow: GET,HEAD,POST,OPTIONS,TRACE
Content-Length: 325
Connection: close
Content-Type: text/html; charset=iso-8859-1
Agent is Running but Not Ready
/oracle/product/agent10g/bin>emctl upload agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
upload failed with ret=-1
/oracle/product/agent10g/bin>emctl stop agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Stopping agent ................................. failed.
/oracle/product/agent10g/sysman/emd>emctl start agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Agent is already running
/oracle/product/agent10g/sysman/emd>ps -ef |grep emagent
oracle 17974 15161 1 12:46:47 pts/18 0:00 grep emagent
/oracle/product/agent10g/sysman/emd>ps -ef |grep emctl
oracle 17984 15161 0 12:46:52 pts/18 0:00 grep emctl
==================================================================

it is not working.. failed to stop
/oracle/product/10g/sysman/emd>emctl stop agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Stopping agent ................................. failed.
/oracle/product/agent10g/bin>emctl stop agent
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Stopping agent ................................. failed.

Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices 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://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" 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://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
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/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi again,
I got it - i've forgot the namespace prefix for the wsdl-port.
Now it works.
Thanks!
"Ben" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices 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://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" 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://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
>
>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
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/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Air port express not found by my mac

Hallo all, I want to extend my wlan, therefore I want to install an additional air port. I have already a time capuse with air port. Now my question:
Do I neet to connect the new air port with a wire? I thougt the connection is wireless? Unitl now the new air port is not found by my mac within the utility air port program. Why? Please help! Thank you, Kailash

To help facilitate setting up your extended network, I would recommend the following:
Perforrm a "factory default" reset on the AirPort Express base station.
Temporarily connect the Express to the Time Capsule using an Ethernet cable between them.
Once you have configured the extended network, you can now disconnect the Express from the TC and place it at the desired location.

DIO Port Config & DIO Port Write Block Diagram Errors (Call Library Function Node:library not found or failed to load)

Hi Guys, need help on this.
I have this LabVIEW program that used to work on the old computer.
The old computer crashes most of the time, so I upgraded the computer
and used its Hard Drive as slave to the new computer.
I have no idea where are its installers since the guy that made the program
is not in my department anymore.
I downloaded all the drivers needed from NI: NIDAQ9.0, NIVISA,NI488.2,
and drivers of some instruments needed in the setup. I'm using LabVIEW8.2.
Everything's fine until I open the LabVIEW program for our testing.
Here goes the error:
   DIO Port Config
   DIO Port Write
Block Diagram Errors
   Call Library Function Node: library not found or failed to load
Attachments:
ErrorList.JPG ‏200 KB

Honestly, I'm a newbie on Labview. I just want this old program to run on the new computer.
The guys that installed the drivers on the old computer are no longer here in my department.
And I have no idea where the drivers are. So I just downloaded the drivers needed for my hardware and instruments.
Here's my hardware: (cards: PCI-DIO-96, PCI-GPIB), (instruments: SCB100,E4407B, HP83623, HP3458, HP8657)
OS: Windows XP Pro
By the way, I have unzipped the TraditionalDAQ drivers. First I tried the 7.4.1, but installation error appeared.
I thought maybe the installer is corrupted, so I downloaded the 7.4.4 and unzipped it.
But, still same installation error appears. I don't understand, both TraditionalDAQ drivers have same installation error.
Now I have tried the DAQmx8.7.2 driver, bu still the DIO Port Config and DIO Port Write have errors.

User not found error when connecting to MDM server using NWDS

Hi,
I am getting the error as " User not found " when i am connecting to MDM server from the code written in NWDS.
If i make that user as admin in usermapping in MDM den it works fine bt if that user is not admin den get the error as user not found.
Please help.

Hi,
Thanks for the reply.
I have added the user in user mapping in MDM server. but i have to give the authority as admin.
other users who are added in usermapping bt not assigned as admin are getting the error.

LMS4.1: Automonitor Link Ports + Instance Not Found

Hello,
In HUM there are no linked interfaces discovered, dispite them exists at CM topology and DCR discovery report sees all CDP neighbors as well.
1.
All Devices Device Availability
Active
1 Minute 5 Minutes 15 Minutes 30 Minutes Don't Monitor
2.
All Devices CPU Utilization
Active
1 Minute 5 Minutes 15 Minutes 30 Minutes Don't Monitor
3.
Link Ports Interface Availability
Instance Not Found
1 Minute 5 Minutes 15 Minutes 30 Minutes Don't Monitor
4.
Link Ports Interface Errors
Instance Not Found
1 Minute 5 Minutes 15 Minutes 30 Minutes Don't Monitor
5.
Link Ports Interface Utilization
Instance Not Found
1 Minute 5 Minutes 15 Minutes 30 Minutes Don't Monitor
What can we do?
march-bundled path for LMS4.1 has allready been installed.
Want to create the interface poller based on a report of linked ports manualy. But neither port nor interfaces have got neighbor attributs.
How is this possible to create a linked port report?
thx for hints,
Steffen

FWIW with Cisco TAC and DiData on similar set of circumstances for our install, it was paramount that devices discovered and/or manually added are actually interconnected. Once added successfully, we De-activated then Activated these three pollers, then their status remained ACTIVE and stable. And stats like Utilization (ONLY on interconnected links) were populating successfully.
In hindsight this makes sense, but yeah if you take the slow and steady approach and like one device at a time, you'll get stuck on this one.
Regards, Christopher

IView not found: com.sap.pct.mdm.tech.systems.MDMSystemWizard

Hello Experts!
I've installed MDM 5.5 SP6 along with the portal content that came from the same download. The portal content files I installed are listed below.
BPMDMAPPLI06_0.sca
BPMDMTECHN06_0.sca
MDM_WEB_UI550.sca
MDMJAVAAPI06_0.sca
When I try to get a new MDM system I get the exception below. I've looked and searched the portal content and this iView (com.sap.pct.mdm.tech.systems.MDMSystemWizard) does indeed appear to be missing. Is there something else I need to install? The SCA files all deployed without errors.
Steps to recreate this error:
System Administration => System Configuration => Portal Content => (landscape directory)
=> Right-Click => New System (from template) => choose MDM System template => Next
Thanks,
John
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: com.sap.pct.mdm.tech.systems.MDMSystemWizard
        at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
        at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)
        at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
        at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
        at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)

Restarting the J2EE engine resolved this problem.

MacbookPro2.4GHzi5 8GB1333MHzDDR3.LION10.7.2.UPDATED. Thunderbolt problem. Correct cable Apple TB HDI converter. Daewoo19"HL92QWA not found. TB Port drivers or other solution please anyone?

MacbookPro2.4GHzi5 : 8GB1333MHzDDR3 : LION10.7.2 UPDATED.
Thunderbolt problem.
Correct cable Apple TB>HDI converter.
Monitor: Daewoo19"HL92QWA (analog or digital) not found by system.
ThunderBolt Port drivers up to date. >> but must be the problem... Any solutions please anyone?
Have reinstalled LION to see if monitor was found before TB driver update. Not found!
Have tried every combination of turning on monitor and rebooting system.
Next logical step: pouring water (with a suspension of copper particles - of course) into computer!
Please help as this computer was only bought on the basis that a secondary `big` monitor could be attached!

Been reading more of the posts that relate to this problem....
Looks like this is a wasted thread!!!
Thanks Anyway!

MDM port not found

Similar Messages

Maybe you are looking for