Microsoft Exchange 5.5

The problem may be the result of Information Store corruption. There are several ways to proceed. The safest method is to work on a backup copy to determine the results before continuing in production. If you do not have a backup of your information store, make sure you make one before using any of the database utilities.

Stop all Exchange services except the System Attendant. Run ISINTEG with the appropriate tests. I recommend you use the verbose flag and log to a text file. ISINTEGwill make several fixes. Run it again until it does not make any fixes then start the exchange services.

Feel free to e-mail me if you want/need more details or advice.

First off, you need to supply a lot more background than that to get an accurate solution to your problem. What service pack are you running on Exchange? What OS are you running on the server? Are your users using Outlook to connect to Exchange?If so, what version? How long has this been happening? What changed between when it did work and now? Are you running Anti-Virus software? If so, what brand/version? Are you doing Exchange-aware backups or file-level backups? Have you looked at the server logs? If so, are there any error messages and exactly what are they? Do your clients get any error messages?

Get all that information together, go out to www.swynk.com and subscribe to the Exchange Discussion List. Best list in theworld with some of the best gurus in the business!