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.
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?
<<image/gif>>
