Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

IMS starting causes Dr. Watson 1085 error, shutsdown store.exe

0 views
Skip to first unread message

Niclas Idestrom

unread,
Feb 8, 2000, 3:00:00 AM2/8/00
to
I have a problem with the Internet Mail Service.. when I start it up it
produces the Dr.Watson error 1085:

"Some data referred to the code page 38598 that is currently not supported
by the operating system.
Install support for this language in the Windows NT International Control
Panel."

Then the store.exe shuts down with a 4116 event: "An error returned from the
messagins software the IMS uses to process messages on the MS Exchange
Server... the message that was being processed was moved to the "BAD"
folder..."

How can I get the IMS service to run together with the Information Store? I
thought that I had found the offending message in the imcdata\in folder and
moved it to the imcdata\in\archive folder. I then deleted the queue.dat file
and re-started the IMS with the same error.

What is causing the error, and if there is an offending message, where do I
find it. If it is the message that I moved to imcdata\in\archive, should I
delete it from there as well.

Any comments would be appreciated.

Nic
nide...@paoc.org

Exchange Guru

unread,
Feb 8, 2000, 3:00:00 AM2/8/00
to
Try deleting the Internet Mail Connector from the Connections Container
in the Admin program and reinstall. The IMS is dependent on the Information
Store. When the IMS is created, there are two distinct invisible folders that
are created within the IS, these are the MTS-IN & MTS-OUT folders, which
are invisible. Generally what happens is a corrupted message is caught in
one of these folders and by this causes the Store.exe to crash because it
can't decode the messages and doesn't know what to do with them.
Another crude way to do this is to stop the IS and rename all the MDBDATA
directories to MDBDATAOLD and create new MDBDATA directories in
their places. By doing this, you will start with a clean IS. Start the IS and
then try to start the IMS and test mail. If it works without crashing, then
you've narrowed the problem down to the IS. There is a tool that you can
obtain from Exchange Engineers as myself, called ResetIMC, which will
purge all messages that may be in the MTS-IN & MTS-OUT folders. You
must obtain this file from a Microsoft Exchange Support Engineer....

Exchange Guru

On Tue, 8 Feb 2000 13:49:55 -0500, "Niclas Idestrom" <nide...@paoc.org>
wrote:

Kirill S. Palagin

unread,
Feb 9, 2000, 3:00:00 AM2/9/00
to
Exchange Guru wrote:

> Try deleting the Internet Mail Connector from the Connections Container
> in the Admin program and reinstall. The IMS is dependent on the Information
> Store. When the IMS is created, there are two distinct invisible folders that
> are created within the IS, these are the MTS-IN & MTS-OUT folders, which
> are invisible. Generally what happens is a corrupted message is caught in
> one of these folders and by this causes the Store.exe to crash because it
> can't decode the messages and doesn't know what to do with them.
> Another crude way to do this is to stop the IS and rename all the MDBDATA
> directories to MDBDATAOLD and create new MDBDATA directories in
> their places.

This is really bad advice.

--
If you feel that anything in my post needs correction - feel free to do so (in
group).

Kirill

BK

unread,
Feb 9, 2000, 3:00:00 AM2/9/00
to
I just encountered this problem with my Exchange 5.0 SP2 server. In fact, every
time the user checked his email, it would stop one one message, crash the email
client, and then crash user32.dll which in turn halted the information store.

I followed the instructions that you have highlighted below (found on MS site),
but it also didn't work. Finally, I performed a "clean mailbox" and it solved
the problem, but it moved all of the mail into the "deleted items". We run
POP3, so I am having trouble getting to this folder with a client. Kirill has
pointed me to using a MAPI client, but I have not really tried it out.

Anyway, the user lost all the mail that came in after the corrupted message, but
it fixed the problem. Anyone else seen this problem? I wish I knew a better
way to fix....

0 new messages