• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TDPExchange - ACN0520E Failed to connect to Local DSMAGENT Node



We are having an issue with 2 seperate Exchange servers, where the Client Acceptor isnt working properly.

Enviroment Info:
TSM Server:
OS: Windows Server 2016

Exchange Server:
Exchange 2016 CU6
Windows Server 2016
TDPExchange -

Our issue is that after we finish installing TDPExchange (with no error codes in the log, or in the eventviewer), we arent able to query the exchange server running this command: tdpexcc query exchange
The specific error code is:

ACN5229E An error occurred while obtaining VSS information from the following Local DSMAgent Node: 'TSMEXCH01'.
ACN0520E Failed to connect to Local DSMAGENT Node 'TSMEXCH01' at address:port ''. Verify that the client acceptor is installed, configured, and running properly.

The Client Acceptor is running with a service account, that has Organization Management and local administrative permissions on the server.
Also when telnetting to the dynamic port, we are able to see that the port is open.

The following entries are found:

dsmerror.log (Baclient)
08/23/2017 14:10:02 ANS0361I DIAG: cuGetSignOnAuthEx(): Error -50 receiving a verb.
08/23/2017 14:29:48 ANS0361I DIAG: cuGetSignOnAuthEx(): Error -50 receiving a verb.

dsmwebcl.log (Baclient)

08/23/2017 14:10:00 (dsmagent) IBM Spectrum Protect
08/23/2017 14:10:00 (dsmagent) Remote Client Agent - Built Nov 11 2016 18:05:27
08/23/2017 14:10:00 (dsmagent) Version 8, Release 1, Level 0.0
08/23/2017 14:10:02 (dsmagent) ANS3002I Session started for user TSMEXCH01_EXCHANGE (TCP/IP
08/23/2017 14:29:48 (dsmagent) ANS3002I Session started for user TSMEXCH01_EXCHANGE (TCP/IP
08/23/2017 14:30:05 (dsmagent) ANS3007I IBM Spectrum Protect Remote Client Agent terminating - idle for 20 minutes.

Cant seem to find an solution to this one :(
Any help would be much appreciated!

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 16.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 32 58.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 16.4%
  • Other (please comement)

    Votes: 5 9.1%

Forum statistics

Latest member