TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
Espen, I believe someone sent you the wrong KB article. UserIssue_1 is not generated in response to communication problems between the WGM and the sensor. So doing any of the things mentioned in your reply will not help. The correct (and typically only) action ever required for UserIssue_1 is to forward the event detail to ISS Technical Support. Paul -----Original Message----- From: Espen Rahd [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 9:23 AM To: Ernest Lopez; [EMAIL PROTECTED] Subject: RE: UserIssue_1 error TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- Hello, I see alot of them, even more after upgrading to X-pressupdate 20.4. Asked support last month: ISS support mail::::)))) Hello, This is a very general error message and can be caused by a number of things. 1. Sometimes when there is network congestion you will see this error message. 2. When the connection is stopped due to the issdaemon not listening any longer. 3. The default ports for the sensor are taken by another application (ex. backups are occurring). 4. The incorrect authentication is being used between the EC and the Sensor. 5. The Heartbeat from the EC to the Sensor was not successfully returned. 6. The SensorEventQueue.ADF gets corrupted. The first things that I would try to do is increase the Sensor poll Interval. You can do this by opening the RS Console|View|Options|System Alerts tab. You will see the Alert Frequency table. Increase the Sensor poll Interval by 100+. You can also push your keys back out to the sensor. Make sure that you are using the same authentication for the EC and Sensor (ex. Make sure that you are using RSA or CerticomNRA on both machines). You can also rename the SensorEventQueue.ADF file and then stop/start the issdaemon. The .ADF file will then be recreated. However, keep in mind that the majority of the time this error message points to network connectivity issues. I hope this helps. I am closing out this incident, if you have any further questions regarding this issue please let me know. -----Original Message----- From: Ernest Lopez [mailto:[EMAIL PROTECTED]] Sent: 18. september 2002 20:59 To: [EMAIL PROTECTED] Subject: UserIssue_1 error TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ------------------------------------------------------------------------ ---- All, We have recently been getting tons of errors like the following: Event: UserIssue_1 From: 0.0.0.0 To: 0.0.0.0 Info: alert0 - Sensor Internal Error alert1 - Contact ISS technical support alert2 - current packet in crash.cap Event: 0xc0000005 Can anyone tell me why this is happening? RS 7.0 Thanks, Ernest
