TSM baclient 6.2.1.0 ANS2613S error using setup wizard. Could not get JDOM tree

cmerrell

cmerrell

ADSM.ORG Member
Joined
Jan 10, 2008
Messages
10
Reaction score
0
Points
0
Location
Michigan
Installed TSM baclient 6.2.1.0 on Windows 2003/2008 clients. If I use the GUI setup wizard to configure the client options/scheduler/web, it immediately fails with an ANS2613S error:

A communications protocol error occurred between the web browser and the client

From dsmcrash:

2010/08/25 09:47:54
IBM Tivoli Storage Manager
Version: 6.2.1.00
Build date: Tue Apr 27 01:16:31 2010
dsmagent.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at 001B:0054D8F4
Register dump:
EAX=00000013 EBX=00000000 ECX=00000000 EDX=00965B8A ESI=04E5FC58
EDI=78552B7E EBP=00965B9D ESP=04E5FA18 EIP=0054D8F4 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:0054D8F4 (0x00303130 0x343A3130 0x32313A38 0x32003600) dsmagent.exe, cXMLiterator::cXMLiterator()+1303764 bytes

From dsmj:

08/25/2010 09:48:17: 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
08/25/2010 09:48:19: 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
08/25/2010 09:48:22: 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
08/25/2010 09:48:25: 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

Opening the preference editor in the GUI produces the same error/result

Running TSM server 6.2.0.0 and I have other Windows 03/08 clients running the 6.2.1.00 client version without this problem
 
Hi,

maybe it has to do with the windows firewall ? Did you open the 1500,1501,1581 Ports ?

Another note: you also should update your 6.2.0.0 Server to 6.2.1.0 or wait a little while till 6.2.2.0 comes out. I have had problems with these 0er releases ;-()
 
Similar problem here.

I've been using TSM 5.5.x for years but haven't gone to 6.x yet. Now I'm conducting a test install on a newly-installed Windows 2008 server (32bit). The Windows firewall is disabled.

I'm trying to install the fixpack directly (6.2.1.0-TIV-TSMBAC-WinX32.exe from the ftp repository) without previous packages installed. The install process itself is uneventful. When I start the GUI, it asks whether to create a new opt file or import an existing one, then the nodename, then it pops out the error message "ANS2613S A communications protocol error occurred between the web browser and the client."

Clicking the dialog away seems to complete the setup without further warnings.

There is no dsmcrash file and even the dsmerror is empty. The dsmj.log says this:

10/26/2010 17:30:40: ANS2613S A communications protocol error occurred between the web browser and the client.Could not get JDOM tree !!!
*** commFlush: java.net.SocketException: Software caused connection abort: socket write error

Another strange thing is that there is no dsmmfc.exe file in the installation directories. Maybe this is due to the fact that I started from a fixpack and not from a release package.

I'm really puzzled by the fact that a fresh, totally standard install on a new, plain vanilla server gives an error. Am I the only one experiencing this? Can anybody suggest how to investigate?
 
Andrey said:
May be it's time to update to 6.2.1.3 BA Client
Click to expand...
Tried it today.
Now the error message pops out at the end of the "Configure TSM Client option file" wizard that starts automatically, when clicking "Apply", instead of shortly after its beginning.

The dsmj.log says:
ANS2613S A communications protocol error occurred between the web browser and the client.Error sending preferences to agent !

It looks like the error pops out only when the wizard is run in absence of a dsm.opt file. The opt file is created normally though.
After that the client seems to work normally.

I still can't believe I'm the only one out in the field experiencing this problem.
 
I just tried installing the latest BA client (6.2.1.3 64-bit) on a freshly installed, plain vanilla Windows 2008-64 bit (Eng).
Same error (as my previous post) popping out when I configure the client the first time.

The dsmj.log says the same:
ANS2613S A communications protocol error occurred between the web browser and the client.Error sending preferences to agent !

The only thing that I can think of is that my server is v.5.5.5 and not 6.x, even though it should be totally compatible with the client.
TSM gurus, any thoughts?
 
Hi cmerrell,

I had the same issue with TSM 6.2.2.0 and found the solution here http://www-01.ibm.com/support/docview.wss?uid=swg21455686 .

I hope that helps.

Cheers

Carlos
Senior Infrastructure Engineer

cmerrell said:
Installed TSM baclient 6.2.1.0 on Windows 2003/2008 clients. If I use the GUI setup wizard to configure the client options/scheduler/web, it immediately fails with an ANS2613S error:

A communications protocol error occurred between the web browser and the client

From dsmcrash:

2010/08/25 09:47:54
IBM Tivoli Storage Manager
Version: 6.2.1.00
Build date: Tue Apr 27 01:16:31 2010
dsmagent.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at 001B:0054D8F4
Register dump:
EAX=00000013 EBX=00000000 ECX=00000000 EDX=00965B8A ESI=04E5FC58
EDI=78552B7E EBP=00965B9D ESP=04E5FA18 EIP=0054D8F4 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:0054D8F4 (0x00303130 0x343A3130 0x32313A38 0x32003600) dsmagent.exe, cXMLiterator::cXMLiterator()+1303764 bytes

From dsmj:

08/25/2010 09:48:17: 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
08/25/2010 09:48:19: 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
08/25/2010 09:48:22: 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
08/25/2010 09:48:25: 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

Opening the preference editor in the GUI produces the same error/result

Running TSM server 6.2.0.0 and I have other Windows 03/08 clients running the 6.2.1.00 client version without this problem
Click to expand...
 
You must log in or register to reply here.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,974
Messages
135,448
Members
21,953
Latest member
jrogers
Back
Top