booktrunk1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2017-09-20
11:58
1291 views
POA Errors
Hi.
We are seeing these errors in the database
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:13 C29E The database function 53 reported error [C042] on msg121.db
11:49:14 C29E The database function 53 reported error [C042] on msg131.db
11:49:14 C29E The database function 53 reported error [C042] on msg131.db
I believe that these are related to one user, she had a huge database that i've now got rid of everything except the last years info from it. So It's gone from very large to just large 7.3Gb
But when I tried doing a GWCHECK on her mailbox at this size using the fix option enabled it basically hung the post office and it wouldn't respond. Until I restarted it.
I am now trying to do a gwcheck on her without any fix options ticked just doing a check, and the rest of the server seems ok with me doing that, but once I started the GWCHECK I started to get these errors.
So I'm a little stuck, the emails are nearly all just in the inbox and sent items, there aren't many 12,000 in total most of them in her sent items. Can I just under her cabinet make a couple of directories old mailbox and old sent items. Then move everything into those, and then run a GWCHECK and then put them back into their normal position. Should that resolve any issues if she has possibly one or two weird corrupt emails?
(i've been on holiday, and now i'm back going through all our GW problems from when i was away).
Thanks in advance for any help.
We are seeing these errors in the database
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:12 C29E The database function 53 reported error [C042] on msg131.db
11:49:13 C29E The database function 53 reported error [C042] on msg121.db
11:49:14 C29E The database function 53 reported error [C042] on msg131.db
11:49:14 C29E The database function 53 reported error [C042] on msg131.db
I believe that these are related to one user, she had a huge database that i've now got rid of everything except the last years info from it. So It's gone from very large to just large 7.3Gb
But when I tried doing a GWCHECK on her mailbox at this size using the fix option enabled it basically hung the post office and it wouldn't respond. Until I restarted it.
I am now trying to do a gwcheck on her without any fix options ticked just doing a check, and the rest of the server seems ok with me doing that, but once I started the GWCHECK I started to get these errors.
So I'm a little stuck, the emails are nearly all just in the inbox and sent items, there aren't many 12,000 in total most of them in her sent items. Can I just under her cabinet make a couple of directories old mailbox and old sent items. Then move everything into those, and then run a GWCHECK and then put them back into their normal position. Should that resolve any issues if she has possibly one or two weird corrupt emails?
(i've been on holiday, and now i'm back going through all our GW problems from when i was away).
Thanks in advance for any help.
2 Replies
laurabuckley

Micro Focus Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2017-09-20
14:53
Hi,
Bear in mind that more than one user could be allocated/associated with a single msgxxx.db.
I would recommend a standalone GWCheck and instead of putting the user's name in the corresponding entry box put in: msg131.db
This will repair just that one database. Do this after hours if you are concerned about your POA grinding to a halt.
Cheers,
Bear in mind that more than one user could be allocated/associated with a single msgxxx.db.
I would recommend a standalone GWCheck and instead of putting the user's name in the corresponding entry box put in: msg131.db
This will repair just that one database. Do this after hours if you are concerned about your POA grinding to a halt.
Cheers,
Laura Buckley
Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
booktrunk1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2017-09-20
15:08
Thanks.
I didn't know that you can do that on individual databases.
I didn't know that you can do that on individual databases.