Failure to start

Lightroom 3.4 on XP. After using LR for a month or more, on startup, I got the  Windows error messge that asks if you want to tell Microsoft.
  Upon clicking on a lrcat file name or trying to start LR from the start menu I get a banner that says
       LIGHTROOM - OPENING CATALOG: IMG_0380.JPG.lrcat
immediately followed by the window that  Lightroom has encountered a problem .As far as I can tell the lrcat does not exist.  Removing and reinstalling LR does not solve the problem.
Can anyone help?

You can also check the instructions in this thread, it applies to Windows XP as well.
Beat

Similar Messages

  • Unable/failure to start upload in DW CS4 (recent issue, was working) and DW CC 2014. Filezilla also fails but BOTH connect to the server. No known changes to desktop system.

    Started: 7/14/2014 12:44 PM
    cContacts\Copy of 0100.html - Transferring
    cContacts\Copy of 0100.html - error occurred - An FTP error occurred - cannot put Copy of 0100.html.  Internal data error, possibly because of failure to start the upload.
    File activity incomplete. 1 file(s) or folder(s) were not completed.
    File Transfer failed due to following reasons:
    - Internal data error, possibly because of failure to start the upload.
    Files with errors: 1
    cContacts\Copy of 0100.html
    Finished: 7/14/2014 12:45 PM
    FROM FILEZILLA
    Command: TYPE A
    Response: 200 Switching to ASCII mode.
    Command: PASV
    Response: 227 Entering Passive Mode (38,102,237,240,170,242).
    Command: STOR 0000.html
    Response: 550 Permission denied.
    Error: Critical file transfer error

    If you cannot upload files with Filezilla, there's a problem with your server.  Have you exceeded your server's space allotment?  If your server is full, it will reject new file uploads.
    Nancy O.

  • HT1386 My IPad2 will not sync with my iMac anymore, keeps giving me an error of failure to start sync after it has tried for 2-3 minutes

    My IPad2 will not sync with my iMac anymore, keeps giving me an error of failure to start sync after it has tried for 2-3 minutes

    Cenzon-
    Are you syncing over WiFi or over the USB cable?  Try doing the opposite.
    Also try a different USB port on the iMac.
    Fred

  • HP Envy 7 interment hard drive failure on start up

    Hello,
    I have a HP Envy 7 with Windows 7. On start up, I get the "Interment Hard drive failure", I ran the hard drive test and the results were good. I didn't get an error message but the message comes up everytime I restart. Is there a way to turn the smart disk message off or should I get ready to purchase a new hard drive?

    Hi
    Can you help me with Product number & the complete model number off you unit. Please find the Link given Here how to find the details.
    Most HP Notebook PCs have SMART (Self-Monitoring Analysis and Reporting Technology System) capable hard drives. SMART is firmware that resides on the hard drive and continuously monitors drive parameters such as performance and error rates. SMART uses a technology known as predictive failure analysis to tell you when a hard drive failure is imminent.
    Common SMART errors are:Hard disk failure is imminent.
    A hard drive in the system reports that it may fail.
    Smart failure imminent, back up your data
    Error 1720 Imminent Hard Drive Failure
    HP Hardware Diagnostic errors that start with HD521
    The use of SMART does not prevent all hard drive failures, but it can give you the opportunity to back up your personal files and replace the hard drive before it fails.
    Let us know how it goes!
    "I work for HP."
    ****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    Regards
    Manjunath

  • Failure to Start JMS Service in Sun Java Server

    Hi,
    I'm using Sun Java Server on Unix platform with Java 5.
    When I start the Sun server I find the JMS service in in unable to start.
    Please find below the Error Log Trace I observe:
    [#|2005-11-18T04:19:13.320-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
    |_ThreadID=10;|JMS5037: Check permissions of MQ instance directory
    /home/jai/cts141/SUNWappserver/imq/var/instances|#]
    [#|2005-11-18T04:19:13.321-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
    |_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service
    broker instance imqbroker. Please refer to the JMS provider documentation for the exact
    location of this log file.|#]
    [#|2005-11-18T04:19:13.322-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
    e|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection
    creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
    (errno:4127)
            at
    com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:
    415)
            at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
            at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
    creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
    (errno:4127)
            at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.ja
    va:233)    at 
    com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.ja
    va:180)
            at
    com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
            at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
            at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
            at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandl
    er.java:53)
            at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
            at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
            at
    com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
            at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
            at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
            at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
            at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
            at om.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
            at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
            at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:32
          at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
            ... 7 more
    Caused by: java.net.ConnectException: Connection refused (errno:4127)
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
            at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
            at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
            at java.net.Socket.connect(Socket.java:507)
            at java.net.Socket.connect(Socket.java:457)
            at java.net.Socket.<init>(Socket.java:365)
            at java.net.Socket.<init>(Socket.java:178)
            at
    com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
            ... 25 more
    |#]
    [#|2005-11-18T04:19:13.327-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
    e|_ThreadID=10;|Server Startup failed. Exiting...|#][
    * The JMS service is unable to start on the port 7676 which I find free .
    * The directory /home/jai/cts141/SUNWappserver/imq/var/instances also holds all permissions to all users
    * The log for MQ startup gets created if I explicitly run the script imqbrokerd located at /home/jai/cts141/SUNWappserver/imq/bin.
    But this script does not get executede when the server is started .
    But all these JMS startup happens fine when I start the sever setup with
    previous version of Java (Java 1.4.2).
    Please clarify the same.
    Thanks in Advance,
    Jay

    I guess if you don't start the managed servers with NodeManager they do come up?
    Not sure if this is related, but did you take a look at MOS note 1336100.1? It basically says there was a failure during configuration of NodeManager; it is not entirely related to forms but to FMW 11.1.1.5 which is somehow the version number of forms 11.1.2. A cause of it is that NodeManager isn't using the correct script when starting a managed server; this also sounds a little bit like your problem...
    Regarding the OutOfMemory exception you might look at note 1312573.1; it is related to running WLS as windows services (without NodeManager); but it might as well apply to running the Servers with NodeManager.
    It might be a shot in the dark, but it might be worth a try.
    In any case when running into (forms related) troubles with weblogic I found very little specific forms related informations on weblogic; this is probably due to the fact that forms doesn't make much use of weblogic at all (all in all most of the work is done by the good old fashioned C- forms runitmes); but the generic notes on weblogic often did the trick.
    cheers

  • Application Launch Failure when starting Office 2004 and Adobe Photoshop

    I've had my powerbook G4 for 3 months now with no problems what so ever, but recently my word, exel, powerpoint applications and even adobe photoshop cs give me a:
    Application launch failure:
    The application "Word" could not be launched because of a shared library error: "3<Microsoft Word><CarbonLib><CFMPriv_ImageCapture>"
    i've google this problem for several days with no solution. I've tried, deleting the pref files, reinstalling office, disk verified my hdd. Nothing worked.
    Does anyone have an idea what's wrong?
    Powerbook G4   Mac OS X (10.4.6)   512MB RAM

    Hi, miek. Welcome to the Discussions.
    Here is some general advice on troubleshooting shared library errors.
    A shared library error, in general terms, implies a missing, corrupted, or incompatible application or operating system framework. Details on frameworks and shared libraries (heavy technical reading) can be found in the "Frameworks" section of the "Software Development Overview" chapter of the Apple Developer Connection document Mac OS X Technology Overview, and the Framework Programming Guide.
    Causes for shared library errors include:
    • The affected application has been corrupted and must be reinstalled.
    • Running incompatible versions of two applications with interdependent shared libraries.
    • Disk or permission corruption.
    • Corrupted operating system installation.
    To resolve shared library errors:
    1. As a start, perform a general checkup by running the procedure specified in my Resolving Disk, Permission, and Cache Corruption FAQ.
    2. If the problem persists and only one application is affected, uninstall, then reinstall the affected application. See my "Uninstalling applications" FAQ for important advice on uninstalling software.
    3. If the problem persists, multiple applications are affected, or the shared library in question is part of the operating system, then reinstall Mac OS X using the Archive and Install process. See my "General advice on performing an Archive and Install" FAQ.
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • Failure to start J2EE Server

    Hi,
    I am trying to start the J2EE server in Windows XP environment. It worked for once. But after that, the server says that it failed to start the domain.
    When I checked the log file in domain directory, I found exceptions that are related to JMS. I don't know how to fix this. I would appreciate if anyone could help me. The following are the exceptions that I found from log file.
    Starting J2EETM 1.4 Application Server Beta 2 ...
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:47:26:643 GMT-05:00][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2] from [Sun Microsystems Inc.]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:716 GMT-05:00][ADM0020:Following is the information about the JMX MBeanServer used:]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0021:MBeanServer Implementation Name:[JMX]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM023:JMX Implementation Version:[1.2_r08]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM024:MBeanServer ID:[vishist_1067363248606]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:806 GMT-05:00][ADM0002:System MBean initialized:[ias:type=controller]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:826 GMT-05:00][ADM0002:System MBean initialized:[ias:type=configurator]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:836 GMT-05:00][ADM0001:MBeanServer initialized successfully]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0005:Timestamp files for configuration created for:[server]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0102: Starting a thread for tracking manual changes]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server. Please refer to the JMS provider documentation for the exact location of this log file.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5024: JMS service startup failed.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][Service com.sun.enterprise.jms.JmsProviderLifecycle@1d33a6b cannot be initialized! : com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:268)
    at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:209)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:166)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:252)
    ... 8 more
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:233)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:509)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1020)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1554)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:438)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:247)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
    at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:733)
    at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:305)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:245)
    ... 8 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
    ... 26 more
    ]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server Startup failed. Exiting...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server shutdown in progress...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:266 GMT-05:00][CORE5051: Shutting down all J2EE applications ...]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:286 GMT-05:00][CORE5049: Unexpected error occurred while shutting down applications
    java.lang.NullPointerException
    at com.sun.enterprise.server.ApplicationLifecycle.onShutdown(ApplicationLifecycle.java:339)
    at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:409)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:184)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    ]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:346 GMT-05:00][ADM0103: Stopping the thread for tracking manual changes]>
    <[WARNING][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][core.tmp_folder_deletion_failed]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][ADM032:The System MBeanServer released]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:406 GMT-05:00][Server stopped due to Server startup failure.]>

    Based on this, assigned JMS port is already in use during the server startup. One possibility is that the previous shutdown of the server did not go through, or some completely unrelated process started using JMS port (default value of JMS port is 7676).
    To fix this, you can either try to find out what is using JMS port and shut that process down, or modify <install_dir>/domains/domain1/server/config/domain.xml file with different JMS port number.

  • Failure to start domain domain1-help needed

    Hi,
    I am trying to start the J2EE server in Windows XP environment. It worked for once. But after that, the server says that it failed to start the domain.
    When I checked the log file in domain directory, I found exceptions that are related to JMS. I don't know how to fix this. I would appreciate if anyone could help me. The following are the exceptions that I found from log file.
    Starting J2EETM 1.4 Application Server Beta 2 ...
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:47:26:643 GMT-05:00][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2] from [Sun Microsystems Inc.]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:716 GMT-05:00][ADM0020:Following is the information about the JMX MBeanServer used:]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0021:MBeanServer Implementation Name:[JMX]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM023:JMX Implementation Version:[1.2_r08]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM024:MBeanServer ID:[vishist_1067363248606]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:806 GMT-05:00][ADM0002:System MBean initialized:[ias:type=controller]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:826 GMT-05:00][ADM0002:System MBean initialized:[ias:type=configurator]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:836 GMT-05:00][ADM0001:MBeanServer initialized successfully]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0005:Timestamp files for configuration created for:[server]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0102: Starting a thread for tracking manual changes]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server. Please refer to the JMS provider documentation for the exact location of this log file.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5024: JMS service startup failed.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][Service com.sun.enterprise.jms.JmsProviderLifecycle@1d33a6b cannot be initialized! : com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:268)
         at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:209)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:166)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:252)
         ... 8 more
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:233)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:509)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1020)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1554)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:438)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:247)
         at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
         at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
         at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
         at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:733)
         at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:305)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:245)
         ... 8 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
         at java.net.Socket.connect(Socket.java:452)
         at java.net.Socket.connect(Socket.java:402)
         at java.net.Socket.<init>(Socket.java:309)
         at java.net.Socket.<init>(Socket.java:124)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
         ... 26 more
    ]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server Startup failed. Exiting...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server shutdown in progress...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:266 GMT-05:00][CORE5051: Shutting down all J2EE applications ...]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:286 GMT-05:00][CORE5049: Unexpected error occurred while shutting down applications
    java.lang.NullPointerException
         at com.sun.enterprise.server.ApplicationLifecycle.onShutdown(ApplicationLifecycle.java:339)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:409)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:184)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    ]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:346 GMT-05:00][ADM0103: Stopping the thread for tracking manual changes]>
    <[WARNING][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][core.tmp_folder_deletion_failed]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][ADM032:The System MBeanServer released]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:406 GMT-05:00][Server stopped due to Server startup failure.]>

    Hi ,
    I too had got a similar exception a while back.The default jms port 7676 was being used by some other application.
    Make sure the kms port is free else you can chnge the jms port using the application server admin console.
    -Amol

  • G5 Power failure during start up and wake

    I have an early G5 20" non-iSight iMac that has a power problem that is steadily getting worse.
    As Apple support has expired and can't be extended, I'm at a loss how to resolve this.
    Description.
    The problem first started as intermittent during wake up from sleep (power light pulsing). I'd move the mouse or tap the keyboard to wake the iMac and I'd hear the disk just start to spin up followed by a sharp 'pop/click' like the power cord had been pulled, and it would be powered off needing the power button to be pressed to restart from scratch.
    Now the problem has worsened in that occasionally I will find the iMac has completely powered down during sleep. When I restart it can take up to 6 or more attempts to get to the point where I can use it. There's a sequence of restarts needed, each starting from pushing the power button, and then ending during the starting sequence with a 'pop/click' as the power suddenly shuts off. Each time the start up will progress a little further than the previous attempt until eventually it finishes building the desk top after login and I can operate normally until the next time I find it powered off after a few hours of non-use. The power failure starts initially from just after the welcome chime, and progresses to maybe 5 or 6 times later to during the desk top build after log-in. However, once logged in and operating the iMac behaves as normal, switching users, log-out and login, screen save and wake from screen save etc are all as I'd expect. I've not (yet at least) had any sudden power failures during normal operation.
    The serial number of the iMac falls within the Sept 05 Repair Extension Program serial number range (not EMC 2056 though), but when I spoke to Apple Support they said that the lack of random behaviour meant that the problem I'm having is not related and so would not be covered by this program.
    So I'm kinda stuck with a problem that is annoying when it occurs, which is daily at the moment, although it's been this bad a few weeks back and then was fine (iMac left switched on for 2 to 3 weeks without a problem) until we had a power cut earlier this week, and it's started again.
    I've searched through the forums and while I could find plenty of references to 'Sudden Power Loss' none seemed to be as predictable and similar to this one.
    Suggestions and ideas welcome. Thanks.

    i am having a similiar issue. I have the same exact computer (iMac G5, non-isight) and it stays on for 30 mins, hour, 3 hours and shuts off. Upon starting up, sometimes it doesn't make it to the login screen before shutting down again. I have downloaded heat temp monitor programs and it seems to get to about 70 degrees celcius sometimes. Upon restarting, I get the "report problem to apple" screen with this information. I have tried to restart the power supply too.
    Thu Apr 17 09:02:18 2008
    panic(cpu 0 caller 0x008E0BE4): "Missing CPU diode calibration information.\n"@/SourceCache/IOPlatformPluginFamily/IOPlatformPluginFamily-312. 0.1/SMUNeo2_PlatformPlugin/SMU_Neo2CPUTempSensor.cpp:124
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x0009B478 0x0009BE1C 0x00029DD4 0x008E0BE4 0x008D0308 0x008CFD78 0x008E309C 0x008D48E8
    0x008E2C6C 0x00342B8C 0x00343CE0 0x00345B90 0x00344CB0 0x000B05D4
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.SMUNeo2PlatformPlugin(3.1.2d1)@0x8dc000->0x8eafff
    dependency: com.apple.driver.IOPlatformPluginFamily(3.1.2d1)@0x8c9000
    com.apple.driver.IOPlatformPluginFamily(3.1.2d1)@0x8c9000->0x8dbfff
    Proceeding back via exception chain:
    Exception state (sv=0x39e04c80)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    9C7010
    Kernel version:
    Darwin Kernel Version 9.2.2: Tue Mar 4 21:23:43 PST 2008; root:xnu-1228.4.31~1/RELEASE_PPC
    System model name: PowerMac8,1
    *>}

  • My Time Machine Error -43 is a failure to start application

    I've posted this elsewhere wrongly as I didn't realise there's a section for Time Machine problems. So I'll re post here to see if anyone knows what Error -43 Time Machine can't be started up. It throws the error up with no Details to click on. Just Error 43
    I attached a buffalo drive to the usb and ran time machine the other day and it wanted to format or wipe the external drive so I aborted by cancel out.
    Next I tried hooking up a Western Digital MyBook 300gig hard drive by firewire which was empty all but a few files left over from Windows. I would have let Time Machine wipe that one and set it all up for a backup but Time Machine won't start. I tried reinstalling it from the Mac Disk 1 and 2 and still it doesn't want to kick start. What have I done to confuse it?
    Does anyone know how the application works or how to give it some medicine and make it get going again please?
    Plado

    That was the very best result so far. I've had an encouraging measure of success. But sorry this is not going to be short!
    But a failure of sorts occurred at the end, through my own lack of understanding.
    I printed out your directions and went through piece-meal and on this occasion because I don't want to lose the data on the Buffalo I didn't deploy it, instead I plugged in the MyBook
    By your very clear system of entry to the settings I found the drive recognized.
    Yes the MyBook for the first time appeared!
    I went right through the Partition and Erase process but was confused to find I needed to name the drive twice (in two places) once for the start of the process of settings and then again when I had to choose 1Partition. So I put MYBOOKBAKUP in the first window and then when it wanted a name for the Partition (I think that's what it was asking for a name for) I put MAYBACKUP. It appeared to Erase and Format the drive or the partition or something but it never said it had completed.
    I ended up closing the window and nothing happened.
    Then I discovered a window box still open that said how much and often the drive will be backed up. It seemed to suggest that it will be backing up every minute then once every hour and then once a week and when the Mac is plugged in. I'm not sure what that meant. I thought the mac never had to be plugged in? It has to be "booted" and it has to have a "drive plugged in" externally but why doesn't it say what it really means?
    I don't want it backing up every minute hour and week because a lot of the time I'm using the macbook without an external drive plugged into the USB so why did it not offer me a MANUAL backup, to start the process when I am available with an external drive to plug in and do one?
    The window I was left with when I went back to Switch the Time Machine slider switch off was one that said in RED "Backup Failed" !
    I clicked on i for info and it said "No volumes to be backed up were available. This can happen if all volumes are in the "Do not back up" list. To view the list, click Options."
    So did I interrupt the backup process before it was finished? I didn't intend to but the system never gave me a progress bar to say it was still doing it. Maybe it is backing up all the time unless you unplug or switch it off. That is not sensible. I must have set something wrong. Is the only way to stop it auto backing up to switch off the TM and tell the computer not to backup to any disk?
    I was confused as to why the Macbook's own drive appears in the list to backup to. Can it back up to its own disk? If so that seems weird as it's like the machine could eat itself!
    Like I said, there's a heck of a lot in this process I just can't get my head around without your excellent help. I'm painting by numbers here and just following lists of things to do.
    I only need to plug in a drive and about once a month or so backup the system to save me in the event of a Hard Drive failure. But because the Mac is as prone to HD failure as any windows machine I'm not really daring to rely on it for important data, which rather defeats the object of using it.
    Anyhow I will await your enlightenment if you can possibly just clarify what I'm doing wrong and thinking wrongly about when it comes to manual backup.
    Thanks and we're nearly there.
    I think the question can close after your next directive as solved because I feel as if I'm on the final straight now.
    Regards
    Plado

  • Windows 8.1 Recovery run after power cut & failure to start. PC back up and running but LR "Unexpected Error opening catalogue" is as far as I get.

    Hi, I had a search about for a solution but failed. Apologies in advance if it has been addressed already. I should add, I am semi proficient with the PC but apart from image tweaks have never really got my head around LR's cataloguing mechanics (cause of the issue anyone)
    Any way, I back up every time LR asks and have a folder full of them, so I thought it would be as simple as just clicking on a backup from before the Windows recovery was run and we would be up and running again.
    So I go to my LR folder/ backups/  select a backup and then get this dialogue box for a short while.
    Followed by
    Now I am out of my depth. Click cancel. Presented with.
    Followed by.
    Joy of joys.
    Fingers crossed I am just being a tard and the solution is simple. Please help and if I have missed any info you need please ask.
    Thanks,
    Matt.

    If you're selecting a LR catalog backup in a folder that doesn't show .lrcat.lock and .lrcat-journal files you have a different issue.
    Try removing your LR Preferences file, which may have been corrupted by the the power failure:
    How do I delete the Lightroom Preferences file? - The Lightroom Queen Help Desk & Members Area - Powered by Kayako Resol…
    If the issue persists try uninstalling LR5.5, delete the Preferences file as described above, and then reinstall LR5.6:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5823

  • How do I overcome version 11 failure to start a service?

    I installed version 11 (64 bit).  It tells me that the mobile device service won't start and asks if I have sufficient privileges.  I tell it to retry.  When I get tired of that I select ignore and the installtion finishes.  I can play my library on my computer just fine.  When I connect my iPod touch, it tells me I don't have the 64 bit software and need to uninstall and install the 64 bit version.  What do I have to do?

    Hi Peter,
    Please click on the given link: -http://helpx.adobe.com/photoshop-elements/archive.html and this link have PSE 11 help PDF achieved.
    Sarika

  • Hit by the famous "Failure to start JBOSS Service During Conf Management.  Error[ALC-LCM-999-032]"

    Hi Everyone,
    I m really frustrated with this issue. I am trying to install Adobe LiveCycle ES Update 1 trial version JBOSS turnkey option.
    It does not work!!
    The installation goes smoothly. But when I launch the config manager, there is no way I get passed the "Error[ALC-LCM-999-032], with a Failed on 'Starting service JBoss For Adobe LiveCycle ES'. Service startup failed for: JBoss for Adobe LivecycelES."
    I tried pretty much anything I could find out there as potential solution to the problem. I even tried it in a brand new machine whit pretty much nothing in it: so no possible port conflict (by the way I tried starting jboss directly from the cmd line under Adobe 8.2 dir and it starts fine. i.e: Only the service is busted!!!), tried changing the local policy right and Allow Logon as a service, tried changing the account the service is running under, to no avail.
    I tried installing it in machines with Win XP, SP2, JavaSDK1.5_017
    Also, tried installing it in machines with Win Server03 SP2 Standard Edition x64. Same JDK. Same thing.
    I have tried several machines w/ the same result
    I am obviously missing something !
    I personally dont care about the windows service. If there is a way to do the config manually, I m more than happy to take that route, as long as I am told what to do. THANKS>
    mb/

    I was able to solve this issue. I put this in another thread also as I treid for hours to get this to work and no one had good explanation on forums.
    I had same problem on Windows XP (32 Bit). I was installing LiveCycle ES on my desktop to do some solution evaluations. I could start the JBOSS server successfully if I did that by myself, but Adobe Configuration Manager and Java Service were failing.
    The issue was the JDK I had assigned to use.
    To resolve:
    1. Make sure you have compliant JDK Version. To get mine to work I had to install JDK Version jdk1.5.0_17.
    2. Switch the JDK that the JBOSS Java Service is pointing to. To do this, you will need to uninstall and reinstall the service.
    2.A Go to your installation folder (C:\Adobe\LiveCycle8.2\jboss) and copy the file "InstallJBossService.bat" and rename it "UnInstallJBossService.bat".
    2.B Change the command line to execute an uninstall by the following: "%LC8DIR%/jboss/JBossService.exe" -uninstall.
    2.C Change your OS Environment Variable for JAVA_HOME to the correct JDK, for example "C:\Program Files\Java\jdk1.5.0_17".
    3. Rerun the Adobe Configuration Manager C:\Adobe\LiveCycle8.2\configurationManager\bin\ConfigurationManager.bat
    It should complete successfully now IF your issue was the wrong JDK like I had.
    Also make sure that the Java Service has Permission to run. Check your control panel -> adimistrative tools -> Service. It will be called "JBoss for Adobe LiveCycle". Make sure it has permission to run as local user is what I did.
    There are some other posts about issues similar to this using wrong JDK or 64Bit Windows or other.

  • Failure to start XE database - spfileXE.ora file size mismatch.

    SQL> startup
    ORA-01078: failure in processing system parameters
    ORA-01565: error in identifying file 'E:\oraclexe\app\oracle\product\10.2.0\server\dbs/spfileXE.ora'
    ORA-27046: file size is not a multiple of logical block size
    OSD-04012: file size mismatch (OS 1464)
    SQL>
    SQL>
    Where is the file size set so that i can change it??
    Help please.
    Thanks in advance.

    Maybe the file was corrupted.
    Have you a backup ?
    Have you still the init.ora file ? Try to restart your db with an pfile instead, then recreate a spfile.
    Nicolas.

  • Acrobat Pro X Failure to start

    I regularly find that Acrobat Pro X fails to start when I double click an acrobat file or double click the program itself.  The fix for this problem is to download and run Acrofix.exe.  But it appears that this fix is of a temporary nature as about every month I have to run that fix again.
    Is there a permanent fix for this problem?

    I'd like to second that this is still a problem. Just popped up for me today. Last time I saw it was several months ago.
    Running 10.1.9

  • Failure to start agent for oracle 10g in window

    Hi Experts,
    I am using oracle 10G R4 in 32 bit window 2003.
    I saw agent stop in EM. I just restart dbconsole form window side.
    Now I saw that emgent with DBSNMP takes hight CPU (20-40%)
    I try to stop and restart dbconsole does not fix this issue.
    I just check that agent does not running even dbconsole is working on.
    below is copy :
    D:\oracle\product\10.2.0\SALE\BIN>SET ORACLE_SID=SHQ
    D:\oracle\product\10.2.0\SALE\BIN>emctl start dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    https://xxxxxx:1158/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsole
    SHQ service is starting................
    The OracleDBConsoleSHQ service was started successfully.
    D:\oracle\product\10.2.0\SALE\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent is Not Running
    D:\oracle\product\10.2.0\SALE\BIN>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    What dio I do can start agent?
    i run emctl status agent that does not work.
    Thanks for help
    JIM

    Hi anand,
    Thanks for your help.
    I check this DOC in metalink.
    But I stil can not get AGENT_HOME patch based on document.
    I try to use emctl getemhome however, I could not see ../../oracle1oGagent that document concern point
    I need to do create <agent_service_name> <AGENT_HOME>\bin\nmesrvc.exe auto
    How do I find agent home patch?
    Thanks
    JIM

Maybe you are looking for