"Element Not Found" when trying to save a maintenance plan

Question

"Element Not Found" when trying to save a maintenance plan

Balance

SSCrazy

Points: 2636
More actions
July 10, 2008 at 7:43 am

#184499

I have a new install of Windows XP running SQL Server 2005 developer edition SP2 (along with Office, Visio, Project, SQL Server 2000 client tools) and all of the Microsoft updates except XP SP 3 have been loaded and I have tried to create a maintenance plan on the SQL 2005 database for the first time.
The wizard works fine but if I go into a plan and try to make changes I get a popup window when trying to save which says "Element Not Found".
I've searched the web to no avail (I've ensured everything is patched up as far as it can go since I identified the problem in the vague hope of a solution) and am looking for any hints that anyone can provide please!
Thanks

Viewing 15 posts - 1 through 15 (of 20 total)

You must be logged in to reply to this topic. Login to reply

george sibbald SSC Guru Points: 104210 More actions · Answer 1

are you connected locallty to the server or logged on remotely as a client? if the latter differences in version level of SSMS can cause this

---------------------------------------------------------------------

Balance SSCrazy Points: 2636 More actions · Answer 2

All the software is installed and being run from the same machine so I think everything should be considered local - I've not tried remote access to see if it is the client or database - I'll ask someone to have a go at accessing the database on my laptop and I'll try accessing a remote database to see if I can identify where the problem lies.

Thanks

Balance SSCrazy Points: 2636 More actions · Answer 3

I've checked and I have the same problem creating maintenance plans on remote servers whilst plans being created by others on my instance don't appear to suffer the same problem so I think the problem is client related.

The client is version 9.00.3042.00 and appears to be the latest & I cannot see an option just to remove the management studio alone.

george sibbald SSC Guru Points: 104210 More actions · Answer 4

is the instance also 9.00.3042?

---------------------------------------------------------------------

Balance SSCrazy Points: 2636 More actions · Answer 5

Interesting, I had thought they were the same but it seems the database is 9.00.3068

Problem is as far as I can tell the system thinks it is fully patched up so the version difference has been created "automatically" - any ideas how to bring them back in line without reinstalling everything from scratch?

Thanks

george sibbald SSC Guru Points: 104210 More actions · Answer 6

apply whichever rollup brings it to 3068 to the client?

---------------------------------------------------------------------

Balance SSCrazy Points: 2636 More actions · Answer 7

That's the problem - it's on SP2 and re-running says the client has higher patches in place so a patch for another product on the machine has probably caused the problem.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 8

i seem to remember this. The first release MS made of SQL 2005 SP2 had a bug with maintenance plans. Get the latest version of the SQL 2005 SP2 and apply that, when last i saw this we had used an old downloaded version of the service pack

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Balance SSCrazy Points: 2636 More actions · Answer 9

Thanks - I've just downloaded a new version but no luck, it thinks client tools have been updated later so won't allow any changes - so I have to suspect an update for MS office / visio / project has caused the problem.

Is there any news about SP3? That might be a handy route to solve the problem.

Balance SSCrazy Points: 2636 More actions · Answer 10

My problem appears to be solved!!

I've just started trying to use the "business intelligence studio" and got a similar message which was resolved via http://forums.msdn.microsoft.com/en-US/vssetup/thread/13eafe4f-ff91-4d31-922a-71767c14d3b3/ and that seems to have resolved my problem on maintenance plans.

Phew!

george sibbald SSC Guru Points: 104210 More actions · Answer 11

good news for info fix is to register msxml 6 (what that?)

To register MSXML 6.0.

1. From the Start menu, click Run.

2. Enter the following command:. regsvr32 %windir%\system32\msxml6.dll.

3. Click OK.

---------------------------------------------------------------------

Allison Stresing Valued Member Points: 72 More actions · Answer 12

I just installed Office 2007 and now I am having this same problem. Has anyone found a fix yet?

When trying to save a maintenance plan on my local machine, I get the error:

Element not found

When I remote to the server and try to save a maintenace plan, I get the error:

Library not registered

Balance SSCrazy Points: 2636 More actions · Answer 13

Yes - the above fix has been stable on my machine since I put it in place.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 14

Allison Stresing (8/5/2008)
I just installed Office 2007 and now I am having this same problem. Has anyone found a fix yet?
When trying to save a maintenance plan on my local machine, I get the error:
Element not found
When I remote to the server and try to save a maintenace plan, I get the error:
Library not registered

go into add\remove programs and run repair on .NET 2 framework

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