error handling flow: maintenance

Showing posts with label maintenance. Show all posts

Wednesday, March 21, 2012

Error in SQL 2005 Maintenance Plan

I'm trying to setup a nightly backup to a remote computer using an SQL
Server 2005 Maintenance Plan. It keeps giving an error. I've narrowed
the cause down to an execute command...
EXECUTE master.dbo.xp_create_subdir
N'\\\\10.2.32.15\\Backup_SQL2005\\\\IOC'
which is giving the error below...
Msg 22048, Level 16, State 1, Line 0
xp_create_subdir() returned error 123, 'The filename, directory name,
or volume label syntax is incorrect.'
I am signed on as administrator on both computers. I'm able to map a
drive though the Windows Explorer and create a subdirectory on the
remote machine.
I have also tried...
EXECUTE master.dbo.xp_create_subdir N'\\10.2.32.15\Backup_SQL2005\IOC'
EXECUTE master.dbo.xp_create_subdir N'\\GOMB-BACKUP\Backup_SQL2005\IOC'
EXECUTE master.dbo.xp_create_subdir N'G:\IOC' (after mapping a drive)
This works...
EXECUTE master.dbo.xp_create_subdir N'C:\IOC'
...but of course it's on the local computer.
Any ideas why this doesn't work?
Thanks,
CThe stuff you do in Explorer uses the Windows account *you* have logged in w
ith. The stuff that SQL
Server does uses the Service account for the SQL Server service. Verify that
the service account has
proper permissions.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"The Cornjerker" <addoty@.gmail.com> wrote in message
news:1140218704.513963.300930@.g44g2000cwa.googlegroups.com...
> I'm trying to setup a nightly backup to a remote computer using an SQL
> Server 2005 Maintenance Plan. It keeps giving an error. I've narrowed
> the cause down to an execute command...
> EXECUTE master.dbo.xp_create_subdir
> N'\\\\10.2.32.15\\Backup_SQL2005\\\\IOC'
> which is giving the error below...
> Msg 22048, Level 16, State 1, Line 0
> xp_create_subdir() returned error 123, 'The filename, directory name,
> or volume label syntax is incorrect.'
> I am signed on as administrator on both computers. I'm able to map a
> drive though the Windows Explorer and create a subdirectory on the
> remote machine.
> I have also tried...
> EXECUTE master.dbo.xp_create_subdir N'\\10.2.32.15\Backup_SQL2005\IOC'
> EXECUTE master.dbo.xp_create_subdir N'\\GOMB-BACKUP\Backup_SQL2005\IOC'
> EXECUTE master.dbo.xp_create_subdir N'G:\IOC' (after mapping a drive)
> This works...
> EXECUTE master.dbo.xp_create_subdir N'C:\IOC'
> ...but of course it's on the local computer.
> Any ideas why this doesn't work?
> Thanks,
> C
>|||Tibor, thanks for the replay.
How do I give the Service account access to create remote
subdirectories?
C|||The Cornjerker (addoty@.gmail.com) writes:
> Tibor, thanks for the replay.
> How do I give the Service account access to create remote
> subdirectories?
As you would to for any other Windows user. (Which if you don't know is
a question for a Windows newsgroup. I hardly know it myself.)
Note howver, that you cannot do this if SQL Server is running under
Local System. In this case you need to change which account under which
SQL Server is running. To do this, right-click My Computer, select Manager,
find Services, and there find the SQL Server service. Double-click, and
log-on information is on the Log On tab.
If you are using SQL 2005, you should use the SQL Computer Manager instead.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland,
Thanks for the replay. Are there any di

vantages to running the
MSSQLSERVER service under the Administrator account?
C

Friday, March 9, 2012

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

Error in maintenance plan after SP2

Error in Maintenance Plan (tempdb)

Hello
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for
database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
José Júlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/defaul...kb;en-us;307487
"Jos Jlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file fo
r database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> Jos Jlio Duarte

Error in Maintenance Plan (tempdb)

