SQL Setup Recomendation - Maintenance Plan Not Removing .b..

I did do this, but for whatever reason, it doesn't work.

Any other ideas?

Thanks,

Tim


"Ekrem Önsoy" wrote in message

> If you are sure that jobs run successfully (right click on the plans and
> see their histories) then ensure that you type a correct file extension,
> which is "bak" without the apostrophes. And ensure that you type a correct
> path for the back up files which are supposed to be deleted after a
> period.
>
> These are the common problems I see when someone complains about deleting
> old backups using a maintenance plan.
>
> --
> Ekrem Önsoy
>
>
>
> "Tim Shoemaker" wrote in message
>
>>I am having the same problem on all 6 of our SQL servers with the backup
>>job not deleting .bak files after a certain amount of days. The Microsoft
>>SQL Backup job runs, but the files are not deleting, even though I have
>>told it to.
>>
>> I am running SQL 2000 and SQL 2005.
>>
>> Does anyone have a good recomendation of a some SQL setup guides that I
>> could look through? I am convinced it has something to do with the SQL
>> Agent service and which user it is using to start the service. My next
>> step is to build a virtual invironment and see if it works on a default
>> installation, then make changes towards our current setup until the
>> process stops working.
>>
>> Thanks,
>>
>> Tim
>
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

Here is the message I get.

Date 10/16/2008 4:17:36 PM
Log SQL Agent (Current - 10/16/2008 4:17:00 PM)

Message
[298] SQLServer Error: 15404, Could not obtain information about Windows NT
group/user Domain\Administrator', error code 0x5. [SQLSTATE 42000]
(ConnIsLoginSysAdmin)

Tim


"Tim Shoemaker" wrote in message

>I did do this, but for whatever reason, it doesn't work.
>
> Any other ideas?
>
> Thanks,
>
> Tim
>
>
> "Ekrem Önsoy" wrote in message
>
>> If you are sure that jobs run successfully (right click on the plans and
>> see their histories) then ensure that you type a correct file extension,
>> which is "bak" without the apostrophes. And ensure that you type a
>> correct path for the back up files which are supposed to be deleted after
>> a period.
>>
>> These are the common problems I see when someone complains about deleting
>> old backups using a maintenance plan.
>>
>> --
>> Ekrem Önsoy
>>
>>
>>
>> "Tim Shoemaker" wrote in message
>>
>>>I am having the same problem on all 6 of our SQL servers with the backup
>>>job not deleting .bak files after a certain amount of days. The
>>>Microsoft SQL Backup job runs, but the files are not deleting, even
>>>though I have told it to.
>>>
>>> I am running SQL 2000 and SQL 2005.
>>>
>>> Does anyone have a good recomendation of a some SQL setup guides that I
>>> could look through? I am convinced it has something to do with the SQL
>>> Agent service and which user it is using to start the service. My next
>>> step is to build a virtual invironment and see if it works on a default
>>> installation, then make changes towards our current setup until the
>>> process stops working.
>>>
>>> Thanks,
>>>
>>> Tim
>>
>
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

Is this SQL Server server a member server of a Domain? If so, what account
do you use as your SQL Server service account?

--
Ekrem Önsoy



"Tim Shoemaker" wrote in message

> Here is the message I get.
>
> Date 10/16/2008 4:17:36 PM
> Log SQL Agent (Current - 10/16/2008 4:17:00 PM)
>
> Message
> [298] SQLServer Error: 15404, Could not obtain information about Windows
> NT group/user Domain\Administrator', error code 0x5. [SQLSTATE 42000]
> (ConnIsLoginSysAdmin)
>
> Tim
>
>
> "Tim Shoemaker" wrote in message
>
>>I did do this, but for whatever reason, it doesn't work.
>>
>> Any other ideas?
>>
>> Thanks,
>>
>> Tim
>>
>>
>> "Ekrem Önsoy" wrote in message
>>
>>> If you are sure that jobs run successfully (right click on the plans and
>>> see their histories) then ensure that you type a correct file extension,
>>> which is "bak" without the apostrophes. And ensure that you type a
>>> correct path for the back up files which are supposed to be deleted
>>> after a period.
>>>
>>> These are the common problems I see when someone complains about
>>> deleting old backups using a maintenance plan.
>>>
>>> --
>>> Ekrem Önsoy
>>>
>>>
>>>
>>> "Tim Shoemaker" wrote in message
>>>
>>>>I am having the same problem on all 6 of our SQL servers with the backup
>>>>job not deleting .bak files after a certain amount of days. The
>>>>Microsoft SQL Backup job runs, but the files are not deleting, even
>>>>though I have told it to.
>>>>
>>>> I am running SQL 2000 and SQL 2005.
>>>>
>>>> Does anyone have a good recomendation of a some SQL setup guides that I
>>>> could look through? I am convinced it has something to do with the SQL
>>>> Agent service and which user it is using to start the service. My next
>>>> step is to build a virtual invironment and see if it works on a default
>>>> installation, then make changes towards our current setup until the
>>>> process stops working.
>>>>
>>>> Thanks,
>>>>
>>>> Tim
>>>
>>
>
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

See if this helps:
http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-...ing.asp


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Tim Shoemaker" wrote in message

>I am having the same problem on all 6 of our SQL servers with the backup
>job not deleting .bak files after a certain amount of days. The Microsoft
>SQL Backup job runs, but the files are not deleting, even though I have
>told it to.
>
> I am running SQL 2000 and SQL 2005.
>
> Does anyone have a good recomendation of a some SQL setup guides that I
> could look through? I am convinced it has something to do with the SQL
> Agent service and which user it is using to start the service. My next
> step is to build a virtual invironment and see if it works on a default
> installation, then make changes towards our current setup until the
> process stops working.
>
> Thanks,
>
> Tim
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

Yes, it uses a local system account that was created and is part of the
administrators group on the local machine.

Thanks,

Tim


"Ekrem Önsoy" wrote in message

> Is this SQL Server server a member server of a Domain? If so, what account
> do you use as your SQL Server service account?
>
> --
> Ekrem Önsoy
>
>
>
> "Tim Shoemaker" wrote in message
>
>> Here is the message I get.
>>
>> Date 10/16/2008 4:17:36 PM
>> Log SQL Agent (Current - 10/16/2008 4:17:00 PM)
>>
>> Message
>> [298] SQLServer Error: 15404, Could not obtain information about Windows
>> NT group/user Domain\Administrator', error code 0x5. [SQLSTATE 42000]
>> (ConnIsLoginSysAdmin)
>>
>> Tim
>>
>>
>> "Tim Shoemaker" wrote in message
>>
>>>I did do this, but for whatever reason, it doesn't work.
>>>
>>> Any other ideas?
>>>
>>> Thanks,
>>>
>>> Tim
>>>
>>>
>>> "Ekrem Önsoy" wrote in message
>>>
>>>> If you are sure that jobs run successfully (right click on the plans
>>>> and see their histories) then ensure that you type a correct file
>>>> extension, which is "bak" without the apostrophes. And ensure that you
>>>> type a correct path for the back up files which are supposed to be
>>>> deleted after a period.
>>>>
>>>> These are the common problems I see when someone complains about
>>>> deleting old backups using a maintenance plan.
>>>>
>>>> --
>>>> Ekrem Önsoy
>>>>
>>>>
>>>>
>>>> "Tim Shoemaker" wrote in message
>>>>
>>>>>I am having the same problem on all 6 of our SQL servers with the
>>>>>backup job not deleting .bak files after a certain amount of days. The
>>>>>Microsoft SQL Backup job runs, but the files are not deleting, even
>>>>>though I have told it to.
>>>>>
>>>>> I am running SQL 2000 and SQL 2005.
>>>>>
>>>>> Does anyone have a good recomendation of a some SQL setup guides that
>>>>> I could look through? I am convinced it has something to do with the
>>>>> SQL Agent service and which user it is using to start the service. My
>>>>> next step is to build a virtual invironment and see if it works on a
>>>>> default installation, then make changes towards our current setup
>>>>> until the process stops working.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Tim
>>>>
>>>
>>
>
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

You did not answer my question which was about if your SQL Server server is
a member server in a domain or not. If it is, then it may need to reach to
AD to verify some info about the account and as you are using Local System
Account, this may cause some problems like this.

So, how about creating an AD account for your SQL Server and use it as your
SQL Server service? Assign this account write\delete\modify rights on that
backup folder and let us know what happens.

--
Ekrem Önsoy




"Tim Shoemaker" wrote in message

> Yes, it uses a local system account that was created and is part of the
> administrators group on the local machine.
>
> Thanks,
>
> Tim
>
>
> "Ekrem Önsoy" wrote in message
>
>> Is this SQL Server server a member server of a Domain? If so, what
>> account do you use as your SQL Server service account?
>>
>> --
>> Ekrem Önsoy
>>
>>
>>
>> "Tim Shoemaker" wrote in message
>>
>>> Here is the message I get.
>>>
>>> Date 10/16/2008 4:17:36 PM
>>> Log SQL Agent (Current - 10/16/2008 4:17:00 PM)
>>>
>>> Message
>>> [298] SQLServer Error: 15404, Could not obtain information about Windows
>>> NT group/user Domain\Administrator', error code 0x5. [SQLSTATE 42000]
>>> (ConnIsLoginSysAdmin)
>>>
>>> Tim
>>>
>>>
>>> "Tim Shoemaker" wrote in message
>>>
>>>>I did do this, but for whatever reason, it doesn't work.
>>>>
>>>> Any other ideas?
>>>>
>>>> Thanks,
>>>>
>>>> Tim
>>>>
>>>>
>>>> "Ekrem Önsoy" wrote in message
>>>>
>>>>> If you are sure that jobs run successfully (right click on the plans
>>>>> and see their histories) then ensure that you type a correct file
>>>>> extension, which is "bak" without the apostrophes. And ensure that you
>>>>> type a correct path for the back up files which are supposed to be
>>>>> deleted after a period.
>>>>>
>>>>> These are the common problems I see when someone complains about
>>>>> deleting old backups using a maintenance plan.
>>>>>
>>>>> --
>>>>> Ekrem Önsoy
>>>>>
>>>>>
>>>>>
>>>>> "Tim Shoemaker" wrote in message
>>>>>
>>>>>>I am having the same problem on all 6 of our SQL servers with the
>>>>>>backup job not deleting .bak files after a certain amount of days.
>>>>>>The Microsoft SQL Backup job runs, but the files are not deleting,
>>>>>>even though I have told it to.
>>>>>>
>>>>>> I am running SQL 2000 and SQL 2005.
>>>>>>
>>>>>> Does anyone have a good recomendation of a some SQL setup guides that
>>>>>> I could look through? I am convinced it has something to do with the
>>>>>> SQL Agent service and which user it is using to start the service.
>>>>>> My next step is to build a virtual invironment and see if it works on
>>>>>> a default installation, then make changes towards our current setup
>>>>>> until the process stops working.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Tim
>>>>>
>>>>
>>>
>>
>
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b.. 

On Oct 16, 4:05 pm, Ekrem Önsoy wrote:
> If you are sure that jobs run successfully (right click on the plans and see
> their histories) then ensure that you type a correct file extension, which
> is "bak" without the apostrophes. And ensure that you type a correct path
> for the back up files which are supposed to be deleted after a period.
>
> These are the common problems I see when someone complains about deleting
> old backups using amaintenanceplan.

Actually my problem, which has been plaguing me for a while, was
dumber and simpler than that.

Be sure you enter your extension without the period. e.g. "bak",
not ".bak". Otherwise the file matching rule will never match your
backup files (it is looking for "foo..bak" and not "foo.bak", and the
Maintenance Plan editor will quite happily let you do this.

<smacks forehead>

ouch!
 >> Stay informed about: SQL Setup Recomendation - Maintenance Plan Not Removing .b..