I've recently upgraded the SQL server from 7 to 2000 SP3. The database
maintenance plans were set to remove backup and log files older than 2 days,
but does not seem to be working any more. I removed the plan and entered a
new one last week and still the files are building and are not being removed
.
Any suggestions.
Thanks
Jim Tyou can write an ActiveX script and have it execute before your job
runs to clean up the server prior to maintenance.
Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 day
s,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being remov
ed.
> Any suggestions.
> Thanks
> Jim T|||I was going to write a vb program and schedule it to clean up, but I'm
surprised that it worked fine in 7 but now fails to work under SQL 2000. May
be I should not be surprised at all.
"GlennThomas5" wrote:
> you can write an ActiveX script and have it execute before your job
> runs to clean up the server prior to maintenance.
> Jim T wrote:
>|||Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 day
s,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being remov
ed.
> Any suggestions.
> Thanks
> Jim T
Check the maintenance plan history (right-click on the maintenance plan
in Enterprise Manager). Any error messages reported there?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Under the Plan History - No errors were reported - Task says 'Succeeded'
"Tracy McKibben" wrote:
> Jim T wrote:
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||I also checked the security on the directory which currently has "EVERYONE"
with all rights (Yes, I know it could be a security breach - but had to try
something)
"Tracy McKibben" wrote:
> Jim T wrote:
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Jim T wrote:
> Under the Plan History - No errors were reported - Task says 'Succeeded'
>
Is that the JOB history, or the PLAN history?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||One of the entries from the Plan history.
I looked at your web site and it reminded me to look into the SQL Server
Agnts jobs and checked the steps on the Database maintenance, even though th
e
DB Maint util says 2days, the script steps is saying
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
12E9433F-9CC4-4ACC-BF1D-EC7E4566B3EA -Rpt "D:\SQLDATA\LOG\DB Maintenance
Plan14.txt" -DelTxtRpt 4DAYS -WriteHistory -VrfyBackup -BkUpMedia DISK
-BkUpDB "D:\SQLDATA\BACKUP" -DelBkUps 4DAYS -CrBkSubDir -BkExt "BAK"'
I changed the script to 2DAYS and will check processing tonight. Since I
only found the issue 4 days ago and the plan is set for 2 days of files, it
was surprising to see the script with 4 instead of 2. I'll let you know
tommorrow if that worked.
"Tracy McKibben" wrote:
> Jim T wrote:
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Resolved, once the script step was changed to 2DAYS it is now cleaning up
after itself. Strange that the PLAN wizard shows 2 days while the script
shows 4DAYS - but I'll keep that in mind.
Thank you Tracy for a good web site
"Tracy McKibben" wrote:
> Jim T wrote:
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Showing posts with label upgraded. Show all posts
Showing posts with label upgraded. Show all posts
Thursday, March 8, 2012
Database Maintenance Plan not removing older files
I've recently upgraded the SQL server from 7 to 2000 SP3. The database
maintenance plans were set to remove backup and log files older than 2 days,
but does not seem to be working any more. I removed the plan and entered a
new one last week and still the files are building and are not being removed.
Any suggestions.
Thanks
Jim Tyou can write an ActiveX script and have it execute before your job
runs to clean up the server prior to maintenance.
Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 days,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being removed.
> Any suggestions.
> Thanks
> Jim T|||I was going to write a vb program and schedule it to clean up, but I'm
surprised that it worked fine in 7 but now fails to work under SQL 2000. May
be I should not be surprised at all.
"GlennThomas5" wrote:
> you can write an ActiveX script and have it execute before your job
> runs to clean up the server prior to maintenance.
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
>|||Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 days,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being removed.
> Any suggestions.
> Thanks
> Jim T
Check the maintenance plan history (right-click on the maintenance plan
in Enterprise Manager). Any error messages reported there?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Under the Plan History - No errors were reported - Task says 'Succeeded'
"Tracy McKibben" wrote:
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||I also checked the security on the directory which currently has "EVERYONE"
with all rights (Yes, I know it could be a security breach - but had to try
something)
"Tracy McKibben" wrote:
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Jim T wrote:
> Under the Plan History - No errors were reported - Task says 'Succeeded'
>
Is that the JOB history, or the PLAN history?
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||One of the entries from the Plan history.
I looked at your web site and it reminded me to look into the SQL Server
Agnts jobs and checked the steps on the Database maintenance, even though the
DB Maint util says 2days, the script steps is saying
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
12E9433F-9CC4-4ACC-BF1D-EC7E4566B3EA -Rpt "D:\SQLDATA\LOG\DB Maintenance
Plan14.txt" -DelTxtRpt 4DAYS -WriteHistory -VrfyBackup -BkUpMedia DISK
-BkUpDB "D:\SQLDATA\BACKUP" -DelBkUps 4DAYS -CrBkSubDir -BkExt "BAK"'
I changed the script to 2DAYS and will check processing tonight. Since I
only found the issue 4 days ago and the plan is set for 2 days of files, it
was surprising to see the script with 4 instead of 2. I'll let you know
tommorrow if that worked.
"Tracy McKibben" wrote:
> Jim T wrote:
> > Under the Plan History - No errors were reported - Task says 'Succeeded'
> >
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Resolved, once the script step was changed to 2DAYS it is now cleaning up
after itself. Strange that the PLAN wizard shows 2 days while the script
shows 4DAYS - but I'll keep that in mind.
Thank you Tracy for a good web site
"Tracy McKibben" wrote:
> Jim T wrote:
> > Under the Plan History - No errors were reported - Task says 'Succeeded'
> >
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
maintenance plans were set to remove backup and log files older than 2 days,
but does not seem to be working any more. I removed the plan and entered a
new one last week and still the files are building and are not being removed.
Any suggestions.
Thanks
Jim Tyou can write an ActiveX script and have it execute before your job
runs to clean up the server prior to maintenance.
Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 days,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being removed.
> Any suggestions.
> Thanks
> Jim T|||I was going to write a vb program and schedule it to clean up, but I'm
surprised that it worked fine in 7 but now fails to work under SQL 2000. May
be I should not be surprised at all.
"GlennThomas5" wrote:
> you can write an ActiveX script and have it execute before your job
> runs to clean up the server prior to maintenance.
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
>|||Jim T wrote:
> I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> maintenance plans were set to remove backup and log files older than 2 days,
> but does not seem to be working any more. I removed the plan and entered a
> new one last week and still the files are building and are not being removed.
> Any suggestions.
> Thanks
> Jim T
Check the maintenance plan history (right-click on the maintenance plan
in Enterprise Manager). Any error messages reported there?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Under the Plan History - No errors were reported - Task says 'Succeeded'
"Tracy McKibben" wrote:
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||I also checked the security on the directory which currently has "EVERYONE"
with all rights (Yes, I know it could be a security breach - but had to try
something)
"Tracy McKibben" wrote:
> Jim T wrote:
> > I've recently upgraded the SQL server from 7 to 2000 SP3. The database
> > maintenance plans were set to remove backup and log files older than 2 days,
> > but does not seem to be working any more. I removed the plan and entered a
> > new one last week and still the files are building and are not being removed.
> >
> > Any suggestions.
> >
> > Thanks
> > Jim T
> Check the maintenance plan history (right-click on the maintenance plan
> in Enterprise Manager). Any error messages reported there?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Jim T wrote:
> Under the Plan History - No errors were reported - Task says 'Succeeded'
>
Is that the JOB history, or the PLAN history?
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||One of the entries from the Plan history.
I looked at your web site and it reminded me to look into the SQL Server
Agnts jobs and checked the steps on the Database maintenance, even though the
DB Maint util says 2days, the script steps is saying
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
12E9433F-9CC4-4ACC-BF1D-EC7E4566B3EA -Rpt "D:\SQLDATA\LOG\DB Maintenance
Plan14.txt" -DelTxtRpt 4DAYS -WriteHistory -VrfyBackup -BkUpMedia DISK
-BkUpDB "D:\SQLDATA\BACKUP" -DelBkUps 4DAYS -CrBkSubDir -BkExt "BAK"'
I changed the script to 2DAYS and will check processing tonight. Since I
only found the issue 4 days ago and the plan is set for 2 days of files, it
was surprising to see the script with 4 instead of 2. I'll let you know
tommorrow if that worked.
"Tracy McKibben" wrote:
> Jim T wrote:
> > Under the Plan History - No errors were reported - Task says 'Succeeded'
> >
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Resolved, once the script step was changed to 2DAYS it is now cleaning up
after itself. Strange that the PLAN wizard shows 2 days while the script
shows 4DAYS - but I'll keep that in mind.
Thank you Tracy for a good web site
"Tracy McKibben" wrote:
> Jim T wrote:
> > Under the Plan History - No errors were reported - Task says 'Succeeded'
> >
> Is that the JOB history, or the PLAN history?
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Database Maintenance Plan dies with error 0x800401F3
I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
instead of my home-grown utility to run Check Database commands. I used the
wizard to create the plan and used the SQL Server Agent account, which has
sysadmin rights for now. When the job runs, it dies with the error:
Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
failed. The step failed.
I can't find any documentation on 0x800401F3. Any ideas? Thanks!There could be more detailed info if you right click on the Maintanence Plan
and click View History? (I'm note sure if you got the error message you
mentioned in your post from View History or not?)
--
Ekrem Ã?nsoy
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> instead of my home-grown utility to run Check Database commands. I used
> the
> wizard to create the plan and used the SQL Server Agent account, which has
> sysadmin rights for now. When the job runs, it dies with the error:
> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> failed. The step failed.
> I can't find any documentation on 0x800401F3. Any ideas? Thanks!|||Jeff,
Here are some discussions for you to check out. Hope that one helps
http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
one.
http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
RLF
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> instead of my home-grown utility to run Check Database commands. I used
> the
> wizard to create the plan and used the SQL Server Agent account, which has
> sysadmin rights for now. When the job runs, it dies with the error:
> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> failed. The step failed.
> I can't find any documentation on 0x800401F3. Any ideas? Thanks!|||The wrox thead recommended registry changes for IUSR. Which one? Repeat for
every domain controller?
The msdn thread below implies that you can only use SQL Security, not
integrated security, with a maintenance plan. Is that right? I have other
Agent jobs that use integrated security with no trouble. The user is
sysadmin and a domain administrator (as a test to see if that solved the
problem), so I don't know how much more privilege I can throw at it.
Most of these seem to be related to ASP pages. I'm not clear how that ties
in to a Database Maintenance plan. Or is it a problem with how Microsoft is
building the plan?
I appreciate the help - I just feel a little lost still. Thanks!
Jeff
"Russell Fields" wrote:
> Jeff,
> Here are some discussions for you to check out. Hope that one helps
> http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
> one.
> http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
> RLF
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
> >I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> > instead of my home-grown utility to run Check Database commands. I used
> > the
> > wizard to create the plan and used the SQL Server Agent account, which has
> > sysadmin rights for now. When the job runs, it dies with the error:
> >
> > Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> > Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> > Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> > create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> > Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> > failed. The step failed.
> >
> > I can't find any documentation on 0x800401F3. Any ideas? Thanks!
>
>|||The error message I posted is the detailed message from the View History.
That's all there is, unless there is more detail somewhere else that I could
not find.
Thanks!
Jeff
"Ekrem Ã?nsoy" wrote:
> There could be more detailed info if you right click on the Maintanence Plan
> and click View History? (I'm note sure if you got the error message you
> mentioned in your post from View History or not?)
> --
> Ekrem Ã?nsoy|||Did you specify a Report file for the plan? If not, give it a try and check that file...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:45E493C1-ADC6-4392-8CD2-6EE0F34BD071@.microsoft.com...
> The error message I posted is the detailed message from the View History.
> That's all there is, unless there is more detail somewhere else that I could
> not find.
> Thanks!
> Jeff
> "Ekrem Önsoy" wrote:
>> There could be more detailed info if you right click on the Maintanence Plan
>> and click View History? (I'm note sure if you got the error message you
>> mentioned in your post from View History or not?)
>> --
>> Ekrem Önsoy
>|||I generated a new version of the plan with the wizard and set the logging,
but no log was created. I also tried the e-mail output. I thinkk it dies
before it gets that far. I added an output file in the Agent job, but it
just repeats the "Could not create DTS.Application because of error
0x800401F3".
"Tibor Karaszi" wrote:
> Did you specify a Report file for the plan? If not, give it a try and check that file...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>|||Jeff,
I observe that you are running 9.00.3042.00, which is the initial SQL
Server 2005 SP2. I know that this had some problems with Maintenance Plans,
but I cannot detail all of the exposures, though some are mentioned here:
http://support.microsoft.com/kb/933508
You probably want to be at least at Cumulative Update 1 of SP2
http://support.microsoft.com/kb/935356/ but there are quite a few
cumulative update packages that have follow CU1.
I have seen recommendations a few months ago by people I respect to go to
3186 (CU3) but not beyond.
http://support.microsoft.com/kb/939537. If you pursue this, be sure to
follow the link regarding a DTS side-effect at
http://support.microsoft.com/kb/919224/.
FYI, there will be an SP3 later this year, according to:
http://blogs.technet.com/dataplatforminsider/archive/2008/04/15/sql-server-2005-sp3-coming-soon.aspx
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:eMKMFMKpIHA.4912@.TK2MSFTNGP03.phx.gbl...
> Jeff,
> Here are some discussions for you to check out. Hope that one helps
> http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
> one.
> http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
> RLF
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
>> instead of my home-grown utility to run Check Database commands. I used
>> the
>> wizard to create the plan and used the SQL Server Agent account, which
>> has
>> sysadmin rights for now. When the job runs, it dies with the error:
>> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
>> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
>> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
>> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
>> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
>> failed. The step failed.
>> I can't find any documentation on 0x800401F3. Any ideas? Thanks!
>|||Thanks! This is very helpful. I will work through the updates and see if
that helps. In the mean time, I can go back to running DBCC commands directly.
Jeff
"Russell Fields" wrote:
> Jeff,
> I observe that you are running 9.00.3042.00, which is the initial SQL
> Server 2005 SP2. I know that this had some problems with Maintenance Plans,
> but I cannot detail all of the exposures, though some are mentioned here:
> http://support.microsoft.com/kb/933508
...
instead of my home-grown utility to run Check Database commands. I used the
wizard to create the plan and used the SQL Server Agent account, which has
sysadmin rights for now. When the job runs, it dies with the error:
Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
failed. The step failed.
I can't find any documentation on 0x800401F3. Any ideas? Thanks!There could be more detailed info if you right click on the Maintanence Plan
and click View History? (I'm note sure if you got the error message you
mentioned in your post from View History or not?)
--
Ekrem Ã?nsoy
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> instead of my home-grown utility to run Check Database commands. I used
> the
> wizard to create the plan and used the SQL Server Agent account, which has
> sysadmin rights for now. When the job runs, it dies with the error:
> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> failed. The step failed.
> I can't find any documentation on 0x800401F3. Any ideas? Thanks!|||Jeff,
Here are some discussions for you to check out. Hope that one helps
http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
one.
http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
RLF
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> instead of my home-grown utility to run Check Database commands. I used
> the
> wizard to create the plan and used the SQL Server Agent account, which has
> sysadmin rights for now. When the job runs, it dies with the error:
> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> failed. The step failed.
> I can't find any documentation on 0x800401F3. Any ideas? Thanks!|||The wrox thead recommended registry changes for IUSR. Which one? Repeat for
every domain controller?
The msdn thread below implies that you can only use SQL Security, not
integrated security, with a maintenance plan. Is that right? I have other
Agent jobs that use integrated security with no trouble. The user is
sysadmin and a domain administrator (as a test to see if that solved the
problem), so I don't know how much more privilege I can throw at it.
Most of these seem to be related to ASP pages. I'm not clear how that ties
in to a Database Maintenance plan. Or is it a problem with how Microsoft is
building the plan?
I appreciate the help - I just feel a little lost still. Thanks!
Jeff
"Russell Fields" wrote:
> Jeff,
> Here are some discussions for you to check out. Hope that one helps
> http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
> one.
> http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
> RLF
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
> >I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
> > instead of my home-grown utility to run Check Database commands. I used
> > the
> > wizard to create the plan and used the SQL Server Agent account, which has
> > sysadmin rights for now. When the job runs, it dies with the error:
> >
> > Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
> > Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
> > Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
> > create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
> > Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
> > failed. The step failed.
> >
> > I can't find any documentation on 0x800401F3. Any ideas? Thanks!
>
>|||The error message I posted is the detailed message from the View History.
That's all there is, unless there is more detail somewhere else that I could
not find.
Thanks!
Jeff
"Ekrem Ã?nsoy" wrote:
> There could be more detailed info if you right click on the Maintanence Plan
> and click View History? (I'm note sure if you got the error message you
> mentioned in your post from View History or not?)
> --
> Ekrem Ã?nsoy|||Did you specify a Report file for the plan? If not, give it a try and check that file...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:45E493C1-ADC6-4392-8CD2-6EE0F34BD071@.microsoft.com...
> The error message I posted is the detailed message from the View History.
> That's all there is, unless there is more detail somewhere else that I could
> not find.
> Thanks!
> Jeff
> "Ekrem Önsoy" wrote:
>> There could be more detailed info if you right click on the Maintanence Plan
>> and click View History? (I'm note sure if you got the error message you
>> mentioned in your post from View History or not?)
>> --
>> Ekrem Önsoy
>|||I generated a new version of the plan with the wizard and set the logging,
but no log was created. I also tried the e-mail output. I thinkk it dies
before it gets that far. I added an output file in the Agent job, but it
just repeats the "Could not create DTS.Application because of error
0x800401F3".
"Tibor Karaszi" wrote:
> Did you specify a Report file for the plan? If not, give it a try and check that file...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>|||Jeff,
I observe that you are running 9.00.3042.00, which is the initial SQL
Server 2005 SP2. I know that this had some problems with Maintenance Plans,
but I cannot detail all of the exposures, though some are mentioned here:
http://support.microsoft.com/kb/933508
You probably want to be at least at Cumulative Update 1 of SP2
http://support.microsoft.com/kb/935356/ but there are quite a few
cumulative update packages that have follow CU1.
I have seen recommendations a few months ago by people I respect to go to
3186 (CU3) but not beyond.
http://support.microsoft.com/kb/939537. If you pursue this, be sure to
follow the link regarding a DTS side-effect at
http://support.microsoft.com/kb/919224/.
FYI, there will be an SP3 later this year, according to:
http://blogs.technet.com/dataplatforminsider/archive/2008/04/15/sql-server-2005-sp3-coming-soon.aspx
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:eMKMFMKpIHA.4912@.TK2MSFTNGP03.phx.gbl...
> Jeff,
> Here are some discussions for you to check out. Hope that one helps
> http://p2p.wrox.com/topic.asp?TOPIC_ID=43327 Read the last post for this
> one.
> http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_21769758.html
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=361588&SiteID=1
> RLF
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:DFEB0C82-CA48-489B-BCFC-D6EC3D125FB7@.microsoft.com...
>>I just upgraded to SQ-Server 2005 and decided to use a Maintenance Plan
>> instead of my home-grown utility to run Check Database commands. I used
>> the
>> wizard to create the plan and used the SQL Server Agent account, which
>> has
>> sysadmin rights for now. When the job runs, it dies with the error:
>> Executed as user: mydomain\username. Microsoft (R) SQL Server Execute
>> Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft
>> Corp 1984-2005. All rights reserved. Started: 11:47:22 AM Could not
>> create DTS.Application because of error 0x800401F3 Started: 11:47:22 AM
>> Finished: 11:47:22 AM Elapsed: 0.046 seconds. The package execution
>> failed. The step failed.
>> I can't find any documentation on 0x800401F3. Any ideas? Thanks!
>|||Thanks! This is very helpful. I will work through the updates and see if
that helps. In the mean time, I can go back to running DBCC commands directly.
Jeff
"Russell Fields" wrote:
> Jeff,
> I observe that you are running 9.00.3042.00, which is the initial SQL
> Server 2005 SP2. I know that this had some problems with Maintenance Plans,
> but I cannot detail all of the exposures, though some are mentioned here:
> http://support.microsoft.com/kb/933508
...
Friday, February 24, 2012
Database mail does not work from Sql Server Agent Job after upgrade to SP1
Upgraded SQL Server 2005 x64 to Service Pack 1 expressly for the purpose of enabling Database Mail from SQL Job, which was a known bug that was listed as fixed in this Service Pack. It still does not work; in fact after installing SP1 on an x86 SQL Server Standard, Database Mail does not work from there now either, although it did prior to the upgrade! I am using Integrated Security.
Error message received: The job succeeded. The Job was invoked by User <name>. The last step to run was step 1 (Select). NOTE: Failed to notify 'Mike Schelstrate' via email.
Message in Error Log: [264] An attempt was made to send an email when no email session has been established.
Send test Email does work on both Servers.
Here is another Error message I found in the SQL Error Logs: [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs). Looks like this may be the root of the problem because it does not exist, I checked. How do I obtain this missing extended stored procedure?
I had the exact same problem with the same error on 2005. To fix it, I did the following:
1. Went into object-explorer, right-clicked on the SQL Server Agent, and selected properties. Then went to the Alert System page, and enabled the mail profile for the server agent. (you may already have this).
2. Then, went to "Database mail", right-clicked and selected "Configure Database mail." Selected "Manage profile security" and made sure my profile was set to public. THEN, and this is the kicker, clicked on the "Default Profile" field and set it to "yes".
|||I am still having issues after working through all these steps. Any other suggestions.
In general I seem to be having a lot of issues with the 64 Bit on 2005.
|||I'm having the exact same issue.
I have SQL Server Standard Edition 2005 (SP1) running and the Database Mail is not working correctly. I get a message in the SQL Agent log saying:
"SQLServer Error: 2812, Could not find stored procedure msdb.dbo.xp_sqlagent_notify"
Any solutions to this? What is this stored procedure? I can't find any documentation on it on Microsoft's site or anywhere for that matter.
|||I just started working on the mail on my test server and I have the same problem.
I have followed the instruction above to no avail. I have set up a job, when it completes it is to email me. I have set up mail and have been able to send a test mail by right clicking the db mail and selecting send test mail. I have se my self up as an operator. I have enabled db mail. The only thing I find odd is when I go to SQL server agent and select properties then select alert system the test button is grayed out.
|||Ok I found another test I could run to see if I have it configured correctly.
EXEC msdb.dbo.sp_send_dbmail
@.recipients=N'User@.Place.com',
@.subject=N'just another mail test.',
@.body=N'just another mail test.',
@.profile_name = 'EMail';
When I run this I get the response that the mail is queued. Shortly there after I get the mail. In my case there must be an issue between the jobs and the operator.
|||Ok it looks like I might have solve it for my self. Follow this link
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322173&SiteID=1
Database mail does not work from Sql Server Agent Job after upgrade to SP1
Upgraded SQL Server 2005 x64 to Service Pack 1 expressly for the purpose of enabling Database Mail from SQL Job, which was a known bug that was listed as fixed in this Service Pack. It still does not work; in fact after installing SP1 on an x86 SQL Server Standard, Database Mail does not work from there now either, although it did prior to the upgrade! I am using Integrated Security.
Error message received: The job succeeded. The Job was invoked by User <name>. The last step to run was step 1 (Select). NOTE: Failed to notify 'Mike Schelstrate' via email.
Message in Error Log: [264] An attempt was made to send an email when no email session has been established.
Send test Email does work on both Servers.
Here is another Error message I found in the SQL Error Logs: [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs). Looks like this may be the root of the problem because it does not exist, I checked. How do I obtain this missing extended stored procedure?
I had the exact same problem with the same error on 2005. To fix it, I did the following:
1. Went into object-explorer, right-clicked on the SQL Server Agent, and selected properties. Then went to the Alert System page, and enabled the mail profile for the server agent. (you may already have this).
2. Then, went to "Database mail", right-clicked and selected "Configure Database mail." Selected "Manage profile security" and made sure my profile was set to public. THEN, and this is the kicker, clicked on the "Default Profile" field and set it to "yes".
|||I am still having issues after working through all these steps. Any other suggestions.
In general I seem to be having a lot of issues with the 64 Bit on 2005.
|||
I'm having the exact same issue.
I have SQL Server Standard Edition 2005 (SP1) running and the Database Mail is not working correctly. I get a message in the SQL Agent log saying:
"SQLServer Error: 2812, Could not find stored procedure msdb.dbo.xp_sqlagent_notify"
Any solutions to this? What is this stored procedure? I can't find any documentation on it on Microsoft's site or anywhere for that matter.
|||I just started working on the mail on my test server and I have the same problem.
I have followed the instruction above to no avail. I have set up a job, when it completes it is to email me. I have set up mail and have been able to send a test mail by right clicking the db mail and selecting send test mail. I have se my self up as an operator. I have enabled db mail. The only thing I find odd is when I go to SQL server agent and select properties then select alert system the test button is grayed out.
|||Ok I found another test I could run to see if I have it configured correctly.
EXEC msdb.dbo.sp_send_dbmail
@.recipients=N'User@.Place.com',
@.subject=N'just another mail test.',
@.body=N'just another mail test.',
@.profile_name = 'EMail';
When I run this I get the response that the mail is queued. Shortly there after I get the mail. In my case there must be an issue between the jobs and the operator.
|||Ok it looks like I might have solve it for my self. Follow this link
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322173&SiteID=1
Friday, February 17, 2012
Database log truncated
Recently we've upgraded SQL 7.0 to SQL 2000. We use a Database Maintenance Plans to backup the databases and transaction logs. Everything seems to be working, but Im getting an error message in the event viewer that has been described in Microsoft Knowledge Base article 818202 "PRB: A'Database log truncated" Error is logged in the Event Log When you try to Backup the Transaction Log. The article describes the cause of this warning, but does not give any fix or some kind of work around. Does anybody knows what to do or may be had this problem before? Please help. Thanks a lot.Switch your database to simple recovery.
backup the transaction log with truncate_only
Switch your database back to Full recovery.
run your maintance plan.|||As the article states, the cause for this entry in Event Log is the presence of either TRUNCATE_ONLY or NO_LOG.
Look into SQLMAINT command line utility, it gives you higher level of control, and you can use it against Database Maintenance plans as well.|||Make sure you issue full backup statement once NO_LOG or TRUNCATE_ONLY is issued on Tlog.|||Originally posted by rdjabarov
As the article states, the cause for this entry in Event Log is the presence of either TRUNCATE_ONLY or NO_LOG.
Look into SQLMAINT command line utility, it gives you higher level of control, and you can use it against Database Maintenance plans as well.
Yes, the article states that, but where I can see presence of these two options(TRUNCATE_ONLY or NO_LOG). I mean this job was created by Maintenance plan and is running as :
EXECUTE master.dbo.xp_sqlmaint N'-PlanID E4B335C8-20F2-4E29-A332-BD4778515EF5 -Rpt "D:\MSSQL7\LOG\DB Maintenance Plan20006.txt" -DelTxtRpt 2WEEKS -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpLog "D:\MSSQL7\BACKUP" -DelBkUps 1DAYS -BkExt "TRN"'
And if i use SQLMAINT utility to run the Database Maintenance plans what swich should i use for TRUNCATE_ONLY or NO_LOG options?
One more thing i don't understand it only happened on one server and 2 other works just fine.|||That's a mystery. Did you try to run the job manually? Could it be that it's not your job that fires NO_LOG, but some other maybe even ad-hoc statement issued from QA?|||http://support.microsoft.com/default.aspx?scid=kb;en-us;288577 KBA to troubleshoot Maint.plans.
HTH
backup the transaction log with truncate_only
Switch your database back to Full recovery.
run your maintance plan.|||As the article states, the cause for this entry in Event Log is the presence of either TRUNCATE_ONLY or NO_LOG.
Look into SQLMAINT command line utility, it gives you higher level of control, and you can use it against Database Maintenance plans as well.|||Make sure you issue full backup statement once NO_LOG or TRUNCATE_ONLY is issued on Tlog.|||Originally posted by rdjabarov
As the article states, the cause for this entry in Event Log is the presence of either TRUNCATE_ONLY or NO_LOG.
Look into SQLMAINT command line utility, it gives you higher level of control, and you can use it against Database Maintenance plans as well.
Yes, the article states that, but where I can see presence of these two options(TRUNCATE_ONLY or NO_LOG). I mean this job was created by Maintenance plan and is running as :
EXECUTE master.dbo.xp_sqlmaint N'-PlanID E4B335C8-20F2-4E29-A332-BD4778515EF5 -Rpt "D:\MSSQL7\LOG\DB Maintenance Plan20006.txt" -DelTxtRpt 2WEEKS -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpLog "D:\MSSQL7\BACKUP" -DelBkUps 1DAYS -BkExt "TRN"'
And if i use SQLMAINT utility to run the Database Maintenance plans what swich should i use for TRUNCATE_ONLY or NO_LOG options?
One more thing i don't understand it only happened on one server and 2 other works just fine.|||That's a mystery. Did you try to run the job manually? Could it be that it's not your job that fires NO_LOG, but some other maybe even ad-hoc statement issued from QA?|||http://support.microsoft.com/default.aspx?scid=kb;en-us;288577 KBA to troubleshoot Maint.plans.
HTH
Subscribe to:
Posts (Atom)