Unsolved
This post is more than 5 years old
22 Posts
0
585
October 7th, 2008 02:00
NML aborts for different databases
Hallo,
we use NML 3.0.1 with latest hotfix. Backup aborts for databases. It is random which database aborts the backup. Notes server is linux, backup server is
W2k3. Networker client and server is 7.2.2 with jumbo patch. NSR_SKIPDBERRORS=TRUE does not apply since it is a critical error. Unfortunately no debug is generated. Has anybody some suggestion to solve
this problem?
regards
Bernd
we use NML 3.0.1 with latest hotfix. Backup aborts for databases. It is random which database aborts the backup. Notes server is linux, backup server is
W2k3. Networker client and server is 7.2.2 with jumbo patch. NSR_SKIPDBERRORS=TRUE does not apply since it is a critical error. Unfortunately no debug is generated. Has anybody some suggestion to solve
this problem?
regards
Bernd
0 events found
No Events found!


amediratta
2 Intern
•
2K Posts
0
October 7th, 2008 04:00
Mostly debug level 3 generates sufficient errors and should be suitable to begin with.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
October 7th, 2008 14:00
However, if these aborts are caused out of blue without any ROC errors then I would focus on Domino side and have Domino running in debug (which Domino admin won't like for sure). If you see aborted message given to module it means Notes API has returned that.
BerndG_42aac9
22 Posts
0
October 9th, 2008 03:00
but not debug was generated.
regards
Berd
amediratta
2 Intern
•
2K Posts
0
October 9th, 2008 09:00
NSR_DEBUG_LEVEL = 3
NSR_DEBUG_FILE = "C:\bkp_log.txt"
This will generate c:\bkp_log.txt on the client.