topic Re: HomePage service not starting in Server Management - Systems Insight Manager

HomePage service not starting

Sam_182 — Wed, 22 Jun 2005 07:28:19 GMT

I am running W2K3 server on DL 380 G2 with terminal services. I have read the deployment guide and tried to install Homepage from both the PSP cd and the Foundation Pack cd.

SNMP accepts any host and has community name of public set to read/write.

No errors on install but the service will not start and the desktop shortcut C:\WINDOWS\inetIcon.url opens an IE location of https://127.0.0.1:2381/ and "The page cannot be displayed"

Service Error:
szAppName: smstart.exe
szAppVer: version 2.0.2.106
szModName: msvcrt.dll
szModVer: 7.0.3790.1830
offset: 00031a02

My hope is to get this fixed, so I can get the VCA agent to communicate with SIM for updates.

Any ideas?

Re: HomePage service not starting

Rich Purvis — Wed, 22 Jun 2005 15:33:10 GMT

Did the error really say:
szAppName: smstart.exe

I think it should be smhstart.exe, at least that is what the properties say on my installation. Perhaps there was a problem with the installation?

If you look in the "\hp\hpsmh\conf" subdirectory do you see a file called smhpd.conf? If so it would indicate that the service tried to start up. If the "conf" file is there do you see any unexpected IP addresses listed in it?

-Rich

Re: HomePage service not starting

Brent Seizer — Wed, 22 Jun 2005 18:36:20 GMT

I recently began integrating my new DL380's into IM. My OS image already had the 7.1 PSP installed. It was the reccomendation of Tech Support to uninstall Sys Manage Homepage, and IM Agents, and the VC Agent.

Make sure you have 2 SNMP groups.
I use public for my read only group.
I use another name for my read/write group.

make sure that the only servers that you will accept SNMP from is 127.0.0.1 and the IP of your CMS server.

Under traps make sure that you install both IP address for both communities.

Then download the 7.3 PSP, and then installed CP005171.EXE(SYS MANAGE HOMEPAGE) first, then installed CP005194.EXE(IM Agents) second, and then CP005177.EXE(VC Agent) third.

Do NOT run the Support pack from a CD.
Running them from a CD causes the EXE to run in read only format and you wont get the interactive promptings. If you copy them off a CD to a temp directory, you will have select all the files and unmark them as read only.

Expand the downloaded file to a temp directory.
Copy the expanded files to your RESPOSITORY directory.
Make sure your using the updated repository manager program that gets installed on your CMS server. This versiion came out after IM 4.2. The 7.3 version control agent works with the new repository manager.

These 3 programs above get installed in this order interactively.

Make sure you have a server cert created on your CMS system. When you run through the questions for the homepage make sure that the ADMINISTRATORS group is added to administrator. Select TRUST ALL, and set the trust cert once you get logged into the home page.

Hopefully this will get you on the right path. Let me know I you have more questions.

Brent

Re: HomePage service not starting

Sam_182 — Thu, 23 Jun 2005 11:41:07 GMT

Rich:
Correction szAppName is smhstart.exe

There is a \hp\hpsmh\conf folder but no *.conf files

Brent:
I followed you procedure with the same results.

I did notice that the are 2 HP folders on 2 separate drives. The install is generating C:\hp\hpsmh and D:\hp\hpsmh is this what is causing the problem?

Note: Also there are c:\compaq\wbem and a d:\cpqsystem\log folders.

I there a way to force the install location.

Re: HomePage service not starting

Rich Purvis — Thu, 23 Jun 2005 12:55:21 GMT

Do you have two OS installations? I am not sure why you would end up with one on each drive. The old \compaq\wbem subdirectory is placed there for backwards compatibility with older applications. Is the "HP System Management Homepage" service listed in the list of the Service Control Manager? If the service had started you would have ended up with CONF file - since it is not there it is either not even getting started or is stopping very early.

-Rich

Re: HomePage service not starting

Sam_182 — Fri, 24 Jun 2005 08:46:16 GMT

The service is listed.

To answer your question the OS is conficured to install all apps on the D: drive, yet it appears Compaq (HP) IM is conflicted as to where to place items.

I copied everything from the D: drive to the C: drive (where the OS resides).

The service started, I double clicked the desktop icon, recieved the Security Alert (clicked yes) but the page cannot be found.

http://127.0.0.1:2381/cpqlogin.htm?RedirectUrl=/&RedirectQueryString=
(all one line)

Re: HomePage service not starting

Sam_182 — Mon, 27 Jun 2005 14:27:30 GMT

SMH installes on the D:\hp drive, but will not start the SMH service.

I think this happens due to a W2K3 set variable.

So I installed it on the d-drive and copied it to the c: and edited the registry to point the service to the c:\hp... directory.

The system homepage works and the IM agents installed and the VC agents installed.

Is it possible to force SHM to install on the c: drive?

Re: HomePage service not starting

Kelly Whitsett — Wed, 06 Jul 2005 11:17:22 GMT

I am not familiar with the OS settings that would (attempt to) install the System Management Homepage on a selected drive. However, the SMH installer will always install on the system drive. This in not a configurable option.

Re: HomePage service not starting

Kelly Whitsett — Wed, 06 Jul 2005 12:41:49 GMT

In my attempt to clarify, it seems that I might have confused the issue further. Let me try again.

It would seem that something in your OS configuration is forcing SMH to install on the D: drive. However,the SMH installer is designed to install on the system drive, in this case, C:. So a conflict is being
introduced. I am unable to determine how this is happening. I thought it might be something as simple as resetting the SystemDrive environment variable, but I tried that to no effect.

Re: HomePage service not starting

Sam_182 — Wed, 06 Jul 2005 13:22:16 GMT

I appears to be only occuring on the servers that were cloned using Ghost.

I reinstalled the OS on one of the problem servers with the latest Smart Start 7.3 and that seemed to fix the issue.

It is my intention to use this newly created server as the original for cloning.