Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
Andy Thanks, Regarding the technote 1308592, does ANYONE know anything about the LsmLOCK file? I could not find much Information on it. The technote say's to remove it, I guess it's not important it does not appear to be. I tried to delete the file per instructions but a message appeared cannotdelete LsmLock : access denied Make sure the disk is not full or write proctectd and the file is not in use. Note: TSM services were stopped before I tried this. Regards Tim Andrew Raibeck wrote: The QUERY STATUS output shows you the maximum *number* of scheduled sessions (HELP QUERY STATUS will tell you this). So it appears your setting it to 100% is in effect. Look up the ANS1902E message and it should explain what's going on. On the surface, seems to be unrelated (at least not directly related) to number of sessions on the TSM server. You can use dsmc help and navigate the help menu to look up the message, or check the messages manual. For the VSS issue, go to the URL in my sig and search for technote 1308592 to see if that addresses that issue. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2009 01:30:26 PM: [image removed] Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Timothy Hughes to: ADSM-L 01/23/2009 01:32 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:16:13 ANS2054E Operating system error 13: d. 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : vssCreateDCInLocalAndTsm TSM function : Failed to lock LSM repository. TSM return code : 101 TSM file : vssback.cpp (4742) 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : baProcessRequest TSM function : VSS create DCs failed TSM return code : 101 TSM file : incrdrv.cpp (8190) 01/23/2009 09:16:15 ANS1074W The operation was stopped by the user. 01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868 01/23/2009 09:19:25 ANS2054E Operating system error 13: d. 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:19
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
Tim, make sure you are logged in to Windows as an administrator. Take a look at the security permissions on the LsmLock file and it's parent directory, and make sure admins have full control. If admins don't have full control, change the permissions so admins have full control (for the parent directory, which should propagate to the LsmLock file as well). Then try deleting the file. Note: if you have any TDP applications installed, make sure you delete only that one LsmLock file. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/27/2009 11:26:21 AM: [image removed] Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Timothy Hughes to: ADSM-L 01/27/2009 11:30 AM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Andy Thanks, Regarding the technote 1308592, does ANYONE know anything about the LsmLOCK file? I could not find much Information on it. The technote say's to remove it, I guess it's not important it does not appear to be. I tried to delete the file per instructions but a message appeared cannotdelete LsmLock : access denied Make sure the disk is not full or write proctectd and the file is not in use. Note: TSM services were stopped before I tried this. Regards Tim Andrew Raibeck wrote: The QUERY STATUS output shows you the maximum *number* of scheduled sessions (HELP QUERY STATUS will tell you this). So it appears your setting it to 100% is in effect. Look up the ANS1902E message and it should explain what's going on. On the surface, seems to be unrelated (at least not directly related) to number of sessions on the TSM server. You can use dsmc help and navigate the help menu to look up the message, or check the messages manual. For the VSS issue, go to the URL in my sig and search for technote 1308592 to see if that addresses that issue. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2009 01:30:26 PM: [image removed] Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Timothy Hughes to: ADSM-L 01/23/2009 01:32 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:16:13 ANS2054E Operating system error 13: d. 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : vssCreateDCInLocalAndTsm TSM function : Failed to lock LSM repository. TSM return code : 101 TSM file : vssback.cpp (4742) 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : baProcessRequest TSM function : VSS create DCs failed TSM return code : 101 TSM file : incrdrv.cpp (8190) 01/23/2009 09:16:15 ANS1074W The operation was stopped by the user. 01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868 01/23/2009 09:19:25 ANS2054E Operating system error 13: d. 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:19:30 ANS2054E Operating system error 13: d. 01/23/2009 09:19:30 ANS5250E An unexpected error was encountered thanks Shawn Drew wrote: The Max sched sessions is just a percentage of the max sessions. So if you increase the max sessions, it will increase the max sched sessions. I would keep the max sched sessions to the default, then just increase the max sessions. Hopefully that made sense! Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 01:57 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message Subject:Re: Windows 2003 Clients failing all of sudden after TSM server upgrade Date: Fri, 16 Jan 2009 13:14:49 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of6df0a779.f79b6849-on85257540.005c416a-85257540.005c6...@americas.bnpparibas.com Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W
[Fwd: Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]]
We also have Solaris clients and it doesn't cause them to fail. regards Original Message Subject: Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Date: Fri, 23 Jan 2009 13:30:26 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of75da3430.6ffa4fd3-on85257540.0069fc8a-85257540.006a1...@americas.bnpparibas.com Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:16:13 ANS2054E Operating system error 13: d. 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : vssCreateDCInLocalAndTsm TSM function : Failed to lock LSM repository. TSM return code : 101 TSM file : vssback.cpp (4742) 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : baProcessRequest TSM function : VSS create DCs failed TSM return code : 101 TSM file : incrdrv.cpp (8190) 01/23/2009 09:16:15 ANS1074W The operation was stopped by the user. 01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868 01/23/2009 09:19:25 ANS2054E Operating system error 13: d. 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:19:30 ANS2054E Operating system error 13: d. 01/23/2009 09:19:30 ANS5250E An unexpected error was encountered thanks Shawn Drew wrote: The Max sched sessions is just a percentage of the max sessions. So if you increase the max sessions, it will increase the max sched sessions. I would keep the max sched sessions to the default, then just increase the max sessions. Hopefully that made sense! Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 01:57 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
The MAXSESSIONS value determines the number of sessions that can run. MAXSCHEDSESSIONS is the percentage of MAXSESSIONS that can run from a schedule. MAXSESSIONS is set in the dsmserv.opt file. The TSM server application will have to be restarted for the changes to take effect. Hope it helps, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Timothy Hughes Sent: Friday, January 23, 2009 12:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:16:13 ANS2054E Operating system error 13: d. 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : vssCreateDCInLocalAndTsm TSM function : Failed to lock LSM repository. TSM return code : 101 TSM file : vssback.cpp (4742) 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : baProcessRequest TSM function : VSS create DCs failed TSM return code : 101 TSM file : incrdrv.cpp (8190) 01/23/2009 09:16:15 ANS1074W The operation was stopped by the user. 01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868 01/23/2009 09:19:25 ANS2054E Operating system error 13: d. 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:19:30 ANS2054E Operating system error 13: d. 01/23/2009 09:19:30 ANS5250E An unexpected error was encountered thanks Shawn Drew wrote: The Max sched sessions is just a percentage of the max sessions. So if you increase the max sessions, it will increase the max sched sessions. I would keep the max sched sessions to the default, then just increase the max sessions. Hopefully that made sense! Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 01:57 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
On Jan 23, 2009, at 1:43 PM, Schneider, Jim wrote: ... MAXSESSIONS is set in the dsmserv.opt file. The TSM server application will have to be restarted for the changes to take effect. Or, nondisruptively, via the SETOPT command. Richard Sims
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
The QUERY STATUS output shows you the maximum *number* of scheduled sessions (HELP QUERY STATUS will tell you this). So it appears your setting it to 100% is in effect. Look up the ANS1902E message and it should explain what's going on. On the surface, seems to be unrelated (at least not directly related) to number of sessions on the TSM server. You can use dsmc help and navigate the help menu to look up the message, or check the messages manual. For the VSS issue, go to the URL in my sig and search for technote 1308592 to see if that addresses that issue. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2009 01:30:26 PM: [image removed] Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] Timothy Hughes to: ADSM-L 01/23/2009 01:32 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Hello, Our Max sched sessions is set to 100, but when I look at q server status it say's the following: Maximum Sessions 75 Maximum Scheduled Sessions 75 We are still getting the following which I am seeing in the clients dsmerror.logs 1/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use or/and 01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022 TSM SERVER LOG is showing the following which by the way doesn't cause our Novell/Linux/AIX client to fail. (WinNT) refused -maximum server sessions (75) exceeded. XXX-X (WinNT) refused - maximum server sessions (75) exceeded. (LinuxPPC) refused - maximum server sessions (75) exceeded. X (LinuxPPC) refused - maximum server sessions (75) exceeded. X (WinNT) refused - maximum server sessions (75) exceeded. XX (WinNT) refused - maximum server sessions (75) exceeded. I ran a manual backup for some of the failing Windows 2003 clients and they worked fine. However I did encounter I VSS issue below with on server which is a seperate issue I believe. 1/23/2009 09:16:05 ANS2054E Operating system error 13: d. 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:16:05 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:16:13 ANS2054E Operating system error 13: d. 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : vssCreateDCInLocalAndTsm TSM function : Failed to lock LSM repository. TSM return code : 101 TSM file : vssback.cpp (4742) 01/23/2009 09:16:13 ANS5250E An unexpected error was encountered. TSM function name : baProcessRequest TSM function : VSS create DCs failed TSM return code : 101 TSM file : incrdrv.cpp (8190) 01/23/2009 09:16:15 ANS1074W The operation was stopped by the user. 01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868 01/23/2009 09:19:25 ANS2054E Operating system error 13: d. 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 01/23/2009 09:19:25 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 01/23/2009 09:19:30 ANS2054E Operating system error 13: d. 01/23/2009 09:19:30 ANS5250E An unexpected error was encountered thanks Shawn Drew wrote: The Max sched sessions is just
[Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message Subject: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade Date: Fri, 16 Jan 2009 13:14:49 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of6df0a779.f79b6849-on85257540.005c416a-85257540.005c6...@americas.bnpparibas.com Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W Session 8894 for node ZDNBURG (WinNT) refused - maximum server sessions (75) exceeded. I wonder If the updrade to TSM 5.5.2 changed the parameter? could that have happen? So far I can't find any of the above messages from prior to the upgrade. I did a Q status here are the results. Maximum Sessions: 75 Maximum Scheduled Sessions: 75 regards Tim Shawn Drew wrote: Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674 01/13/2009 00:20:27
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
The Max sched sessions is just a percentage of the max sessions. So if you increase the max sessions, it will increase the max sched sessions. I would keep the max sched sessions to the default, then just increase the max sessions. Hopefully that made sense! Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 01:57 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message Subject:Re: Windows 2003 Clients failing all of sudden after TSM server upgrade Date: Fri, 16 Jan 2009 13:14:49 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of6df0a779.f79b6849-on85257540.005c416a-85257540.005c6...@americas.bnpparibas.com Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W Session 8894 for node ZDNBURG (WinNT) refused - maximum server sessions (75) exceeded. I wonder If the updrade to TSM 5.5.2 changed the parameter? could that have happen? So far I can't find any of the above messages from prior to the upgrade. I did a Q status here are the results. Maximum Sessions: 75 Maximum Scheduled Sessions: 75 regards Tim Shawn Drew wrote: Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState
