Scheduler service for Domino backup failing after upgrade

[rpandey]

Hi
Recently i have upgraded Domino Server to Level: 11.0.1.4 Build: 452, BA Client v8.1.13.3 and DP for Dom v8.1.13.0. After upgrade Scheduler is failing with below error

================
Executing scheduled command now.
03/07/2022 21:00:29
Executing Operating System command or script:
C:\Progra~1\tivoli\tsm\domino\domarc.cmd
03/07/2022 21:00:33 Finished command. Return code is: -1
03/07/2022 21:00:33 ANS1909E The scheduled command failed.
03/07/2022 21:00:33 ANS1512E Scheduled event 'NON_PROD_DAILY_DOM_ARC' failed. Return code = -1.

==================

But Scheduler is running on foreground mode fine and backup complete successfully.

Can any one please help me to resolve this issue?

 

[marclant]

From the error below, it's failing because the last command in C:\Progra~1\tivoli\tsm\domino\domarc.cmd had a non-zero return code, in this case it was -1. So you'll have to review this script to see what the last command was, and the output file generated by that script if there's one to troubleshoot further.

Executing Operating System command or script:
C:\Progra~1\tivoli\tsm\domino\domarc.cmd
03/07/2022 21:00:33 Finished command. Return code is: -1
03/07/2022 21:00:33 ANS1909E The scheduled command failed.

 

[rpandey]

Hi
Thanks for you feedback.

Here is the the script that use for the command. Seems nothing wrong with the script

@ECHO OFF
rem ==================================================================
rem Sample Command File - domarc.smp
rem
rem Sample command file containing commands to do a scheduled archive
rem of transaction logs to an IBM Tivoli Storage Manager server.
rem
rem This file is meant to be executed by the IBM Tivoli Storage Manager
rem central scheduler in response to a defined schedule on the IBM
rem Tivoli Storage Manager server.
rem
rem Complete paths must be given for all file names and non-system
rem commands.
rem
rem Copy this file to domarc.cmd and edit it to match your
rem local environment.
rem
rem ==================================================================

rem ==================================================================
rem Replace "X:" with the drive where the Data Protection for Lotus
rem Domino is installed.
rem ==================================================================

set dom_dir="C:\Program Files\Tivoli\TSM\domino"

cd /d %dom_dir%

rem ==================================================================
rem The 2 lines below put a date and time stamp in a log file for
rem you.
rem
rem Note: You can change "domarc.log" to whatever you prefer.
rem ==================================================================
echo Current date is: >> domarc.log
date /t < NUL >> domarc.log
echo Current time is: >> domarc.log
time /t < NUL >> domarc.log

rem ==================================================================
rem Now call the command line to do the archive of the logs:
rem
rem Note: You can change "domasch.log" to whatever you prefer.
rem ==================================================================
domdsmc archivelog /adsmoptfile=dsm.opt /logfile=domasch.log >> domarc.log

set RC=%ERRORLEVEL%
echo --------------------- >> domarc.log
echo Return code was %RC% >> domarc.log
echo ===================== >> domarc.log
exit %RC%

 

[marclant]

I didn't say that there was a problem with the script, but rather with one of the commands in the script.

This script ends with: exit %RC%, so this is the -1 you get here:

03/07/2022 21:00:33 Finished command. Return code is: -1

%RC% is set by set RC=%ERRORLEVEL%.
%ERRORLEVEL% is the return code of the previous command.

The previous command is:

domdsmc archivelog /adsmoptfile=dsm.opt /logfile=domasch.log >> domarc.log

So you will need to look at domasch.log and domarc.log to see why it finished with a return code of -1 instead of 0.

 

[rpandey]

Here is output log file. But if i run scheduler on foreground works perfectly

domasch.log

28-03-2022 05:00:32 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 05:00:32 ============== No log entries pruned
28-03-2022 06:00:22 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 06:00:22 ============== No log entries pruned
28-03-2022 07:00:14 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 07:00:14 ============== No log entries pruned
28-03-2022 08:00:14 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 08:00:14 ============== No log entries pruned
28-03-2022 09:00:14 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 09:00:14 ============== No log entries pruned
28-03-2022 10:00:13 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 10:00:13 ============== No log entries pruned
28-03-2022 11:00:14 ============== Log file pruned using log retention period of 60 day(s)
28-03-2022 11:00:14 ============== No log entries pruned



domarc.log

Current date is:
Mon 28/03/2022
Current time is:
02:00 PM

IBM Spectrum Protect for Mail:
Data Protection for HCL Domino
Version 8, Release 1, Level 13.0
(C) Copyright IBM Corporation 1999, 2021. All rights reserved.

ACD5221I The C:\Program Files\Tivoli\TSM\domino\domasch.log log file has been pruned successfully.

ACD0004E An unknown error has been detected.
Warning! Error initializing the connection to the TDP library

Initialization failed
---------------------
Return code was -1
=====================

 

[marclant]

Here is output log file. But if i run scheduler on foreground works perfectly

When you run it in the foreground, are you logged in as the same account that the Scheduler service logs in under? By default, I think it uses the System account and so that access would be different then when you are logged in as a user.

 

[rpandey]

If i run on background under system account scheduler services is failing. works fine if i run on foreground mode. Anyway i have logged case with IBM, It is with development team. Taking toooooooo long time for the feedback as it is IBM way every one knows.

Regards,
Ramesh Pandey