Post reply

@@SERVERNAME returns NULL (after install W2K3 SP1?)

  • December 21, 2005 at 2:46 am

    #92874

    We are running SQL2000 SP3 on a Windows 2003 server.

    Last weekend SP1 for windows was installed. Since then the @@SERVERNAME is returning NULL.

     

    I haven’t had a chance to try the sp_dropserver/ sp_addserver solution which is mentioned in some similar topics on this forum, since a restart of the server is only possible during weekends.

     

    My questions are: “do you think this could have something to do with the W2k3 SP1 (or should I look for another explanation)?”, “did anyone have a similar experience?”, “any suggestions for a fix withoud a server restart” …

     

    Regards,

    Maarten.

     

  • December 21, 2005 at 6:47 am

    #610819

    I'd just go for the reboot followed by the sp_drop/sp_add method, that generally clears this sort of issue.

    Did you reboot the server after you installed SP1?

  • December 21, 2005 at 9:33 am

    #610885

    Haven't applied SP1, was waiting for you

    I'd try Mike's idea and let us know.

  • December 22, 2005 at 2:34 am

    #611053

    First to answer Mike's question; "Yes, After installing SP 1, the server was rebooted."

    In the mean time I was able to reproduce the problem on a ‘non-production’ server.

     

    I ran the sp_dropserver and sp_addserver procedures with the desired effect!

    I’m going to schedule this for the weekend…

     

    Tnx, for you replies!

  • December 22, 2005 at 2:59 am

    #611060

    Even we installed W2K3 SP1 last weekend on our prodcution servers and got the servers rebooted and @@servername is working fine w/o any probs.

    We didn't use sp_dropserver and sp_addserver..

     

     

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply