Zoltan,
I would recommend opening up PMRs with IBM. In this forum, we cannot offer
the degree of assistance that might be needed. Having said that:
- We've seen the ANR0408W in the lab, and will get that corrected.
- I'd be interested in understanding your crash scenario better with the
word QUIET misspelled. I tried that, and I get pop-up message telling me
that the option QUEIT is not valid. It also offers to comment out the
option and continue. So I'm not seeing a crash. Can you provide a more
detailed recreate scenario?
- The MFC GUI is included with 6.1.2, albeit at 5.5 functionality. Instead
of downgrading to 5.5, use the dsmmfc.exe program as a workaround.
- What other issues do you see?
Regards,
andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT 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 AT VM.MARIST DOT EDU> wrote on 11/17/2009
10:50:18 AM:
> [image removed]
>
> Re: Problems with 6.1.2.0 on Windows servers
>
> Zoltan Forray/AC/VCU
>
> to:
>
> ADSM-L
>
> 11/17/2009 10:54 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> I may have to open a ticket with IBM. My symptoms and number of
incidents
> is increasing as more folks install 6.1.2.0.
>
> I can't believe they didn't catch and fix the GUI issue ("connection
> severed") in 6.1.2.0 . I have been experimenting with my XP desktop and
> found this issue goes back to 6.1.0.0.
>
> Plus the issue of the GUI client being so stupid as to crash/hang with
> strange "connection" problems/messages for something as simple as the
word
> "QUIET" being misspelled in the dsm.opt (found it by running the dsmc CLI
> which gave the proper error)
>
> I understand trying to be on one codebase for all platforms, but so far
> JAVA based V6.1 on Windoz has been very problematic and causing us lots
of
> heartburn to the point of having to downlevel clients to keep them
> working!
>
>
>
> From:
> Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
> To:
> ADSM-L AT VM.MARIST DOT EDU
> Date:
> 11/17/2009 02:19 AM
> Subject:
> Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
> Sent by:
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> Hello Zoltan,
>
> Have you tried to report this problem to IBM?
>
> I have tested WEB Client from TSM Client 6.1.2 and found it working fine.
>
> I have tested GUI interface as well and found it working fine, but you
> right - there is next messages in activity log in case of normal exit
from
> GUI:
>
>
> Export table [ console ] for tsmsrv1.bkme.com at 2009-11-17 08:45:01
> 'q act se='11297''
> Num.
>
> DATE/TIME
>
> MESSAGE
>
> 1
>
> 11/17/2009 08:39:18
>
> ANR0406I Session 11297 started for node SMS-GATEWAY (WinNT) (Tcp/Ip
> sms-gateway.kuwait.aub.net(2453)). (SESSION: 11297)
>
> 2
>
> 11/17/2009 08:39:20
>
> ANR0480W Session 11297 for node SMS-GATEWAY (WinNT) terminated -
> connection with client severed. (SESSION: 11297)
>
> 3
>
> 11/17/2009 08:40:22
>
> ANR2017I Administrator TSMEXPLORER issued command: QUERY ACTLOG se=11297
> (SESSION: 11307)
>
> Siberia Software SL<http://www.s-iberia.com>
>
>
>
> It is abnormal, but it does not create any problems.
>
>
>
> We have tested disaster recovery (TSM Client 6.1.2.0 and TBMR 6.2.1) for
> Windows 2003 R2. Windows and all applications, including Oracle instance,
> have been recovered on other server without any problems.
>
>
>
> In addition, after correction initial problem (upgrade TSM 6.1.0.2 to
> 6.1.2.0 is not working, complete reinstall - de-install --> reboot -->
> install --> reboot -->configure - helps to fix problem) backups are
> working fine.
>
> So I think it will be better not to go back to 5.5.2, try to fix problems
> on already upgraded servers. I hope we will have 6.1.3 in December (I saw
> this information somewhere).
>
>
>
> Good luck,
>
>
>
> Grigori G. Solonovitch
>
>
>
> Senior Technical Architect
>
>
>
> Information Technology Bank of Kuwait and Middle East
> http://www.bkme.com
>
>
>
> Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail:
> G.Solonovitch AT bkme DOT com
>
>
>
> Please consider the environment before printing this Email
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Zoltan Forray/AC/VCU
> Sent: Monday, November 16, 2009 6:20 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
>
>
>
> We are having too many issues with the V6.1 client on mostly Windoz
>
> servers.
>
>
>
> So, we are looking at dropping back to V5.5.2.3 (still don't see a 5.3
>
> client), the pre-Java client, for those problem servers.
>
>
>
> What is the impact of downleveling a client?
>
>
>
> Is it going to force a complete backups? What about the inactives?
>
>
>
>
>
>
>
> From:
>
> Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
>
> To:
>
> ADSM-L AT VM.MARIST DOT EDU
>
> Date:
>
> 11/13/2009 01:30 PM
>
> Subject:
>
> Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
>
>
>
>
> Hello Zoltan,
>
> We have started upgrade process from 6.1.0.2 to 6.1.2.0. 5 or 6 servers
>
> Win2003R2 have been upgraded already.
>
> We faced similar problem on one of them. I have fixed it by: de-install
>
> client --> reboot server --> install client --> reboot server -->
>
> configure client services by setup wizard (existing dsm.opt).
>
> Ithink it is a little bit long process, but what to do?
>
> Regards,
>
> Grigori
>
> ________________________________________
>
> From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
> Zoltan
>
> Forray/AC/VCU [zforray AT VCU DOT EDU]
>
> Sent: Friday, November 13, 2009 8:19 PM
>
> To: ADSM-L AT VM.MARIST DOT EDU
>
> Subject: [ADSM-L] Problems with 6.1.2.0 on Windows servers
>
>
>
> We started pushing out 6.1.2.0 since our security officer read about the
>
> security vulnerabilitys in 6.1.x
>
>
>
> Now we are starting to see rashes of problems on W2K3 (both regular and
>
> R2) servers. Yet we have plenty of servers that have upgraded with no
>
> issues.
>
>
>
> ALL of these servers were running just fine with 6.1.0.0 and older
>
> versions of the client.
>
>
>
> Most are manifesting as crashes in dsmagent and/or communications errors
>
> (which I know from previous issues I have seen with 6.x, is often a "red
>
> herring").
>
>
>
> Yes, we have tried complete un/reinstalls, completely deleted the
>
> *:\program files\Tivoli\TSM\directory
>
>
>
> No luck googling for the obvious (dsmagent cXMLiterator)
>
>
>
> Anyone seeing similar problems?
>
>
>
> Excerpts from the various error logs:
>
>
>
> dsmj.log
>
> ---------------
>
> 11/13/2009 09:23:11: ANS2613S A communications protocol error occurred
>
> between the web browser and the client.Could not get JDOM tree !!!
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 09:23:16: ANS2613S A communications protocol error occurred
>
> between the web browser and the client.Could not get JDOM tree !!!
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 09:24:47: ANS2613S A communications protocol error occurred
>
> between the web browser and the client.Could not get JDOM tree !!!
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 09:24:50: ANS2613S A communications protocol error occurred
>
> between the web browser and the client.Could not get JDOM tree !!!
>
> *** commFlush: java.net.SocketException: Connection reset by peer: socket
>
> write error
>
> *** commFlush: java.net.SocketException: Connection reset by peer: socket
>
> write error
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 09:27:24: ANS2610S TCP/IP communications failure between the
>
> client and the server machine.*** commFlush: java.net.SocketException:
>
> Connection reset by peer: socket write error
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 11:30:25: ANS2610S TCP/IP communications failure between the
>
> client and the server machine.*** commFlush: java.net.SocketException:
>
> Connection reset by peer: socket write error
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 11:42:30: ANS2610S TCP/IP communications failure between the
>
> client and the server machine.*** commFlush: java.net.SocketException:
>
> Connection reset by peer: socket write error
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> *** commFlush: java.net.SocketException: Connection reset by peer: socket
>
> write error
>
> *** commFlush: java.net.SocketException: Connection reset by peer: socket
>
> write error
>
> *** commOpen: java.net.ConnectException: Connection refused: connect
>
> 11/13/2009 11:45:47: ANS2610S TCP/IP communications failure between the
>
> client and the server machine.
>
>
>
> dsmcrash.log
>
> -----------------------
>
> 2009/11/13 11:43:03
>
> IBM Tivoli Storage Manager
>
> Version: 6.1.2.00
>
> Build date: Thu Oct 22 15:11:11 2009
>
>
>
> dsmagent.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at
>
> 001B:0053C4A4
>
>
>
> Register dump:
>
> EAX=00000013 EBX=00000000 ECX=00000000 EDX=009891BA ESI=0471FBB8
>
> EDI=78552B7E EBP=009891CD ESP=0471FA1C EIP=0053C4A4 FLG=00010202
>
> CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
>
>
>
> Crash dump successfully written to file 'D:\Program
>
> Files\Tivoli\TSM\baclient\dsmcrash.dmp'
>
>
>
> Stack Trace:
>
> 001B:0053C4A4 (0x00393030 0x333A3531 0x32323A35 0x31003600) dsmagent.exe,
>
> cXMLiterator::cXMLiterator()+1234948 bytes
>
>
>
> tsmstats.ini
>
> -------------------
>
> [fileSystemStatistics.\\dominodc3\c$]
>
> maxPath=193
>
> totalLocalFiles=30471
>
> totalLocalDirs=3059
>
> maxDirCount=5958
>
> maxDirName=C:\I386
>
> [fileSystemStatistics.\\dominodc3\e$]
>
> maxPath=68
>
> totalLocalFiles=24
>
> totalLocalDirs=10
>
> maxDirCount=7
>
> maxDirName=E:\8241623edffcba54df4fdc\amd64
>
> [fileSystemStatistics.\\dominodc3\d$]
>
> maxPath=92
>
> totalLocalFiles=423
>
> totalLocalDirs=45
>
> maxDirCount=211
>
> maxDirName=D:\Program Files\Tivoli\TSM\baclient\jvm50\jre\bin
>
>
>
> dsm.opt
>
> --------------
>
> PASSWORDACCESS GENERATE
>
> TCPSERVERADDRESS tsmlinux4.ucc.vcu.edu
>
> SCHEDLOGR 30 D
>
> ERRORLOGR 30 D
>
> QUIET
>
> TCPClientAddress 192.168.20.58
>
>
>
> Please consider the environment before printing this Email.
>
>
>
> "This email message and any attachments transmitted with it may contain
>
> confidential and proprietary information, intended only for the named
>
> recipient(s). If you have received this message in error, or if you are
>
> not the named recipient(s), please delete this email after notifying the
>
> sender immediately. BKME cannot guarantee the integrity of this
>
> communication and accepts no liability for any damage caused by this
email
>
> or its attachments due to viruses, any other defects, interception or
>
> unauthorized modification. The information, views, opinions and comments
>
> of this message are those of the individual and not necessarily endorsed
>
> by BKME."
>
> ________________________________
> "This email message and any attachments transmitted with it may contain
> confidential and proprietary information, intended only for the named
> recipient(s). If you have received this message in error, or if you are
> not the named recipient(s), please delete this email after notifying the
> sender immediately. BKME cannot guarantee the integrity of this
> communication and accepts no liability for any damage caused by this
email
> or its attachments due to viruses, any other defects, interception or
> unauthorized modification. The information, views, opinions and comments
> of this message are those of the individual and not necessarily endorsed
> by BKME."
|
