Have a look at the following articlse - they discuss using differnt locations for the DB
Do they appear same time as the rpcserv issue in your other posting??
Is there an indication of any issue?? Do you have to stop/start services or kill any processes??
Is this during db purge/optimize tasks??
Is there a consistency in the error like times of High CPU usage ... during backup/maintenance etc
Is DB in default location/Product Install folder/custom location??
This looks like what we are getting as well. Maybe once every 2 weeks or so.
From: IT Alerts
Sent: Saturday, 9 February 2013 8:03 AM
Subject: VSEXCH01: The Detected Items failed to store arecord.
"VSEXCH01" Product database failed to store arecord .
1. Check whether Postgres database is configured to avalid location.
2. If this does configured properly, change the databaselocation to a valid drive that has sufficient disk space.
Anyone ever found a solution?
Also does anyone know how to change the to and from email address? It's backwards for the email alert.
I would ask the same questions again...as above like - Is the error consistent at specific time like times of high cpu activities - backups/exchange maintenance other os activities?? Or clash of activities like MSME Ondemand scan overlapping with a backup???
McAfee have also released a new Rollup1 of fixes after MSME 7.6 Patch 1 - its available for download at McAfee Site with grant number - it should be available in Software Manager if you are running ePO version with Software Manager Capability.
No, we haven't found any consistency between the error and another scheduled event or activity.
The Postgres DB is in the default location, with about 30 GB of free space.
My co-worker had a ticket open with McAFee and it was determined that there is no impact and it can safely be ignored.
It doesn't seem to affect either MSME or Exchange, so we've been ignoring it.
No consistancy for us either. I am not sure what if any kind of cpu monitoring we have on the server, but exchange was unlikely to be doing anything drastic at 8am on Saturday. We only have 50 or so Exchange users.
We have no scheduled task running and backups would have finished +/- 7 hours before the alert.
I think what is being discussed here is a random single event recorded whereby something may have very briefly inteferered with the connection to db and an event gets posted. and after this the connection to the db is re-established - I cannot find in this scenario that there is any problem with the db or that it needs rename/replaced.
If you are stating that the eventlog is flooded with these events then that could suggest db corruption - is this what you are seeing??