Geeting State of Managed SOA as "FAILED_NOT_RESTARTABLE" in console

For two of SOA instance got error as ::"FAILED_NOT_RESTARTABLE" in console..including few extacts from logs pls check..thnx in advance.
<Feb 20, 2013 3:39:11 AM GMT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Feb 20, 2013 3:39:13 AM GMT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PeopleQueryMDB is unable to connect to the JMS destination: jms/bpm/PeopleQueryTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server WLS_SOA1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:WLS_SOA1'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:WLS_SOA1'>
<Feb 20, 2013 3:39:13 AM GMT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BAMActionMDB is unable to connect to the JMS destination: jms/bpm/MeasurementTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server WLS_SOA1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:WLS_SOA1'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:WLS_SOA1'>
<Feb 20, 2013 3:39:13 AM GMT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: CubeActionMDB is unable to connect to the JMS destination: jms/bpm/MeasurementTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.jms.common.JMSException: could not find Server WLS_SOA1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server WLS_SOA1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:WLS_SOA1'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:WLS_SOA1'>

Hi PK,
Maybe your WebLogic or SOA managed servers are not shutdown cleanly.
1. Stop all managers / weblogic server.
2. Go to soa domain home
3. Run the following commands:
find . -name "*.lok" -print -exec rm {} \;
find . -name "*.DAT" -print -exec rm {} \;
4. Start weblogic/domains
(If it will not work try to restart your machine)
Arik

Similar Messages

Composites in "Unknown" state after managed soa server restart

Hi,
I am using SOA suite 11.1.1.6 version on 64 bit OEL Linux. I am getting following error in managed server output log files:
Feb 20, 2013 5:59:32 AM IST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl does not exist.
Though this composites gets loaded, the composites dependent on this composite goes into "Unknown" state. Other composites are properly loaded on server restart.
Please let us know if anybody has any solution to this problem.

