cuGetBackQryResp: Server aborted txn, reason: 1

[LucasSatriano]

Hello people,

Can sameelse help me with that ? I can´t find an answer

"
08/02/2018 05:02:27 cuGetBackQryResp: Server aborted txn, reason: 1
08/02/2018 09:02:31 ANS0361I DIAG: sessSendVerb: Error sending Verb, rc: -50
08/02/2018 09:02:31 ANS0361I DIAG: cuConfirm: Received rc: -50 trying to receive ConfirmResp verb
08/02/2018 09:02:36 ANS1301E This operation cannot continue due to an error on the TSM server. See your TSM server administrator for assistance.

08/02/2018 09:02:37 ANS1512E Scheduled event 'DIARIO_FAZFPS010' failed. Return code = 12."

 

[marclant]

Check the TSM Server activity log during the same timeframe as those errors and go from there.

It does sound like a networking problem between the client and the server though, but check the activity log first to see what's in there for that client's sessions.

 

[LucasSatriano]

When you say "Check the TSM Server activity log" it is DSM.ERROR or DSM.SCHED or the both ?

 

[marclant]

When you say "Check the TSM Server activity log" it is DSM.ERROR or DSM.SCHED or the both ?

Neither. It's on the TSM Server. The errors you showed are from the client.

I'm going to go out on a limb and suggest your not the TSM administrator in this case. If you talk to him or her, they would be able to check it.

 

[LucasSatriano]

Why hold not be the tsm server adm?
There aren't exit other log, just that. The other log that exist is the exchange schedule.

 

[marclant]

I didn't meant to insult you. But if you don't know what the TSM Server activity log is, you are likely not the TSM server administrator. All the logs you are referring to are client logs. The client does backup/restore, but that data is stored on the TSM Server, a different machine.

You have to connect to the TSM server using "dsmadmc" or the "Operations Center" and use the QUERY ACTLOG command.

 

[LucasSatriano]

I know you didnt´t insult me, relax, the problema that I understand wrong. I´m used to it the q act, not the activity log.

The "q act" is:

"
tsm: FAZBKP001>q act search="diario_fazfps010_exc" begind=-5 endd=today

Date/Time Message
-------------------- ----------------------------------------------------------
07/28/2018 19:02:10 ANR2579E Schedule DIARIO_FAZFPS010_EXC in domain FCM_PDEXC
for node FAZFPS010_EXC failed (return code 1819).
(SESSION: 861204)
07/30/2018 19:03:06 ANR2579E Schedule DIARIO_FAZFPS010_EXC in domain FCM_PDEXC
for node FAZFPS010_EXC failed (return code 1819).
(SESSION: 871653)
07/31/2018 19:02:29 ANR2579E Schedule DIARIO_FAZFPS010_EXC in domain FCM_PDEXC
for node FAZFPS010_EXC failed (return code 1819).
(SESSION: 898853)
08/01/2018 19:02:48 ANR2579E Schedule DIARIO_FAZFPS010_EXC in domain FCM_PDEXC
for node FAZFPS010_EXC failed (return code 1819).
(SESSION: 926047)"

But the ANR2579E code is a generic bug, it does not help in my opinion. What do you think ?

 

[marclant]

Must be for the wrong node. The latest message in the activity log you posted is 08/01/2018 19:02:48, the errors you posted in your original message happened between 08/02/2018 05:02:27 and 08/02/2018 09:02:36.

The schedule is named DIARIO_FAZFPS010 while the node you searched on was DIARIO_FAZFPS010_EXC. I have a feeling that it's the local filesystem backup that failed in your original post, and you searched the activity log for the Exchange node.

Searching for the node is good to help you get the session number, but it may miss out on some of the messages. There may be other errors pertaining to those node's sessions that don't have the nodename in them.

Might be easier if you just focus on the few hours that the error occurred:
q ac begindate=08/02/2018 begintime=04:00 endate=08/02/2018 endtime=09:30

I personally like to dump that output to a file, and use a text editor to read the activity log. You can use the find feature to jump around, scroll up, scroll down. That's harder to do if you read it from the Spectrum Protect admin command line.

But the ANR2579E code is a generic bug, it does not help in my opinion. What do you think ?

Not a bug, but a generic message for a failed schedule. But that's not related to your original problem because it's the wrong time frame.

 

[LucasSatriano]

The presents logs here, is the dsmerror_exc, C:\Tivoli\TSM\TDPExchange\logs:
"08/14/2018 19:03:03 ANS1909E The scheduled command failed.
08/14/2018 19:03:03 ANS1512E Scheduled event 'DIARIO_FAZFPS010_EXC' failed. Return code = 1819.
08/15/2018 19:02:25 ANS1909E The scheduled command failed.
08/15/2018 19:02:25 ANS1512E Scheduled event 'DIARIO_FAZFPS010_EXC' failed. Return code = 1819."

And that is the exc_inc:

"IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 7, Release 1, Level 6.0
(C) Copyright IBM Corporation 1998, 2016. All rights reserved.

ACN5057I The C:\Tivoli\TSM\TDPExchange\logs\ExcSch.log log file has been pruned successfully.

Querying Exchange Server to gather database information, please wait...

ACN5350E An unknown Exchange error has occurred."

A little time ago, I told the customer to give all the permissons to the user exchange, because a wrong show me that I needed to give the permission to do the backup on a directory, after that, the wrong FAILED 1819 started.

It´s very confuse, the manual backup works.

There is a node to DIARIO_FAZFPS010 and other node to DIARIO_FAZFPS010_EXC. The schedule DIARIO_FAZFPS010 it´s works, and when I relaun the schedule DIARIO FAZFPS010_EXC, works, but the automatic schedule, does not.

 

[LucasSatriano]

Someone?