May 9, 2011 at 1:09 pm
I am trying to create some maintenance plans on my clustered instance when I recieved this message:
" The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (Microsoft.SqlServer.Management.MaintenancePlanWizard)"
Now, I received that message from my desktop SSMS. However once I RDP'd to the active node and clicked on management >> Maintenance Plans... I was prompted with the Wizard Dialoge box. So just testing it out I tried to create a fake maintenance plan only to get another error "Create Maintenance Plan failed" Error 14234. So it seems SSIS isn't installed. I was not aware you needed SSIS to create maintenance plans. (I know...I'm new at this).
So now it looks like I need to install SSIS on each node of the cluster. However I am worried here b/c I know from the initial installation SQL Server was 'Cluster Aware' when it installed all the existing components. But now that I am coming back around and installing SSIS seperately will SQL Server know that SSIS should be installed with the cluster in mind or will it try and install SSIS as a standalone instance?
May 9, 2011 at 1:28 pm
This article was very helpful however I have one question I was hoping someone could answer...
The article states that one must "modify each of these configuration files to point to all available instances of SQL Server on which packages are stored. This solution provides the high availability that most customers need, without the potential problems encountered when the Integration Services service is configured as a cluster resource. For more information about how to change the configuration file, see Configuring the Integration Services (SSIS) Service."
However, when reading through the reference article on how to modify the config files to point to all instances,...I see nothing showing what needs to be done. Has anyone done this before?
May 9, 2011 at 2:15 pm
SQL Server 2005 RTM required SSIS to be installed to use the maintenance plan feature. As of service pack 1, that requirement was removed.
It sounds like you have not patched SQL Server to the latest service pack (SP4) AND you have not patched the client tools.
Upgrade everything on the server to SP4 and also make sure you upgrade your client tools on your desktop to match.
Once you have that done, you will not need SSIS installed and won't need to worry about configuring it in your cluster.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 10, 2011 at 11:06 am
You are correct! Thank you! I have since patched each node of the cluster up to sp4 individually by pausing the inactive node at the time through clus admin.
Thanks again!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply