Compact messages

Is OE open when you do that? If not, open it and leave it minimized in
the background. That might prevent the problem.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"CESDewar" <CESDewar RemoveThis @discussions.microsoft.com> wrote in message
news:87E1A51F-F936-4C3E-A859-B6B4B6CD2E58@microsoft.com...
>> Something screwy is going with OE after installing XP SP3 with some
>> people. Most people don't seem to be affected but a few are.
>
> I use a Visual Basic program to insert emails into Outlook Express
> using
> DoCmd.SendObject and every time that command is executed, OE *now* ups
> the
> compaction count, rendering this feature a pain as after 100 emails,
> it wants
> to compact the registry. I send out about 500 emails a day using VB,
> and now
> sit on the ESC key for 400 emails. After reading threads here it's
> clear that
> MS is not going to do anything about it, so I guess it's time to get
> dump
> SP3.
>
> It would be helpful if MS just LEFT this program alone. If they ARE
> going to
> have a programmer make changes, then rewrite this application to use a
> proper
> database that doesn't require this nonsense of compaction. Compaction
> was
> done in the 1970's because few programmers then knew how to structure
> databases that did not require compaction, but in the 1980's most
> learnt how
> to do that. That was 25 years ago

"CESDewar" <CESDewar RemoveThis @discussions.microsoft.com> escribió en el mensaje
news:87E1A51F-F936-4C3E-A859-B6B4B6CD2E58@microsoft.com...
>> Something screwy is going with OE after installing XP SP3 with some
>> people. Most people don't seem to be affected but a few are.
>
> I use a Visual Basic program to insert emails into Outlook Express using
> DoCmd.SendObject and every time that command is executed, OE *now* ups the
> compaction count, rendering this feature a pain as after 100 emails, it
> wants
> to compact the registry. I send out about 500 emails a day using VB, and
> now
> sit on the ESC key for 400 emails. After reading threads here it's clear
> that
> MS is not going to do anything about it, so I guess it's time to get dump
> SP3.
>
> It would be helpful if MS just LEFT this program alone. If they ARE going
> to
> have a programmer make changes, then rewrite this application to use a
> proper
> database that doesn't require this nonsense of compaction. Compaction was
> done in the 1970's because few programmers then knew how to structure
> databases that did not require compaction, but in the 1980's most learnt
> how
> to do that. That was 25 years ago

Well, now I can't find who had suggested to install Registry Monitor from
Sysinternals.com, but in my case - WinXP, SP3, regular use of Outlook Express
- I clearly see that each 2o secs the NMIndexStoreSvr (service?) queries the
value: "Compact Check Count', and sets a new value here, incrementing by one.
When the value reaches 100 (decimal), the annoying message prompt re-appears.
I have one crucial question here: what side effects are to be expected by
stopping the service which triggers the counter update in background, causing
that after a little longer than half an hour after compacting we see the
message again? What is the service name to look for in computer management? I
am aware that this is not solving the root cause, but it is obvious that
though SP3 is one thing in common of these problems, they are triggered by
co-incidental influence of many other codes...

"Michael Santovec" wrote:

> Something screwy is going with OE after installing XP SP3 with some
> people. Most people don't seem to be affected but a few are.
>
> Several other programs have been implicated, but even then, not everyone
> with those programs are affected.
>
> --
>
> Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm
>
>
>
> "Opinicus" <gezgin.DeleteThis@spamcop.net> wrote in message
> news:eUfk#ZA2IHA.2068@TK2MSFTNGP05.phx.gbl...
> > "Michael Santovec" <michael_santovec.DeleteThis@prodigy.net> wrote
> >
> >>>> That it keeps coming up indicates that something on your system is
> >>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
> >>>> problem,
> >>>> you need to determine what is causing that.
> >
> > 8<!
> >
> >> But since XP SP3, we've been seeing some issues where various other
> >> programs are triggering the problem.
> >
> > Just curious but what other programs would open and close OE and why?
> >
> > --
> > Bob
> > http://www.kanyak.com
> >
> >
> >
>
>

NMIndexStoreSvr is a Nero plug-in and is one known cause for this behavior:

• Various & sundry anti-virus applications (including Norton);
• Various & sundry anti-spyware applications;
• Various & sundry third-party firewalls;
• Any/all of the above running when WinXP SP3 was installed;
• IBM Rapid Access keyboard (driver) RAKDLL.DLL;
• Nero plug-in(s);
• Windows Desktop Search is installed;
• Windows Live Mail is or had been installed;
• Disk defragmentation, need for;
• Using Visual Basic DoCmd.SendObject command to create an email;
• Using any number third-party applications (e.g., accounting software) to
send emails by via Outlook Express;
• MailWasher; and/or
• Programatically opening EML files while OE is closed (e.g., creating a
New Message via Address Book).

See this recent discussion about the problem:
http://groups.google.com/group/microsoft.public.outlookexpress.general...owse_fr
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


