ISEE_CMS_SWMAGENT fullfilling the application log...

[Ph. de Saint-Georges]

Hello,

does somebody know why the ISEE_CMS_SWMAGENT fill up my windows application log with a huge amount of messages like the ones below so that I have to empty the log each day:

Minimized tuner cleaning up and exiting with code=4
Maximizing due to DDE request. arg= -nologo -minidde -shell 1253
Starting tuner
*** Debug File at C:\Program Files\Hewlett-Packard\SWMAgent\.marimba\ISEE_CMS_SWMAGENT\launch.log
ScheduleThread stopping
etc etc...

Thanks for help

Philippe

[Svefa Helpdesk]

I would also be very interested in getting rid of these messages that are drowning everything else in the application and system event logs.

[David Claypool]

Generally speaking, logging what is going on is a good thing. It will be incredibly helpful in debugging a problem in the future. I would suggest making the log larger and selecting 'Overwrite events as needed."

[Ole Thomsen_1]

Good things can be overdone :-)

I agree that it is rather annoying to have the application event log spammed by insignificant informational events, making it hard to monitor what is really important.

Please log to a file only, or give me the option of changing the logging level, please. In my opinion this level should be used for debugging only.

Ole Thomsen

[Brian Drab]

We have this same issue as well. The answer of "make the application log larger" is not a reasonable answer and doesn't actually answer the original question. These messages should not be generated in the event log, unless I explicitly set the "show me many useless garbage debug messages" option. So how do I turn them off?

[Dan Philippe]

Not only it fills up my evt log, I see this error "ISEE_CMS_SWMAGENT error: 1453 Could not enumerate processes: Insufficient quota to complete the requested service. (0x5ad)" just about 2-3 minutes before the server crashes (unexpected shutdown).

I looked at the disk and Quota is not enabled. Any idea what might be the cause?

[rcseattle]

This is caused by the marimba component, now owned by BMC.

I've got the same issue. Too many "informational" messages in the application log. A lot of noise that does not belong there.

Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:16:28 PM
User: N/A
Computer: SIM
Description:
Tuner minimized, threads=5 names=RPCThread NetDetectThread ScheduleThread DDEThread StopEvent
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:16:28 PM
User: N/A
Computer: SIM
Description:
Using multicast network detection: detected=true, delay=60 sec
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:16:28 PM
User: N/A
Computer: SIM
Description:
Waking up in 29 minutes
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:16:28 PM
User: N/A
Computer: SIM
Description:
The Tuner minimized its memory footprint.
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
Maximizing tuner
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
*** Debug File at C:\Program Files\Hewlett-Packard\SWMAgent\.marimba\ISEE_CMS_SWMAGENT\launch.log
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
WSACleanup done
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
DDEThread stopping
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
RPCThread stopping
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
NetDetectThread stopping
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
Minimized tuner cleaning up and exiting with code=4
*****************************
Event Type: Information
Event Source: ISEE_CMS_SWMAGENT
Event Category: None
Event ID: 1
Date: 5/19/2008
Time: 12:14:26 PM
User: N/A
Computer: SIM
Description:
Maximizing due to scheduled event.
*****************************

On and on about 24 such entries every hour. There has to be a better way to log these information events if it's needed at all. I'd like to just shut this thing up.

[J.Richardson]

This is an old thread, but the HP moderator never gave a real answer - merely babbled something about "logging is good".

Is there a real resolution for this problem?

[Mr Bill]

I'm having the same problem. The application log is full of these Marimba tuner events. I'm thinking of turning the ISEE_CMS_SWMAGEN service off/manual. I echo the posts above, why can't this noise just be sent to a log, or allow me to turn off some of these useless messages which appear every couple of minutes. The Application Log is not the place for this. HP Please help...

[rcseattle]

Let us know how that works for you. I believe the component is required for the VCRM to function.

The component is owned by BMC, so I don't think HP is putting any effort into fixing this behavior.

"Generally speaking, logging what is going on is a good thing."... Noise filling your server application logs is not a good thing David.

[Threonine_1]

I just noticed this on one of my HP SIM servers also. We are not using the Version Control Repository Manager so I just went ahead and disabled the ISEE_CMS_SWMAGENT servivce for now. So far so good.

[JL123]

Has disabling that service caused you any problems for your warranty and contracts collection/notification?