The "Remote Client Agent" is not relevant to performing scheduled backups, 
which would make sense that the reporting says the job is successful.  Are you 
saying there is another reason to believe the db backups are failing?

Otherwise, this error just indicates that the webclient wasn't started, which 
shouldn't affect anything other than the web client (The java client that 
listens on port 1581 (by default)) 

I run into this error when I have "MANAGEDServices webclient" in the opt file 
but I didn't install the remoteagent (dsmcutil install remoteagent...)  I 
usually don't use this client and just remove the "webclient" from the optfile 
to suppress the error.



Regards, 
Shawn
________________________________
Shawn Drew

> -----Original Message-----
> From: ADSM-L AT VM.MARIST DOT EDU [mailto:ADSM-L AT VM.MARIST DOT EDU]
> Sent: Friday, March 07, 2014 5:17 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] What is the newest client version supported on
> Windowsserver 2003?
> 
> I don't have the PMR numbers as a co-worker is working with IBM on the
> issue.  We are trying to use TSM DP SQL 6.3.1 and are seeing this error:
> 
> ANS2619S (RC2036) The Client Acceptor Daemon was unable to start the
> Remote Client Agent.
> 
> Despite this being a "severe error" the backups were still being reported
> as "successful" to the TSM server.  We found this while trying to upgrade
> old clients that are still running TSM 5.5 (which is EOL soon). If we
> remove and re add the services it seems to help but the problem always
> comes back.
> 
> 
> On Fri, Mar 7, 2014 at 3:52 PM, Dave Canan <ddcanan AT gmail DOT com> wrote:
> 
> > Tom, can you give a brief description of the database backup issues
> > you've been working on with IBM? Do you have PMR numbers I could review?
> >
> > Dave Canan
> > IBM TSM Performance
> > 916-723-2410
> > Office hrs: 9:00 - 5:00
> >
> > -----Original Message-----
> > From: "Tom Alverson" <tom.alverson AT GMAIL DOT COM>
> > Sent: 3/7/2014 11:29 AM
> > To: "ADSM-L AT VM.MARIST DOT EDU" <ADSM-L AT VM.MARIST DOT EDU>
> > Subject: Re: [ADSM-L] What is the newest client version supported on
> > Windowsserver 2003?
> >
> > We have been forced onto 7.x to support our 2012R2 servers (that is
> > the only client that is supported) but apparently still need 6.3.x for
> > Windows
> > 2003 (which still has over a year of support left from Microsoft).  We
> > may go to 6.4.x or 7.x on 2008/2012 servers if it will cure our
> > database backup issues (which we have been working with IBM for a few
> > months on).  I have a funny feeling that 7.x would work on 2003 but we
> > do not want any unsupported scenarios for backups.
> >
> > Tom
> >
> >
> > On Fri, Mar 7, 2014 at 1:28 PM, J. Pohlmann <jpohlmann AT shaw DOT ca> 
> > wrote:
> >
> > > Last one is 6.3.1.2 on the ftp site. I agree, I wish IBM C&SI
> > > (former
> > > Tivoli) would keep on supporting Windows 2003 a bit longer, like
> > > into v7.1+.
> > >
> > > Regards,
> > >
> > > Joerg Pohlmann
> > >
> > > -----Original Message-----
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > > Behalf Of Tom Alverson
> > > Sent: Friday, March 07, 2014 10:18
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: [ADSM-L] What is the newest client version supported on
> > > Windows server 2003?
> > >
> > > I can't make sense of the IBM web page with the compatibility matrix.
> >  What
> > > is the highest version client that is supported for Windows 2003
> > > server
> > for
> > > both the standard BACLIENT and also the TDP database client?   We are
> > > having a lot of problems with the TDP 6.3.1 client and were hoping
> > > that moving to BAC 6.4.0.1 / TDP 6.4.1.3 would help but it appears
> > > that will only work on Server 2008?
> > >
> > > Tom
> > >
> >


This message and any attachments (the "message") is intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord 
with its purpose, any dissemination or disclosure, either whole or partial, 
is prohibited except formal approval. The internet can not guarantee the 
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) 
not therefore be liable for the message if modified. Please note that certain 
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.