OpenDeploy 6.1.1 Receiver Installation Issue

First I'd like to say that OpenDeploy has always been a solid product and it's been one of the easiest to install in the past. I'm surprised that I'm having issues...

We have a Windows 2003 Server on which we're installing OD 6.1.1 receiver. Initially it was an upgrade from 6.0.2. We ran the installation and everything went smoothly. Got to the finish screen and it said to reboot, so we did. After the reboot, the OD Receiver service was not started, but was set to automatic. We tried manually starting it and it immediately stopped. We went to the application event log for windows and this was the message right before OD shut off:
The Java Virtual Machine has exited with a code of 3, the service is being stopped.

We went ahead and uninstalled OD 6.1.1 and cleaned up the directories. Only left the logs and the etc directory in tact. Rebooted. Reinstalled to the same location. This time as a new installation rather than an upgrade. After reboot, same issue.

HELP!

Thanks,

Jason

Find more posts tagged with

Comments

nipper

Are there any other errors in logs or in the event log ?

ccprofessional

did you regenerate the license?

Migrateduser

The OD logs are basically useless in this case. They say that OD stopped, but they don't say why. Here's today's event logs:
SEC: 2007-06-27 08:36:48 EDT GMT-04:00 Begin server security shutdown.
SEC: 2007-06-27 08:36:48 EDT GMT-04:00 No need to update Opendeploy Admin role DB File.
SEC: 2007-06-27 08:36:48 EDT GMT-04:00 No need to update OpenDeploy User role DB File.
SEC: 2007-06-27 08:36:48 EDT GMT-04:00 Finished server security shutdown.
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Stopping OD server engine ...
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Stopping listener on 20014
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Receiver stopped.
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Stopped listener on port 20014
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Listener stopped.
ENG: 2007-06-27 08:36:48 EDT GMT-04:00 Stopping event server ...
ENG: 2007-06-27 08:37:48 EDT GMT-04:00 Event server stopped.
ENG: 2007-06-27 08:37:48 EDT GMT-04:00 OD server stopped.

[size=2] The best information is in the windows event log. Yes, we generated new licenses.[/size]
[size=2][/size]
[size=2]- Jason
[/size]

nipper

That mentions the event server, is there anything else in those logs ?

Migrateduser

That's all that's in the receiver log for today. We started the upgrade at about 8:35a this morning. Here is the contents of the receiver events log:
2007-06-27 08:36:48,218 [RMI TCP Connection(2818)-192.168.221.11] INFO - Stopping event reporting system...
2007-06-27 08:37:48,218 [RMI TCP Connection(2818)-192.168.221.11] INFO - Interrupted...
2007-06-27 08:37:48,218 [RMI TCP Connection(2818)-192.168.221.11] WARN - Destroying process 'OpenJMS'.
2007-06-27 08:37:48,218 [RMI TCP Connection(2818)-192.168.221.11] INFO - Process 'OpenJMS' stopped.
2007-06-27 08:37:48,218 [RMI TCP Connection(2818)-192.168.221.11] INFO - Event reporting system stopped.
2007-06-27 08:37:48,218 [ShutdownHook] INFO - Stopping event reporting system...
2007-06-27 08:37:48,218 [ShutdownHook] INFO - Event reporting system stopped.

[size=2]Any other suggestions are more than welcome. I'm RTFM right now, which is a LOT of fun.[/size]
[size=2][/size]
[size=2]- Jason
[/size]

nipper

2007-06-27 08:37:48,218 [RMI TCP Connection(2818)-192.168.221.11] WARN - Destroying process 'OpenJMS'.

I assume that OpenJMS was in the OS directory and not in a different location. Can you remove the DB and let it get recreated ?

Migrateduser

I think I just found something...

In the od.log it's complaining about the Domain Name in the license file. The server is not part of a domain. So, when generating the license, what should we put for domain?

I removed the license file altogether and was able to start the service.

- Jason

nipper

I use a domain of NoDomain

You have 30 days on the temp license to get this fixed. :-)

Migrateduser

Thanks nipper. That solved it.

- Jason