I have a setup of SQL Server 2000 Active \ Passive Cluster on Windows 2003
Environment. Maintenance plans were created when the Node-1 was active.
Two weeks back the SQL Server cluster service failed over to Node-2, where
in all other services are remain in the Node-1.

But the backup jobs and all the other maintenance jobs are failing on Node
-2 with the following error.

"The job failed. The owner () of job DB Backup Job for DB Maintenance Plan
'UserDB Maintplan' does not have server access."

But all these jobs were owned by Windows Domain account which is member of
the 'Local Administrator Group'.

On workaround , I changed the job owner to a 'SQL Server Login' and the jobs
are running successfull now.

Is anyone faced the same kind of error?

Appreciate your views and ideas on what could have casued this problem.

Thanks

Job ownership is a huge pain point in SQL 2000, clustered or not. Much like
making DBO the owner of all objects in a database, I find making SA own all
jobs just keeps wierd things from happening. Next version will probably
change the rules again, but for now this is the way to do it.

Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator




"Siva Prasad [SIVA]" <SivaPrasadSIVA (AT) discussions (DOT) microsoft.com> wrote in
message news:5B1E972B-0A43-441C-94DB-60636DEE5D35 (AT) microsoft (DOT) com...

Was it a member of the 'local administrators' group on both the nodes? Just
checking.
SQL Server determines the server access by running xp_logininfo, there is a
bug in Windows 2003 which may cause it to fail or return incomplete
resultset
Check the KB articel 834859.
hth
--
Vikram Vamshi
Eclipsys Corporation
"Siva Prasad [SIVA]" <SivaPrasadSIVA (AT) discussions (DOT) microsoft.com> wrote in
message news:5B1E972B-0A43-441C-94DB-60636DEE5D35 (AT) microsoft (DOT) com...

Yes the Windows domain account used by SQL Server is member od 'Local
Administrator' Group of the both the nodes.

Also it has following previleges.,

Lock pages in memory -
Log on as a service -
Act as part of the operating system -
Back up files and directories -
Increase quotas
Increase scheduling priority -
Load and unload device drivers -
Restore files and directories -

When I tried with creating a Maintanace place on the current active node
that is Node-2, with job owner as the 'Windows domain account' the job ran
successfull.
It is strange, I won't understand this funny behaviour.



"Vikram Vamshi" wrote: