I am getting the VTK-1000 error ("Unable to connect to the management...").
I DID install OMS through the Enterprise Manager Configuration Assistant.
The OracleOraHome92ManagementServer service is not currently running. It is set to Manual start, but when I try to start it I get a message saying "The OracleOraHome92ManagementServer service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alert service."
Could I be using the wrong login and password? I created one login when I created the OMS repository, but another message box I saw told me to use sysman/oem_temp the first time. I've tried every login I can think of. What the hell...?
If it's not practically useful, then it's practically useless.
I would suggest going to a DOS/Command prompt and issue the command:
OEMCTL START OMS
You should get the Oracle error that is being reported. Also, check the files located in the $ORACLE_HOME\sysman\log directory. You should see something like oms.nohup there -- this file can be rather large at times, so I might suggest renaming the file, then execute the OEMCTL command above.... it will re-create the .nohup file.
Let's backup here a minute. Are you running this on a server or some stand alone machine? That IP you listed is probably not going to work for the OMS, so you'll need the actual IP of the machine you're running this on:
Start->run->cmd (to get a command window)
Then ping the machine name: "ping srv01" (where srv01 = the name of your machine).
This will give you an IP that you should put into the windows/system32/drivers/etc/hosts file in the same format.
Comment out the localhost one and go with the new one:
# 127.0.0.1 localhost
Now here's the rub. If this is a dynamically allocated IP from whereever your machine sits on your network, it might change if the machine is disconnected from the network or re-booted.
Also, when you finally do get the OMS running and log in to the management server, the OEM login window will ask for username, password and management server. For the 'management server' portion, I had to use the IP address specifically instead of the server name because for some reason, the software could not resolve the name alone, but worked fine with the IP.