Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am trying to create a maintenance plan on a instance running SQL Server 2008 R2 SP1 (no CU's installed).

When completing the wizard I get the following error:

The object name cannot be changed from "{1E1746D3-B671-4799-8F61-7EE6117257C2}" to "Clean Up History" because another object in the collection already uses that name. Use a different name to resolve this error. ({1E1746D3-B671-4799-8F61-7EE6117257C2})

I've checked both [msdb].[dbo].[sysjobsteps] and [msdb].[dbo].[sysjobs] and neither contain the name "Clean Up History".

The server is being backed up by Microsoft DPM. Could it be that DPM inserts a cleanup job somewhere that I don't see?

share|improve this question
    
You mentioned sysjobsteps twice. I assume that was a mistake? Also, why don't you simply call the step something else; perhaps Clean_Up_History? –  Max Vernon Apr 13 '13 at 17:55
    
@MaxVernon Woops - corrected. It's the wizard who wants to use the name. I could do it all manually and get it working, but I'd like to know why I have a colliding object (and where I should find it). –  pauska Apr 13 '13 at 18:05
add comment

1 Answer 1

The job is "owned" by a maintenance plan in the following table, and I don't believe the names have to match. So you may want to check the following location:

SELECT name,id,description 
  FROM msdb..sysssispackages
  WHERE name = N'Clean Up History';

So you could rename that one, but it may cause problems later (some automated process may need to match on that name, or simply re-create it if it doesn't find it). So a much safer approach would be to use a different name for your own maintenance plan...

share|improve this answer
    
No results there either. I even installed integration services to see if it was a package, but nothing there. –  pauska Apr 13 '13 at 18:53
    
@pauska and what happens if when you manually create your maintenance plan you use a different name? –  Aaron Bertrand Apr 13 '13 at 18:54
    
It's not the maintenance plan name that collides, but a step. I can't choose the step name during the wizard. I can create manual plans with manual steps and name them whatever I want. I'm interested in finding out what object is holding the name "Clean Up History" –  pauska Apr 13 '13 at 20:03
    
I forgot to add. Yes, I can add a clear history task with a different name manually and it works. –  pauska Apr 13 '13 at 20:05
    
Without full access to your system I don't know that anyone here will be able to pinpoint the location of this mystery step. –  Aaron Bertrand Apr 13 '13 at 20:08
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.