Hi,
Thanks for your help.
we have narrowed down to problem now.
The actual problem occurs while redeploying same composite on same revision.
E.g 3 composites A, B and C are deployed on and in "Up" state.
B And C composites depends on A.
B composite composite.xml has following entry
<import namespace="http://xmlns.oracle.com/A"
location="oramds:/deployed-composites/Enterprise/A_rev1.0/A.wsdl"
importType="wsdl"/>
same entry exist for C composite.xml as well.
Now whenever composite A is redeployed with same revision (1.0 in our case), and managed servers are restarted, B and C composites goes in to "Unknown" state.
Moving A.wsdl to /apps/wsdl/* in MDS works but it duplicates the A.wsdl file beacause it also exists in MDS @ /deployed-composites/Enterprise/A_rev1.0/A.wsdl
Please let us know if anyone has any solution.
Thanks,
Rupesh.

Managed SOA Server not started in cluster environment.

Hi,
I am trying to make a SOA cluster environment on Linux based machines. After doing domain configuration which also involved packing of domain on machine 1 and unpacking on machine2, I tried to start the servers. I'm able to start AdminServer successfully and also the managed soa server on the same machine. When I'm trying to start managed soa server on other machine, I'm getting the following error..
*<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
java.io.IOException>
My machine IP is XXX.XX.XXX.41 for Admin and XXX.XX.XXX.42 for Machine2. I guess the IP 192.168.122.1 is being used for cluster connection by Machine2 to make connection to Machine1. the managed soa server is getting started after the chain of error logs but it is not starting as a part of the entire cluster and comes as shutdown in WLS Console.
I'm using Linux 5 Update 7 OS and SOA 11.1.1.5.0. Any help will be appreciated for resolving this issue.
Please find the logs below.
*<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
java.io.IOException
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
*Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:*
*     java.net.ConnectException: Connection refused; No available router to destination]*
*     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
Caused By: java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:
*     java.net.ConnectException: Connection refused; No available router to destination*
*     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)*
*     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
*     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
*     java.net.ConnectException: Connection refused; No available router to destination*
*     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)*
*     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)*
*     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)*
*     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)*
*     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)*
*     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)*
*     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
*     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
*>*
Cheers,
Varun

hi,
I was able to resolve this issue. I haven't given Listen IP address for Admin Server as I have selected All Local Addresses during domain creation. As per some blog this allows Managed Server on remote machine to use any of the Address to speak to Admin Server. In this case it is using 192.168.122.1 rather than so called IP Address.
Simple fix will be giving DNS Name of Machine or IP Address.
Cheers,
Varun

How to enable Active-State Power Management (ASPM)?

If I'm running the 'powercfg -energy' command in Windows 7 it reports that ASPM has been disabled. It is a long known issue as it has been reported in previous topics around the internet. And it has been reported that enabling it could save 1-2 Watts. The old topics have been reporting how to enable it with the help of a Linux/Win7 dualboot installation.
I have been trying, but unfortunately most links in those articles are dead (topics are several years old). Is there an update on the issue, or a still functioning guide? I would love to get an hour extra juice.
old topics:
PCI Express Active-State Power Management (ASPM) has been disabled ..
Enable ASPM in T61 running Windows for saving ~2W of power consumption
X200s 7470CR9

Actually after a full day on the issue, reading thoroughly Enable ASPM in T61 running Windows for saving ~2W of power consumption and ASPM on Linux I somewhat succeeded:
-I could enable ASPM for my Intel AGN 5300
-But my audio card doesn't support ASPM at all
So the result is that powercfg -energy is still reporting ASPM error and HWinfo reporting all PCIe devices as ASPM L1 but the sound card as unable to do ASPM. So unless someone has an idea how to put the Conexant 20561 into ASPM, I'm afraid that I am not much further than I started with...
X200s 7470CR9

Impossible to start UCM managed server with the WLS console

Hi,
I cannot start the UCM managed server with the WLS console. The node manager is running by startNodeManager.cmd. The admin server by startWebLogic.cmd.
When I start the UCM server with the console WLS (Environment, Servers, Control tab and Start on the checked server), it seems to be running (the state is RUNNING) but when I open the url on the the web server UCM there is a 404 error
In the log, there are many java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup, oracle.security.jps.wls.JpsWlsStartupClass, oracle.core.ojdl.weblogic.ODLConfiguration, oracle.jrf.AppContextStartup, oracle.as.jmx.framework.wls.spi.StartupListener, oracle.ias.cache.Startup, oracle.dms.wls.DMSStartup ...
If I start UCM directly by startManagedWebLogic.cmd and not with the WLS console, everything is OK. No error in the log and UCM server is working well
Any idea ?
Thanks
Hugues

Great!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards,

Error while starting the AqAdapter in SOA Suite 11g Admin Console

facing an issue with the AqAdapter(Resource Adapter) in Soa Suite 11g Admin Console.
we go to Deployments --> Select Aq Adapter --> Currently it shows the status as Prepared
Now we try to Start it again --> it comes back with the error message mentioned below
weblogic.application.ModuleException: weblogic.connector.exception.RAException:
Jndi Name is null or empty. Errors were encountered while performing this operation.
source path on the admin server is mentioned here for this AqAdapter:
/opt101/app/oracle/SOAD/SOA11gR1/fmw/Oracle_SOA1/soa/connectors/AqAdapter.rar
deployment plan :
/opt101/app/oracle/SOAD/SOA11gR1/fmw/Oracle_SOA1/soa/connectors/was/Plan. xml
We check in the Configuration tab --> Outbound Connection Pools -->
here it shows the Group as javax.resource.cci.ConnectionFactory and under it we have setup
2 connection pool instances with JNDI names as : eis/AQ/aqSample & eis/aq/B2BAQ
Could someone please help here as to what could be the reason why this error is coming and
how we could resolve this.
With Regards & thanks

This is what we have done :
1.Created the JDBC data source & connection pool as below :
data source name : B2BAQ , JNDI name : jdbc/B2BAQ
Connection Pool :
URL : taken from the tns entries of the instance
Driver Class Name : oracle.jdbc.OracleDriver
Tested this connection ..it works fine from the Admin Console
2.Then go to Deployments --> AqAdapter -> Configuration tab --> Outbound Connection Pool Group -->
Create a new connection pool instance -- General tab
connection interface factory : javax.resource.cci.ConnectionFactory
JNDI Name : eis/AQ/B2BAQ
Then in Properties tab : Enter the Data Source Name : jdbc/B2BAQ
Then we try to Start the AqAdapter from the Admin Console..it goes into Prepared status.
The error message which comes is mentioned above.
Is there any way we could resolve this ..that would be very helpful
Regards
Edited by: user5149250 on Mar 13, 2012 6:33 AM

Error showing while adding a management pack to 2007R2 authoring console

Hi Every one,
While trying to add an unsealed management pack to 2007 authoring console we are getting error
XSD Verification failed for management pack[line: 1, "color:#222222;font-family:arial,sans-serif;font-size:13px;line-height:normal;">
system.xml.schema.xmlschemavalidationException:The schemaversion atribute is not declared
any help will be thank full
Regards,
Nikhil

The Authoring Console has not been updated and does not understand the OpsMgr 2007R2 MP Schema version. It can still be used to produce MP that will work on OpsMgr 2007 R2, but you need to reference the old versions of the libraries.
You can check this link , it will help you in your issue
http://blogs.inframon.com/post/2012/06/12/Choosing-the-correct-Management-Pack-Solution-with-Visual-Studio-Authoring-Extensions.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Managed soa server doesn't start

Hi,
I have a Problem starting soa server.
I have successfully installed SOA 11.1.1.5 on my Windows 7 on 64 bit machine.
Admin server starts without a problem, but when I start Soa server, It asks for username. Here I enter weblogic and the following error shows:
<BEA-090783><Server is running in production mode and the Native Library(Terminalio) to read the password securely is not found.>

Hi,
To implement the solution execute the following steps:
There are two workarounds to this problem:
Either (Linux and Windows):
1. Navigate to $MIDDLEWARE_HOME/user_projects/domains/<domain_name>/servers/<managed_server>/security/. If the /security folder does not exist then create it. Then create a boot.properties file in the /security folder that contains:
username=weblogic
password=<password>
2. Then run startManagedWeblogic.sh and it will not ask for the username/password on startup
OR (Linux only):
1. Edit the /user_projects/domains/<DOMAIN_NAME>/bin/setDomainEnv.sh and change:
<MIDDLEWARE_HOME>/wlserver_10.3/server/native/linux/i686
to:
<MIDDLEWARE_HOME>/wlserver_10.3/server/native/linux/x86_64
OR:
1.Run the startManagedWebLogic.sh script with:
startManagedWebLogic.sh <managed_server> -Dweblogic.management.allowPasswordEcho=true.
Regards,
Kal

11g OEPE with managed SOA domains

Is there any way OEPE 11.1.1.2 can be configured with a WebLogic 11g R1 managed domain such as a SOA domain? When I try to add the server I get the following error, pointing to the 11g SOA managed domain.
+'The server is invalid. Error occurred reading server credential. If the domain was recreated, the server instance in Eclipse must also be recreated. Required classpath for credential detection is missing. Detection is disabled.'+
It has been suggested that OEPE does not support managed domains Eclipse oepe error when creating weblogic 10.3 server Is this the case?
If so are there any plans to update OEPE to support managed domains so that components written within Eclipse can be deployed into SOA environments. This is possible within JDeveloper and would be beneficial to the Oracle community using OEPE.
Regards
Neil

Hi Neil,
Could you provide some additional information on the issue you noticed.
Are you running OEPE on Eclipse 3.4 or Eclipse 3.5 ?
You had mentioned an old JDK being picked up. could you provide the specific JDK version which Eclipse was using ?
Regarding your question related to managed server. While deployment and iterative development against a local manager server is unsupported, the user can deploy applications to a remote managed server or remote cluster.
Do let us know if you have any other questions.
cheers
Raj

WF-Workflows in permanent warning state (SCOM Management Pack)

Hi,
We're starting to monitor a small Service Manager 2012 R2 installation with SCOM 2012 R2.
After all discoveries have ran we have a permanent Warning on the Management Server, this warnign relates to the WF Workflows
The Repeats above are from my resetting the health the monitor. If I leave this alone the alert just stays Yellow/warning.
I've done some research into this but have now hit a brick wall and would like some help.
All workflows in the Service manager Workflows/Status pane are in good health.
Investigating further
I found this SQL script to list failed workflows.
SELECT
Rules.RuleName,
Rules.Comment,
Rules.RuleCategory,
Rules.RuleEnabled,
[JobStatusView].Status,
[JobStatusView].TimeScheduled,
[JobStatusView].TimeStarted,
[JobStatusView].TimeFinished,
[JobStatusView].Output,
[JobStatusView].RunningAs,
[JobStatusView].SubmittedBy,
dbo.MySubscriptions.LastModified,
dbo.MySubscriptions.UserSID as LastModifiedBy,
GETUTCDATE() as CurrentTime
FROM dbo.WindowsWorkflowTaskJobStatus
LEFT OUTER JOIN dbo.JobStatusView ON dbo.[JobStatusView].[BatchId] = dbo.[WindowsWorkflowTaskJobStatus].[BatchId]
LEFT OUTER JOIN dbo.MySubscriptions ON dbo.[WindowsWorkflowTaskJobStatus].[RuleId] = dbo.[MySubscriptions].[RuleEntityId]
LEFT OUTER JOIN dbo.BaseManagedEntity ON dbo.WindowsWorkflowTaskJobStatus.BaseManagedEntityId = dbo.BaseManagedEntity.BaseManagedEntityId
LEFT OUTER JOIN dbo.Rules on dbo.WindowsWorkflowTaskJobStatus.RuleId = dbo.Rules.RuleId
WHERE (( dbo.[WindowsWorkflowTaskJobStatus].[Processed] IS NULL AND
( (dbo.[WindowsWorkflowTaskJobStatus].[ErrorMessage] IS NOT NULL)
OR (dbo.[JobStatusView].Status = 3)
OR ((dbo.[JobStatusView].Status = 0
OR dbo.[JobStatusView].Status = 1)
AND (DATEDIFF(MINUTE, dbo.[JobStatusView].TimeScheduled, GETUTCDATE()) >= 25) )
OR( dbo.[JobStatusView].Status = 2) OR( dbo.[JobStatusView].Status is NULL) ) ))
The output of which is
Our Exchange connector appears healthy, it's certainly processing email and no errors relating to it appear in the Operations Manager event log on the SCSM workflow/Management server.
As for MonitoringHostKeepAlive any ideas how to troubleshoot this? Again I see no errors and Service manager appears to be fully functioning.
All help gratefully recieved.

This one is bugging me too.
Am tempted to remove the Microsoft.SystemCenter.MonitoringHostKeepAlive management pack:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/592a5abd-4974-415a-9cfa-91c46c929a18/microsoftsystemcentermonitoringhostkeepalive-doesnt-start-sometimes?forum=systemcenterservicemanager

Managing SOA Deployed Composites

Hi everyone,
Should inactive SOA composites be undeployed from the server? I could not find any documentation stating that this was a best practice. I know undeploying inactive SOA composites speeds up restarting a downed server because it would have less composites to redeploy, but I am not sure of any other advantages.

Do you have any compelling reason to keep them deployed? Its always good to undeploy the unwanted composites. This would not only help in reducing the startup time as you mentioned but also result in less memory footprint at runtime because SOA caches lot of artifacts of a composite during runtime to boost the performance.
regards,
Sandeep

How do I use the Session State to manage bind variables & download xml data

I have a Report Query with more than 30 queries; many have bind variables in them. I'd like to create sample xml so that I can develop my word templates. When I try to download the XML data Source for Layout, it doesn't ask for the bind variable values.
How can I download the XML data without replacing the bind variable values in each of the queries?
Thank you.

If you are using the Standalone version, then first of all make sure to UNCHECK (BIP10g 10.1.3.4.1)
"AUTO RUN" (it is under General Settings when you select your Report Definition)
Next, you should define the parameters in the corresponding parameter Section.
Its simplest form is of "Text" type so you will have to enter values at runtime.
Then these parameters can be used in your query as bind variables.
When you run the report it will prompt for parameter values. Enter these values
and you would get a sample of your XML data.
This should work and you should not find any issues.
regards
Jorge

Service Manager Portal not displaying VM console and related details

Hi All,
We have deployed private cloud with system center products using Cloud Services Process Pack and we have deployed Service Manger portal for VM provisioning in Cloud
The Service Manger portal does not display VM console and VM details
I have following queries
How to take remote console of VM deployed by end user through service manager portal
How will user come to know quota limit utilized in cloud under his account
The VM are deployed through SCSM portal are in shutdown state how to auto start the VM after provisioning
Please help since we are not able to find any solution for the above
Appreciate if any workaround is available for the same
Thanks
Manzoor Ahmed

The component of System Center that is capable to give console access to your VMs, is App Controller.
Once the user are logged in here, they should see their quota, limits and resources available.
Yes, the VMs are powered off by default when using the CSPP. You can edit the runbooks and add a task that will start them after provisioning.
For your information:
Many things has changed since the release of Cloud Service Process Pack. A new set of tools are provided with Windows Azure Pack to have a streamlined Infrastructure as a Service offering within the enterprise. Windows Azure Pack will leverage VMM (in the
same way as SCSM does) but in conjunction with SPF (component within Orchestrator) to give you a framework that is identical to Windows Azure (Microsoft's own cloud) running on-premise.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

SOA Suite 11g Admin console EM link

I have installed SOA suite 11g onto a windows XP machine with a local loop back network adaptor. When I go to the WebLogic Server Administration Console home page the link for the Oracle Enterprise Manager is picking up the loop back network adaptors IP address (10.10.10.10). This results in the link not working when accessed over the network. I can replace the local IP address with the machine name or DHCP IP address within the browser to work round the issue. However, is there any way to correct this and re-configure the link to use the actual IP address like the other links?
Regards
Neil

Another way is to get rid of the Loopback Adapter (ie unconfigure it) and just install it. WLS has no issues with DHCP environments.
--olaf

Tomcat 4.1.12 - Manager App Configuration & Output to Console on W2K?

Hi
i just upgraded to Tomcat 4.1.12 for Tomcat 4.0.4 in w2k. Not i have to problems (worked before):
- On the new version i can't get the Manager Application running. In the documentation i rad about two ways to install the Manager Application but none of them worked (deploying the manager.xml or installing the manager app in server.xml). Unlike the old tomcat version 4.0.4 in the new version the manager dir is not under webapps but under a new dir called servler/webapps. Any Suggestions?
- Unlike in the Tomcat 4.0.4 version 4.1.12 doesn't output the System.out.println() command to console for all calls of that methode that are in init() methode of the servlet (but in the tomcat logfile the System.out.prinln commands are logged). As soon as the servlet is initialized the System.out.println() is printed to the console again. I read about that tag to redirect the System.out und System.err to the log file and i deactivated that for my servlet but this didn't help. Any suggestions?
Thanks for your help.
Josh

I can't remember what i've done excatly, i just remeber that i was wrong and the manager app doesn't have to be installed since it comes in an installed state in the tomcat distribution. Only thing i had to do is to set up a user account with manager or admin priviledge. This can be done somewhere in the conf/ dir if i remember right.

Geeting State of Managed SOA as "FAILED_NOT_RESTARTABLE" in console

Similar Messages

Maybe you are looking for