On a fairly heavily used SQL2000 SP2 + security fixes server we get the
following messages quite often:-

[165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
[382] Logon to server '(local)' failed (JobManager)

and our transaction log backup jobs fail at this time.

We are looking at 306457 as a fix but does anybody have any other ideas why
this could be happening?

Thanks

Chris Wood
Alberta Department of Energy
CANADA

Hi There,

I had a problem the last couple of days on error382 in SQL 2000 relating
to invalid login ids and what else more.

I traced it back that someone resotred several databases on the network.

My setup is 7 SQL instances and what seems to happen is the SA account
of the other sql instances were used as the actual SQL instance (The one
with the problem) and running the jobs.

The jobs worked fine yea, but the notifications and all did not go away.

I changed the job owner to my local account on the domain and ever since
then i did not get a repsonse from SQL Agent.

God Luck , and if it fixed your problem please buzz.

Kind Regards
Xcorporation

--
Posted via http://dbforums.com

Thanks

Chris