Thanks a bunch. Server name is indeed "NULL" and I did run the SP on the 
server.Will have to wait till the weeknd because of GM Production so can't 
reboot the server.

Appreciate all your help.
--

On Mon, 23 Sep 2002 13:51:55
 Del Hoobler wrote:
>> I keep on getting a Dr. Watson error on one of the SQL 7.0 SP3
>> servers as soon as I launch TDPSQL GUI session. SQL server is
>> installed on Windows Nt 4.0 SP6a. I do have four more servers
>> with same Hardware and software configuration and TDP runs without any
>problems.
>
>Prasanna,
>
>We have seen this when the SQL server name was "null'ed".
>To check this issue the following T-SQL command:
>      select @@servername
>If it comes back with no name or "null", try the following:
>
>1. From the QA (Query Analyzer) issue the system procedure command:
>         sp_addserver 'servername',local
>   where 'servername' is the server name if accessing a SQL Server default
>   instance, and is servername\instancename if accessing a named instance.
>
>2. Stop and restart the SQL Server instance.
>
>3. From the QA issue:
>      select @@servername
>   You should see the servername you used in sp_addserver.
>
>4. Retry the TDP-SQL operation.
>
>If it still fails, please call IBM support.
>
>Thanks,
>
>Del
>
>----------------------------------------------------
>
>Del Hoobler
>IBM Corporation
>hoobler AT us.ibm DOT com
>


____________________________________________________________
Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS
http://www.mail.lycos.com/brandPage.shtml?pageId=plus