Error in maintenance plan after SP2

Before SP2 my maintenance plan was stable.
Now, I get the following when I try to modify the plan:
Microsoft SQL Server Management Studio is unable to load this document:
Retrieving the COM class factory for component with CLSID
{E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error:
8007007e
I can't edit the plan or delete the plan.
The logs say that the plan is running and succesfully backing up the
databases, but there are no files being produced in the backup directory. I
do not know where the files are going.
Note that the only modification to the SQL Server was the addition of SP2.
Prior to that everything was working.
Any suggestions will be appreciated.Ron
What is the status of MP? Is it in progress. I got the error when I tried to
run MP created on SP1 after installing SP2, but I was able to delete it an d
re-create. After that it works fine
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
> Before SP2 my maintenance plan was stable.
> Now, I get the following when I try to modify the plan:
> Microsoft SQL Server Management Studio is unable to load this document:
> Retrieving the COM class factory for component with CLSID
> {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error:
> 8007007e
> I can't edit the plan or delete the plan.
> The logs say that the plan is running and succesfully backing up the
> databases, but there are no files being produced in the backup directory.
> I
> do not know where the files are going.
> Note that the only modification to the SQL Server was the addition of SP2.
> Prior to that everything was working.
> Any suggestions will be appreciated.|||I can't delete it, look at it, modify it, or anyhting. I get the same error
if I try to create a new plan. The Microsoft.SqlServer.ManagedDTS is
mentioned in the error that appears when I try to create a new entry.
The log files indicate that it does run, but the backup is being sent to the
VIRTUAL_DEVICE. Note that the plan history has not had any entries since I
installed the SP2, but the SQL Server log says that the maintenance plan is
making the backup at the correct time.
The full error that appears when I try to create a new plan is below:
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
--
Program Location:
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
===================================
Retrieving the COM class factory for component with CLSID
{E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error:
8007007e. (Microsoft.SqlServer.ManagedDTS)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
"Uri Dimant" wrote:
> Ron
> What is the status of MP? Is it in progress. I got the error when I tried to
> run MP created on SP1 after installing SP2, but I was able to delete it an d
> re-create. After that it works fine
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
> > Before SP2 my maintenance plan was stable.
> >
> > Now, I get the following when I try to modify the plan:
> > Microsoft SQL Server Management Studio is unable to load this document:
> > Retrieving the COM class factory for component with CLSID
> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error:
> > 8007007e
> >
> > I can't edit the plan or delete the plan.
> >
> > The logs say that the plan is running and succesfully backing up the
> > databases, but there are no files being produced in the backup directory.
> > I
> > do not know where the files are going.
> >
> > Note that the only modification to the SQL Server was the addition of SP2.
> > Prior to that everything was working.
> >
> > Any suggestions will be appreciated.
>
>|||Ron
It looks like you have a DTS/SSIS Package tied in MP. Am I right?
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:EBD00BB2-A0A2-412C-AA31-33AA51B3EF1B@.microsoft.com...
>I can't delete it, look at it, modify it, or anyhting. I get the same error
> if I try to create a new plan. The Microsoft.SqlServer.ManagedDTS is
> mentioned in the error that appears when I try to create a new entry.
> The log files indicate that it does run, but the backup is being sent to
> the
> VIRTUAL_DEVICE. Note that the plan history has not had any entries since I
> installed the SP2, but the SQL Server log says that the maintenance plan
> is
> making the backup at the correct time.
> The full error that appears when I try to create a new plan is below:
> ===================================> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle&
> ctor,
> Boolean& bNeedSecurityCheck)
> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> fillCache)
> at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
> skipVisibilityChecks, Boolean fillCache)
> at System.Activator.CreateInstance(Type type, Boolean nonPublic)
> at
> Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
> ===================================> Retrieving the COM class factory for component with CLSID
> {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error:
> 8007007e. (Microsoft.SqlServer.ManagedDTS)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
>
> "Uri Dimant" wrote:
>> Ron
>> What is the status of MP? Is it in progress. I got the error when I tried
>> to
>> run MP created on SP1 after installing SP2, but I was able to delete it
>> an d
>> re-create. After that it works fine
>> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
>> > Before SP2 my maintenance plan was stable.
>> >
>> > Now, I get the following when I try to modify the plan:
>> > Microsoft SQL Server Management Studio is unable to load this document:
>> > Retrieving the COM class factory for component with CLSID
>> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following
>> > error:
>> > 8007007e
>> >
>> > I can't edit the plan or delete the plan.
>> >
>> > The logs say that the plan is running and succesfully backing up the
>> > databases, but there are no files being produced in the backup
>> > directory.
>> > I
>> > do not know where the files are going.
>> >
>> > Note that the only modification to the SQL Server was the addition of
>> > SP2.
>> > Prior to that everything was working.
>> >
>> > Any suggestions will be appreciated.
>>|||.Hi
There has been an issue with maintenance plans for SP2 see
https://blogs.msdn.com/sqlrem/ for more information, although on the face of
it your descriptions does not seem to be the same thing. It seems that a COM
class has been unregistered.
Is this a legacy maintenance plan or a new one?
Have you tried re-applying the Microsoft SQL Server 2000 DTS Designer
Components from the February 2007 - Feature Pack for Microsoft SQL Server 2005
http://www.microsoft.com/downloads/details.aspx?familyid=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en
John
"Ron" wrote:
> Before SP2 my maintenance plan was stable.
> Now, I get the following when I try to modify the plan:
> Microsoft SQL Server Management Studio is unable to load this document:
> Retrieving the COM class factory for component with CLSID
> {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error:
> 8007007e
> I can't edit the plan or delete the plan.
> The logs say that the plan is running and succesfully backing up the
> databases, but there are no files being produced in the backup directory. I
> do not know where the files are going.
> Note that the only modification to the SQL Server was the addition of SP2.
> Prior to that everything was working.
> Any suggestions will be appreciated.|||Thanks for your help...
The maintenance plan was created under SQL Server 2005 SP1 early in December
using the maintnenance wizard. All it is supposed to do is to back the
databases up to an internal drive. It worked OK until I installed SP2. The
only thing that has changed on the machine is the application of SQL Server
SP2 and any updates applied by the Windows Update program.
The SQL Server 2005 installation was done on a fresh computer about December
5. This is a development machine with the Visual Studio, etc. installed.
At this point, I cannot do anything with maintenance plans without getting
the same error. Whether I go through the wizard or by hand, I cannot create a
new MP, I cannot delete the existing MP and I cannot alter the existing MP.
"John Bell" wrote:
> .Hi
> There has been an issue with maintenance plans for SP2 see
> https://blogs.msdn.com/sqlrem/ for more information, although on the face of
> it your descriptions does not seem to be the same thing. It seems that a COM
> class has been unregistered.
> Is this a legacy maintenance plan or a new one?
> Have you tried re-applying the Microsoft SQL Server 2000 DTS Designer
> Components from the February 2007 - Feature Pack for Microsoft SQL Server 2005
> http://www.microsoft.com/downloads/details.aspx?familyid=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en
> John
> "Ron" wrote:
> > Before SP2 my maintenance plan was stable.
> >
> > Now, I get the following when I try to modify the plan:
> > Microsoft SQL Server Management Studio is unable to load this document:
> > Retrieving the COM class factory for component with CLSID
> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error:
> > 8007007e
> >
> > I can't edit the plan or delete the plan.
> >
> > The logs say that the plan is running and succesfully backing up the
> > databases, but there are no files being produced in the backup directory. I
> > do not know where the files are going.
> >
> > Note that the only modification to the SQL Server was the addition of SP2.
> > Prior to that everything was working.
> >
> > Any suggestions will be appreciated.|||Thanks for your help...
The maintenance plan was created under SQL Server 2005 SP1 early in December
using the maintnenance wizard. All it is supposed to do is to back the
databases up to an internal drive. It worked OK until I installed SP2. The
only thing that has changed on the machine is the application of SQL Server
SP2 and any updates applied by the Windows Update program.
The SQL Server 2005 installation was done on a fresh computer about December
5. This is a development machine with the Visual Studio, etc. installed.
At this point, I cannot do anything with maintenance plans without getting
the same error. Whether I go through the wizard or by hand, I cannot create a
new MP, I cannot delete the existing MP and I cannot alter the existing MP.
"Uri Dimant" wrote:
> Ron
> It looks like you have a DTS/SSIS Package tied in MP. Am I right?
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:EBD00BB2-A0A2-412C-AA31-33AA51B3EF1B@.microsoft.com...
> >I can't delete it, look at it, modify it, or anyhting. I get the same error
> > if I try to create a new plan. The Microsoft.SqlServer.ManagedDTS is
> > mentioned in the error that appears when I try to create a new entry.
> >
> > The log files indicate that it does run, but the backup is being sent to
> > the
> > VIRTUAL_DEVICE. Note that the plan history has not had any entries since I
> > installed the SP2, but the SQL Server log says that the maintenance plan
> > is
> > making the backup at the correct time.
> >
> > The full error that appears when I try to create a new plan is below:
> > ===================================> >
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > --
> > Program Location:
> >
> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle&
> > ctor,
> > Boolean& bNeedSecurityCheck)
> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > fillCache)
> > at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
> > skipVisibilityChecks, Boolean fillCache)
> > at System.Activator.CreateInstance(Type type, Boolean nonPublic)
> > at
> > Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
> >
> > ===================================> >
> > Retrieving the COM class factory for component with CLSID
> > {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error:
> > 8007007e. (Microsoft.SqlServer.ManagedDTS)
> >
> > --
> > Program Location:
> >
> > at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
> >
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Ron
> >>
> >> What is the status of MP? Is it in progress. I got the error when I tried
> >> to
> >> run MP created on SP1 after installing SP2, but I was able to delete it
> >> an d
> >> re-create. After that it works fine
> >>
> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
> >> > Before SP2 my maintenance plan was stable.
> >> >
> >> > Now, I get the following when I try to modify the plan:
> >> > Microsoft SQL Server Management Studio is unable to load this document:
> >> > Retrieving the COM class factory for component with CLSID
> >> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following
> >> > error:
> >> > 8007007e
> >> >
> >> > I can't edit the plan or delete the plan.
> >> >
> >> > The logs say that the plan is running and succesfully backing up the
> >> > databases, but there are no files being produced in the backup
> >> > directory.
> >> > I
> >> > do not know where the files are going.
> >> >
> >> > Note that the only modification to the SQL Server was the addition of
> >> > SP2.
> >> > Prior to that everything was working.
> >> >
> >> > Any suggestions will be appreciated.
> >>
> >>
> >>
>
>|||Ron,
I had something similar in trying to delete a job created by an SQL2005 MP.
You could do this in SQL2000 but not 2005. Maybe try deleting the job(s)
then try deleting the MP.
Chris
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:3FC825C3-1059-4DBA-8E23-34666B8B5F5E@.microsoft.com...
> Thanks for your help...
> The maintenance plan was created under SQL Server 2005 SP1 early in
> December
> using the maintnenance wizard. All it is supposed to do is to back the
> databases up to an internal drive. It worked OK until I installed SP2. The
> only thing that has changed on the machine is the application of SQL
> Server
> SP2 and any updates applied by the Windows Update program.
> The SQL Server 2005 installation was done on a fresh computer about
> December
> 5. This is a development machine with the Visual Studio, etc. installed.
> At this point, I cannot do anything with maintenance plans without getting
> the same error. Whether I go through the wizard or by hand, I cannot
> create a
> new MP, I cannot delete the existing MP and I cannot alter the existing
> MP.
>
> "John Bell" wrote:
>> .Hi
>> There has been an issue with maintenance plans for SP2 see
>> https://blogs.msdn.com/sqlrem/ for more information, although on the face
>> of
>> it your descriptions does not seem to be the same thing. It seems that a
>> COM
>> class has been unregistered.
>> Is this a legacy maintenance plan or a new one?
>> Have you tried re-applying the Microsoft SQL Server 2000 DTS Designer
>> Components from the February 2007 - Feature Pack for Microsoft SQL Server
>> 2005
>> http://www.microsoft.com/downloads/details.aspx?familyid=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en
>> John
>> "Ron" wrote:
>> > Before SP2 my maintenance plan was stable.
>> >
>> > Now, I get the following when I try to modify the plan:
>> > Microsoft SQL Server Management Studio is unable to load this document:
>> > Retrieving the COM class factory for component with CLSID
>> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following
>> > error:
>> > 8007007e
>> >
>> > I can't edit the plan or delete the plan.
>> >
>> > The logs say that the plan is running and succesfully backing up the
>> > databases, but there are no files being produced in the backup
>> > directory. I
>> > do not know where the files are going.
>> >
>> > Note that the only modification to the SQL Server was the addition of
>> > SP2.
>> > Prior to that everything was working.
>> >
>> > Any suggestions will be appreciated.|||Rom
I have no idea, sorry, probably you will need to re-install SQL Server 2005
and apply SP2
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:AD4BA58C-E05E-4A30-AD87-B2A9096CBA65@.microsoft.com...
> Thanks for your help...
> The maintenance plan was created under SQL Server 2005 SP1 early in
> December
> using the maintnenance wizard. All it is supposed to do is to back the
> databases up to an internal drive. It worked OK until I installed SP2. The
> only thing that has changed on the machine is the application of SQL
> Server
> SP2 and any updates applied by the Windows Update program.
> The SQL Server 2005 installation was done on a fresh computer about
> December
> 5. This is a development machine with the Visual Studio, etc. installed.
> At this point, I cannot do anything with maintenance plans without getting
> the same error. Whether I go through the wizard or by hand, I cannot
> create a
> new MP, I cannot delete the existing MP and I cannot alter the existing
> MP.
> "Uri Dimant" wrote:
>> Ron
>> It looks like you have a DTS/SSIS Package tied in MP. Am I right?
>> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> news:EBD00BB2-A0A2-412C-AA31-33AA51B3EF1B@.microsoft.com...
>> >I can't delete it, look at it, modify it, or anyhting. I get the same
>> >error
>> > if I try to create a new plan. The Microsoft.SqlServer.ManagedDTS is
>> > mentioned in the error that appears when I try to create a new entry.
>> >
>> > The log files indicate that it does run, but the backup is being sent
>> > to
>> > the
>> > VIRTUAL_DEVICE. Note that the plan history has not had any entries
>> > since I
>> > installed the SP2, but the SQL Server log says that the maintenance
>> > plan
>> > is
>> > making the backup at the correct time.
>> >
>> > The full error that appears when I try to create a new plan is below:
>> > ===================================>> >
>> > Exception has been thrown by the target of an invocation. (mscorlib)
>> >
>> > --
>> > Program Location:
>> >
>> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
>> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle&
>> > ctor,
>> > Boolean& bNeedSecurityCheck)
>> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
>> > fillCache)
>> > at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
>> > skipVisibilityChecks, Boolean fillCache)
>> > at System.Activator.CreateInstance(Type type, Boolean nonPublic)
>> > at
>> > Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
>> >
>> > ===================================>> >
>> > Retrieving the COM class factory for component with CLSID
>> > {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following
>> > error:
>> > 8007007e. (Microsoft.SqlServer.ManagedDTS)
>> >
>> > --
>> > Program Location:
>> >
>> > at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
>> >
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Ron
>> >>
>> >> What is the status of MP? Is it in progress. I got the error when I
>> >> tried
>> >> to
>> >> run MP created on SP1 after installing SP2, but I was able to delete
>> >> it
>> >> an d
>> >> re-create. After that it works fine
>> >>
>> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> >> news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
>> >> > Before SP2 my maintenance plan was stable.
>> >> >
>> >> > Now, I get the following when I try to modify the plan:
>> >> > Microsoft SQL Server Management Studio is unable to load this
>> >> > document:
>> >> > Retrieving the COM class factory for component with CLSID
>> >> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following
>> >> > error:
>> >> > 8007007e
>> >> >
>> >> > I can't edit the plan or delete the plan.
>> >> >
>> >> > The logs say that the plan is running and succesfully backing up the
>> >> > databases, but there are no files being produced in the backup
>> >> > directory.
>> >> > I
>> >> > do not know where the files are going.
>> >> >
>> >> > Note that the only modification to the SQL Server was the addition
>> >> > of
>> >> > SP2.
>> >> > Prior to that everything was working.
>> >> >
>> >> > Any suggestions will be appreciated.
>> >>
>> >>
>> >>
>>|||Hi Ron
Have you check the service pack log to see if there was any error when
installing SP2? What does SELECT @.@.VERSION return?
John|||Again, thanks for the help.
The @.@.Version...
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
On the error logs.......
The summary.txt file showed error number 3010 under the SQL Server Native
Client and the MSXML 6.0 Parser. There was no error description included.
When I looked at the detail logs for these items I found the following entry
at the end of the log (the entry was similar for both logs):
MSI (s) (78:B8) [08:26:27:812]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (78:B8) [08:26:27:812]: Post-install cleanup: removing installer
file 'C:\WINDOWS\Installer\b817255.msi'
MSI (s) (78:B8) [08:26:27:890]: Post-install cleanup: removing installer
file 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\ARPIco'
MSI (s) (78:B8) [08:26:27:906]: Post-install cleanup: removing installer
folder 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\' (if
empty)
MSI (s) (78:B8) [08:26:27:921]: MainEngineThread is returning 3010
MSI (s) (78:B4) [08:26:28:015]: Destroying RemoteAPI object.
MSI (s) (78:94) [08:26:28:015]: Custom Action Manager thread ending.
=== Logging stopped: 2/22/2007 8:26:27 ===MSI (c) (B0:F0) [08:26:28:015]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B0:F0) [08:26:28:015]: MainEngineThread is returning 3010
=== Verbose logging stopped: 2/22/2007 8:26:28 ===
This is the only reference to 3010 and I did not see anything in the detail
logs that looked like an error. However, since I am not familiar with those
logs and they are big, there may be somethng that I missed.
I think that the 3010 just indicates that a reboot will be required to
finish the job.
"John Bell" wrote:
> Hi Ron
> Have you check the service pack log to see if there was any error when
> installing SP2? What does SELECT @.@.VERSION return?
> John|||Thanks for your help!
"Uri Dimant" wrote:
> Rom
> I have no idea, sorry, probably you will need to re-install SQL Server 2005
> and apply SP2
>
>
>
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:AD4BA58C-E05E-4A30-AD87-B2A9096CBA65@.microsoft.com...
> > Thanks for your help...
> >
> > The maintenance plan was created under SQL Server 2005 SP1 early in
> > December
> > using the maintnenance wizard. All it is supposed to do is to back the
> > databases up to an internal drive. It worked OK until I installed SP2. The
> > only thing that has changed on the machine is the application of SQL
> > Server
> > SP2 and any updates applied by the Windows Update program.
> >
> > The SQL Server 2005 installation was done on a fresh computer about
> > December
> > 5. This is a development machine with the Visual Studio, etc. installed.
> >
> > At this point, I cannot do anything with maintenance plans without getting
> > the same error. Whether I go through the wizard or by hand, I cannot
> > create a
> > new MP, I cannot delete the existing MP and I cannot alter the existing
> > MP.
> >
> > "Uri Dimant" wrote:
> >
> >> Ron
> >>
> >> It looks like you have a DTS/SSIS Package tied in MP. Am I right?
> >>
> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> news:EBD00BB2-A0A2-412C-AA31-33AA51B3EF1B@.microsoft.com...
> >> >I can't delete it, look at it, modify it, or anyhting. I get the same
> >> >error
> >> > if I try to create a new plan. The Microsoft.SqlServer.ManagedDTS is
> >> > mentioned in the error that appears when I try to create a new entry.
> >> >
> >> > The log files indicate that it does run, but the backup is being sent
> >> > to
> >> > the
> >> > VIRTUAL_DEVICE. Note that the plan history has not had any entries
> >> > since I
> >> > installed the SP2, but the SQL Server log says that the maintenance
> >> > plan
> >> > is
> >> > making the backup at the correct time.
> >> >
> >> > The full error that appears when I try to create a new plan is below:
> >> > ===================================> >> >
> >> > Exception has been thrown by the target of an invocation. (mscorlib)
> >> >
> >> > --
> >> > Program Location:
> >> >
> >> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> >> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle&
> >> > ctor,
> >> > Boolean& bNeedSecurityCheck)
> >> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> >> > fillCache)
> >> > at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
> >> > skipVisibilityChecks, Boolean fillCache)
> >> > at System.Activator.CreateInstance(Type type, Boolean nonPublic)
> >> > at
> >> > Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
> >> >
> >> > ===================================> >> >
> >> > Retrieving the COM class factory for component with CLSID
> >> > {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following
> >> > error:
> >> > 8007007e. (Microsoft.SqlServer.ManagedDTS)
> >> >
> >> > --
> >> > Program Location:
> >> >
> >> > at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
> >> >
> >> >
> >> >
> >> > "Uri Dimant" wrote:
> >> >
> >> >> Ron
> >> >>
> >> >> What is the status of MP? Is it in progress. I got the error when I
> >> >> tried
> >> >> to
> >> >> run MP created on SP1 after installing SP2, but I was able to delete
> >> >> it
> >> >> an d
> >> >> re-create. After that it works fine
> >> >>
> >> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> >> news:6AAF8BAC-21E4-4C90-86BE-248AE268A0A0@.microsoft.com...
> >> >> > Before SP2 my maintenance plan was stable.
> >> >> >
> >> >> > Now, I get the following when I try to modify the plan:
> >> >> > Microsoft SQL Server Management Studio is unable to load this
> >> >> > document:
> >> >> > Retrieving the COM class factory for component with CLSID
> >> >> > {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following
> >> >> > error:
> >> >> > 8007007e
> >> >> >
> >> >> > I can't edit the plan or delete the plan.
> >> >> >
> >> >> > The logs say that the plan is running and succesfully backing up the
> >> >> > databases, but there are no files being produced in the backup
> >> >> > directory.
> >> >> > I
> >> >> > do not know where the files are going.
> >> >> >
> >> >> > Note that the only modification to the SQL Server was the addition
> >> >> > of
> >> >> > SP2.
> >> >> > Prior to that everything was working.
> >> >> >
> >> >> > Any suggestions will be appreciated.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Hi
3010 is a reboot required status see
http://support.microsoft.com/default.aspx/kb/290158/
I can't really suggest anything else apart from a call to PSS if you want to
get this resolved without re-installing.
John
"Ron" wrote:
> Again, thanks for the help.
> The @.@.Version...
> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
> NT 5.1 (Build 2600: Service Pack 2)
> On the error logs.......
> The summary.txt file showed error number 3010 under the SQL Server Native
> Client and the MSXML 6.0 Parser. There was no error description included.
> When I looked at the detail logs for these items I found the following entry
> at the end of the log (the entry was similar for both logs):
> MSI (s) (78:B8) [08:26:27:812]: Cleaning up uninstalled install packages, if
> any exist
> MSI (s) (78:B8) [08:26:27:812]: Post-install cleanup: removing installer
> file 'C:\WINDOWS\Installer\b817255.msi'
> MSI (s) (78:B8) [08:26:27:890]: Post-install cleanup: removing installer
> file 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\ARPIco'
> MSI (s) (78:B8) [08:26:27:906]: Post-install cleanup: removing installer
> folder 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\' (if
> empty)
> MSI (s) (78:B8) [08:26:27:921]: MainEngineThread is returning 3010
> MSI (s) (78:B4) [08:26:28:015]: Destroying RemoteAPI object.
> MSI (s) (78:94) [08:26:28:015]: Custom Action Manager thread ending.
> === Logging stopped: 2/22/2007 8:26:27 ===> MSI (c) (B0:F0) [08:26:28:015]: Decrementing counter to disable shutdown. If
> counter >= 0, shutdown will be denied. Counter after decrement: -1
> MSI (c) (B0:F0) [08:26:28:015]: MainEngineThread is returning 3010
> === Verbose logging stopped: 2/22/2007 8:26:28 ===> This is the only reference to 3010 and I did not see anything in the detail
> logs that looked like an error. However, since I am not familiar with those
> logs and they are big, there may be somethng that I missed.
> I think that the 3010 just indicates that a reboot will be required to
> finish the job.
>
> "John Bell" wrote:
> > Hi Ron
> >
> > Have you check the service pack log to see if there was any error when
> > installing SP2? What does SELECT @.@.VERSION return?
> >
> > John|||Thanks for your help. I can probably reinstall faster than I can call PSS so
that is what I will do.
"John Bell" wrote:
> Hi
> 3010 is a reboot required status see
> http://support.microsoft.com/default.aspx/kb/290158/
> I can't really suggest anything else apart from a call to PSS if you want to
> get this resolved without re-installing.
> John
> "Ron" wrote:
> > Again, thanks for the help.
> >
> > The @.@.Version...
> > Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07
> > Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
> > NT 5.1 (Build 2600: Service Pack 2)
> >
> > On the error logs.......
> > The summary.txt file showed error number 3010 under the SQL Server Native
> > Client and the MSXML 6.0 Parser. There was no error description included.
> >
> > When I looked at the detail logs for these items I found the following entry
> > at the end of the log (the entry was similar for both logs):
> > MSI (s) (78:B8) [08:26:27:812]: Cleaning up uninstalled install packages, if
> > any exist
> > MSI (s) (78:B8) [08:26:27:812]: Post-install cleanup: removing installer
> > file 'C:\WINDOWS\Installer\b817255.msi'
> > MSI (s) (78:B8) [08:26:27:890]: Post-install cleanup: removing installer
> > file 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\ARPIco'
> > MSI (s) (78:B8) [08:26:27:906]: Post-install cleanup: removing installer
> > folder 'C:\WINDOWS\Installer\{50A0893D-47D8-48E0-A7E8-44BCD7E4422E}\' (if
> > empty)
> > MSI (s) (78:B8) [08:26:27:921]: MainEngineThread is returning 3010
> > MSI (s) (78:B4) [08:26:28:015]: Destroying RemoteAPI object.
> > MSI (s) (78:94) [08:26:28:015]: Custom Action Manager thread ending.
> > === Logging stopped: 2/22/2007 8:26:27 ===> > MSI (c) (B0:F0) [08:26:28:015]: Decrementing counter to disable shutdown. If
> > counter >= 0, shutdown will be denied. Counter after decrement: -1
> > MSI (c) (B0:F0) [08:26:28:015]: MainEngineThread is returning 3010
> > === Verbose logging stopped: 2/22/2007 8:26:28 ===> >
> > This is the only reference to 3010 and I did not see anything in the detail
> > logs that looked like an error. However, since I am not familiar with those
> > logs and they are big, there may be somethng that I missed.
> >
> > I think that the 3010 just indicates that a reboot will be required to
> > finish the job.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Ron
> > >
> > > Have you check the service pack log to see if there was any error when
> > > installing SP2? What does SELECT @.@.VERSION return?
> > >
> > > John