I was trying to Run compact -a mail\xxxxxxxx.nsf on Server to test new Policy that I’ve just created.
When I issue the command line, I get:
Archiving mail\xxxxxxxx.nsf
Pushing mail\xxxxxxxx.nsf to server ServerName/Domain a_archive\a_xxxxxx.nsf
and CRASH (-NSD)
I’ve stopped router and antigen task before trying it again. But I’ve got the same result.
Have anyone experienced this problem before or am I doing something wrong?
Subject: Compact -a mail\xxxxx.nsf Crashing the Server
You need to analyze the contents of the output in the NSD file which was generated to learn more details as to the nature of the crash -
See the following URL for the PDF of Best Practices Practices RIP and NSD Analysis
http://media.lotus.com/lotusphere2004/bp/bp106.pdf
Search the NSD file and find the crashing thread - search for key word “Fatal” which is the most common indication of the crashing task If you don’t find fatal, look for “Panic”, “Access Violation” or “Segmentation Fault”, “Signal” messages. Then analyze the calls in the call-stack and search support KB for related articles.
Hope this helps…
Fletcher
Subject: RE: Compact -a mail\xxxxx.nsf Crashing the Server
Thanks Fletcher. this is going to be extremelly usefull.
Cristina