Vista - Windows Live Mail daily error

I have had WLM installed and using it for almost 3 weeks now. I'm running on
WinXP Pro sp2 fully updated.

Each night I close down WLM by selecting File/Exit. There is no icon in the
tray after this, so I assumed it was fully closed. However, each morning I
have an error message on the screen that occurs sometime after midnight and
says that WLM had to close because of an error and asked if I want to send a
report to MS. Reviewing the event log the following is recorded for the
error:
"The description for Event ID ( 1000 ) in Source ( Windows Live Mail )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description;
see Help and Support for details. The following information is part of the
event: wlmail.exe, 12.0.1606.1023, 471e44f8, uxcore.dll, 12.0.1606.1023,
471e445f, 0, 00037408."

Why would WLM being getting an error and closing down when it is already
closed down?
What would be the cause of this error and is there a solution? I've googled
and searched MS for this error, without luck.
ric

Hi ric.

There is a shut-down bug in WLMail that may be the cause of your problem, whereby wlmail.exe remains resident after exiting, and requires termination [End Process] through Windows Task Manager. It generally occurs when "Upload Larger Images to the Web When Sending a Photo E-mail" is *un-checked*, but it does not usually manifest until a new compose window, or a saved draft has been opened.

This option is available only when you are signed in, but if it is un-checked it still causes the shutdown bug even when not signed in.

So make sure the option "Upload Larger Images to the Web When Sending a Photo E-mail" is *checked* at: Tools->Options->Send [tab] (available only when signed into Windows Live through WLMail).

However, if you do find that "Upload Larger Images to the Web When Sending a Photo E-mail" is actually checked (which it is by default), then just uncheck it and click "Apply", then check it again and click "Apply" again. Some have had to do that to fix their WLMail shut down bug that was occurring despite that option having never been unchecked.

--
Cheers,
Peter
(Windows Vista Home Premium with Windows Live Mail 12.0.1606)
"There are more things in Heaven and earth, Horatio, than are dreamt of in your philosophy." - Shakespeare
---------------

"ric" <cooblob@xxxxxx> wrote in message news:BA2F7266-9CD7-4F71-9E26-18423FBA1C00@xxxxxx

"ric" <cooblob@xxxxxx> wrote in message
news:BA2F7266-9CD7-4F71-9E26-18423FBA1C00@xxxxxx
That is one buggy module. FWIW my most common crash
in it is at offset 0003c4f7. I haven't figured what I am doing
that causes it. I almost wish it would happen more frequently.
Then I might take the trouble to try and diagnose it.

One possibility is your compaction schedule is involved.
E.g. see if you have this checked:
Compact the database on shutdown every [1] runs
(in the Maintenance dialog, via the Options, Advanced tab)

Who knows? You would need at least a Stack Trace
to find out what modules were involved, e.g. uxcore.dll
sounds low level to me, so it's probably caused by a caller.
Then it would be best to have it with Symbols,
otherwise you are just getting these fairly meaningless
offset indicators. E.g. offsets would only be useful for
comparing whether your symptom was identical to someone
else's who had already done the necessary diagnosis for
that case.

If your symptom occurs more predictably you may want
to try doing some diagnosis. E.g. see if drwtsn32.exe
is capturing any information for your crash. Another easy
possibility would be capturing stack information using
ProcMon. E.g. just let ProcMon capture the crash event
and then open that record to see the list of modules involved.
Again, use of symbols in your formatting would be much more
informative than not. I'm not sure whether symbols are
available for WLMail and its modules or not.


HTH

Robert Aldwinckle
---

"Robert Aldwinckle" <robald@xxxxxx> wrote in message
news:#Ivlz7kiIHA.5780@xxxxxx
I tried the suggestion with the option "Upload Larger Images to the Web When
Sending a Photo E-mail", unselecting it, applying, and reselecting it. I
didn't have the error for 2 nights. Then I had it again last night, same
error. It always happens well after I have shutdown WLM and between midnight
and 1:50am, before any of my nightly tasks run (backup and updates).

My compaction schedule is set to the default of 100 runs.

When I get the error, there is a Windows message about having to shut down
WLM and prompting to send the information to MS. There is a stack trace in
that error report, very voluminous! Not much useful information, however.

--
ric

I've been getting this error for months upon months, despite moving to new
machines and fresh installations. WLM support haven't been much help other
than to tell me to start windows with no other services etc running and see
if it still occurs. Annoyingly there isn't anything I can do to reproduce
the crash, it just happens at random once, twice a day, sometimes not at all.
It could be RSS feed issues? HTML email issues? Who knows?
Very strange.

"Borntoclone" <Borntoclone@xxxxxx> wrote in message
news:AACFD143-0F37-4993-B040-73DDDAE7FDED@xxxxxx
Have you tried getting any of the diagnostics I suggested to
the OP?


---

Fiddler traces proved fruitless, there was no network traffic between exiting
WLM and it crashing 5-10 minutes later.
Asking to start WLM with no non-MS services running is not an issue since
this crash was occuring on a fresh installation of Windows with nothing else
except WLM installed.
This is a particularly buggy programme, there are numerous issues I have
with it other than the random crashes.

"Borntoclone" <Borntoclone@xxxxxx> wrote in message
news:38B99D78-E42A-4E96-9B86-202FCEAB561B@xxxxxx
I didn't suggest Fiddler.


I don't know what you are referring to.
Not something that I suggested either, I suspect.


Agreed. But if nobody tries to collect any diagnostics
it's unlikely to get any better... ; }


Robert
---

Well I clearly haven't understood who the "OP" is that I'm supposed to be
getting diagnostics, nor do I have any idea whether you're linked with WLM
development.

I've been in contact with WLM support who have suggested running fiddler
traces etc. If there is any way of collecting proper diagnostics that will
actually reveal something I am more than willing to do so and send them to
wherever they need to go.

"Borntoclone" <Borntoclone@xxxxxx> wrote in message
news:13CF6EDF-CD37-4FDB-8C16-E30B09B4B727@xxxxxx
OP is newsgroup shorthand for Opening Post
(or, depending on the context, Opening Poster).
So, in the latter case that would be the person you
were initially replying to (ric apparently).


I suggested getting a Stack Back Trace which corresponded
with the Error Signature which was provided. I also suggested
an alternative might be capturing ProcMon's record of the
crash event. E.g. it may at least record all the modules which
were involved in the calls which led up to crash, which is essentially
all we users can take advantage of as supplementary clues
about a crash. In fact, since then I have noticed that my
WLMail somehow suppresses Dr Watson's error handler
so I don't get the snapdump I was expecting to be able to browse,
so ProcMon's record may be the easiest way of getting such
details. The problem then is that in order to do that you have
to have ProcMon running before the crash occurs, so if it is not
a reliably reproducible event that may be too awkward to do.

However, the stated conditions that this crash occurs under
could make running ProcMon more practical. E.g. if the problem
only occurs soon after closing WLMail you could start ProcMon
before starting the close sequence and stop it as soon as the
crash occurs.


That would be irrelevant. I gave suggestions of what
I would do in the same circumstances as the OP.


I can't understand what they expect to see by running Fiddler.
What was the "etc"?


BTW what is it that you are trying to accomplish?
If you just want to avoid a late night crash after closing
the app, why not just Exit the app? E.g. right-click the
WLMail icon in the SysTray. Just don't try doing it
when a compaction is scheduled.


Good luck

Robert
---