September 13, 2010 at 11:56 pm
i want to create maintenance plan, but it shows the following error
TITLE: Maintenance Plan Wizard Progress
------------------------------
Create maintenance plan failed.
------------------------------
ADDITIONAL INFORMATION:
The connection type "ADO.NET:SQL" specified for connection manager "{CE5FB5CA-60FD-4932-B454-A0368F8F9A2E}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
(MaintenancePlan)
------------------------------
The connection type "ADO.NET:SQL" specified for connection manager "{CE5FB5CA-60FD-4932-B454-A0368F8F9A2E}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
(MaintenancePlan)
------------------------------
BUTTONS:
OK
------------------------------
plzzzzzzzzzzz help me
thankssssssss
September 14, 2010 at 12:14 am
What are you trying to accomplish and what are the steps you are doing to accomplish that?
When do you get this error message (at which step)?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 14, 2010 at 6:27 am
first step of the maintenance plan gets that error.
September 14, 2010 at 6:35 am
what sort of maintainence plan are you trying to create?
September 14, 2010 at 6:45 am
steveb. (9/14/2010)
what sort of maintainence plan are you trying to create?
I wonder if that matters here. It errors on the first step of the wizard according to the OP. Any idea what would cause that?
My thinking is that maybe the OP doesn't have the privs to run the wizard so it gives a connection error. Dunno for sure, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2010 at 6:56 am
I must have missed that second post.
It does seem like a permission issue, perhaps with the account IS is running under.
What service pack are you running?
September 15, 2010 at 7:11 am
Is SSIS installed on the server? I remember trying to create a plan where is was not and the error was cryptic and had nothing to do with SSIS missing.
September 15, 2010 at 8:39 am
i already installed ssis but the same problem has occured
September 15, 2010 at 8:42 am
and what service pack are you running?
I have had issues like this prior to installing SP2
September 15, 2010 at 8:48 am
There were lots of fixed in SP2, and there is a hot fix that you need post SP2 for 2005 servers. I would actually recommend SP3 for the server AND client tools.
Does this happen on other workstations for this server? Or for other servers from this workstation?
September 15, 2010 at 8:48 am
sql server 2005 service pack3
September 15, 2010 at 9:24 am
Do you get any errors in the event logs?
Is the maintenance plan being setup to run against a SQL server, or are you trying to connect it to some other db?
are you editing it directly from SSMS or did you try to create it in BIDS first? (if created in bids, i believe you won't be able to edit it from SSMS)
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 15, 2010 at 9:26 am
One simple thing to check is what version(s) of MSSQL are you running. I've had problems saving/editing maintenance plans using the 2008 management studio with SQL Server 2005.
You could also try running the management studio directly from the server, though this is not a best practice.
September 15, 2010 at 9:29 am
chrisph (9/15/2010)
One simple thing to check is what version(s) of MSSQL are you running. I've had problems saving/editing maintenance plans using the 2008 management studio with SQL Server 2005.You could also try running the management studio directly from the server, though this is not a best practice.
Or run it from any different machine. Running it from the server would at least eliminate that variable. Running from another machine removes the question as to whether it is a global or local issue - or if it is an SP issue on the server.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply