Check the dsmerror.log on the client, it may give furthe info.
If I had to guess I would suggest that the dir/file you want to archive
doesn't exist or the dir is empty.I have experienced a similar error
when using archive and specified a dir that doesn't exist.

Regards
Laurie

> -----Original Message-----
> From: Wade Huang [SMTP:Weigang_Huang/CAM/Lotus AT LOTUS DOT COM]
> Sent: Tuesday, April 14, 1998 10:18 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Archive Failed
>
> Hi, All,
>
> I tried to use the ADSM server Centrol Scheduler to schedule an
> archive
> through Immediate Client Actions, objects -> c: d:  Action -> ARCHIVE,
> and
> got the following message from the server activity log and the archive
> failed.
>
> ======================================================================
> =====
> =
> ====
> Actitvity Log
> -------------
> Date and Time       Message
>
> ----------------------------------------------------------------------
> -----
> -
> ----------------------------------------
> 04/13/1998 20:48:29 ANR2500I Schedule @27 defined in policy domain
> STANDARD.
> 04/13/1998 20:48:29 ANR2510I Node CAMDYSHUB01 associated with schedule
> @27
> in policy domain STANDARD.
> 04/13/1998 20:48:29 ANR2505I 1 schedules were defined for DEFINE
> CLIENTACTION.
>
> 04/13/1998 20:53:01 ANR2561I Schedule prompter contacting CAMDYSHUB01
> (session 29) to start a scheduled operation.
> 04/13/1998 20:53:04 ANR0406I Session 30 started for node CAMDYSHUB01
> (WinNT) (Tcp/Ip 9.95.97.196(4049)).
> 04/13/1998 20:53:05 ANR0484W Session 30 for node CAMDYSHUB01 (WinNT)
> terminated - protocol violation detected.
>
>
> I can archive the same files through the ADSM Backup Client(GUI)
> without
> any problem.
>
> Any idea what caused this?  Any help will be much appreciated!
>
> I am running ADSM for AIX server version 3.1.1.1 and ADSM for NT
> client
> version 3.1.0.3, communication -> TCPIP.
>
> Regards,
> Wade