I had the same problem with a user.  We are now at the point where a Backup
Schedule with ACTION=command and OBJECTS=sqldsmc etc., activates a session.
Now it disconnects immediately with a protocal violation.  The machine's
owner cannot find an error log for the node, so if anyone could help with
that.

>Hi.
>
>We are trialing the ADSM Connect Agent for MS SQL.
>
>We can't get the NT Scheduling Service to do a SQL
>backup.  It performs a regular ADSM incremental backup
>when we schedule a backup from the ADSM Server.
>
>What is the secret to get the NT Service to perform a SQL
>Connect Agent backup instead of a Windows32 client backup?
>
>Thanks in advance.
>Mike Martin
>Baptist Health System of East TN

Fred Johanson
System Administrator
SEA
NSIT
University of Chicago
773-702-8464