2005 Maintenance Plan or Security bug?

Curious if this scenario is by design or a possible bug. As recommended by MS best practices for SQL 2000 we always removed the BUILTIN\Administrators login. After doing the same on our 2005 installations it appears to have caused errors in the edit\view functionality in the Maintenance Plans and jobs. One example is to open a plan in modify mode and then select the logging button. - 'Unhandled exception has occured in a component in your application' (have debug file)

Another error occurs when attempting to edit a step of the Maintenance Plan job. Select the subplan step > edit > select any tab other than General and this error occurs.

TITLE: SSIS Execution Properties

The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'domain\xxxxx'.). The SQL statement that was issued has failed.

I re-added the BUILTIN\Administrator to one 2005 instance and it corrected the errors completely. We are running Enterprise edition on W2K3 SP1 server using mixed mode auth. I do have Admin rights to the servers so it appears that windows security is being used for some maintenance plan functionality rather than the sql security. The errors could be reproduced running the Management Studio locally or remote connected as sa.

Any insight to this weirdness would be appreciated.

Allison

Check that you SQL Services have explicit access granted and aren't going through BUILTIN admins

|||Not sure exactly what you mean by 'have explicit access' but I did add the SQL Services start up account (domain account with server admin rights) as a sysadmin and it did not correct the problem.

All jobs execute with out the start up account having an explicit sql login.

Allison|||The (Login failed for user 'domain\xxxxx'.) is this a literal posting or have you blocked out the name of the account the SQL agent uses?
|||Might be that something in your plan accesses a location that doesn't exist or no permissions a granted for the user opening the plan...there should be useful information in the paramters passed to the LoadFromSQLServer method that could resolve this.
|||Yes I did block it out of the message but it was not the SQL Services account in the error message it was my user account. So what you are saying is that I can create a maintenance plan but when I attempt to edit it my credentials, not the service credentials are being checked?

Not sure hove to look at the parameters for LoadFromSQLServer.

Thanks
A|||Yes, when you automate a job it will run under a specified or agent account. When you are editing it, your account is being used to access the objects involved.