Hello
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
JosÃ© JÃºlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/default.aspx?scid=kb;en-us;307487
"José Júlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> José Júlio Duarte

Error in Maintenance Plan (one of database)

Hello
When i execute the Maintenance Plan,
Database Maintenance Plan (Optimization):
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Sucess
[1] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:04:00
SQLMAINT.EXE Process Exit Code: 0 (Success)
************************************************************
but when i add this,
Database Maintenance Plan (Optimization):
(Check) Reorganize data and index pages
with
Reorganize pages with the original amount of free space
or
Change free space per page percentage to 10 %
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Failed - error
[1] Database openview: Index Rebuild (leaving 100%% free space)...
Rebuilding indexes for table 'OV_MS_Annotation'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
Server Driver][SQL Server]The log file for database 'openview' is full. Back
up the transaction log for the database to free up some log space.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
** Execution Time: 0 hrs, 0 mins, 2 secs **
[2] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:03:02
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Will it be that it doesn't let to execute everything in the same maintenance
Plan?
Regards,
JosÃ© JÃºlio DuarteJosÃ© JÃºlio Duarte wrote:
> Hello
> When i execute the Maintenance Plan,
> Database Maintenance Plan (Optimization):
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Sucess
> [1] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:04:00
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> ************************************************************
> but when i add this,
> Database Maintenance Plan (Optimization):
> (Check) Reorganize data and index pages
> with
> Reorganize pages with the original amount of free space
> or
> Change free space per page percentage to 10 %
>
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Failed - error
> [1] Database openview: Index Rebuild (leaving 100%% free space)...
> Rebuilding indexes for table 'OV_MS_Annotation'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The log file for database 'openview' is full. Back
> up the transaction log for the database to free up some log space.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> ** Execution Time: 0 hrs, 0 mins, 2 secs **
> [2] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:03:02
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> Will it be that it doesn't let to execute everything in the same maintenance
> Plan?
>
> Regards,
> JosÃ© JÃºlio Duarte
>
Reindexing generates a log of transaction log activity, and your
transaction log isn't big enough to handle the volume. Exactly what the
error message says.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hello Tracy
Where can i change to resolve this? and how?
Regards
"Tracy McKibben" wrote:
> JosÃ© JÃºlio Duarte wrote:
> > Hello
> >
> > When i execute the Maintenance Plan,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Sucess
> >
> > [1] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:04:00
> > SQLMAINT.EXE Process Exit Code: 0 (Success)
> >
> > ************************************************************
> > but when i add this,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Reorganize data and index pages
> > with
> > Reorganize pages with the original amount of free space
> > or
> > Change free space per page percentage to 10 %
> >
> >
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Failed - error
> >
> > [1] Database openview: Index Rebuild (leaving 100%% free space)...
> >
> > Rebuilding indexes for table 'OV_MS_Annotation'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The log file for database 'openview' is full. Back
> > up the transaction log for the database to free up some log space.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> > terminated.
> >
> > ** Execution Time: 0 hrs, 0 mins, 2 secs **
> >
> > [2] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:03:02
> > SQLMAINT.EXE Process Exit Code: 1 (Failed)
> >
> > Will it be that it doesn't let to execute everything in the same maintenance
> > Plan?
> >
> >
> > Regards,
> >
> > JosÃ© JÃºlio Duarte
> >
> Reindexing generates a log of transaction log activity, and your
> transaction log isn't big enough to handle the volume. Exactly what the
> error message says.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||JosÃ© JÃºlio Duarte wrote:
> Hello Tracy
> Where can i change to resolve this? and how?
>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your head.
Read about "Creating and Maintaining Databases" in Books Online to learn
how to configure automatic file growth.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> JosÃ© JÃºlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
> Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
> You should not be creating processes like this without understanding
> their impact. The fact that you have to ask how to expand (or
> auto-grow) a transaction log file tells me that you are in over your head.
> Read about "Creating and Maintaining Databases" in Books Online to learn
> how to configure automatic file growth.
>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||This is a multi-part message in MIME format.
--090306080204040602090200
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Tracy McKibben wrote:
> Tracy McKibben wrote:
>> JosÃ© JÃºlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
>>
>> Hmmmm... This is precisely why I DESPISE that maintenance plan
>> wizard. You should not be creating processes like this without
>> understanding their impact. The fact that you have to ask how to
>> expand (or auto-grow) a transaction log file tells me that you are in
>> over your head.
>> Read about "Creating and Maintaining Databases" in Books Online to
>> learn how to configure automatic file growth.
>>
> After re-reading this, I should clarify. I wasn't attacking you, my
> apologies if it looks that way. Those maintenance plan wizards
> frustrate me greatly, because they attempt to gloss over what are some
> very critical and potentially dangerous processes. Reindexing is an
> intensive process, and shouldn't be possible using a wizard, the
> administrator should fully understand what's going on throughout the
> process. Transaction log backups, if not done properly, can result in
> unusable backups, full log files, all sorts of things.
>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it.
Regards
Steen SchlÃ¼ter Persson
Databaseadministrator / Systemadministrator
--090306080204040602090200
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tracy McKibben wrote:
<blockquote cite="midOTbkp%23ppGHA.1140@.TK2MSFTNGP05.phx.gbl"
type="cite">Tracy McKibben wrote:
 
