Hello,
if I try to create a Maintenance Plan from my local workstation I get the following Error Message:
TITLE: Microsoft SQL Server Management Studio
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 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.
What is the problem?
Thanks,
Markus
It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.
Thanks,
Steve
Hello Markus,
this is happening to me after installing SQL2005 SP1. have you found a resolution?
SQL 2005 standard on x64...
Thanks, -justin
|||As suggested above, more detail will be helpful to address this problem.
Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.
Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?
Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.
If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.
In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.
|||Hey, if it makes you feel any better, I'm getting the same error.I'm using SQL Server 2005 x64, and recently installed SP1.
The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||
James,
I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.
I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.
Problems:
1) Could not create mainenace plans as explained by threadopener
2) Could not create new jobs, getting:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Please advice !
TIA
acki
|||Another little add on comment.
Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)
Problems:
1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"
Any help is highly appreciated !
acki
|||I'm having the same issue. Have any of you resolved it?
Running Windows Server 2003 R2 x64 with x64 SQL 2005.
Todd
|||I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.
Has anyone solved this? It's a big problem!
-md
|||Todd
As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.
|||I am also getting the same error. Sounds like a hot fix will be in order.
Did everyone else install the recent hotfixes as well?
|||We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.
Thanks,
jkh
|||
So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...
|||Let me see if I can clarify this a little.
We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.
SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.
Thanks,
jkh
|||Im not sure... fy im not running 64bit.. 32bit.
No comments:
Post a Comment