Newbie please help

I just hard to rebuild my entire pc and that included reinstall SQL 2000 SP4
Developers Edition.

I have a database that is configured recovery model full
this gives me transaction log backup also.

Now when my maintenance plan runs I get this error

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6004
Date: 8/28/2008
Time: 7:01:53 AM
User: N/A
Computer: TGKW001
Description:
Sqllib error: Database WrestlingHistory is not simple.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0008: 31 39 39 00 00 00 00 00 199.....
0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0018: 31 34 35 00 00 00 00 00 145.....

If I make the database simple then I can not backup the transaction log

This use to work and I never got the errors before.

I have SP4 installed for SQL

My pc is running Windows XP PRO SP3

I searched for a fix but I can not find one.

Anyone have any other idea?

Thanks

Tom

Tom,

The message you are getting makes it see that the maintenance plan is
confused. When you rebuilt your pc did you recreate the maintenance plan?
Or are you using a recovered maintenace plan?

In any case, can you do a log backup as a TSQL statement successfully? E.g.
BACKUP LOG Northwind TO DISK = 'D:\NorthwindBackup.TRN'

If you cannot, then maybe you will get a more meaningful message.

If you can, then the database itself is fine and the maintenance plan is
flaky. In that case, you might just try to recreate the maintenance plan.

Or, you could set your database to simple, then back to full. (This would
lose the current transaction log, of course.) Then do a full backup and try
the log backup again.

(Truth in advertising, I don't use the maintenance plans, but have my own
scripts. If you google around, you will find several sample 'maintenance
plan' TSQL scripting solutions available, should you want to go that
route. )

RLF

"Thomas R Grassi Jr" wrote in message
news:u4fTb9QCJHA.4576-at-TK2MSFTNGP05.phx.gbl...
>I just hard to rebuild my entire pc and that included reinstall SQL 2000
>SP4 Developers Edition.
>
> I have a database that is configured recovery model full
> this gives me transaction log backup also.
>
> Now when my maintenance plan runs I get this error
>
> Event Type: Error
> Event Source: VSS
> Event Category: None
> Event ID: 6004
> Date: 8/28/2008
> Time: 7:01:53 AM
> User: N/A
> Computer: TGKW001
> Description:
> Sqllib error: Database WrestlingHistory is not simple.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
> 0008: 31 39 39 00 00 00 00 00 199.....
> 0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
> 0018: 31 34 35 00 00 00 00 00 145.....
>
> If I make the database simple then I can not backup the transaction log
>
> This use to work and I never got the errors before.
>
> I have SP4 installed for SQL
>
> My pc is running Windows XP PRO SP3
>
> I searched for a fix but I can not find one.
>
> Anyone have any other idea?
>
> Thanks
>
> Tom
>

Russell

Thanks for your help

I created all new maint plans

I followed your steps and it seems to be working now
I will keep an eye on the main plan for the next couple of days once it
starts working properly it stays working from my past experience it is just
getting it right the first time that takes time.

If you have an example of a full recovery database script you did and you do
not mind sending me a sample that would be great.

But how do you schedule the scripts to run at a predetermined time? Day of
week and time of day etc.

Thanks

Tom



"Russell Fields" wrote in message
news:eRVdpORCJHA.1628-at-TK2MSFTNGP03.phx.gbl...
> Tom,
>
> The message you are getting makes it see that the maintenance plan is
> confused. When you rebuilt your pc did you recreate the maintenance plan?
> Or are you using a recovered maintenace plan?
>
> In any case, can you do a log backup as a TSQL statement successfully?
> E.g.
> BACKUP LOG Northwind TO DISK = 'D:\NorthwindBackup.TRN'
>
> If you cannot, then maybe you will get a more meaningful message.
>
> If you can, then the database itself is fine and the maintenance plan is
> flaky. In that case, you might just try to recreate the maintenance plan.
>
> Or, you could set your database to simple, then back to full. (This would
> lose the current transaction log, of course.) Then do a full backup and
> try the log backup again.
>
> (Truth in advertising, I don't use the maintenance plans, but have my own
> scripts. If you google around, you will find several sample 'maintenance
> plan' TSQL scripting solutions available, should you want to go that
> route. )
>
> RLF
>
> "Thomas R Grassi Jr" wrote in message
> news:u4fTb9QCJHA.4576-at-TK2MSFTNGP05.phx.gbl...
>>I just hard to rebuild my entire pc and that included reinstall SQL 2000
>>SP4 Developers Edition.
>>
>> I have a database that is configured recovery model full
>> this gives me transaction log backup also.
>>
>> Now when my maintenance plan runs I get this error
>>
>> Event Type: Error
>> Event Source: VSS
>> Event Category: None
>> Event ID: 6004
>> Date: 8/28/2008
>> Time: 7:01:53 AM
>> User: N/A
>> Computer: TGKW001
>> Description:
>> Sqllib error: Database WrestlingHistory is not simple.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>> 0008: 31 39 39 00 00 00 00 00 199.....
>> 0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>> 0018: 31 34 35 00 00 00 00 00 145.....
>>
>> If I make the database simple then I can not backup the transaction log
>>
>> This use to work and I never got the errors before.
>>
>> I have SP4 installed for SQL
>>
>> My pc is running Windows XP PRO SP3
>>
>> I searched for a fix but I can not find one.
>>
>> Anyone have any other idea?
>>
>> Thanks
>>
>> Tom
>>
>
>

Tom,

My backup scripts depend on a lot of infrastructure pieces that I have in
place, but there are scripts such as:

http://www.sqlteam.com/article/database-backup-script -- by Nigel Rivett
http://www.sqlservercentral.com/scri...Restore/62380/ -- by Ola
Hallengren.

If you have such scripts, you simple create a SQL Agent job and schedule it
for when you want it to run. The Maintenance Plans are also actually
scheduled through SQL Agent.

All the best,
RLF

"IfThomas R Grassi Jr" wrote in message
news:ekBtMyRCJHA.3484-at-TK2MSFTNGP04.phx.gbl...
> Russell
>
> Thanks for your help
>
> I created all new maint plans
>
> I followed your steps and it seems to be working now
> I will keep an eye on the main plan for the next couple of days once it
> starts working properly it stays working from my past experience it is
> just getting it right the first time that takes time.
>
> If you have an example of a full recovery database script you did and you
> do not mind sending me a sample that would be great.
>
> But how do you schedule the scripts to run at a predetermined time? Day of
> week and time of day etc.
>
> Thanks
>
> Tom
>
>
>
> "Russell Fields" wrote in message
> news:eRVdpORCJHA.1628-at-TK2MSFTNGP03.phx.gbl...
>> Tom,
>>
>> The message you are getting makes it see that the maintenance plan is
>> confused. When you rebuilt your pc did you recreate the maintenance
>> plan? Or are you using a recovered maintenace plan?
>>
>> In any case, can you do a log backup as a TSQL statement successfully?
>> E.g.
>> BACKUP LOG Northwind TO DISK = 'D:\NorthwindBackup.TRN'
>>
>> If you cannot, then maybe you will get a more meaningful message.
>>
>> If you can, then the database itself is fine and the maintenance plan is
>> flaky. In that case, you might just try to recreate the maintenance
>> plan.
>>
>> Or, you could set your database to simple, then back to full. (This would
>> lose the current transaction log, of course.) Then do a full backup and
>> try the log backup again.
>>
>> (Truth in advertising, I don't use the maintenance plans, but have my own
>> scripts. If you google around, you will find several sample 'maintenance
>> plan' TSQL scripting solutions available, should you want to go that
>> route. )
>>
>> RLF
>>
>> "Thomas R Grassi Jr" wrote in message
>> news:u4fTb9QCJHA.4576-at-TK2MSFTNGP05.phx.gbl...
>>>I just hard to rebuild my entire pc and that included reinstall SQL 2000
>>>SP4 Developers Edition.
>>>
>>> I have a database that is configured recovery model full
>>> this gives me transaction log backup also.
>>>
>>> Now when my maintenance plan runs I get this error
>>>
>>> Event Type: Error
>>> Event Source: VSS
>>> Event Category: None
>>> Event ID: 6004
>>> Date: 8/28/2008
>>> Time: 7:01:53 AM
>>> User: N/A
>>> Computer: TGKW001
>>> Description:
>>> Sqllib error: Database WrestlingHistory is not simple.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> Data:
>>> 0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>>> 0008: 31 39 39 00 00 00 00 00 199.....
>>> 0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>>> 0018: 31 34 35 00 00 00 00 00 145.....
>>>
>>> If I make the database simple then I can not backup the transaction log
>>>
>>> This use to work and I never got the errors before.
>>>
>>> I have SP4 installed for SQL
>>>
>>> My pc is running Windows XP PRO SP3
>>>
>>> I searched for a fix but I can not find one.
>>>
>>> Anyone have any other idea?
>>>
>>> Thanks
>>>
>>> Tom
>>>
>>
>>
>
>

