January 29, 2010 at 10:27 am
I need assistance with troubleshooting a error received when trying to create a maintenance plan/or job. :w00t:
OS - MS Windows 2003 R2 Enterprise Ed/SP2 PAE
Clustered server - active/passive nodes
DB server - MS SQL Server Standard Ed/SP3
All programs installed including SSIS
Errror received when I try to create a maintenance plan
Cannot show requested dialog.
Additional information:
Unable to execute requested command.
Method not found: 'Void
Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'.(Microsoft.SqlServer.Management.MaintenancePlanWizard)
Unable to create jobs too...
January 29, 2010 at 3:35 pm
This will generally happen when the client tools have not been upgraded to at least the same version as the server you are connecting to.
Validate your clients tools have been upgraded to at least SP3.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
February 1, 2010 at 7:09 am
It is generally recommended to use coded scripts for maintenance instead of using maintenance plans, especially in case of enterprise servers.
You would be able to find a lot of scripts on the site depending on your need and then schedule to run as jobs.
They also allow for efficient management and troubleshooting.
Regards
Akhil
February 1, 2010 at 10:26 am
Actually, that is what I genearlly use when creating maintenance plans. However, everytime I created a new job using the maintenance stored procedures, clicked Ok to save and go back in to the job, everything was gone. That's why I tried creating a plan using the wizard just to see what would happen. Plan was created, but no contents. I did try reinstalling SP3 based on the first reply & received two failures.
Failure 1:
Database Services (MSSQLSERVER)
Error Number: 11009
No passive nodes were successfully patched
Failure 2:
Client Components
MSP Error: 29549 Failed to install and configure assemblies
(The transaction Manager is not available)
February 1, 2010 at 2:14 pm
Resolved the issue.
MSDTC would not start due to the fact that I needed to create a resource through cluster admin on both nodes. Started the MSDTC service, reinstalled SP3 with no errors. Job creation was successful. 😀
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply