Scheduler crash with ANS2050E error

[fede_pg]

Hi all, this is my first post, so I hope I did choose the right forum



My scenario: a two-nodes Windows Server 2003 SP1 Cluster, with a Exchange 2003 SP1 virtual server, a MS Sql 2000 SP4 virtual server and some file share resources. Every single resource has a separated SAN disk resource.



I installed TSM Server 5.3 on another machine, in order to backup the cluster and several other servers/clients. All is running fine, but I've got a nasty problem with the scheduler for the sql resource. For every disk resource (Exchange, MS SQL and file server) I created a generic service resource on the cluster, using the reg key SoftwareIBMADSMCurrentVersionBackupClientNodesNodename ,



after having installed on both nodes the three scheduler services using this command line instruction:



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> dsmcutil install scheduler /name:"tsm scheduler 1" /clientdir:"Crogram filesTivoliTSMBaclient" /optfile:"X:ackup_exchangedsm.opt" /node:nodename /passwordass /validate:no /autostart:yes /startnow:no</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>



Scheduler services for the Exchange Resource and for the File server Resource started immediately, receiving the right schedule from the TSM server and they are running smoothly now. The MS Sql one instead, after a few days of right schedules, began to crash!



I can't start the service: after a few seconds in fact it stops suddenly and then it goes in failed state. I'm currently receiving these errors:



Windows Event Log ->

Event 4099 - Adsm Client Service - Scheduler exited with a result code of 12.

Event 4098 - Adsm Client Service - Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log



My Dsmsched.log ->

21-06-2005 15:30:47 Querying server for next scheduled event.

21-06-2005 15:30:47 Node Name: TGSQL

21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.

21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.

21-06-2005 15:30:47 ANS1029E Communication with the TSM server is lost.

21-06-2005 15:30:47 Scheduler has been stopped.



Here's my dsm.opt



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> NODename Node

CLUSTERnode yes

DOMAIN S:

COMPRESSIon Off





Errorlogname S:Backup_SQLdsmerror.log

Schedlogname S:Backup_SQLdsmsched.log



Errorlogretention 14

Schedlogretention 7



DATEFORMAT 2





COMMMethod TCPip

TCPPort 1500

TCPServeraddress TGTSM

TCPWindowsize 63

TCPBuffSize 32



SCHEDLOGRetention 15 D

SCHEDMODE Prompted

DIRMC MCDIR





</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>



I tried to delete the cluster generic service resource, uninstall the scheduler service and then reinstall all, but the result didn't changed :cry: .

I did try also to update the password via command line, but I didn't solve the problem.



The other schedulers are running fine, but I can't fix this one, can someone help me, please?



PS: I am a really tsm newbie!!

PS2: Sorry for my english!!!

 

[fede_pg]

Up :cry:

 

[may]

are you using TDP SQL??



did you try updating your SQL Schedule password by the GUi (why are using command line in windows world?)

 

[fede_pg]

Yes, I'm using TDP SQL and now I'm going to try to update the password via GUI. Do you think the command line it's the problem?



(I'm a command line junkie :grin: ... damn Linux!)

 

[fede_pg]

Password updated via GUI, but the scheduler continues to crash... :sad:

 

[may]

the dsm.opt which you showed us is the TSM One?



what about your TDP's dsm.opt!



did you try adding an another Scheduler and if it won't work why not creat a bran new dsm.opt



just to have a try.



am just not guessing wht is happening

 

[cheffern]

Did you start up your scheduler in the foreground for the initial passwd setting/verification?

 

[cheffern]

I doubt the command line is the problem here -

I would seriously ask for a reboot.

You may want to search the registry for the variables and delete / re-add.

 

[manureano]

I'm not sure, but I think the password should be set to Generate in the dsm.opt. Have you tried it?

 

[cheffern]

Ha - yes - I'll bet that is it -



In your dsm.sys file, the Schedmode should be set to: SCHEDmode prompted

And the password should be set to: PASSWORDAccess generate

Overlooked that one



So if I'm not mistaken, the info you have below - you say is from dsm.opt?



Your dsm.opt file should only have the SErvername, DOMain &amp; COMpression info...the rest should be in your dsm.sys I think - it is that way for Unix....likely for NT I would think as well...



Please let us know - thanks -

 

[may]

there is no "dsm.sys" in Windows world .



i Think you should try by erasing the

PASSWORDAccess generate

line in your TDP's dsm.opt

 

[blagrange]

I agree with the below, comment out the passwordaccess generate then execute the dsmc command.



Another thing to try is a dsmcutil update sched /name:schedname /passwordassword. This will update the password in the registry.



If that does not work then comment out passwordaccess generate and put the following line in your dsm.opt.



password &lt;password>



Obviously the third is worst case scenario.

 

[fede_pg]

Hi all.



I'm sorry I can post my reply only now ( a few days of vacation!) and many thanks for your precious advices.



Now I'm going to try all of yours tips and I will post the results here in a little while.



BTW:



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE> Another thing to try is a dsmcutil update sched /name:schedname /passwordassword. This will update the password in the registry. </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE> >> Tried, no results :sad:





<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE> I doubt the command line is the problem here -

I would seriously ask for a reboot.

You may want to search the registry for the variables and delete / re-add. </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE> >> Tried, no results :sad:







<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE> the dsm.opt which you showed us is the TSM One?



what about your TDP's dsm.opt! </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE> >> Yes, it's my tsm opt file. Here's my TDPSQL opt file (however my sql backups are running fine, I have only to schedule the backupsql.cmd file via Windows and not via TSM Server)



*======================================================================*

* *

* IBM Tivoli Storage Manager for Databases *

* *

* Data Protection for Microsoft SQL Server *

* *

* Sample Options File *

* *

*======================================================================*



NODename Mynode

CLUSTERnode yes

PASSWORDAccess Generate



*======================================================================*

* TCP/IP Communication Options *

*======================================================================*

COMMMethod TCPip

TCPServeraddress 172.20.101.88

TCPPort 1500

TCPWindowsize 63

TCPBuffSize 32



*======================================================================*

* Named Pipes Communication Options *

*======================================================================*

*COMMMethod NAMEdpipe

*NAMedpipename \\.\pipe\tsmpipe



*======================================================================*

* - Compression Options *

* *

* Use the "COMPRESSION" option to compress the data before sending *

* it to the IBM Tivoli Storage Manager server. Use the *

* "COMPRESSALWAYS" option to specify whether to continue compressing *

* the data if it grows during compression. *

* *

*======================================================================*

COMPRESSIon NO

*COMPRESSAlways NO



*======================================================================*

* *

* - Scheduling Options *

* *

* The default scheduling mode is the client polling method. *

* To use server prompted scheduling, you must be sure to use a tcp *

* client port different than the one used by the regular backup *

* client. *

* *

*======================================================================*

SCHEDMODE Polling

*SCHEDLOGRetention 14

*SCHEDMODE Prompted

*TCPCLIENTADDRESS yy.yy.yy.yy

*TCPCLIENTPORT 1502



*======================================================================*

* Include/Exclude Processing *

* *

* For a more complete description of include/exclude processing refer *

* to the Data Protection for Microsoft SQL Server Installation and *

* User's Guide. *

*======================================================================*



*======================================================================*

* The following include statements assign all meta objects to *

* management class SqlDbMetaMgmtClass and all data objects to *

* SqlDbDataMgmtClass *

*======================================================================*

*INCLUDE "\...\meta\...\*" SqlDbMetaMgmtClass

*INCLUDE "\...\data\...\*" SqlDbDataMgmtClass



*======================================================================*

* The following include statements assign all log meta objects to *

* management class SqlLogMetaMgmtClass and all log data objects to *

* SqlLogDataMgmtClass *

*======================================================================*

*INCLUDE "\...\meta\...\log*" SqlLogMetaMgmtClass

*INCLUDE "\...\data\...\log*" SqlLogDataMgmtClass



*======================================================================*

* The following exclude statements exclude all log backups for *

* databases master and msdb *

*======================================================================*

*EXCLUDE "\...\master\...\log*"

*EXCLUDE "\...\msdb\...\log*"



*======================================================================*

* The following exclude statement excludes the "db1" database *

* from being compressed (if compression is enabled for backups.) *

*======================================================================*

*EXCLUDE.COMPRESSION "\...\db1\...\*"





Thanks for your help!

 

[nallshouse]

I had the exact same problem with the Exchange TDP agent and this is what I did to fix it:



on each node,



tdpexcc query tsm /tsmpassword=mypassword



The specific instruction from the manual:

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>Verify that the clusternode option in the dsm.opt file is set to yes. After this is

verified, enter a command that connects with the Tivoli Storage Manager

Server. Specify the /tsmpassword=yourpassword parameter to ensure the correct

password is stored in the registry. This allows the scheduler to properly

connect automatically to the Tivoli Storage Manager Server.

tdpexcc query tsm /tsmpassword=mypassword</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>



I hope this helps somehow