Maintenance Plan Fails

9 May 2009 6:59 PM

Rick

Hello Group,

We were running SQL2000 and upgraded to SQL2005. After backing up our
databases to a remote HD and restoring them onto SQL2005 I can no longer run
a maintenance plan against the restored databases. For a test I created a
test database and used the maintenance plan wizard to create the backup plan.
When I execute the plan it works fine on the newly created test database. I
have been looking and looking for the reason for the failures against the
restored databaseâ€™s but just canâ€™t pin it down. So Iâ€™m hoping someone can
help out with my problem.

Thanks,
Rick Morgan

9 May 2009 8:51 PM

Andrew J. Kelly

Is the compatibility mode set to 80 or still at 70?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

Show quoteHide quote

"Rick" <R***@discussions.microsoft.com> wrote in message
news:45B30EA1-01CF-4170-B2D2-DDF69FF7A65F@microsoft.com...
> Hello Group,
>
> We were running SQL2000 and upgraded to SQL2005. After backing up our
> databases to a remote HD and restoring them onto SQL2005 I can no longer
> run
> a maintenance plan against the restored databases. For a test I created a
> test database and used the maintenance plan wizard to create the backup
> plan.
> When I execute the plan it works fine on the newly created test database.
> I
> have been looking and looking for the reason for the failures against the
> restored databaseâ€™s but just canâ€™t pin it down. So Iâ€™m hoping someone can
> help out with my problem.
>
> Thanks,
> Rick Morgan
>

11 May 2009 1:30 AM

Rick

It is set to 70.

Show quoteHide quote

"Andrew J. Kelly" wrote:

> Is the compatibility mode set to 80 or still at 70?
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Rick" <R***@discussions.microsoft.com> wrote in message
> news:45B30EA1-01CF-4170-B2D2-DDF69FF7A65F@microsoft.com...
> > Hello Group,
> >
> > We were running SQL2000 and upgraded to SQL2005. After backing up our
> > databases to a remote HD and restoring them onto SQL2005 I can no longer
> > run
> > a maintenance plan against the restored databases. For a test I created a
> > test database and used the maintenance plan wizard to create the backup
> > plan.
> > When I execute the plan it works fine on the newly created test database.
> > I
> > have been looking and looking for the reason for the failures against the
> > restored databaseâ€™s but just canâ€™t pin it down. So Iâ€™m hoping someone can
> > help out with my problem.
> >
> > Thanks,
> > Rick Morgan
> >
>
>

11 May 2009 1:37 AM

Rick

I set it to 80 and tried it failed. Here is part of the error.

Error: 2009-05-10 21:32:19.71 Code: 0xC001000E Source:
Description: The connection "{AFB82EF1-9A11-409C-81B1-9178A8A320C5}" is not
found. This error is thrown by Connections collection when the specific
connection element is not found. End Erro

11 May 2009 12:53 PM

Andrew J. Kelly

I am a little lost on exactly what you are doing. Did you restore MSDB as
well and is this a maintenance plan that was created on the 2000 server?
The 2000 plans are considered legacy and should be totally redone from
scratch using the new 2005 MP.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

Show quoteHide quote

"Rick" <R***@discussions.microsoft.com> wrote in message
news:58E8E920-6041-481A-AC77-A73CBF4E1B20@microsoft.com...
>I set it to 80 and tried it failed. Here is part of the error.
>
> Error: 2009-05-10 21:32:19.71 Code: 0xC001000E Source:
> Description: The connection "{AFB82EF1-9A11-409C-81B1-9178A8A320C5}" is
> not
> found. This error is thrown by Connections collection when the specific
> connection element is not found. End Erro

11 May 2009 9:59 PM

Erland Sommarskog

Rick (R***@discussions.microsoft.com) writes:

> I set it to 80 and tried it failed. Here is part of the error.

There was a little confusion in Andy's post. 70 is for SQL 7, 80 is the
mode for SQL 2000. The compatibility level for SQL 2005 is 90. However:

> Error: 2009-05-10 21:32:19.71 Code: 0xC001000E Source:
> Description: The connection "{AFB82EF1-9A11-409C-81B1-9178A8A320C5}" is
> not found. This error is thrown by Connections collection when the
> specific connection element is not found. End Erro

This error does not look like something that could depend on the
compat level.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx