Strange HP SIM behaviour

[B. ten Berge]

Hello,

I'm not even sure where to start with this problem, so here goes.

We're running HP SIM 5.2 on Windows Server 2003 Enterprise Edition.
Things seemed to go alright, until the MS SQL templog.ldf file filled the entire C: partition.

Here's a summary of the strange things I see:
- I see a couple of ORPHAN entries; example: SERVER1 is now an orphaned entry, but when I edit the properties of this server and try to save it, I get an error that says that there's already a device with that name.
So, when I click on the + sign in front of the Operating System where it should be listed, I see the name SERVER1. When I click on SERVER1, I get a blank page in the right frame.
However, when I click on the OS name to list all servers running that OS in the right frame, SERVER1 isn't in that list.

- SERVER17 has 4 IP addresses, according to HP SIM. 3 of these IP addresses belong to other systems that are no longer in the system lists. One of these 3 unlisted systems can be found using the Search function....
When I try to manually add the other 2 servers, they won't get listed, nor can they be found.
When I delete SERVER17 and manually add the 3 previously missing servers, they appear visible like they should, but, when I add SERVER17 again, the 3 servers go byebye again and this SERVER17 shows their IP addresses.

I'm completely losing it, I can't even explain clearly what's going on, since these aren't the only strange things that are happening.
Any advice would be really welcome.

Thanks in advance,
Bob

[Ananthak23]

Make sure that DNS has the correct record for Sever17. Instead of manually adding the servers try auto discovering these servers.

-Anantha

[B. ten Berge]

Thanks for your reply.

The DNS records are correct, when I do nslookups on these servers, all the IP's and reversed lookups are correct.
An automatic discovery occurs each morning at 5am, even well into the next day the other servers still don't appear in the lists and the IP addresses of the different servers still appear listed as being SERVER17's in HPSIM.

When I add a server manually, I tried it 2 ways, by IP address and by servername. Both have the same results.

Another thing that I noticed, is that all the Windows servers only appeared under the Trusted list, only after I edited each server's configuration (OS description and version, hardware description) they appear under the correct OS listings.
But when I delete a server and readd it even a day later, all those details I entered manually are back again?

[Albert_39]

My tempdb log file is growing like crazy as well. I narrowed it down to te Bi-Weekly data collection task or the software version status polling task. I moved the software version scan out two hours so they didn't run at the same time and my log is still growing. of course the software scan has been running for almost 3 hours.

from SQL profiler.
I'm stuck in what looks like a loop of
create proc #jdts...
exec proc ....
delete proc ....

I canceled the task and it took 10-15 mins for the stored procedures to disappear from my SQL profiler trace. During the last running task my tempdb log file increased 6 fold. (I canceled it before it finished was only at 38%)

Specs Windows 2003 Standard Server
remote SQL Server 2000 stander w/SP3a.

[Massimo Ripamonti]

I have the same problem.

HP SIM 5.2 is on W2003 Server with MSDE.

I'm managing 45 systems; I disabled automatic Discovery.

templog.ldf is filling the C partition.

Help!

[Tony van den Heuvel]

I have the same problem.

HP SIM 5.2 is on W2003 Server with MSDE.

I'm managing 170 systems; I disabled automatic discovery

templog.ldf is filling the C partition.

Help!

[B. ten Berge]

I know how to solve the growing database problem.
You should change the Recovery mode for the tempdb to Simple instead of Full.
The only way I know how to do this, is from the MSSQL Enterprise Manager, one of the properties of the database.
Another option is to move the tempdb.mdf and templog.ldf to a larger partition, there's a Microsoft KB article on how to do this here: http://support.microsoft.com/default.aspx?scid=kb;en-us;224071#XSLTH3207121122120121120120

[B. ten Berge]

Problem solved!

I now know what caused most strange anomalies, some of the servers were from the same Ghost image, thus had the same HostGUID under HKLM/Software/Compaq Insight Management.
After removing that key and restarting the HP Insight Server Agents service, a unique HostGUID was created and the servers/IP addresses are no longer linked/incorrect in HP SIM.

[Albert_39]

Sorry, I'm running a full version SQL server and you can't change it from Simple. ;-}

[Massimo Ripamonti]

I'm using MSDE and I don't know how to change the properties of database: Is there the MSSQL Enterprise Manager in MSDE?

[Hornos]

Hi,

Same problem here.
Using MSDE.
templog.ldf will grow (up to 4 Gb!) and fill my partition.

I've found a temporary fix by running the following command:
sqlservr -c -f
(source: http://support.microsoft.com/kb/307487/en-us).

But I need a permanent fix!!

[David Semler]

Hey folks,

I have the exact same problem, but I think I found the issue. Stop your HP Virtual Machine Management Service. See if that stops the templdf.log from growing out of control. I think here is definitely a bug in this version of SIM on a Windows 2003 SQL 2000 server.

I don't have a fix, I believe this service held a lock and was blocking one of the spids in SQL. I hope this helps somebody and that someone in the HP camp is paying attention to this thread.

[COOPERCAV]

If your using MSDE locally, don't forget you could always connect remotely using Enterprise Manager on another full SQL server on the network, should you have one. Until I changed the HPSIM database to simple the ldf file would regularly exceed 80GB. This does not account for the size of the temp.ldf though. MSDE can also be configured by command line (good luck), and although you could install SQL Server Client Tools only (exc db), I belive this still has licence implications.

[B Symonds]

Disabling the HP Virtual Machine Management Service has work for me but if you do need to run this service there is a fix

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00683753&jumpid=reg_R1002_USEN

[Lawrance Lee_1]

I have SIM 5.1 with SP1 running on a server with 16GB of RAM.

I only ever experience this problem when I am deleting systems off from the database. It doesn't matter whether I'm using the GUI of SIM or using the command line mxnode command.

The database is SQL server 2000 (the full version).

I've checked out that service advisory and my settings are already as per the article.

Has anyone else got a solution?

Thanks,

Lawrance