Database moved - How to change subscriptions

I want to change a subscription that has been created by another user. I'am NOT an administrator of the server, but I've given me all Reporting-Services permissions (including systemadministrator). The logfile says that I have to be a member of the sysadmin-role to change subscriptions owned by another user.
Thanks
Benjamin

I found out, that the problem appears when I move the database from one machine to another. All works fine, but the owner of the SQL-Server-Agent Job seems to cause the problems. On the source-machine it is ASPNET and on destination-machine its SYSTEM, when I manually change it back to ASPNET I can edit/save the subscriptions.

So how do I set the owner of the SQL-Server Agent Jobs programaticly for all Jobs?
Or is my concept of moving the database via backup/restore not the best solution?

Thanks
Benjamin

|||

After you have moved the database to another machine, you could actually go ahead and just delete all the RS generated SQL Agent Jobs before you start up the report server windows service.

On startup of the RS windows service it will automatically recreate the agent jobs if they were deleted.

-- Robert

|||Restarting the Service creates the jobs, thats right, but they have still the wrong owner..
On both machines the owner is ASPNET if I create a new subscription (or look at a existing subscription on the test-server). Deleting the Agent-Job and starting the Report-Server Service creates the Agent-Jobs with System as owner!
Even on the test-machine(source) deleting the Agent-Job and restarting ReportingServices produces this error..
I've made a little stored procedure which changes the owners, after running it all works as expected..
Create PROCEDURE [dbo].[sp_AlterOwnerOfAgentJob] ( @.username nvarchar(128))
AS
BEGIN
SET NOCOUNT ON;
declare @.jobname nvarchar(128),@.servername nvarchar(128),@.UserID uniqueidentifier
DECLARE job_cursor CURSOR FOR select name from msdb.dbo.sysjobs
OPEN job_cursor
FETCH NEXT FROM job_cursor INTO @.jobname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC msdb.dbo.sp_update_job @.job_name=@.jobname, @.owner_login_name=@.username
FETCH NEXT FROM job_cursor INTO @.jobname
END
CLOSE job_cursor
DEALLOCATE job_cursor
END
GO
exec sp_AlterOwnerOfAgentJob 'SERVERNAME\ASPNET'
GO

Is there any sp to list all jobs? That would make my sp work in further versions..
|||

Thanks for reporting this issue. We will look into this in more detail.

-- Robert

sql

Database moved - How to change subscription of another user.

I want to change a subscription that has been created by another user. I'am NOT an administrator of the server, but I've given me all Reporting-Services permissions (including systemadministrator). The logfile says that I have to be a member of the sysadmin-role to change subscriptions owned by another user.
Thanks
Benjamin

I found out, that the problem appears when I move the database from one machine to another. All works fine, but the owner of the SQL-Server-Agent Job seems to cause the problems. On the source-machine it is ASPNET and on destination-machine its SYSTEM, when I manually change it back to ASPNET I can edit/save the subscriptions.

So how do I set the owner of the SQL-Server Agent Jobs programaticly for all Jobs?
Or is my concept of moving the database via backup/restore not the best solution?

Thanks
Benjamin

|||

After you have moved the database to another machine, you could actually go ahead and just delete all the RS generated SQL Agent Jobs before you start up the report server windows service.

On startup of the RS windows service it will automatically recreate the agent jobs if they were deleted.

-- Robert

|||Restarting the Service creates the jobs, thats right, but they have still the wrong owner..
On both machines the owner is ASPNET if I create a new subscription (or look at a existing subscription on the test-server). Deleting the Agent-Job and starting the Report-Server Service creates the Agent-Jobs with System as owner!
Even on the test-machine(source) deleting the Agent-Job and restarting ReportingServices produces this error..
I've made a little stored procedure which changes the owners, after running it all works as expected..
Create PROCEDURE [dbo].[sp_AlterOwnerOfAgentJob] ( @.username nvarchar(128))
AS
BEGIN
SET NOCOUNT ON;
declare @.jobname nvarchar(128),@.servername nvarchar(128),@.UserID uniqueidentifier
DECLARE job_cursor CURSOR FOR select name from msdb.dbo.sysjobs
OPEN job_cursor
FETCH NEXT FROM job_cursor INTO @.jobname
WHILE @.@.FETCH_STATUS = 0
BEGIN
EXEC msdb.dbo.sp_update_job @.job_name=@.jobname, @.owner_login_name=@.username
FETCH NEXT FROM job_cursor INTO @.jobname
END
CLOSE job_cursor
DEALLOCATE job_cursor
END
GO
exec sp_AlterOwnerOfAgentJob 'SERVERNAME\ASPNET'
GO

