Connecting to Management Server

Oracle 8.1.7 installed on RedHat 7.0. Two databases created. Oracle Management Server installed. OEM console installed. Repository for Management Server installed in one of the databases. Problem: Can not connect to the Management Server. Database is open. Connecting with default administrator sysman/oem_temp fails. How can I see whether the Management Server process is running? What's wrong here?

First configure management server on a node using configuration assistant. then use sysman/oem_temp to connect to management server(in console. This works 100%.
Sandeep
[email protected]

Similar Messages

Not able to connect with managed server using ssl connection

Hi Guys,
My weblogic server is running on linux. I have setup ssl connction bu using Demo Identity and Demo Trust.In server logs i can find the following infomation that server is running on secure port.
But once i try connect to managed server using client i m facing below error:
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://host:port: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:767)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
     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:684)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
     at javax.naming.InitialContext.init(InitialContext.java:242)
     at javax.naming.InitialContext.<init>(InitialContext.java:216)
     at com.akt.client.WLCLIENT.makeConnection(WLCLIENT.java:40)
     at com.akt.client.WLCLIENT.main(WLCLIENT.java:60)
Caused by: java.net.ConnectException: t3s://host:port: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; 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:165)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     ... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; 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:260)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     ... 15 more
But in server logs i can see below message
opt/Oracle/Middleware/wlserver_12.1/server/lib/DemoIdentity.jks.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/Oracle/Middleware/wlserver_12.1/server/lib/DemoTrust.jks.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.7.0_21/jre/lib/security/cacerts.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on hostname:port for protocols iiops, t3s, ldaps, https.>
<May 27, 2013 2:47:06 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started the WebLogic Server Managed Server "Server-Test" for domain "base_domain" running in development mode.>
Please suggest
Edited by: 1008140 on May 27, 2013 2:37 AM

Welcome to OTN
This section related to Database question not fusion middle ware Post your question
Oracle Discussion Forums » Fusion Middleware

Management console fails connecting to Management server.

