topic Re: HP SIM user interface not working in Server Management - Systems Insight Manager

HP SIM user interface not working

sdb_2 — Tue, 01 Jun 2010 09:04:12 GMT

Hi,

The user interface of our HP SIM stopped working for some reason.
HPSIM is still sending mails about systems, but accessing SIM itself isn't possible anymore.

I only see this error in eventlog:
Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 1/06/2010
Time: 11:48:05
User: N/A
Computer: ICTS-S-HPSIM
Description:
svchost (840) The database engine stopped.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Has anyone seen this behaviour before?
Thanks.

Re: HP SIM user interface not working

sdb_2 — Tue, 01 Jun 2010 11:43:56 GMT

Ok. This seems to have something to do with the lsass.exe process, which is also using port 50000.

As far as I know, HPSIM uses port 50000 for the https access to the user interface (http://localhost:280 gets redirected to https://localhost:50000). So This would explain the java error I see in the mxdomainmgr.log:

LifecycleException: service.getName(): "jboss.web"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:50000

Does anyone know how I can change the port for the user interface in hpsim to an available port (e.g. 60000)?

Thanks.

Re: HP SIM user interface not working

Change_happens — Wed, 02 Jun 2010 11:36:23 GMT

actually sim connects to 50000-50004 ports.
wanna change it should be in jBoss:
c:\programfiles\hp\SIM\jboss\server\hpsim\deploy\jboss-web.deployer

in xml "server.xml" change connector port.

Re: HP SIM user interface not working

Newton S — Wed, 02 Jun 2010 11:46:03 GMT

What is the CMS OS

Re: HP SIM user interface not working

sdb_2 — Wed, 02 Jun 2010 11:56:48 GMT

Great. Thanks, HPSIM is working now :-)

Re: HP SIM user interface not working

sdb_2 — Wed, 02 Jun 2010 11:57:52 GMT

For the record:
We use HP SIM 5.3 SP1 on a W2k3 OS.

Re: HP SIM user interface not working

sdb_2 — Tue, 15 Jun 2010 05:06:25 GMT

see solution above