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/micro...d35fbfa457fd6f
--
~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 he 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" wrote in message
...
"Michael Santovec" 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