I have installed Oracle 9.2 on Red Hat Advanced Server V2.1.
Also installed Management server and client software on the system.
Started everything up: oemctl start oms, agentctl start agent, apachectl start...
Run Manager Console on Linux machine (i.e. locally)
Runs successfully - connecting stand-alone
Runs successfully - connecting to management sever
Installed client software on a Windows NT PC.
Runs successfully - connecting stand-alone
FAILS - connecting to Management server
On another NT PC, try running web interface to Management server
FAILS - Same error as when using thick client.
Failure is the same in both cases: The exception (java.lang.NullPointerException) occured.
Failure of both of these suggested a server issue...
Don't know where to find management server logs?
Looking at $ORACLE_HOME/Apache/Apache/logs/error_log seems unable to find files, e.g.:
[Mon Nov 25 10:01:46 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/readme/emreadme.htm
[Mon Nov 25 10:01:57 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/java/awt/KeyboardFocusManager.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.properties
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/vt/console/app/ConsoleBean
Info.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/sun/beans/infos/ConsoleBeanInfo.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/emSDK/client/appContainer/
WebApplicationBeanInfo.class
I have tried reinstalling Oracle website, however this made no difference.

Can you ping the server which is running OEM from the client NT machine?
Are you trying to connect using DNS or IP?
Verify that this works first.

Issue while connecting to managed server through WSLT

Hi All,
we have one Admin Server and 6 managed server.
we are successfully able to connect to Admin server which is running on port 7001 but
when we are trying to connect to any of the managed server at port 8001 we are getting below error:
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://<host>:8001
Use dumpStack() to view the full stacktrace
Please let us know how to enable WLST to connect to managed servers.
Thanks

This was a silly mistake from my side.
Actually our server hosts multiple managed server on same machines using VIP.
hence using Alias in WLST connect command solved the issue,
Thanks.

EJB3: JNDI connection problem managed server

Hi all,
In a JUnit test, I tried to look up a Session EJB from a remote managed server:
Hashtable<String, String> props = new Hashtable<String, String>();
props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
props.put(javax.naming.Context.PROVIDER_URL, "t3://server1.ux.yucom.es:1751");
props.put(javax.naming.Context.SECURITY_PRINCIPAL, "userName");
props.put(javax.naming.Context.SECURITY_CREDENTIALS, "pwd");
props.put(weblogic.jndi.WLContext.ALLOW_EXTERNAL_APP_LOOKUP, "true");
InitialContext context = new InitialContext(props);
Command command = (Command) context.lookup(jndiName);
But the code already fails while instantiating the InitialContext, because of a connection problem:
Caused by: java.net.ConnectException: t3://server1.ux.yucom.es:1751: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection timed out: connect; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
     ... 34 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection timed out: connect; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
     ... 36 more
I'm able to connect to the the Admin server... In this case I receive a javax.naming.NameNotFoundException, obviously, since the remote EJB is only targetted on the managed server and not on the admin.
This is confirmed by following little test on the command line:
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url t3://server1.ux.yucom.es:1700 -username <user> -password <pwd> PING
=> OK, packets received
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url t3://server1.ux.yucom.es:1751 -username <user> -password <pwd> PING
=> Failure:
Failed to connect to server1.ux.yucom.es:1751: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination
Does anyone has an idea why the connection to the managed server fails??
Is it a configuration problem in WebLogic?
Thx a lot!
Wim.

Hi,
Are you able to Remotely Access any Simple Web Application deployed on "server1.ux.yucom.es:1751".
Example: http://server1.ux.yucom.es:1751/TestApp/index.jsp
If NOT: Means Some where there is a problem with the Port...Just for testing Try Changin Manged Server port to Default HTTP Port (80).
If Yes: Then there are chances that Your Box is not allowing any t3-Protocol Traffic on 1751 Port. Just for Testing Enable HTTP Tunneling on this Server from Admin Console
AdminConsole --> Home-->Summary Of Servers --->ManagedServer1 ---> Protocol (Tab) ---> HTTP (SubTab) --->Enable Tunneling (Check This Check Box)    Save the changes.
And then After restarting your Server ... Try to ping your Server using:
java -cp %WL_HOME%\server\lib\weblogic.jar weblogic.Admin -url http://server1.ux.yucom.es:1751 -username <user> -password <pwd> PING
In the Above command Use HTTP protocol instead of T3. If Now u are able to Ping the Server means Your Port 1751 was not allowing any other Protocol except HTTP.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic (Middleware magic Is Here)

Gateway unable to connect to Management server

Hi,
We are currently having an issue with one of Gateway servers which is not able to connect to RMS server. We had tried re-issuing the Root certificate and the other client certificates as per http://www.definit.co.uk/2012/01/troublewithscom2007r2certificates/
But still we have the same issue. PSB the events being triggered on the G/W server.
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 6/4/2014 8:21:07 AM
Event ID: 20067
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: XXXXXX
Description:
A device at IP RMS IP:5723 attempted to connect but the certificate presented by the device was invalid. The connection from the device has been rejected. The failure code on the certificate was 0x800B010A (A certificate chain could not be built
to a trusted root authority.).
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 6/4/2014 8:21:07 AM
Event ID: 21002
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: XXXXXX
Description:
The OpsMgr Connector could not accept a connection from RMS IP:5723 because mutual authentication failed.
Jesty

Steps to solve issue:
Check for eventids (20067, 20070, 21016)
Export certificate from Local\Computer\Personal\Certificate Folder
Save as DER encoded binary X.509 (.CER) file.
Run certutil -urlfetch -verify <cert.cer> tool on cer file exported in step 2.
Search certutil output for errors, like “retrieving URL: The server name or address could not be resolved 0x80072ee7 (WIN32: 12007)”
Open Internet Explorer and copy URL that cannot be resolved. If you cannot download the *.crt file look at your proxy settings. These should be empty of correct.
Correct proxy settings.
[not sure if step 7 is really needed] Remove certificates from Local\Computer\Personal\Certificate Folder and Local\Computer\Operations Manager\Certificate folder
Import certificate again in Local\Computer\Personal\Certificate folder
You can run certutil -urlfetch -verify <cert.cer> tool again to see if there are still any errors.
Run MomCertImport <nameofcertexport>.pfx again.
Check eventlog for restart of HealthService (will be restarted after running MOMCertImport) and if everything is ok now.
Also refer below link
http://blogs.technet.com/b/stefan_stranger/archive/2009/06/21/the-failure-code-on-the-certificate-was-0x800b010a-a-certificate-chain-could-not-be-built-to-a-trusted-root-authority.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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Unable to connect to the Data Access service for this management server

Hate to raise a sleeping horse but was hoping someone might have some insight into why SCOM Report Server install is failing. I am using a domain account for SCOM 2012 R2 services in a distributive environment
with 2 management servers and 2 SQL servers…one for Ops db and one for DW db.
Install was failing on selecting the management server. Research led me to
Kevin Holman's site. I followed his doc and SPN are set per your config and can telnet to MGMT1 on 5723…firewall is off on all servers. I am a domain admin and scom.mgmt account (MSOMSdkSvc) is a local admin on the MGMT servers.
>setspn -l domain\scom.mgmt
Registered ServicePrincipalNames for CN=scom.mgmt,OU=Service Accounts,DC= domain,DC=net:
MSOMSdkSvc/SCOM-MGMT1
MSOMSdkSvc/SCOM-MGMT1.domain.net
MSOMSdkSvc/SCOM-MGMT2
MSOMSdkSvc/SCOM-MGMT2.domain.net
>setspn -l domain\scom-mgmt1
Registered ServicePrincipalNames for CN=SCOM-MGMT1,OU=SCOM,OU=INTERNAL,DC=domain,DC=net:
MSOMHSvc/SCOM-MGMT1.domain.net
TERMSRV/SCOM-MGMT1.domain.net
WSMAN/SCOM-MGMT1.domain.net
RestrictedKrbHost/SCOM-MGMT1.domain.net
HOST/SCOM-MGMT1.domain.net
MSOMHSvc/SCOM-MGMT1
TERMSRV/SCOM-MGMT1
WSMAN/SCOM-MGMT1
RestrictedKrbHost/SCOM-MGMT1
HOST/SCOM-MGMT1
>setspn -l domain\scom-mgmt2
Registered ServicePrincipalNames for CN=SCOM-MGMT2,OU=SCOM,OU=INTERNAL,DC=domain,DC=net:
MSOMHSvc/ SCOM-MGMT2.domain.net
MSOMHSvc/ SCOM-MGMT2
WSMAN/SCOM-MGMT2.domain.net
WSMAN/SCOM-MGMT2
        TERMSRV/SCOM-MGMT2.domain.net
TERMSRV/SCOM-MGMT2
RestrictedKrbHost/SCOM-MGMT2
HOST/CHH-SCOM-MGMT2
RestrictedKrbHost/CHH-SCOM-MGMT2.osi-asp.net
HOST/CHH-SCOM-MGMT2.osi-asp.net
>setspn -l domain\scom-ssrs
Registered ServicePrincipalNames for CN=SCOM-SSRS,OU=SCOM SQL,OU=SCOM,OU=CHH-INTERNAL,DC=domain,DC=net:
    WSMAN/SCOM-SSRS
WSMAN/SCOM-SSRS.domain.net
MSSQLSvc/SCOM-SSRS.domain.net
MSSQLSvc/SCOM-SSRS.domain.net:1433
    TERMSRV/SCOM-SSRS.domain.net
TERMSRV/SCOM-SSRS
RestrictedKrbHost/SCOM-SSRS
  HOST/SCOM-SSRS
RestrictedKrbHost/SCOM-SSRS.domain.net
HOST/SCOM-SSRS.domain.net
When I point to the MGMT server, I keep getting “Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are
all the same version”.
OpsMgrSetupWizard.log states…
Info:
:Could not connect to Management Server: scom-mgmt1.domain.net with exception: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or
too long.
Info:
:StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result) at System.Version..ctor(String version) at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.IsManagementServerCurrentVersion(String
managementServer) at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.CanConnectToManagementGroup(String managementServer)
When I searched on "Exception.Message: Version string portion was too short or too long" it led me to .Net strings in the reg. i deleted all refs to older versions (3.x) but still no good.
Bob

Well, I’m back to trying to get SCOM Report Server up and running. This time I decided to try the command line silent install and rely on logs to debug. But it still fails.
This is the script: SETUP /install /InstallPath:D:\Program Files\Microsoft System Center 2012 R2\Operations Manager /components:OMReporting /ManagementServer:<server>.<domain> /SRSInstance:<instance> /DataReaderUser:<domain>\<account>
/DataReaderPassword:******** /SendODRReports:0 /UseMicrosoftUpdate:0 /AcceptEndUserLicenseAgreement:1
When I run the script, I get a pop-up: “System CenterOperations Manager Setup has stopped working with the following:
Problem signature:
Problem Event Name:
CLR20r3
Problem Signature 01:
setupchainerui.exe
Problem Signature 02:
7.0.5000.0
Problem Signature 03:
522a5b85
Problem Signature 04:
mscorlib
Problem Signature 05:
4.0.0.0
Problem Signature 06:
53b4fc1e
Problem Signature 07:
e4d
Problem Signature 08:
5a
Problem Signature 09:
System.FormatException
OS Version:
6.1.7601.2.1.0.274.10
Locale ID:
1033
Additional Information 1:
4911
Additional Information 2:
49111a576c61a461b7f2900e4224563c
Additional Information 3:
a1e6
Additional Information 4:
a1e62e9c159c1d7601a31ccff83dbf94
App Event Log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-29T19:02:39.000000000Z" />
<EventRecordID>4999</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER NAME</Computer>
<Security />
</System>
- <EventData>
<Data>Application: SetupChainerUI.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception.
Exception Info: System.FormatException Stack: at Microsoft.SystemCenter.Essentials.SetupFramework.Program.Main()</Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-29T19:02:41.000000000Z" />
<EventRecordID>5000</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER NAME</Computer>
<Security />
</System>
- <EventData>
<Data>SetupChainerUI.exe</Data>
<Data>7.1.10226.0</Data>
<Data>522a5b85</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.18409</Data>
<Data>5315a05a</Data>
<Data>e0434352</Data>
<Data>000000000000940d</Data>
<Data>a64</Data>
<Data>01d03bf626a03a7a</Data>
<Data>C:\Users\USER NAME\AppData\Local\SCOM\Setup\SetupChainerUI.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>65be21be-a7e9-11e4-a4d7-005056966e1b</Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-29T19:03:27.000000000Z" />
<EventRecordID>5001</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER NAME</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>CLR20r3</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>setupchainerui.exe</Data>
<Data>7.0.5000.0</Data>
<Data>522a5b85</Data>
<Data>mscorlib</Data>
<Data>4.0.0.0</Data>
<Data>53b4fc1e</Data>
<Data>e4d</Data>
<Data>5a</Data>
<Data>System.FormatException</Data>
<Data />
<Data />
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_setupchainerui.e_9724aaa8eec4ffba07c27fea369e612e949d75_5b269652</Data>
<Data />
<Data>0</Data>
<Data>65be21be-a7e9-11e4-a4d7-005056966e1b</Data>
<Data>0</Data>
</EventData>
</Event>
OpsMgrSetupWizard.log
[13:48:16]:
Error:     :Uncaught Exception: Threw Exception.Type: System.FormatException, Exception Error Code: 0x80131537, Exception.Message: Input string was not in a correct format.
[13:48:16]:
Error:     :StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
   at Microsoft.SystemCenter.Essentials.SetupFramework.PropertyBagDictionary.GetProperty[T](String property)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.ValidateBureaucraticSwitches()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.RationalizeCommandLineArguments.ValidateSilentInstallCommandLineOptions()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.RationalizeCommandLineArguments.Rationalize()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.RationalizeGeneralInstall()
   at Microsoft.SystemCenter.Essentials.SetupFramework.Program.RationalizeInstall()
   at Microsoft.SystemCenter.Essentials.SetupFramework.Program.Main()
Any ideas? I feel like I’m just going in circles…Bob

To connect to oracle manager server

i try to connect to manager server but maybe i am with windows 2000 pro this function don't start.
when i go to de Panneau de configuration > Services. i don't find manager server so what i can do to connect to oracle manager server?
thanks for answer

If you have installed the Oracle AS 10.1.3 using an Apache in front the default port is 7777 as far as I know.
You wrote that the main page is accessible, that's why I would suspect that you might have a problem with your hostname. Are you accessing the mainpage via the full qualified hostname or via ip?
Please ensure that you can reach the server using the full qualified hostname!
If you are not sure about it, add an entry to your local hosts-file.
Please tell us if this was your problem!
Regards,
Eric

Unable to start Manager server using Node Manager

Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)

You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Starting Manage Server using node manager

Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advance

An example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped."

EM (management server) doesn't find node

i created a new database.
when i start EM(management server) and search for new nodes it doesn't find the db.
when i start EM standalone i can easy add this DB to the tree.
can i add the DB manually when connected to management server?
i set the global db-name to the same as the sid. could this be the problem? i didnt specify the global db-name like this: sid.domain.yy.
thanks a lot

You need to Discover the nodes from navigator menu...or by pressing ctrl + D
Make sure Oracle intelligence service is running on Nodes which you want to discover.
like for Oracle 9i
Oracle9iAgent

Oracle Management server is not started

hey all,
i have installed oracle 8i on windows 2000 professional. i want to import some database. for that purpose when i want to login in oracle management server, and put login and password, it gives error "VTK-1000 unable to connect to Management Server galaxy.pk.oracle.com. Please verify that u have entered the correct hostname and the status of the Management server."
i checked the status of the management server from control panel/services. it was manual. i started that but in the end it gave me error
"could not start the OracleOraHome81Management Service on Local computer. the service did not return an error. this can be an internal window error or an interanl service error.if the problem persist contact ur administrator."
Plz help me in this regard.
waiting for anyone s kind response

"could not start the OracleOraHome81Management Service on Local computer. the service did not return an error. this can be an internal window error or an interanl service error.if the problem persist contact ur administrator."Did you use the EMCA to create the OEM repository in one of your databases?
William Coldiron

How remote managed server to connect to admin server

I have an admin server on one machine and created a managed server on different
machine, I am not able to start managed server from either machine. When I used
the admin server machine to start the managed server remotely I got this message
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server (running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Thanks.

Is your applications deployed to Cluster?
If yes it will automatically deploy to new managed servers added to cluster when it comes to running mode

Connecting managed server to cluster's administration server

Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster (DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) and DEserver3
in machine A
I'm going to bind a same service into these above servers of my DECluster.
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations I have to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I have to
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain's config.xml
from machine A.
I'm sure I have missed some fundamental idea for building clustered services
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri

Hi Kumar,
and thank you. That fixed my problem
Best regards,
Harri
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]...
It appears you had set the administration port & listen port on the admin
server.
Logging onto admin server via admin port is broken currently. I wouldsuggest
you to set only listen port
and see how that goes.
Kumar
"Harri Töhönen" wrote:
Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password
xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster(DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) andDEserver3
in machine A
I'm going to bind a same service into these above servers of myDECluster.
>>
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
>>
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
>>
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations Ihave to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I haveto
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain'sconfig.xml
from machine A.
I'm sure I have missed some fundamental idea for building clusteredservices
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri

Connecting to Management Server

Similar Messages

Maybe you are looking for