Is there any sp to list all jobs? That would make my sp work in further versions..
|||

Thanks for reporting this issue. We will look into this in more detail.

-- Robert

Database Move

I have a web project in VS.NET 2005 on my development computer that uses an ASP.NET database (ASPNETDB.MDF) to manage user roles. Now I would like to move that database to a test computer with IIS. After copying the web project and database I am able to read from it but when I try to update I get the following error:

Failed to update database "C:\INETPUB\WWWROOT\MyWebApp\APP_DATA\ASPNETDB.MDF" because the database is read-only.

I think this is because the user 'Network Service' that IIS uses does not have access to the database. So how do I give 'Network Service' access to the database using SQL commands?

The problem is solved by closing VS.NET 2005 before moving the database and giving the user 'Network Service' full control to the database files.

database move

I recently moved a database and its transaction log file to another drive due
to space issues. I followed the kb article 224071 on how to move a user
database and it appears that it worked correctly.
However, now the database comes up as "read-only" and if I view the
properties of the db and try to remove the "read-only" designation, I get an
error that it can't.
Any thoughts'
RobertHi Robert
Check the SQL Server error log to see if there is any information on the
problem. You may also want to check that the readonly attribute is not set on
the mdf and ldf files.
John
"Robert Gandrud" wrote:
> I recently moved a database and its transaction log file to another drive due
> to space issues. I followed the kb article 224071 on how to move a user
> database and it appears that it worked correctly.
> However, now the database comes up as "read-only" and if I view the
> properties of the db and try to remove the "read-only" designation, I get an
> error that it can't.
> Any thoughts'
> Robert|||In the move of this large db/log to another volume, the sql service account
that starts mssqlserver didn't have specific rights to the new location. I
gave it full control to the new db location and rebooted.
The error log then stated that it performed a full recovery on that db,
which it couldn't do before. I was then able to remove the Read-only
property in the db properties in Ent. Mgr.
Thanks for your help.
Also, for some reason, I have about a 30GB log file. I was under the
understanding that if I backup the transaction log, that it would commit the
transactions and severly reduce my log file size, but that didn't seem to
work.
Any thoughts on that?
Thanks again,
Robert
"John Bell" wrote:
> Hi Robert
> Check the SQL Server error log to see if there is any information on the
> problem. You may also want to check that the readonly attribute is not set on
> the mdf and ldf files.
> John
> "Robert Gandrud" wrote:
> > I recently moved a database and its transaction log file to another drive due
> > to space issues. I followed the kb article 224071 on how to move a user
> > database and it appears that it worked correctly.
> >
> > However, now the database comes up as "read-only" and if I view the
> > properties of the db and try to remove the "read-only" designation, I get an
> > error that it can't.
> >
> > Any thoughts'
> >
> > Robert|||Hi
Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
on shrinking the transaction log.
John
"Robert Gandrud" wrote:
> In the move of this large db/log to another volume, the sql service account
> that starts mssqlserver didn't have specific rights to the new location. I
> gave it full control to the new db location and rebooted.
> The error log then stated that it performed a full recovery on that db,
> which it couldn't do before. I was then able to remove the Read-only
> property in the db properties in Ent. Mgr.
> Thanks for your help.
> Also, for some reason, I have about a 30GB log file. I was under the
> understanding that if I backup the transaction log, that it would commit the
> transactions and severly reduce my log file size, but that didn't seem to
> work.
> Any thoughts on that?
> Thanks again,
> Robert
> "John Bell" wrote:
> > Hi Robert
> >
> > Check the SQL Server error log to see if there is any information on the
> > problem. You may also want to check that the readonly attribute is not set on
> > the mdf and ldf files.
> >
> > John
> >
> > "Robert Gandrud" wrote:
> >
> > > I recently moved a database and its transaction log file to another drive due
> > > to space issues. I followed the kb article 224071 on how to move a user
> > > database and it appears that it worked correctly.
> > >
> > > However, now the database comes up as "read-only" and if I view the
> > > properties of the db and try to remove the "read-only" designation, I get an
> > > error that it can't.
> > >
> > > Any thoughts'
> > >
> > > Robertsql

database mirroring, methods for keeping logins synced.

I am in the process of implementing database mirroring. I am trying to get an understanding about manageable ways of keeping sql user logins synced between instances.

I have looked at KB918992 which makes sense for the initial intallation, but what about keeping passwords synced in the long-term. I don't want to have to manually set a users password on the failover every time they change it.

How is everyone else accomplishing this using sql logins (not windows auth)? Pointers to articles and/or documentation would be great.

Thanks.

Hi,

Came across this while trying to find out how to ensure that SQL logins have the same SIDs on the mirror server as well as the prinicipal server. There's a script shown that details how to create all the logins on the mirror server from the principal server. You could just add something to drop them at the start and run it every night or whenever necessary.

Hope this helps

http://www.mssqltips.com/tip.asp?tip1166

database mirroring

I am new user of SQl and preparing the exam database mirroring....can you tell me how i start the mirroirng ..what is my first tep..and is there only one instance

The first step is, you need at least 2 instances for mirroring, otherwise it's meaningless.

I suggest you open up SQL Server 2005 Books Online and read every topic on mirroring thoroughly.

Why are you taking an exam in it if you don't know anything about it? Seems a bit pointless to me, maybe I'm just jaded and cynical.

|||hi thanks for replying...i know about sql server..but i m a new user,but i know every thing about mirrioring....but i want to take some step that i directly use mirrioing,..and i want to clear MCTS sql and but i read rea 12 time the database mirrioirng topic on msdn, one day i will be a shinner administrator..I will prove you after few months, but i need some help that why i reply you..please do me in a favour

database mirroring

I am new user of SQl and preparing the exam database mirroring....can you tell me how i start the mirroirng ..what is my first tep..and is there only one instance

The first step is, you need at least 2 instances for mirroring, otherwise it's meaningless.

I suggest you open up SQL Server 2005 Books Online and read every topic on mirroring thoroughly.

Why are you taking an exam in it if you don't know anything about it? Seems a bit pointless to me, maybe I'm just jaded and cynical.

|||hi thanks for replying...i know about sql server..but i m a new user,but i know every thing about mirrioring....but i want to take some step that i directly use mirrioing,..and i want to clear MCTS sql and but i read rea 12 time the database mirrioirng topic on msdn, one day i will be a shinner administrator..I will prove you after few months, but i need some help that why i reply you..please do me in a favoursql

Database Marked as Single User Pls Help

Hi All,
Sql Server 7

I have database called ecatalog

i have a scheduled job which shrinks the database every day once at 12 am

today the job got failed

In the view Job history its showing the below contents
-----------------
Database 'ecatalog' is already open and can only have one user at a time. [SQLSTATE 42000] (Error
924) DBCC execution completed. If DBCC printed error messages, contact your system
administrator. [SQLSTATE 01000] (Message 2528). The step failed.

And in Application Log of event viewer its showing the below contents
------------------------
The description for Event ID ( 208 ) in Source ( SQLServerAgent$ABCSQL ) cannot be found. The
local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Shrink Database
- ecatalog, 0xA0C4F8157A744244A61A4ECABE8C6056, Failed, 4/19/2004 12:00:03 AM, The job failed.
The Job was invoked by Schedule 27 (Shrink Database - ecatalog). The last step to run was step 1 (Shrink Database - ecatalog)..

I ran the job manually it worked fine

but now when i go and see the database ecatalog in my Enterprise Manager
it is showing ecatalog(Single User)
What is the meaning of this, will this make any problem to my database

Please help me in this.

Waiting for Reply

AdilIt means only one connection can be allowed in this db. use sp_dboption 'ecatalog', 'single', 'false' to turn it off.|||Hi Thanks for reply,

I wanted to know that does this happens on its own or has some one has done it.

Thanks waiting for reply
Adil|||No it won't do this on its own. check all jobs to see if any sp_dboption command would have done that. Also check sql error logs and look for a series of Closing file, Starting up database and Opening file. that may represent an event to put the db in single user mode.

Note some operatins do require single user mode, such as using sp_rename to change a db name.|||I think that many of the maintenance jobs will put the database into SINGLE USER mode because it is required for some kinds of maintenance. Those jobs normally take the database back out of SINGLE USER automagically when they complete.

-PatP

Database Maintenance Plans

Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default...b;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry
Have you verified that the SQL Server Agent is running?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default...b;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry
|||Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Have you verified that the SQL Server Agent is running?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default...b;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>
|||Do you have any entries in the SQL Server or SQL Agent error logs - or the
Windows event logs?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Have you verified that the SQL Server Agent is running?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default...b;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>
|||There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>
>
|||Right click on SQL Server Agent in EM. Click on Display Error Log. I the
drop-down, select All Types. See if anything pops out.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
(Error
>
|||Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
> (Error
>
|||What did the warning say?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
the[vbcol=seagreen]
1).[vbcol=seagreen]
> (Error
Opened
>
|||[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:

> What did the warning say?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
> the
> 1).
> Opened
>
|||Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
narrow down the scope of the problem.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081433390.1425@.pastpower.ne t...
[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> What did the warning say?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
the[vbcol=seagreen]
> the
which[vbcol=seagreen]
View[vbcol=seagreen]
> 1).
have
> Opened
>

Database Maintenance Plans

Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
HarryHave you verified that the SQL Server Agent is running?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry|||Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Have you verified that the SQL Server Agent is running?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>|||Do you have any entries in the SQL Server or SQL Agent error logs - or the
Windows event logs?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Have you verified that the SQL Server Agent is running?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>|||There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>|||Right click on SQL Server Agent in EM. Click on Display Error Log. I the
drop-down, select All Types. See if anything pops out.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
(Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>|||Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>|||What did the warning say?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>|||[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
> What did the warning say?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>|||Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
narrow down the scope of the problem.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
> What did the warning say?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I
have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>|||Yes, I believe so.
I have other successfully completed jobs in SQL Server Agent > Jobs
Such as:
Start_Full on Palmas.PagesSearch.[15.6]
Desc: Scheduled full-text full population for full-text Catalog
PagesSearch in database Palmas. This job was created by the full-text
scheduling dialog or full-text index wizard..
SmartRisk Daily Content Expiry
Desc: Execute package: SmartRisk Daily Content Expiry
Which have completed successfully...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
> narrow down the scope of the problem.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
> [396] An idle CPU condition has not been defined - OnIdle job schedules
> will have no effect
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I
> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>|||I get the feeling that somehow, the DLL's relating to DBmaint may be
corrupted. I know you've tried re-doing the job. How about a new, simple
DB maintenance plan - just Northwind, full backup? Does that work?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
Yes, I believe so.
I have other successfully completed jobs in SQL Server Agent > Jobs
Such as:
Start_Full on Palmas.PagesSearch.[15.6]
Desc: Scheduled full-text full population for full-text Catalog
PagesSearch in database Palmas. This job was created by the full-text
scheduling dialog or full-text index wizard..
SmartRisk Daily Content Expiry
Desc: Execute package: SmartRisk Daily Content Expiry
Which have completed successfully...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
> narrow down the scope of the problem.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
> [396] An idle CPU condition has not been defined - OnIdle job schedules
> will have no effect
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
because
>> under 'Next Run Date' it says (Date and time are not available). I
> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>|||No, I tried that too before but with a different database.
I also tried it again now with Northwind.
It does not seem to execute. Under next run date it says dat and time are
not available. I also tried right clicking on the job and pressing start
job. Nothing seemed to happen...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> I get the feeling that somehow, the DLL's relating to DBmaint may be
> corrupted. I know you've tried re-doing the job. How about a new, simple
> DB maintenance plan - just Northwind, full backup? Does that work?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
> Yes, I believe so.
> I have other successfully completed jobs in SQL Server Agent > Jobs
> Such as:
> Start_Full on Palmas.PagesSearch.[15.6]
> Desc: Scheduled full-text full population for full-text Catalog
> PagesSearch in database Palmas. This job was created by the full-text
> scheduling dialog or full-text index wizard..
> SmartRisk Daily Content Expiry
> Desc: Execute package: SmartRisk Daily Content Expiry
> Which have completed successfully...
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
>> narrow down the scope of the problem.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
>> [396] An idle CPU condition has not been defined - OnIdle job schedules
>> will have no effect
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
>> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
> on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
>> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
> latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
>> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
> because
>> under 'Next Run Date' it says (Date and time are not available). I
>> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>>
>|||I think you're gonna have to open a ticket with Product Support Services.
It sounds like something has been corrupted.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081547010.1425@.pastpower.net...
No, I tried that too before but with a different database.
I also tried it again now with Northwind.
It does not seem to execute. Under next run date it says dat and time are
not available. I also tried right clicking on the job and pressing start
job. Nothing seemed to happen...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> I get the feeling that somehow, the DLL's relating to DBmaint may be
> corrupted. I know you've tried re-doing the job. How about a new, simple
> DB maintenance plan - just Northwind, full backup? Does that work?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
> Yes, I believe so.
> I have other successfully completed jobs in SQL Server Agent > Jobs
> Such as:
> Start_Full on Palmas.PagesSearch.[15.6]
> Desc: Scheduled full-text full population for full-text Catalog
> PagesSearch in database Palmas. This job was created by the full-text
> scheduling dialog or full-text index wizard..
> SmartRisk Daily Content Expiry
> Desc: Execute package: SmartRisk Daily Content Expiry
> Which have completed successfully...
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
>> narrow down the scope of the problem.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
>> [396] An idle CPU condition has not been defined - OnIdle job schedules
>> will have no effect
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
>> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server
log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I
find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
> on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
>> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
> latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so
I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
>> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
> because
>> under 'Next Run Date' it says (Date and time are not available). I
>> have
>> also tried simply right clicking the job and clicking Start Job.
This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>>
>