Critical System Protection

I am trying to determine the cause (or workaround) for a CSP agent upgrade failure when upgrading from 5.2.0.510 or 5.2.0.563 to 5.2.4.266 on Windows 2003. I have also seen this happen from 5.0 and 5.1 to 5.2.  The installation of the agent appears to be upgraded but the configuration settings are wrong and can not be set via sisipsconfig.exe. As shown below. The heartbeat dies and the sisids services lock up.  Has anyone seen this before? Know the cause?

C:\Program Files\Symantec\Critical System Protection\Agent\IPS\bin>sisipsconfig -v
---------------------------------------------------------------------------
Agent Configuration Tool version 5.2.4.266
---------------------------------------------------------------------------
Server Host List -
Current Management Server -
Port - -1
Protocol -
CertFile -
Failback Interval - 60 minutes
Tracing - false
Force Retranslation - true
Prevention Feature - enabled

Tim,

I was actually able to replicate this issue just recently, the individual had a 3rd party autostart application restarting the sisipsagent as well as the util agent which somehow messed up the install to lock the service. If you ensure that is not occuring I would then recommend the normal drop agent into debug mode (trace for ips), getagentinfo, and start case with Symc since it appears to be in multiple versions - hard to do as its random - you can't "tell" what instance will do this, hence you cant put the IPS driver into trace debug *before* it happens. Im pretty sure you can't post getagentinfo's onto here per your employer policy too for us to help.