Cannot Target JSM server under weblogic6.1sp2

          I just downloaded and installed weblogic6.1sp2. When I created JMS server and target
          the JMS server to the WL server node, I got the following error. Can someone help
          me:
          Here is my system info:
          Windows NT 2000 server service pack 2
          960 Mhz
          512 Mbytes of RAM
          Weblogic6.1sp2
          ------ error ----------
          weblogic.management.DistributedManagementException: Distributed Management [1
          exceptions]
               at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy22.addDeployment(Unknown Source)
               at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
               at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
               at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
               at $Proxy13.setTargets(Unknown Source)
               at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Distributed update exception
          - remote object: ose:Location=oseapp1,Name=oseapp1,Type=ServerConfig
          - remote server: weblogic.management.internal.RemoteMBeanServerImpl@7b80c9
          - actionName: addDeployment
          - params: [Ljava.lang.Object;@5c0eb
          - signature: [Ljava.lang.String;@3cb509
          Distributed update exception
          - remote object: ose:Location=oseapp1,Name=oseapp1,Type=ServerConfig
          - remote server: weblogic.management.internal.RemoteMBeanServerImpl@7b80c9
          java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
               at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
               at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
               at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
               at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
               at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
               at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
               at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
               at $Proxy62.bind(Unknown Source)
               at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
               at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
               at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
               at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
               at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
               at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy22.addDeployment(Unknown Source)
               at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
               at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
               at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
               at $Proxy13.setTargets(Unknown Source)
               at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
               <>
          --------------- nested within: ------------------
          weblogic.management.DeploymentException: - with nested exception:
          [java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
               at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
               at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
               at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
               at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
               at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
               at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
               at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
               at $Proxy62.bind(Unknown Source)
               at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
               at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
               at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
               at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
               at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
               at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy22.addDeployment(Unknown Source)
               at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
               at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
               at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
               at $Proxy13.setTargets(Unknown Source)
               at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End  server side stack trace
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:338)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy22.addDeployment(Unknown Source)
               at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
               at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
               at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
               at $Proxy13.setTargets(Unknown Source)
               at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.management.DistributedOperationUpdateException: - with nested exception:
          [weblogic.management.DeploymentException:  - with nested exception:
          [java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
               at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
               at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
               at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
               at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
               at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
               at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
               at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
               at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
               at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
               at $Proxy62.bind(Unknown Source)
               at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
               at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
               at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
               at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
               at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
               at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               --------------- nested within: ------------------
          weblogic.management.console.utils.SetException: An error occurred while updating
          Target on Proxy for ose:Name=oseapp1_jms_server,Type=JMSServer - with nested exception:
          [weblogic.management.DistributedManagementException: Distributed Management [1
          exceptions]]
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Console Release Build6.1.2.0Server Release Build6.1.2.0Server BuildWebLogic Server
          6.1 SP2 12/18/2001 11:13:46 #154529 All Server Product VersionsWebLogic Server
          6.1 SP2 12/18/2001 11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001
          11:28:02 #154529
          

Hi Khoivu,
          This is a new one. I believe this is fixed in 7.0, and I will
          post a support case to get this fixed by 6.1SP3.
          Please post your config.xml (if you can the one
          from before you make the change the one after if they are different.).
          Meanwhile, I suspect there is a name collision in JNDI, perhaps youv have a destination with
          the same JNDI name as one of the default connection factories or another JNDI
          advertised object?
          Tom
          Khoivu wrote:
          > I just downloaded and installed weblogic6.1sp2. When I created JMS server and target
          > the JMS server to the WL server node, I got the following error. Can someone help
          > me:
          >
          > Here is my system info:
          >
          > Windows NT 2000 server service pack 2
          > 960 Mhz
          > 512 Mbytes of RAM
          > Weblogic6.1sp2
          >
          > ------ error ----------
          >
          > weblogic.management.DistributedManagementException: Distributed Management [1
          > exceptions]
          > at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy22.addDeployment(Unknown Source)
          > at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
          > at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
          > at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
          > at $Proxy13.setTargets(Unknown Source)
          > at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
          > at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
          > at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
          > at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
          > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > Distributed update exception
          > - remote object: ose:Location=oseapp1,Name=oseapp1,Type=ServerConfig
          > - remote server: weblogic.management.internal.RemoteMBeanServerImpl@7b80c9
          > - actionName: addDeployment
          > - params: [Ljava.lang.Object;@5c0eb
          > - signature: [Ljava.lang.String;@3cb509
          > Distributed update exception
          > - remote object: ose:Location=oseapp1,Name=oseapp1,Type=ServerConfig
          > - remote server: weblogic.management.internal.RemoteMBeanServerImpl@7b80c9
          > java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          >
          > Start server side stack trace:
          > java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          > at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
          > at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
          > at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
          > at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
          > at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          > at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          > at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          > at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          > at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
          > at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          > at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
          > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          > at $Proxy62.bind(Unknown Source)
          > at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
          > at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
          > at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
          > at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
          > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
          > at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy22.addDeployment(Unknown Source)
          > at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
          > at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
          > at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
          > at $Proxy13.setTargets(Unknown Source)
          > at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
          > at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
          > at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
          > at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
          > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > <>
          > --------------- nested within: ------------------
          > weblogic.management.DeploymentException: - with nested exception:
          > [java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          >
          > Start server side stack trace:
          > java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          >         at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
          >         at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
          >         at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
          >         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          >         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          >         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          >         at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
          >         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          >         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          >         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
          >         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
          >         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >         at $Proxy62.bind(Unknown Source)
          >         at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
          >         at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
          >         at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
          >         at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
          >         at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
          >         at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
          >         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
          >         at java.lang.reflect.Method.invoke(Native Method)
          >         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          >         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          >         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
          >         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
          >         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
          >         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          >         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          >         at $Proxy22.addDeployment(Unknown Source)
          >         at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
          >         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
          >         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
          >         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
          >         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
          >         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
          >         at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
          >         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
          >         at $Proxy13.setTargets(Unknown Source)
          >         at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
          >         at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
          >         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
          >         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          >         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          >         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          >         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
          >         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End  server side stack trace
          > ]
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:338)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy22.addDeployment(Unknown Source)
          > at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
          > at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
          > at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
          > at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
          > at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
          > at $Proxy13.setTargets(Unknown Source)
          > at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
          > at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
          > at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
          > at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
          > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > --------------- nested within: ------------------
          > weblogic.management.DistributedOperationUpdateException: - with nested exception:
          > [weblogic.management.DeploymentException:  - with nested exception:
          > [java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          >
          > Start server side stack trace:
          > java.lang.ClassCastException: weblogic.rmi.cluster.ClusterableRemoteObject
          >         at weblogic.jms.common.DestinationImpl.equals(DestinationImpl.java:343)
          >         at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:315)
          >         at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:104)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:278)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:285)
          >         at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
          >         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          >         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          >         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          >         at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
          >         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          >         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          >         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
          >         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
          >         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >         at $Proxy62.bind(Unknown Source)
          >         at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
          >         at weblogic.jms.common.JMSUtilities.bindAsSU(JMSUtilities.java:171)
          >         at weblogic.jms.backend.BEDestination.start(BEDestination.java:625)
          >         at weblogic.jms.backend.BackEnd.start(BackEnd.java:492)
          >         at weblogic.jms.JMSService.addJMSServer(JMSService.java:1278)
          >         at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
          >         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
          >         at java.lang.reflect.Method.invoke(Native Method)
          >         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          >         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          >         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
          >         --------------- nested within: ------------------
          > weblogic.management.console.utils.SetException: An error occurred while updating
          > Target on Proxy for ose:Name=oseapp1_jms_server,Type=JMSServer - with nested exception:
          > [weblogic.management.DistributedManagementException: Distributed Management [1
          > exceptions]]
          > at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
          > at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
          > at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
          > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          > --------------------------------------------------------------------------------
          >
          > Console Release Build6.1.2.0Server Release Build6.1.2.0Server BuildWebLogic Server
          > 6.1 SP2 12/18/2001 11:13:46 #154529 All Server Product VersionsWebLogic Server
          > 6.1 SP2 12/18/2001 11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001
          > 11:28:02 #154529
          

Similar Messages

  • Why I always encounter SocketException in weblogic6.1sp2?

    when I use weblogic6.1sp2 to develop my j2ee B/S program,I find the weblogic server
    alway throw follow exception,
    java.net.SocketException: ReadFile failed: &#25351;&#23450;&#30340;&#32593;&#32476;&#21517;&#19981;&#20877;&#21487;&#29992;&#12290;
    (error 64, fd 2348)
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
    at weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java:410)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP
    .java:222)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImp
    l.java:992)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2209)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    but the result is browser is right.Is my program has some bug or may be the config
    of the weblogic server is wrong?

    Hello kmschmehl-
    I cannot truly express how sorry I am to hear about your total experience with the delivery and subsequent return of this fridge.  It certainly sounds as though Best Buy has put you through the ringer and I can absolutely understand your disappointment and anger with us.
    While it sounds like some aspects of the purchase and delivery were at least adequate, any opportunity that we had to show you why you should purchase from Best Buy went by the wayside.  However, Best Buy is not in the business to provide merely adequate experiences and I am saddened that this is the best we could summon for your purchase.  We are capable of better than what we showed you.
    I’m glad to hear that you have finally been able to get the assistance you needed to get this refund resolved and make you whole again.  In addition, I do hope that you are enjoying the fridge you purchased at Lowe’s.  I certainly wish that it had been a Best Buy fridge in your kitchen instead, but I can understand why you chose to go with another retailer.
    It sounds like the store has you in good hands once your card arrives and I believe that the reason they need the physical card is that the credit card company requires it to be physically scanned for returns.  Hopefully you will not run into any further issues with this refund and it’s my hope that sometime in the future, you might grant us another chance at your business.  I will be sending you a Private Message with some additional details as well.  To check your Private Messages, please log into the forum and click on the envelope in the upper right hand corner.
    Please let us know if you run into any further concerns.
    Sincerely,
    Bill|Senior Social Media Specialist | Best Buy® Corporate
     Private Message

  • External Data Refresh Failed. We cannot locate a server to load the workbook Data Model. ThisWorkBookDataModel

    Hi All,
    I have been trying to fix this for days now. I have tried solutions in many articles but to no avail. So while the error message is something you may have seen may times, I just can't find a solution in my case.
    This is the error:
    And in text just in case the image isn't viewable:
    "External Data Refresh Failed. We cannot locate a server to load the workbook Data Model. We were unable to refresh one or more data connections in this workbook. The following connections failed to refresh: ThisWorkBookDataModel."
    What is worse is I have checked the ULS (SharePoint Trace Logs), the Event Viewer Logs and the OWA Logs and I cannot find a specific error that would help pin point the problem.
    Excel Workbook
    So what am I doing? I have an Excel 2013 workbook and I create an "SQL Server" connection to the AdventureWorksDW database, add a pivot table and a pivot chart, test in in Excel and all works fine.
    I save the Excel workbook to SharePoint 2013 and then select "Data" then "Refresh All Connections" and then I get the error in the picture above.
    Even more puzzling is I have another Excel workbook that also has pivot tables and pivot charts in the AdventureWorksDW2012Multidimensional cube database in "SQL Analysis Services" and this works fine. Hmmm.
    My Environment
    My environment is Windows 2008 R2 Server, SharePoint 2013 with the April Service Pack1 and a separate server with OWA2013 SP1. It has an SQL Server 2008 R2 database which has been upgraded to SQL Server 2012.
    Data Model Settings
    In Excel Services this is set to my server name which is "server-name". As I do not have instances all I can enter is the server name. As this works everywhere else including the workbook outside of SharePoint I do not think this is the problem.
    But I could be wrong.
    Unattended Account
    I have set this up for the PowerPivot Services App and Excel Services App.
    ODC Connections in Excel
    I have tried all 3 authentication modes, Windows, Secure Store ID and "None" which is the unattended account. I have not tried the other connection types, should I?
    Not in WOPI
    I am not in WOPI mode.
    AD Accounts
    I have added permissions in the SharePoint Services and SQL Server, and as they work in Excel outside of SharePoint, I do not think it is a permissions issue. I could be wrong of course, but the problem is in one of SharePoint, OWA, AD,
    SQL Server, Excel, and Windows Server.
    Isolate the Error
    Below is a list of errors I think are relevant but they do not tell me much. The SharePoint logs are not really giving me an error that tells me what to do and where to do it, or even why it cannot refresh, (perhaps not noticeable by the untrained eye).
    Problem with SQL Server Not Analysis Services
    So my cube database in analysis services works fine in SharePoint/OWA but not the databases in sql server. This is my best clue but I have no idea what it means. Why would it work with an Analysis Services connection but not an "SQL Server" connection?
    It Works Outside of SharePoint
    If I run the excel worksheet outside of SharePoint all works fine. When inside OWA this is where the refresh error occurs.
    Errors from Event Viewer on SharePoint Server using ULS Viewer
    "Failed to create an external connection or execute a query. Provider message: There are no servers available or actively being initialized., ConnectionName: , Workbook:"
    "Refresh failed for 'ThisWorkbookDataModel' in the workbook 'http://server...'. [Session: 1.V22.26itT0lx8piNFeqtuGVhN214.5.en-US5.en-US36.98c0e158-9113-46e9-850e-edda81d9ed1c1.A1.N User: 0#.w|ad\testuser1]"
    And an error in the ULS under the "Data Model" category:
    "--> Check Deployment Mode (server-name): Fail (Expected: SharePoint, Actual: Multidimensional)."
    This last error, as it turned out, defined the problem concisely, although I was yet to work out what it meant in some detail.

    I finally solved this myself (or should I say with the help of several key articles).
    The refresh did not work because the database was not in "SharePoint Mode". Yes, SQL Server has modes, 3 of them in fact.
    If you installed SharePoint to the default SQL instance which would be called <servername> then you cannot use this default instance for Excel 2013 workbooks in OWA 2013 because the refresh only works if the database is in SharePoint mode.
    So what are these 3 modes? The Deployment Mode property in the msmdsrv.ini file has them as:
    0 = Multidimensional mode (the default whenever you install SQL Server normally)
    1 = PowerPivot for SharePoint mode
    2 = Tabular mode mode
    How do you know what mode you are in? That's easy, open SQL Studio Manager and connect to all your SQL database engine instances (ignore Analysis Services or SSRS as they are not database engines). If you only have the default instance then that is almost
    definately in Multidimensional mode which is the default and what SharePoint installs its databases to.
    You must have an instance called <servername>\POWERPIVOT. This instance is the "sharepoint mode" needed, and the default instance name when you install an SQL instance in this mode.
    If you don't see <servername>\POWERPIVOT in SQL server then you are not in "sharepoint mode". It is more accurate to say, you do not have an instance that is in sharepoint mode. This is because you cannot simply switch modes on an SQL server.
    You have to install a new instance in the required mode, thats the only way.
    That's easy enough. Load up the SQL Server setup CD and run setup. Install a brand new instance and select "SQL Server PowerPivot for SharePoint" when you get there in the wizard.
    Now you will have the default instance that stores all the SharePoint databases and that is in mode 0, and a new instance called <servername>\POWERPIVOT that is in mode 1. The "<servername>\POWERPIVOT" instance connection is what you
    will use for Excel 2013 when rendering in OWA 2013.
    You also need to ensure OWA 2013 is not in WOPI mode for Excel worksheets. See the last link below for more information about WOPI.
    Next you should go to the Excel Service App in CA and click Data Model Settings and add the <servername>\POWERPIVOT instance.
    Then you have to either turn off the firewall on the SQL server machine, or create an inbound rule on the Windows firewall to open the TCP port for the <servername>\POWERPIVOT instance:
    1. Start Task Manager and then click Services to get the PID of the MSOLAP$InstanceName.
    2. Run netstat –ao –p TCP from the command line to view the TCP port information for that PID.
    Finally, you can now create Excel 2013 workbooks that run in OWA without refresh errors, as long as you are connecting to the <servername>\POWERPIVOT instance. Hooray.
    REFERENCES
    Look for the string "There are no servers available or actively being initialized" in this article:
    http://blogs.msdn.com/b/analysisservices/archive/2012/08/02/verifying-the-excel-services-configuration-for-powerpivot-in-sharepoint-2013.aspx
    Determine the server mode:
    http://msdn.microsoft.com/en-au/library/gg471594(v=sql.110).aspx
    Install the SharePoint PowerPivot instance (aka SharePoint mode)
    http://msdn.microsoft.com/en-au/library/eec38696-5e26-46fa-bc83-aa776f470ce8(v=sql.110)
    Open the port for the new SQL instance:
    http://msdn.microsoft.com/en-us/library/ms174937(v=sql.110).aspx
    Turn Off WOPI for Excel OWA
    http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/01/31/powerpivot-for-sharepoint-browser-refresh-fails-data-refresh-not-supported-in-office-web-apps.aspx

  • "Cannot connect to server" error when setting up MAMP local server in Dreamweaver cc 2014

    I am trying to set up my Wordpress 4.1 site with MAMP 3.0.7.3 in Dreamweaver cc 2014, but I am getting a "Cannot connect to server" error when trying to view the site live. The site works fine on the localhost:8888. I am using OS X Yosemite and PHP 5.6.2. Below are screenshots of my Dreamweaver settings. Thanks in advance.

    Hi Subhadeep!
    Think I'm getting closer (Lol). I did as you suggested and changed the web url to http://localhost:8888/Documents/projects/whoknew/. As you suggested I moved the local site to the Documents folder under the sub-folder projects. It is connecting to the server, but now I am getting the requested url cannot be found on the server. Below are screenshots of my current settings.
    http://localhost:8888/Documents/projects/whoknew/. As you suggested I moved the local site to the Documents folder under the sub-folder projects. It is connecting to the server, but now I am getting the requested url cannot be found on the server. Below are screenshots of my current settings. Thank you!

  • No Integration Server under Adapter Engine at Communication Channel

    Hello all,
    This is new PI7.0 install.
    I configured a file Adapter communication channel for an Integration Scenario.
    At field "Adapter Engine" under Parameters tap I am not able to select the Integration Server.
    Pull down menu is empty.
    I did sxmb_adm and blog 6077 that got "Integration Server" in file adapter. Later to that file to file scenario worked yesterday. However after java+abap stack complete restart (to cleanup unwanted manually created business system of type WEB AS ABAP) the problem came back today.
    I repeated again same blog /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory   sxmb_adm, sldcheck, rz70 all looks good, but no luck.
    There is a note from forum to change the content maintenance under
    SLD->Administration->Content Maintenance->Subset (Landscape description)...
    Need some pointers on what to change & get the file adapter to work? Thanks.
    Another observation is all adapters got empty menu (no Integration Server). However IDOC, HTTP got integration server populated.
    ====================
    Re: No Integration Server under Adapter Engine at Communication Channel config  
    Posted: Sep 12, 2007 4:46 PM    in response to: Jochen Schertel      
    Hi All,
    the problem was related to missing some Associations under Contend Maintenance for the Integration Server.
    After implementing again, the problem was solved!
    Regards,
    Jochen
    ====================

    Hi Jochen,
    Can you please check following parameters in sxmb_adm on your application server.
    Goto TC : sxmb_adm...select Integration Engine configuration n check whether you have maintained global configuration data as
    Role of Business System  : Application system
    and Corresponding Integ. Server : http://xi hostname:port/sap/xi/engine?type=entry
    Also check if you have created following RFC destinations:
    1. INTEGRATION_DIRECTORY_HMI(H)
    2.LCRSAPRFC (TCP/IP)
    3.SAPSLDAPI
    Nilesh
    Nilesh

  • TS1398 iTunes , cannot connect to server. At both, my fathers and at my place, with both, his iPad1 and my iPad 3

    Started out with "Text Plus" triple charging me. Gave up on them.  iTunes sent me an email with the receipt of all 3 charges with "report a problem"  under each purchase. I clicked on it and that's when I had on my screen "cannot connect to server". This happens with both my iPodtouch 4 th gen. &amp; my new iPad3 , both are WiFi. This also happens at my place and my fathers, with my products and the iPad 1 WiFi I gave to him. I can get on my iTunes but can't buy anything. I can sync . Please someone help, Sue

    I just now did what you said and now it says; iTunes, cannot connect to iTunes store.
    Very puzzling indeed, I contacted iTunes the other day and Derrick told me to go to Apple , I did and they said their support community has dealt with this problem before and now I am here. I think I am going to sync my iPad with iTunes for the 8th time and see if that does anything, it's been about 24 hrs. Since I did it last. Thank you for your help,Sue

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Safari Cannot Connect with Server (mountain lion) on wifi

    I Posted this under Mountain Lion as Safari had no connectivity issues for me when I got my mbp and it had lion installed and ran beautifully-
    NOW my apple (s) run fine on mountain lion
    for a little bit,
    and then I get "Safari Cannot Connect to Server"
    Now during this frequent occurance the  APP store hangs and hangs as well.
    This is most annoying-
    The only way to use my apple products after this happens is to restart them
    and then they work until they go into sleep mode,
    sometimes they screw up before that and then
    "Safari Cannot Connect to Server"
    my Airport utility shows that it is scanning for  networks-
    When I was right in the middle of buying something from amazon-- I had to go to my decrepit old windows xp connected up only for cox email to complete the transaction-
    This is not acceptable. Since it occurs on both of my apple computers and only started when I installed mountain lion.
    This has continually gotten worse to the point I must restart my laptop continually-
    Apple better get the lead out of their butts and fix this glaring fault- or should I install another web browser?
    which I am disinclined to do-
    I spent a fortune on these apple products and I expect them to work properly- I went to apple because I was so sick of microsoft and its endless headaches and updates and freezes lol--
    kind of funny if you think about it.

    Hi BSU1960, 
    I found the solution to my problem on a different forum.  Turns out for some reason the anti-virus software that I run was interferring with my browsers' connecting to the internet.  Once I disabled the web protion of the anti-virus my problem went away.
    I have a question to Kaspersky Security, hopefully will find out what was the root cause.

  • Cannot Connect to Server OSX 10.8

    Please be patient, I am new to server administration.
    I had set up a Mac Mini (mid 2011) running lion and lion server as a home server for Time Capsule, file sharing, and itunes home sharing.  Everything worked fine In April.
    It seems a system update knocked the server off and I could not connect to it.  (ARD or VNC).  I checked forums and tried a bunch of things, but could not get it working.  Hoped Mountain Lion would fix it, but it did not help.
    Cannot connect to server through VNC or ARD.  (Can connect from server to laptop, but not laptop to server).  Cannot connect to server through Finder (afp://with ip address) or just connecting to shared file location on the Finder.  All things I had been able to do.
    Time Machine on my laptop cannot see the Time Capsule set on my server.
    Currently running Mountain Lion with OSX Server 10.8.  File sharing turned on in server settings and also in the sharing settings under my preferences.  Remote management turned under sharing settings also.

    So I verified the computer firewall was turned off.  Then I turned off the server firewall settings through the command line, restarted the computer, and the server was available to control under ARD and VNC.
    I am going to update my data files, then make a bootable copy.
    Thank you for reminding me to doublecheck the firewall. 

  • Cannot connect to server in Icloud

    i had changed my email for my apple ID and I did not change it in icloud.... I cannot remember my password to my first apple ID  on the icloud account. I need to know how to change my icloud info on my Ipad. It keeps telling me to review the terms and when I try it says cannot connect to server. I have tried to delete the Icloud account so I can add my new one but I need to know my password to old apple ID. I have tried to get them to email me to change the password but I am not getting any emails to do this. please someone help me
    thank you

    Steve,
    If the mail was moved to a mailbox under "On My Mac", it should no longer have any connection to the original mailbox. Deleting (delinking) the IMAP email account from Mac Mail should have no effect on that message.
    In fact, I just confirmed that by adding an IMAP email account of mine to this Mac (which had not used it before), sending it a message from my phone, moving the message to an "On My Mac" mailbox, and deleting the account from Mac Mail. The moved message remains in the "On My Mac" mailbox. Re-adding the IMAP account to Mail makes the server mailboxes available again.
    Note that the situation would be different for an account accessed through POP, depending on mail retention settings. Any mail which had been downloaded to your Mac, deleted from the server immediately of after a period of time, but left in Mac Mail's Inbox for that POP account, would truly be lost if you delete the POP account from your Mac. This may be the situation of which you were warned.

  • JMS Server targeted to Server cluster

    Hi , Can JMS Server be targeted to Server Cluster? Are there any
              architectural best practices for this?

    Thanks Tom.
              <Tom Barnes> wrote in message news:[email protected]...
              There's no underlying machinery (code) that supports targeting a JMS server
              to a cluster.
              The targeting problem can actually get fairly involved - for a variety of
              reasons, I tend to recommend the following cookie cutter approach.
              This is a cut-and-paste from my notes:
              (1) Create a custom WL store on each server, and target it to a migratable
              target (most of the time you can use the default migratable target that each
              server provides).
              (2) Target the JMS servers to a migratable target each, the same MT as the
              store (don't worry, the JMS server won't wander to a different server
              unless you configure the MT to allow this!)
              (3) Target jms configuration system modules to the cluster (that's it! - not
              to anything else)
              (4) Create one subdeployment per module (and only one), populate the
              subdeployment only with JMS servers from step (2) above.
              (5) When targeting destinations always use advanced targeting to target
              destinations to the subdeployment from above - not the 'default target'.
              If you have both non-distributed and distributed destinations, use two
              different JMS modules. (The idea is to keep things simple to understand -
              each module should yield the same targeting solution for all of its
              component resources. Default targetting can be problematic - it is far too
              easy for destination members to end up on JMS servers that you don't want
              them on.).
              (6) When targeting a CF you have two options (A) use advanced targeting to
              target it to the subdeployment (for access by applications that are remote
              to the cluster) or (B) don't target it all (this will cause it to use the
              module target, which if you recall, we just set to the cluster, (for access
              by applications that run on a server within the cluster). The choice
              actually depends on how you plan to use the CF - use (B) for apps running on
              servers within the cluster, and (A) for apps running remote to the cluster.
              See the otherwise-largely-outdated JMS Performance Guide for the reasoning.
              It may be that you don't have to use migratable targets, as you may not have
              a use for "migration" at the moment - but it'll help in the future if you
              ever plan to use the migration features.
              Tom

  • IPhone 5 won't let me set up yahoo mail it just says cannot connect to server

    I've just set up my mother in laws new iPhone 5 and everything was fine until I tried to set up yahoo mail, i just got a message saying cannot connect to server, any ideas how to fix?
    Also has signal issues compared to 4s.
    Thanks
    Zoomer.

    When you set it up, under settings, Add Account but don't select "yahoo!" select "Other" instead and then set it up...
    Incoming Server - imap.mail.yahoo.com
    Outgoing Server - smtp.mail.yahoo.com
    Incoming Port - 993 (requires SSL)
    Outgoing Port - 465 (requires SSL/TLS)
    Username: full email address (example: [email protected])
    Password: the password you login to Yahoo with.

  • Can't connect to vista pc anymore/ cannot connect to server because

    I'm getting an error saying it cannot connect to server because username or password is not correct. Everything was fine on my old belkin router but i've had this issue since changing over to the new airpotr extreme.
    My windows vista pc has sharing on (for the folders i need) I even shut my firewall down etc but the pc still doesn't show up in my networks. I tried my laptop and that worked no problem but its a power book not windows.
    any suggestions out there? thanks

    Hello,
    Try this:
    1. Make sure you have installed the AirPort software on your Vista PC
    2. Reboot the PC
    3. On the AEBS(n), under Disks --> File Sharing, set Guest Access: Read and Write
    4, On Vista PC, select "Guest Access" in the AirPort Utility
    5. AirPort Disk should show up in "My Computer" as z/AirPortDiskName
    At least that's how mine is et up, and it works fine for Vista.

  • 0n hp m276nw error printer cannot connect the server

    i am trying to set up scan to email every time i go through the proses at the end i get this message on hp m276nw error (printer cannot connect the server) i put the out going email in then i put in the printer port and server number in when i do the test it says  error printer cannot connect the server any help will be well come

    Hello youssi,
    Welcome to the HP Forums!
    I understand when you scan to email you're receiving a message stating cannot connect to server. I will do my best to assist you! Please follow this entire HP document on How to Scan: From the Control Panel (Including Scan to Email, to a PDF, and to a Network Folder) just to make sure everything is correct.
    If this doesn't work, then please follow these steps to try setting an alternative DNS to see if that resolves the issue:
    •    Open the Embedded Web Sever on your computer.
    •    Click the Network tab.
    •    Under Wireless click on IPv4.
    •    Under DNS Address Configuration select Manual.
    •    Set the Preferred address as 8.8.8.8
    •    Set the Alternate address as 8.8.4.4
    •    Click Apply twice to confirm the change.
    •    Turn the printer Off and back On and see if the issue is resolved.
    Please post your results, as I will be looking forward to hearing from you. Have a great night!
    I worked on behalf of HP.

  • TS1398 every so often i lose wi fi internet, even though laptops in house still get wi fi signal. phone message says cannot connect to server.

    lose wi fi signal at home, message says cannot connect with server. can access wi fi with laptops
    but not with iphone5

    Your problem is completely different from the subject of this thread, which is about intermittent connections to ONE WiFi network, not all networks. As you have an iPhone 5 just take it to an Apple store and they will replace it under warranty if they can't resolve the problem.

Maybe you are looking for