Corrupt Database?

[bbawkon]

Good day everyone,

I have a problem that was noticed by one of my users this morning.

We have an Exchange 2003 Sever running on Windows 2003 Server. Clients are Outlook 2003.

Suddenly, some email (mostly older messages) are 'missing'. The header (who it's from and subject) shows up in outlook, but the preview pane displays
"This item cannot be displayed in the reading pane. Open the item to read its contents."

trying to open the message provokes the error "Can't open this item. The operation failed"

Attempting to open the message in OWA gives
"The page cannot be displayed
The page you are trying to reach cannot be retrieved.

--------------------------------------------------------------------------------

Please try the following:

Open the mail.mydomain.com home page, and then look for links to the information you want.
Click the Refresh button, or try again later.

Click Search to look for information on the Internet.
You can also see a list of related sites.



Error 501/505 - Not implemented or not supported
Internet Explorer"


--------------------------------------------------------------------------------------
Can anyone give me a clue as to what i'm looking at? I'd rather not have to restore from backup, as we are willing to loose the old messages - we just don't want a corrupt database.

The error was noticed during an Archive someone tried to perform. The messages that could not be opened caused the Archive to fail with
"Error while archiving folder "Inbox" in store "Mailbox - One of my users". Some items could not be copied. They were either moved or deleted, or access was denied."

Thanks for any help!
Ben

 

[xmsre]

are the messages signed?

 

[bbawkon]

Forgive me, but i'm unsure what you mean by 'signed'.

Ben

 

[Casbot]

Have you tried running an ESEUTIL check on the database or even an ISINTEG to fix the corruption??? I'd do that before thinking that you have to restore from backup, because if this has been going on for a while, your backups are corrupt as well.

Casbot.

 

[dnthompson]

I am having the exact same problem with one of our users.

We get exactly the same problems and have tried connecting to the mailbox using Outlook 2000, 2002, 2003 and OWA. Also ,when trying to download the problem messages via POP3 we also get the following in the eventlog:

Event Type: Error
Event Source: POP3SVC
Event Category: Content Engine
Event ID: 1023
Date: 13/02/2004
Time: 15:51:07
User: N/A
Computer: MAIL
Description:
Error 0x80040102 occurred while rendering message 0001-0000000c3ec7 for download for user xxx@xxx.xxx.

My collegue informs me that he has just ran ESEUTIL and found no corruption.

The only common link I can find with these messages is that thay have all been flagged for follow-up using Outlook 2000.

Any suggestions?

 

[dinger69]

See the attached link. I believe this is what you are describing.

support.microsoft.com/?kbid=175406

 

[corystuart]

What does this have to do with the fact that the messages aren't showing up on the server? I'm experiencing the same thing. It seems as thought the message are just gone! For another user, his messages show that they're in his inbox, but he can't view them.

 

[xmsre]

Eseutil checks for page level corruption in the edb [ie. checksums don't match], I don't see how this relates to your problem. Try isinter with -tests mailbox.

Another point is that this happens during rendering for download by pop. This means content conversion from mapi to mime format. Content conversion takes place in the %systemroot%\temp directory. What are the permissions on that directory? Is AV grabbing it?

It could also be that you are dropping the connection in the middle of the download. 80040102 is a winerr for an invalid file handle.

 

[corystuart]

As it turns out, it's a "problem" with exmerge. My server is fairly new. I'm using exmerge to import pst files into mailboxes. If there's any corruption at all in the pst file, it does not import very well. That's why messages disappear or you have message headers that don't point to a message body. Before importing pst files into mailboxes, run ScanPST to clear out any corruption.

 

[jtw1981]

I've just had a similar problem - the solution was restarting the Symantec mail scanning service.