ADSM-L

Re: Return Code

1998-08-12 07:42:09
Subject: Re: Return Code
From: Post Jan <Post_Jan AT DELAWARE-COMPUTING DOT COM>
Date: Wed, 12 Aug 1998 13:42:09 +0200
Dell,

Currently I'm using the FIXTEST - Version 1.1.1.1"A", but the service is
also loged in as the exchange Site Service Account, with local Admin
authority.
The whole thing was running perfect untuil I newly installed my Exchange
server.

There are no entries in the dsierror.log and the excdsm loggin files related
to the mentioned problem. It seems the only entry I can find in any log-file
is the one I posted in my e-mail earlier. So on that point I can not give
you any more information. There are no erros in the NT server eventlog.

Schedular log:
=========================================================
08/11/1998 17:54:48 TCP/IP accepted connection from server.
08/11/1998 17:54:49 Querying server for next scheduled event.
08/11/1998 17:54:50 Node Name: DCZEXCHG
08/11/1998 17:54:50 Session established with server ADSM: MVS
08/11/1998 17:54:51   Server Version 2, Release 1, Level 0.13
08/11/1998 17:54:51   Server date/time: 08/11/1998 18:00:08  Last access:
08/11/1998 14:27:07

08/11/1998 17:54:51 --- SCHEDULEREC QUERY BEGIN
08/11/1998 17:54:51 --- SCHEDULEREC QUERY END
08/11/1998 17:54:51 Next operation scheduled:
08/11/1998 17:54:51
------------------------------------------------------------
08/11/1998 17:54:51 Schedule Name:         EXCHANGE_INCREMENTAL
08/11/1998 17:54:51 Schedule Name:         EXCHANGE_INCREMENTAL
08/11/1998 17:54:51 Action:                Command
08/11/1998 17:54:51 Objects:               c:\excincr.cmd
08/11/1998 17:54:51 Options:
08/11/1998 17:54:51 Server Window Start:   18:00:00 on 08/11/1998
08/11/1998 17:54:51
------------------------------------------------------------
08/11/1998 17:54:51
08/11/1998 17:54:51
Executing scheduled command now.
08/11/1998 17:54:52
Executing Operating System command or script:
   c:\excincr.cmd
08/11/1998 17:54:57 Finished command.  Return code is:
   128
08/11/1998 17:54:57 Scheduled event 'EXCHANGE_INCREMENTAL' completed
successfully.
08/11/1998 17:54:57 Sending results for scheduled event
'EXCHANGE_INCREMENTAL'.
08/11/1998 17:54:57 Results sent to server for scheduled event
'EXCHANGE_INCREMENTAL'.

08/11/1998 17:54:57 ANS1483I Schedule log pruning started.
08/11/1998 17:54:57 Schedule Log Prune: 242 lines processed.  0 lines
pruned.
08/11/1998 17:54:57 Pruned lines saved to
c:\adsm32\agentexc\logs\dsmsched.pru.
08/11/1998 17:54:57 ANS1484I Schedule log pruning finished successfully.
08/11/1998 17:54:57 Querying server for next scheduled event.
08/11/1998 17:54:57 Node Name: DCZEXCHG
08/11/1998 17:54:57 Session established with server ADSM: MVS
08/11/1998 17:54:57   Server Version 2, Release 1, Level 0.13
08/11/1998 17:54:57   Server date/time: 08/11/1998 18:00:16  Last access:
08/11/1998 18:00:09

08/11/1998 17:54:57 --- SCHEDULEREC QUERY BEGIN
08/11/1998 17:54:57 --- SCHEDULEREC QUERY END
08/11/1998 17:54:58 Next operation scheduled:
08/11/1998 17:54:58
------------------------------------------------------------
08/11/1998 17:54:58 Schedule Name:         EXCHANGE_INCREMENTAL
08/11/1998 17:54:58 Schedule Name:         EXCHANGE_INCREMENTAL
08/11/1998 17:54:58 Action:                Command
08/11/1998 17:54:58 Objects:               c:\excincr.cmd
08/11/1998 17:54:58 Options:
08/11/1998 17:54:58 Server Window Start:   18:00:00 on 08/12/1998
08/11/1998 17:54:58
------------------------------------------------------------
08/11/1998 17:54:58 Waiting to be contacted by the server.
08/11/1998 17:54:58 Waiting to be contacted by the server.
=================================================================


The problem seems to only occure with a scheduled event.

The excincr.cmd commands suggested in apendix C are indeed executed on the
scheduled event. So everything is set up as in Apendix C is stated.


Jan


On ADSM: Dist Stor Manager, Del Hoobler[SMTP:hoobler AT US.IBM DOT COM] wrote:
> Jan,
>
> It's hard to tell from your description what is going on.
> The normal problem when running the Exchange Agent backups
> from a scheduled event is that the NT service that is running
> the scheduler is not running with the proper authority to
> perform the backup of Microsoft Exchange.  If you are running
> the GA version (1.1.0.0), you need to be running the
> scheduled NT service "logged in" as the Exchange Site Services Account.
> If you are running the FIXTEST version (1.1.0.0 "A"), then
> you need to be running from an account with local Admin authority.
> Can you run the backup script from a DOS prompt OK?
> If so, try changing the "Control Panel/Services/Startup/Log On As"
> value to match the account you are logged in as.
>
> Are the problems only occurring when you run as a scheduled event?
> The RC=128 depends on where the RC is coming from, i.e. ADSM API,
> the scheduler, Exchange Server... (check dsierror.log, excdsm.log)
> Please read Appendix C (starting on page 55) of the
> Exchange Agent User's Guide very closely for details on setting
> up automated scheduling of the Exchange Agent backups.
>
> If after reading Appendix C, you still cannot get it to work,
> provide more details on the error that you are receiving
> and post info to this list or call IBM support.  Thanks.
>
> Del Hoobler
> ADSM Agent Development
>
>
> >> Dear All,
> >>
> >> Can anyone inform me what the return code 128 means.
> >>
> >> I get this in the logging from the ASM agent for MS Exchange after I
> >> scheduled an incremental backup. Nothing is backuped and there is only
> >> information in the schedular log and not in any other log of this
backup.
> >>
> >> Jan
> >>
> >> > Delaware Computing Group
> >> > Delaware Infrastructure Management
> >> > Blokkestraat 29A
> >> > B-8550 Zwevegem
> >> > Phone    +32-56-76.76.00
> >> > Direct    +32-56-76.76.52
> >> > Fax         +32-56-76.77.93
> >> > E-mail        post_jan AT delaware-computing DOT com
> >> > URL   http://www.delaware-computing.com
> >> >
> >> >
<Prev in Thread] Current Thread [Next in Thread>