<blockquote type="cite">JosÃ© JÃºlio Duarte wrote:
 
<blockquote type="cite">Hello Tracy
 
Where can i change to resolve this? and how?
 
 
</blockquote>
 
Hmmmm...Â This is precisely why I DESPISE that maintenance plan wizard.
Â You should not be creating processes like this without understanding
their impact.Â The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your
head.
 
 
Read about "Creating and Maintaining Databases" in Books Online to
learn how to configure automatic file growth.
 
 
 
</blockquote>
 
After re-reading this, I should clarify.Â I wasn't attacking you, my
apologies if it looks that way.Â Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes.Â Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process.Â Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
 
 
</blockquote>
 
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it. 
 
 
-- 
Regards 
Steen SchlÃ¼ter Persson 
Databaseadministrator / Systemadministrator 

</body>
</html>
--090306080204040602090200--

Error in Maintenance Plan (one of database)

Error in Maintenance Plan

I saw recently the problem in Maintnence plan, it
reported following error
"[Microsoft][ODBC SQL Server Driver][SQL Server]Table
error: Object ID 1657877073. The text, ntext, or image
node at page (1:40241), slot 0, text ID 231871348736 is
not referenced."
I searched on Microsoft support site found Microsoft
Knowledge Base Article - 816084 and wondering Do any of
you has fix for it?
Thanks.
This is what the updated Books Online has to say about the error 8964:
Error 8964
Topic last updated -- January 2004
Severity Level 23
Message Text
Table error: Object ID O_ID. The text, ntext, or image node at page P_ID, slot S_ID, text ID TEXT_ID
is not referenced.
Explanation
The text node was not referenced in any complex column in any heap or clustered index. It is
effectively orphaned.
Action
HARDWARE FAILURE
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system
and application logs and the SQL ServerT error log to see if the error occurred as the result of
hardware failure. Fix any hardware related problems.
If you have persistent data corruption problems, try to swap out different hardware components to
isolate the problem. Check to ensure that your system does not have write caching enabled on the
disk controller. If you suspect this to be the problem, contact your hardware vendor.
Finally, you might find it beneficial to switch to a completely new hardware system, including
reformatting the disk drives and reinstalling the operating system.
RESTORE FROM BACKUP
If the problem is not hardware related and a known clean backup is available, restore the database
from the backup.
DBCC CHECKDB
If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the
extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC
CHECKDB with the appropriate repair clause to repair the corruption.
Caution If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact
your primary support provider before executing this statement.
Repair will cause the text node to be deleted.
Caution This repair may cause data loss.
If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your
primary support provider.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Farhan" <fsoomro@.chartlinks.com> wrote in message news:0fa701c49c2d$a5c4dc60$a301280a@.phx.gbl...
>I saw recently the problem in Maintnence plan, it
> reported following error
> "[Microsoft][ODBC SQL Server Driver][SQL Server]Table
> error: Object ID 1657877073. The text, ntext, or image
> node at page (1:40241), slot 0, text ID 231871348736 is
> not referenced."
> I searched on Microsoft support site found Microsoft
> Knowledge Base Article - 816084 and wondering Do any of
> you has fix for it?
> Thanks.
begin 666 update_topic.gif
M1TE&.#EA$@.`6`/<`````````A ``_P!"0@."$A #_`$*$A(0`A(2$`(2$A(2$
M_\;&QO\``/__`/______________________________________________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_____________________RP`````$@.`6```(? `="!188*#!@.PX*$ARH$.'"
MA \=,H384"+#!046:-RHD6&!CQ@.3?E2XP$')@.P4K"CQYDF!(E0IBQEP8$B+"
M!0ILAI3)<V7.@.34EXC1XDJ=,GT0M(@.4JT.A,DS]7*H6:U('3GT.9*LTJU:K3
3I5TM<C4Y=2S'LQRC>KUJ-" `.P``
`
end
begin 666 caution.gif
M1TE&.#EA# `+`/<``````#,``&8``)D``,P``/\````S`#,S`&8S`)DS`,PS
M`/\S``!F`#-F`&9F`)EF`,QF`/]F``"9`#.9`&:9`)F9`,R9`/^9``#,`#/,
M`&;,`)G,`,S,`/_,``#_`#/_`&;_`)G_`,S_`/__````,S,`,V8`,YD`,\P`
M,_\`,P`S,S,S,V8S,YDS,\PS,_\S,P!F,S-F,V9F,YEF,\QF,_]F,P"9,S.9
M,V:9,YF9,\R9,_^9,P#,,S/,,V;,,YG,,\S,,__,,P#_,S/_,V;_,YG_,\S_
M,___,P``9C,`9F8`9ID`9LP`9O\`9@.`S9C,S9F8S9IDS9LPS9 O\S9@.!F9C-F
M9F9F9IEF9LQF9O]F9@."99C.99F:99IF99LR99O^99@.#,9C/,9F;,9IG,9LS,
M9O_,9@.#_9C/_9F;_9IG_9LS_9O__9@.``F3,`F68`F9D`F<P`F?\`F0`SF3,S
MF68SF9DSF<PSF?\SF0!FF3-FF69FF9EFF<QFF?]FF0"9F3.9F6:9F9F9F<R9
MF?^9F0#,F3/,F6;,F9G,F<S,F?_,F0#_F3/_F6;_F9G_F<S_F?__F0``S#,`
MS&8`S)D`S,P`S/\`S `SS#,SS&8SS)DSS,PSS/\SS !FS#-FS&9FS)EFS,QF
MS/]FS "9S#.9S&:9S)F9S,R9S/^9S #,S#/,S&;,S)G,S,S,S/_,S #_S#/_
MS&;_S)G_S,S_S/__S ``_S,`_V8`_YD`_\P`__\`_P`S_S,S_V8S_YDS_\PS
M__\S_P!F_S-F_V9F_YEF_\QF__]F_P"9_S.9_V:9_YF9_\R9__^9_P#,_S/,
M_V;,_YG,_\S,___,_P#__S/__V;__YG__\S______P``````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M`````````````````````"'Y! $``*P`+ `````,``L`0 @.B`%D)'$BPH,&#
;K HH1)AP(4*%!1A"9$A1X,2'#BMBC#@.P( `[
`
end

Wednesday, March 21, 2012

Error in SQL 2005 Maintenance Plan

Friday, March 9, 2012

Error in maintenance plan after SP2

Error in maintenance plan after SP2

Error in maintenance plan after SP2

Error in Maintenance Plan (tempdb)

Error in Maintenance Plan (tempdb)

Error in Maintenance Plan (one of database)

Error in Maintenance Plan (one of database)

Error in Maintenance Plan

error handling flow

Blog Archive

About Me