Dachshound wrote:
> Well, now I can't find who had suggested to install Registry Monitor from
> Sysinternals.com, but in my case - WinXP, SP3, regular use of Outlook
> Express - I clearly see that each 2o secs the NMIndexStoreSvr (service?)
> queries the value: "Compact Check Count', and sets a new value here,
> incrementing by one. When the value reaches 100 (decimal), the annoying
> message prompt re-appears. I have one crucial question here: what side
> effects are to be expected by stopping the service which triggers the
> counter update in background, causing that after a little longer than half
> an hour after compacting we see the message again? What is the service
> name
> to look for in computer management? I am aware that this is not solving
> the
> root cause, but it is obvious that though SP3 is one thing in common of
> these problems, they are triggered by co-incidental influence of many
> other
> codes...
>
> "Michael Santovec" wrote:
>
>> Something screwy is going with OE after installing XP SP3 with some
>> people. Most people don't seem to be affected but a few are.
>>
>> Several other programs have been implicated, but even then, not everyone
>> with those programs are affected.
>>
>> --
>>
>> Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm
>>
>>
>>
>> "Opinicus" <gezgin RemoveThis @spamcop.net> wrote in message
>> news:eUfk#ZA2IHA.2068@TK2MSFTNGP05.phx.gbl...
>>> "Michael Santovec" <michael_santovec RemoveThis @prodigy.net> wrote
>>>
>>>>>> That it keeps coming up indicates that something on your system is
>>>>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>>>>>> problem,
>>>>>> you need to determine what is causing that.
>>>
>>> 8<!
>>>
>>>> But since XP SP3, we've been seeing some issues where various other
>>>> programs are triggering the problem.
>>>
>>> Just curious but what other programs would open and close OE and why?
>>>
>>> --
>>> Bob
>>> http://www.kanyak.com

That is the Nero Scout program. If you don't have the documentation,
you can get it here:

ftp://ftp6.nero.com/user_guides/nero8/scout/NeroScout_Enu.pdf

There is an option to exclude selected file types from Indexing. Be
sure to add
..DBX;.EML;.NWS;

to the list so that it doesn't try indexing OE files.

Let us know if that helps.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"Dachshound" <Dachshound.DeleteThis@discussions.microsoft.com> wrote in message
news:E87242F0-DD88-4178-AD2C-06C7B21A395E@microsoft.com...
> Well, now I can't find who had suggested to install Registry Monitor
> from
> Sysinternals.com, but in my case - WinXP, SP3, regular use of Outlook
> Express
> - I clearly see that each 2o secs the NMIndexStoreSvr (service?)
> queries the
> value: "Compact Check Count', and sets a new value here, incrementing
> by one.
> When the value reaches 100 (decimal), the annoying message prompt
> re-appears.
> I have one crucial question here: what side effects are to be expected
> by
> stopping the service which triggers the counter update in background,
> causing
> that after a little longer than half an hour after compacting we see
> the
> message again? What is the service name to look for in computer
> management? I
> am aware that this is not solving the root cause, but it is obvious
> that
> though SP3 is one thing in common of these problems, they are
> triggered by
> co-incidental influence of many other codes...
>
> "Michael Santovec" wrote:
>
>> Something screwy is going with OE after installing XP SP3 with some
>> people. Most people don't seem to be affected but a few are.
>>
>> Several other programs have been implicated, but even then, not
>> everyone
>> with those programs are affected.
>>
>> --
>>
>> Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm
>>
>>
>>
>> "Opinicus" <gezgin.DeleteThis@spamcop.net> wrote in message
>> news:eUfk#ZA2IHA.2068@TK2MSFTNGP05.phx.gbl...
>> > "Michael Santovec" <michael_santovec.DeleteThis@prodigy.net> wrote
>> >
>> >>>> That it keeps coming up indicates that something on your system
>> >>>> is
>> >>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>> >>>> problem,
>> >>>> you need to determine what is causing that.
>> >
>> > 8<!
>> >
>> >> But since XP SP3, we've been seeing some issues where various
>> >> other
>> >> programs are triggering the problem.
>> >
>> > Just curious but what other programs would open and close OE and
>> > why?
>> >
>> > --
>> > Bob
>> > http://www.kanyak.com
>> >
>> >
>> >
>>
>>

Thanks guys, it helped immediately to fix the annoying behaviour. For
simplicity I followed the advice of Michael Santovec, and specified the three
file extensions in Nero Scout program for excluding from Indexing job. Since
that very moment the NMIndexStoreSvr stopped to update the Compact Check
counter value in registry, and the message disappeared. Thanks again - if
only the same symptoms caused by different codes are so easy to fix. Very
useful advice!

"Michael Santovec" wrote:

> That is the Nero Scout program. If you don't have the documentation,
> you can get it here:
>
> ftp://ftp6.nero.com/user_guides/nero8/scout/NeroScout_Enu.pdf
>
> There is an option to exclude selected file types from Indexing. Be
> sure to add
> ..DBX;.EML;.NWS;
>
> to the list so that it doesn't try indexing OE files.
>
> Let us know if that helps.
>
> --
>
> Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm