2
2012
ACO0156E Could not load the Tivoli Storage Manager API
After installing TDPv5.5.1 on SQL Server 2000 as per following link , TDP GUI should work fine, but in case you uninstall and reisnatll TDP client then you may start facing below issue while opening up TDP GUI,
In addition to above, you may see other error as below,
After researching in IBM documentation, found following link which provides information on this error,
ACN0156E: Could not load the Tivoli Storage Manager API.
Explanation
The Tivoli Storage Manager API could not be loaded.
User response
Ensure the Tivoli Storage Manager API is correctly installed. Run the Data Protection for Microsoft SQL Server application client with the /TRACEFLAGS=API /TRACEFILE=filename options and view the tracefile to determine why it could not be loaded. Another possible cause is that the TSMAPI.DLL does not exist in the system directory. Re-install the Tivoli Storage Manager API, if this is the case.
When we reran tdp gui it with trace option, we got error as,
——–
03/02/2012 10:22:46.121 [002808] [1564] : dsmapid.cpp ( 622): ERROR: could not load tsmapi.dll. It is not in PATH
03/02/2012 10:22:46.121 [002808] [1564] : dsmapid.cpp ( 630): Exit DDsmApiDL::loadAdsmDll()
03/02/2012 10:22:46.121 [002808] [1564] : dsmapid.cpp ( 528): Exit DDsmApiDL::Setup(), rc = 104
03/02/2012 10:22:49.856 [002808] [1564] : dsmapi.cpp ( 565): Enter DDsmApi::Term()
03/02/2012 10:22:49.856 [002808] [1564] : dsmapi.cpp ( 569): dsmSetup not done, dsmCleanUp will not be done
———
Even after correcting path, no progress. So we requested TSM vendor to reinstall Tivoli Storage Manager API to fix this issue.
Once Tivoli Storage Manager API is installed, this issue was fixed.
Other links:
http://ezbdist.cit.cornell.edu/techsup-v5.4/ibmdocs/messages/html/anrcms5875.htm
References:
http://www.cryer.co.uk/brian/windows/trbl_nt_prcentptcnbl.htm
http://support.microsoft.com/kb/142606

Related Posts
Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5