I would appreciate anyone's help. I'm trying to figure out what would cause Remedy to deregister a user? What's happening is, the records are going to the Alert-Events table but for some reason they either aren't being received by the client at all, or at times they ARE receiving them, but up to 45 minutes later. Also in the Alert-Events table, the records the client is saying they arent receiving are marked Read. What actually causes that field to be marked?
Additional information: Here's an error message we're seeing in the Alert logs. <ALRT> <TID: 000004> <RPC ID: 0000000000> <Queue: Alert > <Client-RPC: 390601 > <USER: AR_NOTIFIER Ø /* Tue Aug 29 2006 03:12:01.4568 */ Socket write call failed with error 32. I have been told there is no firewall issue. The following things took place right before this started happening: 1. OS Patches were applied to Remedy server. (Sun OS 5.9) ARS 5.1.2 (patch 1288...yea, yea...I know) 2. Client physically moved their server. Is there any sort of configuration changes that should have taken place that we just missed?? Thanks! _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
