You might want to make sure each of the SQL users for your event collector still have datareader, datawriter, and ISSApplication access to RealSecureDB.
Tom Chmielarski IT Security Engineer Motorola Information Protection Services Tel: 1+ (847) 435 - 5382 Mobil: 1+ (847) 815 - 0586 Pager: [EMAIL PROTECTED] -------------------------------------------------- [X] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ernie Chen \(XBOX\) Sent: Monday, April 12, 2004 3:33 PM To: [EMAIL PROTECTED] Subject: [ISSForum] Help: Siteprotector Database/Event Collector Fatal Error Event Collector Status is reporting: Offline - Fatal Error! The event collector cannot connect to the database or there is a database error. The Event Collector must be shutdown. Its connection to the database and the sensors in order to prevent events from getting lost. This could be due to a misconfiguration of the Event Collector, network communication problems, or a problem with the database itself (e.g. database full) [ID=0xc734002f] This occurred after I tried running manual maintenance on the database because it grew to the point where automatic maintenance could not run. To save time, I followed the following instructions to truncate all data, then shrink the database files. I am now getting the event collector error above. I have tried downloading the latest XPU and applying, restarting the server, etc. CLEARING/TRUNCATING THE DATABASE Truncating the database is much faster than purging the database because it simply deletes all of the event data from the database. WARNING: Only do this if you want to remove *ALL* of your data. The query to truncate the event data is: exec iss_TruncateTables The query to truncate the transaction logs is: backup log realsecuredb with truncate_only SHRINKING THE DATABASE Your database files are very large preallocated files and the size of the files does not necessarily reflect the size of the database. You may be using a lot less data than the size of the file. If you would like to shrink your filesize down to the size of the database, this is how you do it. The query to shrink your event data is: Dbcc shrinkfile ('SiteProtector enterprise database primary data file', TRUNCATEONLY) (Note: I had to substitute 'enterprise' with 'site' for this to work) To shrink your transaction logs, use the query: Dbcc shrinkfile ('SiteProtector enterprise database log file', TRUNCATEONLY) (Note: I had to substitute 'enterprise' with 'site' for this to work) _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
