Reconfigure or Restart JMS service !!!

Hi
<b>Reconfigure or Restart JMS service !!!</b>
This we have observed while going through AF logs.
Should we restart JMS Connector and JMS Provider services in Visual Admin?
We tried though but to no avail.
Any suggestions...
Regards,
Varun

yes the drivertool.bat does it for me
<?xml version="1.0" encoding="UTF-8"?>
<provider-descriptor>
    <display-name>com.sap.aii.af.jmsproviderlib</display-name>
    <component-name>com.sap.aii.af.jmsproviderlib</component-name>
    <major-version>7</major-version>
    <minor-version>0</minor-version>
    <micro-version>6</micro-version>
    <provider-name>sap.com</provider-name>
      <references>
         <reference type="library" strength="weak">jms</reference>
      <reference type="library" strengh="weak">com.sap.aii.messaging.runtime</reference></references>
    <jars>
    <jar-name>sonic_Client.jar</jar-name><jar-name>sonic_XA.jar</jar-name></jars>
  <
At this moment i am receiving the following error on the communication channel
Exception caught by adapter framework: The JMS channel with channel ID f055fe2451203cd5b39d81c7647b281e is errornous. Details:Error during channel initialization; exception trace: javax.jms.JMSException: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:2600 at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source) at progress.message.jimpl.Connection.(Unknown Source) at progress.message.jimpl.QueueConnection.(Unknown Source) ... [104] progress.message.client.ENetworkFailure: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:260

Similar Messages

  • Authentication error when using JMS service

    I'm currently trying to send String messages from LiveCycle to Websphere MQ (Both running on the same server), but I'm having some problems...
    I''m quite sure that my WAS setup is correct (or at least close to correct) because I've build some test Java classes that are able to put and get messages from MQ using JMS. However, when I'm usng the LiveCycle JMS service I get the following exception thrown:
    [5/26/10 17:46:44:705 CAT] 00000027 QueueMessageS A com.adobe.livecycle.jms.QueueMessageSender sendMessageToQueueWithProperties Error occurred when creating queue connection. Reason: MQJMS2013: invalid security authentication supplied for MQQueueManager.
    Since I'm not a Websphere fundi I trawled through Google and was able to figure out that the problem probably lies with the configuration of my queue connection factory. Changing the transport type from "Bindings" to "Client" didn't resolve the problem and I'm rapidly running out of good ideas. Hopefully somebody here would be able to help.
    The following info might be useful:
    OS = Windows Server 2003
    I'm using WAS 6.1.0.29
    Websphere MQ is running on the same machine (v6.0)
    I've used the Websphere MQ JMS Provider that comes with WAS
    I've configured a Queue Connection Factory and a Queue in the server scope
    No SSL or anything like that is set up yet
    I did notice that when configuring the Queue there is a section titled "WebSphere MQ Queue Connection Properties" where I am able to specify a user Id and password. However, nothing seemed to work. I tried my WAS administration user name, as well as a windows user who is indeed a member of the mqm group. Also tried it without any value, but no luck
    On the MQ side I couldn't really find any settings under either the Queue Manager or the Channel that would make much of a difference. Since I was able to access the queues using a servlet deployed on the same WAS instance I'm thinking it has something to do with the way that LC call the JMS provider. But to be honest, I don't really have a clue.
    Any help would be much appreciated.
    Greg

    Haven't solved the problem yet, but here's an update:
    I created an "ExecureScript" operation that contains simple Java code to write a message to MQ using the same JMS connection factory and JMS queue. It does work correctly, so clearly my setup it correct enough to send messages from LiveCycle to MQ via JMS.
    Here's the code for the ExecuteScript:
    //import the classes that the script references
    import java.util.List;
    import java.lang.String;
    import java.util.Map;
    import java.util.HashMap;
    import javax.jms.*;
    import javax.naming.*;
    //get a list of file names that are stored in the process variable named files
    String strMessage = patExecContext.getProcessDataStringValue("/process_data/@strMessage");
    //get connection factory
    String strQcf = patExecContext.getProcessDataStringValue("/process_data/@strQcf");
    //get queue
    String strQ = patExecContext.getProcessDataStringValue("/process_data/@strQ");
    try
        // Look up administered objects
        System.out.println("Looking up administered objects...");
        InitialContext initContext;
        initContext = new InitialContext();
        QueueConnectionFactory factory = (QueueConnectionFactory) initContext.lookup(strQcf);
        Queue queue = (Queue) initContext.lookup(strQ);           
        initContext.close();
          // Create JMS objects
          System.out.println("Creating JMS objects...");
          QueueConnection connection = factory.createQueueConnection();
          QueueSession session =    connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
        QueueSender sender = session.createSender(queue);
          //Send messages
          TextMessage message = session.createTextMessage(strMessage);
          sender.send(message);
           //Exit
           System.out.println("Exiting...");
           connection.close();
           System.out.println("Goodbye!");   
    } catch (Exception e)
            e.printStackTrace();
    Interestingly I don't provide any authentication information and yet LC is able to connect to MQ
    Cheers

  • After restarting the Services, Foundation service is not starting

    Hi All,
    Recently, i have applied patch and restarted the services, later found that foundation services is not starting. I have referred the logs and it showing below error.
    <Apr 29, 2015 7:45:30 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-x86_64 from Oracle Corporation>
    <Apr 29, 2015 7:45:31 PM PDT> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}9e8e9w8ADkG/3Hx33gkE9Ukm29IxHIISKLeLw/FYfxTO0GcnA= from the file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    Enter username to boot WebLogic server:
    I have logged to Weblogic server and checked, the foundation service is not started.
    We dont have the backup of installation folder.
    I manually edited the user name and password and started the services, but no luck.
    Do any one idea about processBootProperties.cmd, shall i trigger it to get the new boot.properties.
    Please suggest.
    Thanks

    Hi all,
    I manually enter the credential for the Web logic server and started the services. It worked out.
    I did the same first, but i did some typo error in credential, it killed me for more that 1 hour... ):
    Thanks

  • JMS Internal Error at Server Client Adapter!JMS Service is not started

    Hi
    Can any one tell me how to trouble shoot for following errors:
    Failed to Create Connection! Reason: Response from the server could not be reached.
    JMS Internal Error at Server Client Adapter!JMS Service is not started
    The following hosts could not be reached 143:223:221:10:50310
    We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
    but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
    regards
    Rambarki...

    Rambarki,
    What is the error displayed on the Adapter Monitoring pages?
    Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
    Other possible reasons could be :
    <i>JMS Service is not started
    The following hosts could not be reached 143:223:221:10:50310</i> This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
    Regards,
    Amol

  • 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

  • Restart Systemd service after laptop resume

    Hi!
    After resume my laptop (from suspend, I've no tried hibernation) I need to restart NetworkManager service. How can I do this automaticaly?, I've searched in google and Systemd documentation but I have not a clear idea about how to do it.
    thanks

    Gazpacho wrote:
    lucke wrote:As boast said, you can make pm-utils run "systemctl restart networkmanager.service" after resume for you. https://wiki.archlinux.org/index.php/Pm … _own_hooks
    Sorry (to boast too), you are right. I've read the wiki and created a hook, now NM restarts after resume. Thanks!
    And now I've discovered that my computer only suspends the first time. Second time nothing happens when I close the tap, execute pm-suspend or the KDE menu option suspend to ram
    If you have any idea it is welcome. If not I will mark the thread as solved in a couple of days and search in forums and wiki.
    this usually happens when your hook doesn't exit. pm-suspend never finishes because it's waiting for the hook to exit and the second pm-suspend will block until the other pm-suspend is finished. Please post your hook.

  • JMS5024: JMS service startup failed.

    I have created a hellowworld.jsp. I deployed the project using server Sun Java Application Server Edition 8.1 and Type exploded. The deploy was successful. When I try to start the sun Java Application Server Edition 8.1, I am receiving a JMS5024: JMS service startup failed SEVERE error. Any help would be appreciated. The error is below:
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21
    recursive call into SystemOutandErrhandler
    java.lang.RuntimeException: recursivecall
         at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189)
         at java.io.PrintStream.write(PrintStream.java:260)
         at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
         at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
         at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
         at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
         at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
         at java.io.Writer.write(Writer.java:126)
         at java.util.logging.StreamHandler.publish(StreamHandler.java:191)
         at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:87)
         at java.util.logging.Logger.log(Logger.java:424)
         at java.util.logging.Logger.doLog(Logger.java:446)
         at java.util.logging.Logger.log(Logger.java:469)
         at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198)
         at java.io.PrintStream.write(PrintStream.java:260)
         at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
         at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
         at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
         at java.util.logging.StreamHandler.flush(StreamHandler.java:224)
         at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
         at java.util.logging.Logger.log(Logger.java:424)
         at java.util.logging.Logger.doLog(Logger.java:446)
         at java.util.logging.Logger.log(Logger.java:469)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:285)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFa
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.ja
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)

    Hi
    successful. When I try to start the sun Java
    Application Server Edition 8.1, I am receiving a
    JMS5024: JMS service startup failed SEVERE error. Any
    help would be appreciated. The error is below:Could you share your MQ broker log file [$AS_INSTALL_DIR/domains/domain1/imq/instances/imqbroker/log/log.txt]? Does this error occur after you had installed the jsp app? Was the earlier shutdown a clean shutdown? Could you check and see if there are any jms processes around[ ps -efa | grep
    imqbrokerd] ?
    >
    WARNING: Feb 21, 2005 11:34:38 AM
    com.sun.enterprise.server.ss.ASLazyKernel
    startASSocketServices
    SEVERE: UnknownException during startup. Disable
    quick startup by setting system property
    com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleExceptionIs AS startup successful if you disable application server lazy startup using the above system property?
    --Siva.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • How to start or restarted Oracle_Secure_Backup service in RedHat linux

    Hi
    when i try to connect oracle secure backup using the following command, i am getting the follwoing message
    [root@midevdb bin]# obtool
    obtool: Error: can't connect to administrative observiced - observiced not running
    so how i can start, stop and restart Oracle_Secure_Backup service in redhat linux.
    thanks
    Settu Gopal

    the below is the logs from observiced.log log file.
    2009/03/31.12:19:28 observiced version 10.2.0.3.0 (linux) -- Tue Sep 23 10:36:22 PDT 2008
    Copyright (c) 1992, 2007, Oracle. All rights reserved. on midevdb.in.valtech.com pid 27248
    2009/03/31.12:19:28 listening for requests on --
    2009/03/31.12:19:28 virbr0 (192.168.122.1) port 400
    2009/03/31.12:19:28 eth0 (192.168.140.22) port 400
    2009/03/31.12:19:28 info: local host identity not readable or not yet established - no .hostid file
    2009/03/31.12:19:28 listening for NDMP connections on --
    2009/03/31.12:19:28 virbr0 (192.168.122.1) port 10000
    2009/03/31.12:19:28 eth0 (192.168.140.22) port 10000
    2009/03/31.12:27:04 failure to negotiate SSL connection with component obtool on fd 6 - no matching cipher suites (FSP Oracle network security functions)
    Thanks
    Settu Gopal

  • AS startup - JMS service startup failed

    After sucessful instalation of AS7 on sparc Solaris 8, I've got error during startup.
    [10/Jul/2003:16:42:12] INFO ( 1145): CORE1116: Sun ONE Application Server 7.0.0_01
    [10/Jul/2003:16:42:13] INFO ( 1146): CORE3016: daemon is running as super-user
    [10/Jul/2003:16:42:18] INFO ( 1146): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_01] from [Sun Microsystems Inc.]
    [10/Jul/2003:16:42:56] INFO ( 1146): JMS5035: Timed out after 30000 milliseconds while trying to verify if the JMS service startup succeeded.
    [10/Jul/2003:16:42:56] INFO ( 1146): JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server1. Please refer to the JMS provider documentation for the exact location of this log file.
    [10/Jul/2003:16:42:56] SEVERE ( 1146): JMS5024: JMS service startup failed.
    [10/Jul/2003:16:42:56] SEVERE ( 1146): CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
    at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
    Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:231)
    ... 2 more
    Caused by: javax.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:145)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
    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.iplanet.ias.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:284)
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:224)
    ... 2 more
    [10/Jul/2003:16:42:56] SEVERE ( 1146): CORE3186: Failed to set configuration

    This seems to be the same problem as one described in: http://swforum.sun.com/jive/thread.jsp?forum=68&thread=20049
    Double check JMS port assignments - port might already be in use by some other process and should be changed.
    Hope this helps...

  • Restart Network services

    I hope this isn't a repost but I was wondering if there is a way to restart network services in leopard, similar to this command in linux:
    /etc/init.d/networking restart
    I want to troubleshoot my connection to the router in my home, and my linux install works after giving this command, but leopard is having trouble.
    Thanks
    hah nevermind I found what I need
    Message was edited by: Dak

    Try this
    $ sudo ifconfig en0 down
    $ sudo ifconfig en0 up
    Use en1 for your AirPort card

  • When to restart the services OC4J_BI_FORMS & HTTP_SERVER

    During the deployment of our application on the 10G application server, we generally make entries in the following files:
    1) Default. 2) fmrweb.res 3) forms90 4) formsweb and 5) registry files.
    but i am not sure changes into which files needs me to restart the
    1)OC4J_BI_FORMS
    2) HTTP_SERVER.
    as of now i am just restarting these services whenever i make any changes in formsweb file.

    As I only can see that you made changes to Forms files, then you only need to restart the OC4J_BI_FORMS for the files mentioned:
    opmnctl restartproc ias-component=OC4J_BI_FORMSHowever, most changes in formsweb.cfg doesn´t need a restart.
    Regards,
    Martin

  • Regarding restart of services

    Hi Frnds,
    Can i know what is the sequence to restart the services i.e services like open ldap,Shared services,analytic services,administration services and also the sequence to shut down/restart.
    Thanks,
    KRK.

    Hi,
    Following is the sequence to start Hyperion product services: -
    1. Databases for repositories. (SQL Server, DB2, Oracle)
    2. Shared Services OpenLDAP
    3. Shared Services application server
    4. Reporting and Analysis Core Services
    5. Performance Management Architect Services
    6. Oracle's Hyperion® Essbase® – System 9
    7. Administration Services application server
    8. Oracle's Essbase® Integration Services
    9. Provider Services application server
    10. Reporting and Analysis (in the following order):
    a. Oracle's Hyperion® Interactive Reporting – System 9
    b. Financial Reporting
    c. Reporting and Analysis Web server
    d. Workspace application server
    e. Oracle's Hyperion® Web Analysis – System 9 application server
    11. Application server services or processes (in any order):
    ● Performance Management Architect application server
    ● Performance Management Architect Data Synchronizer application server
    ● Financial Reporting application server
    12. Remaining services (in any order):
    ● Planning application server
    ● Financial Management
    ● Oracle's Hyperion® Strategic Finance
    ● Performance Scorecard application server
    ● Performance Scorecard Alerter application server
    ● Data Relationship Management
    ● FDM
    ● Oracle's Hyperion® Data Integration Management
    ● Oracle's Hyperion® Translation Manager
    Just do the reverse of it shut down services.
    Hope it answers you.
    Atul K,
    Edited by: Atul Kushwaha on May 5, 2009 10:44 PM

  • Remote Restart of Services (with dependencies)

    Hello all,
    i've a short question about restarting a service on a remote machine with powerhell.
    I've tried the following:
    get-service -computername ServerXY -name ServiceXY | Set-Service -Status stopped
    And it works like a charm. But some services have dependencies. For example DFSR:
    PS C:\Windows\system32> get-service -ComputerName ServerXY -name dfsr | Set-Service -Status Stopped
    Set-Service : Cannot stop service 'DFS Replication (dfsr)' because it is dependent on other services.
    At line:1 char:51
    + get-service -ComputerName ServerXY -name dfsr | Set-Service -Status Stopped
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (System.ServiceProcess.ServiceController:ServiceController) [Set-Servi
    ce], ServiceCommandException
    + FullyQualifiedErrorId : ServiceIsDependentOnNoForce,Microsoft.PowerShell.Commands.SetServiceCommand
    Is there a possiblity to restart services with dependencies remote, too?
    Regards, Heyko

    Instead of Set-Service, use the Stop-Service cmdlet with the -Force parameter in order to stop services that have dependencies. If you want to restart the service, as you've mentioned, then pipe you Get-Service command to the Restart-Service cmdlet. This
    cmdlet will also take the -Force parameter, allowing services to restart even when there are dependent services.
    Update: Added info about the Restart-Service cmdlet.

  • Restart Data Services 3.2 fails

    I can not access  trace log, monitor log and error log files. Every time accessing through links I get a time out error. The Server is available and accessible. I just tried to restart the BusinessObjects Data Service - Server through the BO-DS-Servermanager. This has not worked. I can not restart the service "BusinessObjects Data Services".
    This Error occures : Error 1053: The service did not respond to the start or control request in a timely fashion"
    This happened sometime last months. When I restart the server then all is ok again.
    How can I restart the service without reboot?

    Hello,
    1. What is the version of the Microsoft .NET Framework? (Control Panel > Add/Remove Programs).
    2. What is the error message in Event Viewer (Start > Run > eventvwr.msc)?
    3. What user run this service (Start > Run > services.msc > Business Objects Data Services > Properties > Log On tab)?
    4. Is Data Execution Prevention disabled? (My Computer > Properties > Advanced > Performance > Settings > Data Execution Prevention tab)?
    Thank you,
    Viacheslav.

  • Scheduled webi reports fail, why? If I restart BO services they work again

    Hello.
    I'm having a problem with my scheduled Webi reports and I don't know what is causing it.  I have some reports scheduled to run at 8:00 am, and are supposed to be sent to a determined e-mail. Last week it worked well and the reports were sent to their destination successfuly, then this week the same reports didn't reach their destination.  I verified in the History option and all of them showed a Failed status.  I checked the detail and this is what it shows:
    Unexpected exception caught. Reason: [java.lang.NullPointerException: i_statusInfo is null.]
    If I try to reschedule these reports or any other report or a new report I get the same error.  The only way I can make the schedule option work again  for my webi reports is restarting  BusinessObjects services.
    But I guess this is not the right solution.
    What can I do? How can I determine what is causing my scheduled webi reports fail?
    What does  this java.lang.NullPointerException: i_statusInfo is null message mean?
    Is there a way I could track the service that is failing? which BO service is the service that manage the Schedule reports?
    Any help is welcome.
    Edited by: Erika Atencio on Sep 1, 2010 6:27 PM

    >
    Efstratios Karaivazoglou wrote:
    > Which version of BOBJ (incl. SP and FP) are you using?
    >
    > Regards,
    >
    > Stratos
    BusinessObjects XI 3.1 SP2
    FixPack 2.6
    Edited by: Erika Atencio on Sep 1, 2010 8:46 PM

Maybe you are looking for

  • Re-Installing iPhoto on 10.6.8

    Hi ! - Bought iPhoto on the Mac App Store a few months ago - Did a clean install of 10.6.8 today. - Tried to install newest iPhoto version. --> This failed, because the latest iPhoto needs at least 10.7.4 How do I get a working version of iPhoto for

  • Background job failing with license check error

    Hi Experts In our ERP 6.0 system ,all the background jobs are failing with license check error. Have checked the license in SLICENSE and the license is fine. There is no warning while users are loggign in ,but when any background job is runing its fa

  • Table under F4 option

    hi, After runing the report on web, when the selection screen  is displayed, instead of entering values if we click on F4 button for the characteristic, then values will be displayed in the separate window. I would like to know from where these value

  • IPhoto can't access photo library

    I recently updated iPhoto. Now it can't access my photo library. How do I fix this?

  • Installing/deploying CS4 and dynamic Folder location

    I've utilsed the admin tool to create the install and uninstall xml files for a CS$ deployment. I found that it static to be installed from a network location, could this be changed to have it pushed as a deployment of MDT or CA DISM? I would like to