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 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Sims
Sent: Sunday, December 11, 2005 6:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
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 
> 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 
> 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