If the application is not known, NSD can
be configured to collect information on all processes running on the box
(not just Domino processes) when a crash occurs. The offending application
will then be identified.
Notice that a standard NSD will not collect the necessary information to
find the offending application, and if configured to do so, will take longer
to execute during any crash. To enable NSD to include all processes which
are accessing files, use the ALLHANDLES option with NSD. Locate the
NSD.INI file (not the NOTES.INI file) in the DATA directory and add the
line:
ALLHANDLES=1
...followed by a carriage return. Save
the file. (This may be done while Domino is up.) When NSD next
runs, it will now include all applications on the box in the data collection.
When NSD is used with the ALLHANDLES option, it will take longer to run,
due to the additional data collection required. This could result
in NSD timing out if the maximum time set in the Server Document is exceeded.
In the Server Document section labeled, "Automatic Server
Recovery, Cleanup Script/NSD Maximum Execution Time: " the default
value is 300 seconds (5 minutes). While it is impossible to know
exactly how long NSD will run, a value of 600 seconds (10 minutes) is unlikely
to be reached and would be suggested to be set.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There is also outside tools that can be used to track what is touching
the Domino Files.
Microsoft Process Monitor:
Setup Process Monitor to track the Data directory Example (D:\Notes\Data)
& (G:\Notes\Data). Instructions:
A. Download process monitor:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
B. Click on Filter, then Filter...:
C. Remove all pre-existing entries in the filter.
D. Setup the filter like so:
E.Setup
process monitor to store its data to a file on the disk&
not the Page File as this will cause severe performance issues. To
do this, click on File, then Backing Files.... Then select "use
file named" and create a file to capture the Process Monitor. Make
sure you are disconnected at this point. Then restart the program
and click on Capture. The
bottom of the program should say backed by "xxxxxxx.plm" rather
than page file.
F. Lastly, select the "Drop Filtered Events"
option under the Filter tab, it will configure Process Monitor to delete
any data that's excluded by a filter at the time the data is captured.
This should limit the amount of disk space needed for the PLM file.
Some additional things to note :
If you are running Anti-virus and full OS backups and you want to make
sure that the Antivirus is not scanning the Data Folder, and excludes the
.txn & lfh file
& nsf. You also want
to make sure when completing full OS backups that they exclude the entire
Transactional log folder as this has been known to cause this issue as
well. If you need assistance with setting your OS Backups to exclude these
files from being touched you can open a ticket with backup vendor to discuss
exclusions. The
only way backups should run on the TXN files is by using the Notes API.
Nothing else should touch anything in that folder while Domino is up and
running. Most commonly that means your OS level backup and OS level anti-virus
programs should exclude the TXN directory.