Hi Zoltan,

Regarding the QUITE vs QUIET issue: This looks like APAR IC61768 and is
fixed in 6.1.2.0.

Regarding the dsmagent crash: please open a PMR for that, and support will
provide guidance on where to upload the crash dumps. This may not be
specific to 6.1 (though I understand that is the code level where you are
seeing the crash).

Regarding the dsmmfc.exe suggestion: The only real "showstopper" issue you
mentioned is the GUI crash in dsmagent. I take this to mean the Java GUI.
Instead of back-leveling the client, you can try the dsmmfc.exe which ships
with 6.1, to see if the native GUI will serve until we understand what the
Java GUI/dsmagent.exe is crashing. Of course, if you rely on the web
client, and you see the crash with the web client (which also uses
dsmagent.exe) then the native GUI is not a replacement for the web client
functionality.

Best 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/19/2009
01:41:53 PM:

> [image removed]
>
> Problems with 6.1.2.0 on Windows servers
>
> Zoltan Forray/AC/VCU
>
> to:
>
> ADSM-L
>
> 11/19/2009 01:45 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Here is a screenshot with "QUIET" mispelled as "QUITE" and the
> resulting error when starting up the GUI (this is 6.1.0.0 since I
> was testing downlevel versions to see where the "connection severed"
> errors started.).  Above the error is the complete DSM.OPT file.
>
> [image removed]
>
>
> As for the other problems/crashes we have had on 5-different W2K3
> servers,  I can send you the dsmcrash.dmp file as well as other
> logs. Just tell me where.
>
> The dsmcrash.log says:
>
>
--------------------------------------------------------------------------------

> 2009/11/13 09:58:15
> 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=0461FBB8
> EDI=78552B7E  EBP=009891CD  ESP=0461FA1C  EIP=0053C4A4  FLG=00010202
> CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=0000
>
> Crash dump successfully written to file 'C:\Program Files\Tivoli\TSM
> \baclient\dsmcrash.dmp'
>
> Stack Trace:
> 001B:0053C4A4 (0x00393030 0x333A3531 0x32323A35 0x31003600)
> dsmagent.exe, cXMLiterator::cXMLiterator()+1234948 bytes
>
>
> These all started after installing 6.1, replacing 5.5.  Even after
> repeatedly uninstalling, installing 6.1.2.0, deleting complete TSM
> directory, rinse-lather-repeat, kept seeing these crashes at startup
> of the GUI.  Could not see a patterns since other systems upgraded
worked.
>
> I also thought the problem was that everything was located on a D:
> \Program Files drive vs C: (I recall an earlier version/problem
> having issues with it being anywhere other than C:)  but we had a
> system that was upgrade with the client on D: that worked fine.
>
> Now, after again un/reinstalling and putting it on C:, it works
> (after 6+ install/uninstall/reinstall attempts).  No explanation as
> to why it suddenly works.
>
> Albert Einstein once said “The definition of insanity is doing the
> same thing over and over again and expecting different results”.
>
> Well, in this case, we did get different results.................
>
> - 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.
>
> Don't understand what you want me to do with this?