Server cannot resolve (local) name

Question

Server cannot resolve (local) name

jima

SSCrazy

Points: 2192
More actions
November 21, 2006 at 1:12 am

#171096

Hi,
We have a server that occasionaly cannot resolve the local name (local) i.e in DTS or in an import/export wizard & even QueryAnalyzer, although the EM seems to be ok as we can still connect & expand the tabs below the (LOCAL) registration name. Applications still can connect, you can query the Db from a client if you use the full server network name, but when this problem occurs we cannot even open DTS on the server.
This problem is resolved when we reboot the server, but re-occurs sporadically.
Anyone have any idea what is going on?
Thks in advance for any insight into this.
jim

Viewing 11 posts - 1 through 10 (of 10 total)

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

Johan Bijnens SSC Guru Points: 135379 More actions · Answer 1

regarding DTS, do you use your client's EM to edit the package ? (and have no local default instance of sqlserver at your client)

or do you use remote desktop to the server and then edit the package ?

Wich version of sqlserver are you using ( and SP?)

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

jima SSCrazy Points: 2192 More actions · Answer 2

Hi alzdba,

We edit the packages direct on our (Dev) server(s) with connection (local), this way we can src control them, then once tested successfully, we port them to other servers i,e test, uat, prod without having embedded Servernames in them.

Our clients are only clients with no instances of Sql on the client pc's.

We are using Win2003 Server SE + Sql 2000 SP3a.

Thks

j

Johan Bijnens SSC Guru Points: 135379 More actions · Answer 3

- Can you find anything related in Win-eventlog and/or sqlserver-logfiles ?

- Haven't encountered this issue yet, although I also RDC the server to manipulate packages.

- Are you using windows or sql-authentication for the connection(s) ?

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

jima SSCrazy Points: 2192 More actions · Answer 4

Hi,

Nothing in the event log & any errors reported in the Sql log come from our DTS packages failing because they can't connect ( resolve ) to 'local'.

Server is using NT & sql authentication, but when we are on the server we login using Sql authentication.

Other than that i'm stumped as there's no apparent error messages being logged, so we know the result of the problem, but cannot track down in the slightest the cause !

jim

Ian Yates SSCoach Points: 19738 More actions · Answer 5

Could you try using localhost rather than (local)?

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 6

can you run the following and send the results back

select @@servername

select serverproperty('machinename')

maybe the machine has been renamed since sql was installed? if so then the 2 vlaues will be different

possibly barking up the wrong tree here

MVDBA

barsuk SSChampion Points: 12280 More actions · Answer 7

Shoot in a dark: It can be your sysservers table in messed up?!

Also by placing select @@servername in a job and running it, say, every 5 minutes ( detecting when select @@servername returns Null, so it sends you notification) you can be earlier notified of the issue, before actually running the DTS.

jima SSCrazy Points: 2192 More actions · Answer 8

Hi,

Ok, this issue is an intermittent one, so unfortunately until the next time it occurs all options such as 'localhost', sysservers, serverproperty & servername are all ok, however at least i have a range of options to try the next time it occurs.

Thanks for all your input & should our issue happen again soon, I will post the results of your suggestions.

Regards.

j

jima SSCrazy Points: 2192 More actions · Answer 9

Hi barsuk,

Forgot to say your suggestion is something that we will implement to try & give us some warning of when the issue is going to happen.

Thanks.

j

ShekharNaidu SSCrazy Points: 2092 More actions · Answer 10

haiii.. I have similar issue like when I tried to start my SQL Server Agent it is getting stopped with the below error message in event log

"

SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).

"

Can anybody please help me in this regard

Thank You

Shekhar..

Thanks ,

Shekhar