Russell

I fixed the problem

It was not my maint plans or even SQL

It was Windows Live One Care which uses NTBACKUP and it runs every day at
7:00 AM
forgot all about that

I excluded my "F" drive and now it works

Thanks for the help and info

Tom
"Russell Fields" wrote in message
news:ux3FPfSCJHA.2476-at-TK2MSFTNGP06.phx.gbl...
> Tom,
>
> My backup scripts depend on a lot of infrastructure pieces that I have in
> place, but there are scripts such as:
>
> http://www.sqlteam.com/article/database-backup-script -- by Nigel Rivett
> http://www.sqlservercentral.com/scri...Restore/62380/ -- by
> Ola Hallengren.
>
> If you have such scripts, you simple create a SQL Agent job and schedule
> it for when you want it to run. The Maintenance Plans are also actually
> scheduled through SQL Agent.
>
> All the best,
> RLF
>
> "IfThomas R Grassi Jr" wrote in message
> news:ekBtMyRCJHA.3484-at-TK2MSFTNGP04.phx.gbl...
>> Russell
>>
>> Thanks for your help
>>
>> I created all new maint plans
>>
>> I followed your steps and it seems to be working now
>> I will keep an eye on the main plan for the next couple of days once it
>> starts working properly it stays working from my past experience it is
>> just getting it right the first time that takes time.
>>
>> If you have an example of a full recovery database script you did and you
>> do not mind sending me a sample that would be great.
>>
>> But how do you schedule the scripts to run at a predetermined time? Day
>> of week and time of day etc.
>>
>> Thanks
>>
>> Tom
>>
>>
>>
>> "Russell Fields" wrote in message
>> news:eRVdpORCJHA.1628-at-TK2MSFTNGP03.phx.gbl...
>>> Tom,
>>>
>>> The message you are getting makes it see that the maintenance plan is
>>> confused. When you rebuilt your pc did you recreate the maintenance
>>> plan? Or are you using a recovered maintenace plan?
>>>
>>> In any case, can you do a log backup as a TSQL statement successfully?
>>> E.g.
>>> BACKUP LOG Northwind TO DISK = 'D:\NorthwindBackup.TRN'
>>>
>>> If you cannot, then maybe you will get a more meaningful message.
>>>
>>> If you can, then the database itself is fine and the maintenance plan is
>>> flaky. In that case, you might just try to recreate the maintenance
>>> plan.
>>>
>>> Or, you could set your database to simple, then back to full. (This
>>> would lose the current transaction log, of course.) Then do a full
>>> backup and try the log backup again.
>>>
>>> (Truth in advertising, I don't use the maintenance plans, but have my
>>> own scripts. If you google around, you will find several sample
>>> 'maintenance plan' TSQL scripting solutions available, should you want
>>> to go that route. )
>>>
>>> RLF
>>>
>>> "Thomas R Grassi Jr" wrote in message
>>> news:u4fTb9QCJHA.4576-at-TK2MSFTNGP05.phx.gbl...
>>>>I just hard to rebuild my entire pc and that included reinstall SQL 2000
>>>>SP4 Developers Edition.
>>>>
>>>> I have a database that is configured recovery model full
>>>> this gives me transaction log backup also.
>>>>
>>>> Now when my maintenance plan runs I get this error
>>>>
>>>> Event Type: Error
>>>> Event Source: VSS
>>>> Event Category: None
>>>> Event ID: 6004
>>>> Date: 8/28/2008
>>>> Time: 7:01:53 AM
>>>> User: N/A
>>>> Computer: TGKW001
>>>> Description:
>>>> Sqllib error: Database WrestlingHistory is not simple.
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>>>> 0008: 31 39 39 00 00 00 00 00 199.....
>>>> 0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
>>>> 0018: 31 34 35 00 00 00 00 00 145.....
>>>>
>>>> If I make the database simple then I can not backup the transaction log
>>>>
>>>> This use to work and I never got the errors before.
>>>>
>>>> I have SP4 installed for SQL
>>>>
>>>> My pc is running Windows XP PRO SP3
>>>>
>>>> I searched for a fix but I can not find one.
>>>>
>>>> Anyone have any other idea?
>>>>
>>>> Thanks
>>>>
>>>> Tom
>>>>
>>>
>>>
>>
>>
>
>