Configure custom application properties from admin console on 10gR3

Is there a way to promote a property in an application, deploy that application EAR to weblogic server 10gR3 and configure the property from admin console?
E-g: creating two properties loggingEnabled, logLevel in an application and based on the needs configure logging from server admin console.

You have to write your own management mbean,
Examples can be found here:
- http://blogs.oracle.com/WebLogicServer/2009/10/developing_custom_mbeans_to_ma.html
- http://blogs.oracle.com/WebLogicServer/2009/11/developing_custom_mbeans_to_manage_j2ee_applications_part_ii.html
- http://blogs.oracle.com/WebLogicServer/2010/03/developing_custom_mbeans_to_ma_1.html
Good luck

Similar Messages

  • Sun java system application server 8 custom realm lock the admin console up

    Hi:
    I implemented a custome realm. After I installed the custom realm to Sun App server 8 PE, I can get into the admin console any more. According to the log, the user is authenticated. However, this user isn't in write group to access the admin console. What would be the user group in a custom realm to access admin console?
    In version 7, even you set up custom realm the admin console still not affected by the custom realm. Why is the admin console in version 8 picking up custom realm?
    Thanks.

    Previous reply was quite misleading - there is no such thing as default admin password for standalone installation of Application Server. Default values only apply to Application Server installation installed through Creator or NetBeans installer.
    Otherwise, you have to specify admin user name and password at installation time. Admin username value is defaulted to "admin" so unless you changed it in your installation that should still apply. You had to enter explicit password values.
    If you forgot those, you can either uninstall and reinstall or you can take a look at Troubleshooting Guide for instructions on reseting admin authentication:
    http://docs.sun.com/source/817-6085/troubleshooting.html#1026910

  • Unable to start Managed servers from admin console

    Hello!
    We have a problem to start Managed Servers throw Node manager.
    We get an error:
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Additional information:
    weblogic 10.3.3
    PT8.51.11
    Linux x86_64 RH5
    When we starting Manged servers manualy, it's works fine.
    Thank you.

    Hello!
    The problem is found.
    We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
    The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
    So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
    ./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
    Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
    <Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    There are no errors in managed servers logs.
    PIA1.out:
    <Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Attempting to start WebLogic Server PIA1
    No activity will be logged to this window.
    Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
    PID for WebLogic Server PIA1 is: 27018
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
    <Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
    What can be the reason?
    Thank you.

  • Failes to start Managed server using Nodemanager from admin console

    Hi
    I have created the cluster using Weblogic version 9.2 MP3 with
    Machine 1 --> Admin (AS) + Managed server (MS1)
    Machine 2 --> Managed server(MS2)
    All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
    Machine is associated with each managed server and node manager is up and running.
    I have made Host name verification as "None"
    When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
    The server logs states that "Could not connect to admin server"
    Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
    Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
    Node manager is not configured to SSL.
    Any Clue what i am missing????

    Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
    Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
    Your boot.properties only needs 2 lines, like:
    password=your plain text password
    username=your plain text username

  • 11g node manager reachable but server does not start from admin console

    I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
    If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
    i see below error when try to check machine monitor tab.
    <Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
    Ckr10ycOJN username in config.xml
    node manager and managed servers are not root user process.
    Please help me if have any suggestions.

    Pls. make sure the following points in your environment.
    1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
         a) This file should have the entry for your domain 'dom_11gint'.
         b) Ensure the path referred in the nodemanager.domains file is correct one.
    2) Ensure the following remote server startup parameters are passed properly.
         a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
         b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

  • How to remove disconnected client from admin console

    Hi All,
    I have developed a video chat application and during my testing, I found that if video chat is going on and in between the call if some one unplugged Internet cable then FMS admin console is taking too much time to disconnect as well as remove from list.
    Is there any way to remove disconnected client immediately from admin console then please help me either by doing any configuration or logic.
    Thanks
    Ram

    You can set the AutoCloseIdleClients parameter for your application (simple), or write your own active detection method (harder).
    Here is a link to old documentation for AutoCloseIdleClients:
    http://livedocs.adobe.com/flashmediaserver/3.0/docs/help.html?content=03_configtasks_18.ht ml

  • Problem while Deploying application in weblogic admin console

    Hi all,
    Recently i got an issue while deploying application through weblogic admin console,
    I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
    My weblogic 10.3 was running in windows 2008 r2
    Kindly need a help to resolve this problem ASAP.
    Regards,
    Rakhi

    Hi sir,
    thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
    The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
    Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
    Kindly give me a perfect resolution on this issue. because i was so confused on this part.
    Regards,
    Rakhi..

  • Unable to start Managed server from admin console using nodemanager

    I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

    Hi there,
    Can you check the following configuration in Weblogic admin console ?
    1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
    2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
    3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
    Thanks
    Lakshman

  • Error while starting ManagedServer from admin console.

    HI,
    can any one please help me on the below error.
    i got the below error when i tried to start managedserver from admin console. and below are the steps i have done before start the manages server.
    1. started admin server.
    2. started nodemanager from C:\bea\wlng400\server\bin\startNodeManager.cmd
    3. started managed server from the admin console.
    managed server name is "QualcommServer"
    Error from QualcommServer.out file is :
    <Apr 27, 2009 4:46:37 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.ClassNotFoundException: com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean>
    Below is config.xml file which i am using:
    <jms-server>
    <name>JMSServer-AdminServer</name>
    <target>AdminServer</target>
    </jms-server>
    <jms-system-resource>
    <name>WLNGJMSResource</name>
    <target>AdminServer</target>
    <descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <custom-resource>
    <name>networktier</name>
    <target>QualcommServer</target>
    <descriptor-file-name>custom/nt.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
    </custom-resource>
    <custom-resource>
    <name>wlng-edr</name>
    <target>QualcommServer</target>
    <descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
    </custom-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>wlng.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>wlng.localTX.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    Thanks,
    Srinu Babu P

    This classs is usually found in server\lib\wlng\wlng-management.jar, make sure it has that class and that jar is getting loaded by the server.

  • Can't start CMS 4.7 from admin console

    I can't start cms instance from admin console. When i try to start it says "operation error: unable to start the server". I tried to start the server from command line, it seems ok, so when i back to admin console and try to open CMS, it says "server off" and the server was already started from command line successfully.
    DOES ANYONE KNOW WHAT HAPPENS???
    thanks,
    Marcelo

    Hi, did you manage to solve the problem mentioned here...i'm having the same problem now.
    Br

  • What web service & xml will be used for deleting the packged epub/pdf file from Admin Console

    What web service & xml will be used for deleting the packged epub/pdf file from Admin Console?
    I am able to delete the files from Admin console directy but not able to get which web service is calling on deleting the file from admin console:
    Mangal

    Hi Jim,
    I tired following web service and xml to delete the packaged ebook but it is giving me error instead of response:
    Web Service & XML
    http://myserver_url/admin/ManageResourceKey
    <request action="delete" auth="builtin" xmlns="http://ns.adobe.com/adept">
    <nonce>" . $nonce . "</nonce>
    <expiration>'. $expiration .'</expiration>
    <resourceKey>
    <resource>resource_id</resource>
    <resourceItem>1</resourceItem>
    </resourceKey>
    </request>
    Error Message
    <error xmlns="http://ns.adobe.com/adept"
    data="E_ADEPT_DATABASE http://myserver_url/admin/ManageResourceKey
    Cannot%20delete%20or%20update%20a%20parent%20row:%20a%20foreign%20key%20constraint%20fails %20(`adept`.`distributionrights`,%20CONSTRAINT%20`distributionrights_ibfk_2`%20FOREIGN%20K EY%20(`resourceid`)%20REFERENCES%20`resourcekey`%20(`resourceid`))"/>
    Magal Varshney

  • MANAGED SERVER NOT COMMING UP  FROM ADMIN CONSOLE,

    Hi All,
    I can't start managed server from admin console.
    The status is showing FAILED_NOT_RESTARTABLE.
    below is the error it is showing in the node manager.
    But i can start managed server from the back-end successfully. If i start the nodemanager then managed server is not comming up.
    <May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed
    _server'>
    java.io.IOException: Server failed to start up. See server output log for more d
    etails.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
    rManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)
    May 24, 2011 4:12:22 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'my_managed_server'
    java.io.IOException: Server failed to start up. See server output log for more d
    etails.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
    rManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)
    Please help.
    Regards,
    nag.

    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain'>
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out00039">
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server error log also redirected to server log>
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out'>
    <May 24, 2011 4:12:22 AM> <INFO> <weblogic_domain> <my_managed_server> <Server failed during startup so will not be restarted>
    <May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed_server'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    This is what i found in nodemanager log file
    Regards,
    Nag.

  • Start and Stop Weblogic From Admin Console

    Hi All,
    I am using weblogic7.0.I wanted to start and stop the weblogic server from the
    Admin Console(ie., from the GUI).I can stop the server but I cannot start.In order
    to start from admin console what should I do.
    Please post your suggestions.
    Thanks blazix

    You need to run the Node Manager on the manged servers you wish to remotely
    start.
    Chris
    "blazix" <[email protected]> wrote in message
    news:3fc37eea$[email protected]..
    >
    Hi All,
    I am using weblogic7.0.I wanted to start and stop the weblogic server fromthe
    Admin Console(ie., from the GUI).I can stop the server but I cannotstart.In order
    to start from admin console what should I do.
    Please post your suggestions.
    Thanks blazix

  • Finding DB details from Admin console

    Hi All,
    We have SOA11g server. Now i want to find the database used for that server from Admin Console.
    please help me in this.
    TIA,
    Bob

    Hi Bob
    1. Basically a SOA Domain by default needs 2 Schemas to store all the meta data. They are SOAINFRA and MDS. They are prefixed like DEV_ or anything you want. And if your SOA Domain also has BAM Reports stuff, there is another schema named ORABAM created.
    2. So you want to know where these schemas are existing like in which database host, port, sid, username.
    3. If you have Admin privileges, login into weblogic console. On left side, expand Services -> Data Sources. Now on right side, you will see bunch of datasources created specifically for SOA Domain. Click one DS named SOADataSource. Click on Connection Pool tab. Here in top you should see db url, db driver and db username. You cannot see the plain text password though. Do the same for other datasource named mds-soa, BAMDataSource (if you have BAM). Do not worry about many datasources. Basically, if you get details for one that is ok. Because most of the times, all the schemas will be in the same database though its not compulsory.
    4. If you have access to the physical location of this domain on the machine, then you can navigate to this folder structure and open the .xml files to see the same details. This is where all the data source xml files are stored. The location is: yourSOADomain/config/jdbc
    Thanks
    Ravi Jegga

  • PXI Platform Services version on the target appears to be older then 2.0.0 this host only supports targets running PXI Platform Servies 2.0.0 and later Upgarade your target in order to configure its PXI properties from this Host

    after formating  when tryed to install software to the target  this Error Shown
    NI PXi 8108
    The Selcted Target does not support this function 
    when I try to add PXi chassis this Error Shown
    PXI Platform Services version on the target appears to be older then 2.0.0 this host only supports targets running PXI Platform Servies 2.0.0 and later Upgarade your target in order to configure its PXI properties from this Host
    Help me!

    Hi Lukas,
    I think the problem is caused by differenet drivers for the CAN communication.
    NI provides two driver for CAN: NI-CAN and NI-XNET.
    NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
    You wrote:
    In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
    3. NI_CAN 2.7.3
    NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
    Regards, stephan

Maybe you are looking for