OnDemand User Group

Support Forums => MP Server => Topic started by: teera_aoo on June 03, 2019, 08:11:46 PM

Title: Cannot start CMOD 10.1 with TSM 8.1
Post by: teera_aoo on June 03, 2019, 08:11:46 PM

I cannot start CMOD 10.1 with TSM 8.1. There is error in ARCHIVE.trace.log

SM Error: ANS0238E (RC2041) The sequence of calls is invalid., Return Code=2041, Reason=0, File=arssmsms.cpp, Line=2440  Srvr->[SERVERNAME]<-

I opened PMR for 2 Weeks and no progress. Do have anyone ever seen this?

Thanks.

Title: Re: Cannot start CMOD 10.1 with TSM 8.1
Post by: Justin Derrick on June 04, 2019, 06:16:50 AM

What do the TSM logs say?

Check the CMOD wiki troubleshooting page too:  https://cmod.wiki/index.php?title=Main_Page#IBM_CMOD_Troubleshooting

-JD.

Title: Re: Cannot start CMOD 10.1 with TSM 8.1
Post by: jsquizz on June 04, 2019, 07:02:04 AM

Found this on developer.ibm.com -

Researched the error shared: Error: Connector exited with error:
'ANS0238E (RC2041) The sequence of calls is invalid.' and found the
following explanation about this TSM Error:

ANS0238E - The sequence of calls is invalid.- Explanation
https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.2/com.ibm.itsm.msgs.client.doc/msg-ANS0238E.html

Since the issue is intermitent, it maybe caused by network/server
congestion and changing the schedule start times so that fewer backups
run at the same time seems to usually resolve the errors.

Title: Re: Cannot start CMOD 10.1 with TSM 8.1
Post by: teera_aoo on September 05, 2019, 08:41:36 PM

Quote from: teera_aoo on June 03, 2019, 08:11:46 PM

I cannot start CMOD 10.1 with TSM 8.1. There is error in ARCHIVE.trace.log

SM Error: ANS0238E (RC2041) The sequence of calls is invalid., Return Code=2041, Reason=0, File=arssmsms.cpp, Line=2440  Srvr->[SERVERNAME]<-

I opened PMR for 2 Weeks and no progress. Do have anyone ever seen this?

Thanks.

For this issue, No resolution from IBM PMR.

I was found that TSM Client API stanza in ars.cfg was conflicted with ARS_LDAP_BIND_* parameters. (I don't know why)
Proved by remove out of ARS_LDAP_BIND_* parameters  then TSM Client API worked fine and ARSSOCKD can be started.


Workaround Fix:
Remove out of ARS_LDAP_BIND_* parameters  then TSM Client API worked fine and ARSSOCKD can be started.

But you will cannot control parameter ARS_LDAP_BIND_* must leave it all to default.
(For Example, ARS_LDAP_BIND_ATTRIBUTE used to control LDAP's attibute to binding has default as CN, but MS AD almost used sAMAccountName, you will cannot changed if cannot use this parameter.)

Permanent Fix :
Apply CMOD 10.1.0.5