Hi Robert, The " isFileNameValid: Invalid file name favicon.ico" message is logged if you run the TSM Client Web GUI from the Mozilla browser. If you use IE you do not see this message. Basically the browser is looking for this favorites icon to associate with TSM our client URL. The browser makes this request via the Client Acceptor Daemon (CAD) which acts like a mini Web browser. However the CAD does not recognize icon file types and hence the message. This is a harmless message and does not affect the functioning of the product. We will fix it in one of our upcoming releases. Regards, -Seema ______________________________ Seema Gururaj TSM Client development IBM San Jose
Date: Mon, 12 Dec 2005 14:59:38 +0200 From: Robert Ouzen <[EMAIL PROTECTED]> Subject: Re: Novell error Me again The error : 12/12/2005 14:51:56 Error -50 sending ht request 12/12/2005 14:51:56 Error writing to http socket. I got when I tried to connect my Tsm client via Web , automatically when = pressing the backup or restore button got this error message !!!!!!!!!! Regards Robert=20 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of = Richard Sims Sent: Sunday, December 11, 2005 6:27 PM To: [email protected] Subject: Re: Novell error On Dec 11, 2005, at 8:50 AM, Robert Ouzen wrote: > Hi to all > > Today I found a very strange error in a Netware server 6.05 with Tsm=20 > client version 5.3.0 > > The backup is abort with this error message on my dsmerror.log > > 12/11/2005 15:13:09 ANS1074W *** User Abort *** > > 12/11/2005 15:13:59 isFileNameValid: Invalid file name favicon.ico > - file type not allowed. > 12/11/2005 15:13:59 Error -50 sending ht request > 12/11/2005 15:13:59 Error writing to http socket. > > It's the first ime I saw this kinf of error , any ideas where to=20 > search ???????? More information about the environmental context of the condition would = help, but I believe it is the case that you are running the Web Client = (which is actually a specialized Web server which performs TSM client = functions on behalf of a remote browser session). To address the latter error set first: Modern Web browsers may ask the = Web server for the Favorites Icon (favicon) that the site may have, = which the browser will display alongside the URL in the address bar, and = potentially store in Favorites if the page is bookmarked. But not all Web servers will either support or respond to a favicon = request - particularly limited Web servers such at the TSM client. It is = merely logging that. Such an entry appears when a Web browser is = entering into session, prior to any user authentication associated with = the session. The timing you see reflects the Web browser reattempting = session initiation, possibly after having been cut off by the event = reflected by the ANS message. The second error set is thus of no = significance. Refer to your dsmwebcl.log to identify the session origin. The ANS1074W message is the thing to pursue. It's not one of our = favorites, in that it tells us nothing which helps identify the problem. = Look in the TSM server log for that time period. Often, the message is = involved with mount point issues. I'd be interested to hear what you = find in there. Richard Sims http://people.bu.edu/rbs ------------------------------ Date: Mon, 12 Dec 2005 08:18:32 -0500 From: Richard Sims <[EMAIL PROTECTED]> Subject: Re: Novell error On Dec 12, 2005, at 7:59 AM, Robert Ouzen wrote: > Me again > > The error : > > 12/12/2005 14:51:56 Error -50 sending ht request > 12/12/2005 14:51:56 Error writing to http socket. > > I got when I tried to connect my Tsm client via Web , automatically > when pressing the backup or restore button got this error > message !!!!!!!!!! Robert - Recent client README files have contained this info: - Web Client JRE 1.4 issue When using the Web Client with JRE 1.4 and above, these error message will be logged in the dsmerror.log on the machine where the TSM Client Acceptor resides when push buttons on the applet are pressed: Error -50 sending ht request Error writing to http socket ANS1005E TCP/IP read error on socket = X, errno = Y, reason : 'Connection reset by peer' or 'Connection aborted by host machine' ANS1006E TCP/IP write error on socket = X, errno = Y, reason : 'Connection reset by peer' or 'Connection aborted by host machine' This could potentially fill up your dsmerror.log with these messages. In order to prevent these messages from appearing in the error log, please disable caching in the JRE. This can be done through the "Java Plug-in Control Panel" under the "Cache" tab. Once this has been disabled, these error message should no longer appear. If you are using JRE 1.3.1_XX, this will not be a problem. If you are experiencing hangs with the web client using JRE 1.4 and above, disabling caching on the Java Plug-in will usually resolve this issue as well. There may be other causes, but this is a documented one. This is yet another reason that so many of us avoid using the Web Client. Richard Sims ------------------------------
