sql error: maintenance

Showing posts with label maintenance. Show all posts

Thursday, March 8, 2012

"Remove files older than" doesn't work

Hi,
My company is using MS SQL 7. There is a database
maintenance plan to do the backup. It sets the "Remove
files older than 1 day". It used to work properly.
Last week, I suddenly found that this remove function
didn't work, and the files remain there for a whole week
until the disk full and backup fail. I don't know what
happen. I try to solve it by restart the server (Windows
2000 server), and change the setting from "1 day" to "23
hours", it totally doesn't work. Now I have to manually
delete the old file every day.
Anybody have the solution?
Thanks in advance.
ToddBelow KB might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Todd Chen" <powerful_tech@.yahoo.com> wrote in message
news:039901c39fa0$65479680$a001280a@.phx.gbl...
> Hi,
> My company is using MS SQL 7. There is a database
> maintenance plan to do the backup. It sets the "Remove
> files older than 1 day". It used to work properly.
> Last week, I suddenly found that this remove function
> didn't work, and the files remain there for a whole week
> until the disk full and backup fail. I don't know what
> happen. I try to solve it by restart the server (Windows
> 2000 server), and change the setting from "1 day" to "23
> hours", it totally doesn't work. Now I have to manually
> delete the old file every day.
> Anybody have the solution?
> Thanks in advance.
> Todd|||Wow, reply so fast.
Thanks a lot. Will try.
Todd
>--Original Message--
>Below KB might help:
>http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;303292&Product=
=3Dsql2k
>
>Also, check out below great troubleshooting suggestions
from Bill H at MS:
>
>-- Log files don't delete --
>This is likely to be either a permissions problem or a
sharing violation
>problem. The maintenance plan is run as a job, and jobs
are run by the
>SQLServerAgent service.
>Permissions:
>1. Determine the startup account for the SQLServerAgent
service
>(Start|Programs|Administrative
tools|Services|SQLServerAgent|Startup). This
>account is the security context for jobs, and thus the
maintenance plan.
>2. If SQLServerAgent is started using LocalSystem (as
opposed to a domain
>account) then skip step 3.
>3. On that box, log onto NT as that account. Using
Explorer, attempt to
>delete an expired backup. If that succeeds then go to
Sharing Violation
>section.
>4. Log onto NT with an account that is an administrator
and use Explorer to
>look at the Properties|Security of the folder (where the
backups reside)
>and ensure the SQLServerAgent startup account has Full
Control. If the
>SQLServerAgent startup account is LocalSystem, then the
account to consider
>is SYSTEM.
>5. In NT, if an account is a member of an NT group, and if
that group has
>Access is Denied, then that account will have Access is
Denied, even if
>that account is also a member of the Administrators group.
Thus you may
>need to check group permissions (if the Startup Account is
a member of a
>group).
>6. Keep in mind that permissions (by default) are
inherited from a parent
>folder. Thus, if the backups are stored in C:\bak, and if
someone had
>denied permission to the SQLServerAgent startup account
for C:\, then
>C:\bak will inherit access is denied.
>Sharing violation:
>This is likely to be rooted in a timing issue, with the
most likely cause
>being another scheduled process (such as NT Backup or
Anti-Virus software)
>having the backup file open at the time when the
SQLServerAgent (i.e., the
>maintenance plan job) tried to delete it.
>1. Download filemon and handle from www.sysinternals.com.
>2. I am not sure whether filemon can be scheduled, or you
might be able to
>use NT scheduling services to start filemon just before
the maintenance
>plan job is started, but the filemon log can become very
large, so it would
>be best to start it some short time before the maintenance
plan starts.
>3. Inspect the filemon log for another process that has
that backup file
>open (if your lucky enough to have started filemon before
this other
>process grabs the backup folder), and inspect the log for
the results when
>the SQLServerAgent agent attempts to open that same file.
>4. Schedule the job or that other process to do their work
at different
>times.
>5. You can use the handle utility if you are around at the
time when the
>job is scheduled to run.
>If the backup files are going to a \\share or a mapped
drive (as opposed to
>local drive), then you will need to modify the above (with
respect to where
>the tests and utilities are run).
>Finally, inspection of the maintenance plan's history
report might be
>useful.
>Thanks,
>Bill Hollinshead
>Microsoft, SQL Server
>
>
>-- >Tibor Karaszi, SQL Server MVP
>Archive at:
http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
>
>"Todd Chen" <powerful_tech@.yahoo.com> wrote in message
>news:039901c39fa0$65479680$a001280a@.phx.gbl...
>> Hi,
>> My company is using MS SQL 7. There is a database
>> maintenance plan to do the backup. It sets the "Remove
>> files older than 1 day". It used to work properly.
>> Last week, I suddenly found that this remove function
>> didn't work, and the files remain there for a whole week
>> until the disk full and backup fail. I don't know what
>> happen. I try to solve it by restart the server (Windows
>> 2000 server), and change the setting from "1 day" to "23
>> hours", it totally doesn't work. Now I have to manually
>> delete the old file every day.
>> Anybody have the solution?
>> Thanks in advance.
>> Todd
>
>.
>

"Remove files older than" does not work

Hi.
The Database Maintenance Plan that is configured to backup
the DB every day as the "Remove files older than" option
set to 1 days.
The old files are no being removed. The backups are
working and placed in the specified folder. The "Backup
file extension:" is "bak". What am I missing?
Thanx.Does
BUG: Sqlmaint Does Not Delete Expired Backup Files on Windows 95, 98 or ME
Computers
http://support.microsoft.com/default.aspx?scid=kb;en-us;278667
apply?
--
Jacco Schalkwijk
SQL Server MVP
"Hector" <anonymous@.discussions.microsoft.com> wrote in message
news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
> Hi.
> The Database Maintenance Plan that is configured to backup
> the DB every day as the "Remove files older than" option
> set to 1 days.
> The old files are no being removed. The backups are
> working and placed in the specified folder. The "Backup
> file extension:" is "bak". What am I missing?
> Thanx.|||The server runs Windows 2000 (SP4).
I might be missing part of your response. It's sort of
distored.
Thanx!
>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
>> Hi.
>> The Database Maintenance Plan that is configured to
backup
>> the DB every day as the "Remove files older than" option
>> set to 1 days.
>> The old files are no being removed. The backups are
>> working and placed in the specified folder. The "Backup
>> file extension:" is "bak". What am I missing?
>> Thanx.
>
>.
>|||I'm sorry. Now I understood your message. I'm reading
the article now.
Thanx again.
>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
>> Hi.
>> The Database Maintenance Plan that is configured to
backup
>> the DB every day as the "Remove files older than" option
>> set to 1 days.
>> The old files are no being removed. The backups are
>> working and placed in the specified folder. The "Backup
>> file extension:" is "bak". What am I missing?
>> Thanx.
>
>.
>|||I reviewed the article and it doesn't apply. We have SQL
Server 2000 running on a Windows 2000 Server.
>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
>> Hi.
>> The Database Maintenance Plan that is configured to
backup
>> the DB every day as the "Remove files older than" option
>> set to 1 days.
>> The old files are no being removed. The backups are
>> working and placed in the specified folder. The "Backup
>> file extension:" is "bak". What am I missing?
>> Thanx.
>
>.
>|||Below KB might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hector" <anonymous@.discussions.microsoft.com> wrote in message
news:217f301c45ac5$cfffc700$a501280a@.phx.gbl...
> I reviewed the article and it doesn't apply. We have SQL
> Server 2000 running on a Windows 2000 Server.
>
> >--Original Message--
> >Does
> >BUG: Sqlmaint Does Not Delete Expired Backup Files on
> Windows 95, 98 or ME
> >Computers
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;278667
> >apply?
> >
> >--
> >Jacco Schalkwijk
> >SQL Server MVP
> >
> >
> >"Hector" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
> >> Hi.
> >>
> >> The Database Maintenance Plan that is configured to
> backup
> >> the DB every day as the "Remove files older than" option
> >> set to 1 days.
> >>
> >> The old files are no being removed. The backups are
> >> working and placed in the specified folder. The "Backup
> >> file extension:" is "bak". What am I missing?
> >>
> >> Thanx.
> >
> >
> >.
> >|||I've recently taken over management of an SQL 2000 server also o
Windows 2000 server (and relatively new to SQL) and have exactly th
same problem.
Read through this thread but as yet no success to resolving th
problem.
Hector - did you get this resolved?
Anyone have any other ideas not suggested here?
Regards,
Glen.
Did you ever get a fix?
Hector wrote:
> *Hi.
> The Database Maintenance Plan that is configured to backup
> the DB every day as the "Remove files older than" option
> set to 1 days.
> The old files are no being removed. The backups are
> working and placed in the specified folder. The "Backup
> file extension:" is "bak". What am I missing?
> Thanx.
-
Glen Sutti
----
Posted via http://www.webservertalk.co
----
View this thread: http://www.webservertalk.com/message273097.htm|||I don't have access to the old thread, but perhaps below might help?
Below KB might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Glen Suttie" <Glen.Suttie.1hdx2u@.mail.webservertalk.com> wrote in message
news:Glen.Suttie.1hdx2u@.mail.webservertalk.com...
> I've recently taken over management of an SQL 2000 server also on
> Windows 2000 server (and relatively new to SQL) and have exactly the
> same problem.
> Read through this thread but as yet no success to resolving the
> problem.
> Hector - did you get this resolved?
> Anyone have any other ideas not suggested here?
> Regards,
> Glen.
>
>
> Did you ever get a fix?
> Hector wrote:
>> *Hi.
>> The Database Maintenance Plan that is configured to backup
>> the DB every day as the "Remove files older than" option
>> set to 1 days.
>> The old files are no being removed. The backups are
>> working and placed in the specified folder. The "Backup
>> file extension:" is "bak". What am I missing?
>> Thanx. *
>
> --
> Glen Suttie
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message273097.html
>

"Remove files older than" does not work

Hi.
The Database Maintenance Plan that is configured to backup
the DB every day as the "Remove files older than" option
set to 1 days.
The old files are no being removed. The backups are
working and placed in the specified folder. The "Backup
file extension:" is "bak". What am I missing?
Thanx.
Does
BUG: Sqlmaint Does Not Delete Expired Backup Files on Windows 95, 98 or ME
Computers
http://support.microsoft.com/default...b;en-us;278667
apply?
Jacco Schalkwijk
SQL Server MVP
"Hector" <anonymous@.discussions.microsoft.com> wrote in message
news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
> Hi.
> The Database Maintenance Plan that is configured to backup
> the DB every day as the "Remove files older than" option
> set to 1 days.
> The old files are no being removed. The backups are
> working and placed in the specified folder. The "Backup
> file extension:" is "bak". What am I missing?
> Thanx.
|||The server runs Windows 2000 (SP4).
I might be missing part of your response. It's sort of
distored.
Thanx!

>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
backup
>
>.
>
|||I'm sorry. Now I understood your message. I'm reading
the article now.
Thanx again.

>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
backup
>
>.
>
|||I reviewed the article and it doesn't apply. We have SQL
Server 2000 running on a Windows 2000 Server.

>--Original Message--
>Does
>BUG: Sqlmaint Does Not Delete Expired Backup Files on
Windows 95, 98 or ME
>Computers
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;278667
>apply?
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Hector" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2176001c45ab8$54616d90$a401280a@.phx.gbl...
backup
>
>.
>
|||Below KB might help:
http://support.microsoft.com/default...&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hector" <anonymous@.discussions.microsoft.com> wrote in message
news:217f301c45ac5$cfffc700$a501280a@.phx.gbl...[vbcol=seagreen]
> I reviewed the article and it doesn't apply. We have SQL
> Server 2000 running on a Windows 2000 Server.
>
> Windows 95, 98 or ME
> us;278667
> message
> backup
|||I've recently taken over management of an SQL 2000 server also on
Windows 2000 server (and relatively new to SQL) and have exactly the
same problem.
Read through this thread but as yet no success to resolving the
problem.
Hector - did you get this resolved?
Anyone have any other ideas not suggested here?
Regards,
Glen.
Did you ever get a fix?
Hector wrote:
> *Hi.
> The Database Maintenance Plan that is configured to backup
> the DB every day as the "Remove files older than" option
> set to 1 days.
> The old files are no being removed. The backups are
> working and placed in the specified folder. The "Backup
> file extension:" is "bak". What am I missing?
> Thanx. *
Glen Suttie
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message273097.html
|||I don't have access to the old thread, but perhaps below might help?
Below KB might help:
http://support.microsoft.com/default...&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Glen Suttie" <Glen.Suttie.1hdx2u@.mail.webservertalk.com> wrote in message
news:Glen.Suttie.1hdx2u@.mail.webservertalk.com...
> I've recently taken over management of an SQL 2000 server also on
> Windows 2000 server (and relatively new to SQL) and have exactly the
> same problem.
> Read through this thread but as yet no success to resolving the
> problem.
> Hector - did you get this resolved?
> Anyone have any other ideas not suggested here?
> Regards,
> Glen.
>
>
> Did you ever get a fix?
> Hector wrote:
>
> --
> Glen Suttie
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message273097.html
>

"Remove files older than" does not work

quote:
Originally posted by Hector
Hi.
The Database Maintenance Plan that is configured to backup
the DB every day as the "Remove files older than" option
set to 1 days.
The old files are no being removed. The backups are
working and placed in the specified folder. The "Backup
file extension:" is "bak". What am I missing?
Thanx.

|||I don't have access to the old thread, but perhaps below might help?
Below KB might help:
http://support.microsoft.com/defaul...2&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Glen Suttie" <Glen.Suttie.1hdx2u@.mail.webservertalk.com> wrote in message
news:Glen.Suttie.1hdx2u@.mail.webservertalk.com...
> I've recently taken over management of an SQL 2000 server also on
> Windows 2000 server (and relatively new to SQL) and have exactly the
> same problem.
> Read through this thread but as yet no success to resolving the
> problem.
> Hector - did you get this resolved?
> Anyone have any other ideas not suggested here?
> Regards,
> Glen.
>
>
> Did you ever get a fix?
> Hector wrote:
>
> --
> Glen Suttie
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message273097.html
>

Tuesday, March 6, 2012

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
Julie
Hi Julie
"Kaidi" wrote:

> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John
|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
|||Hi Julie
"Kaidi" wrote:

> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!

> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.

> :P
> Julie
>
John
|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!

> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:

> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, yo
u
will see a node for management under which is SQL Server Agent and then Jobs
.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should b
e
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenan
ce plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:

> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!

> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.

> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!

> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> > Followup, for anyone who happens to hit this post on a usenet search.
> > (I hate finding my problem with no solution.
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> > Do *not* simply delete the job rows that are causing the problem from
> > the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> > taken me a couple of hours to track down all of the pieces/references
> > to the job in other tables. I'm just hoping to heck I got them all...I
> > went manually through all of the delete commands in the sp_delete_job
> > procedure, and praying that it worked!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

Sunday, February 19, 2012

"GUID should contain 32 digits" when saving brand new Maintenance

Someone help me please. I'm confused.
I've got a brand new Maintenance Plan which reorganizes indexes, clears out
the MP history and updates DB stats. It refused to save with a schedule of
once a week on Sunday at 1:00 a.m., but did save without a schedule (on
demand).
I have reopened the Maintenance Plan and tried to create a schedule. Every
time I try to close out and save (X on the upper right), it gives me the
Error: "GUID should contain 32 digits with 4 dashes
(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
information.
What is going on? Does anyone know? Help would be appreciatedd since we're
right on top of our official 2000-to-2005 server switch over.
Thanks,
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)Check this link out, hopefully it should resolve your issue.
http://www.kbalertz.com/Feedback_922651.aspx
Bob
"Catadmin" wrote:
> Someone help me please. I'm confused.
> I've got a brand new Maintenance Plan which reorganizes indexes, clears out
> the MP history and updates DB stats. It refused to save with a schedule of
> once a week on Sunday at 1:00 a.m., but did save without a schedule (on
> demand).
> I have reopened the Maintenance Plan and tried to create a schedule. Every
> time I try to close out and save (X on the upper right), it gives me the
> Error: "GUID should contain 32 digits with 4 dashes
> (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
> information.
> What is going on? Does anyone know? Help would be appreciatedd since we're
> right on top of our official 2000-to-2005 server switch over.
> Thanks,
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)|||Just an FYI. I tried creating a new job that contained the above 3 steps and
the Notify Operator (set with a fail precendence from the other three tasks)
for another user db. I hit save, then the X up in the right hand corner and
got the following error message:
"Apply to target server failed for job 'MyJobName' "
I did get this error message on the other job and wonder if maybe there's a
connection between this and the GUID message?
Thanks,
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Catadmin" wrote:
> Someone help me please. I'm confused.
> I've got a brand new Maintenance Plan which reorganizes indexes, clears out
> the MP history and updates DB stats. It refused to save with a schedule of
> once a week on Sunday at 1:00 a.m., but did save without a schedule (on
> demand).
> I have reopened the Maintenance Plan and tried to create a schedule. Every
> time I try to close out and save (X on the upper right), it gives me the
> Error: "GUID should contain 32 digits with 4 dashes
> (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
> information.
> What is going on? Does anyone know? Help would be appreciatedd since we're
> right on top of our official 2000-to-2005 server switch over.
> Thanks,
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)|||No these issues are not related. The second issue you are seeing is probably
because you are using SQL Server Management studio to connect to a server
which is not local. If you terminal service to the machine itself and use sa
account to connect to it from there then you shouldn't see this issue. This
issue is somehow related to security but haven't found a solution yet.
Bob
"Catadmin" wrote:
> Just an FYI. I tried creating a new job that contained the above 3 steps and
> the Notify Operator (set with a fail precendence from the other three tasks)
> for another user db. I hit save, then the X up in the right hand corner and
> got the following error message:
> "Apply to target server failed for job 'MyJobName' "
> I did get this error message on the other job and wonder if maybe there's a
> connection between this and the GUID message?
> Thanks,
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)
>
> "Catadmin" wrote:
> > Someone help me please. I'm confused.
> >
> > I've got a brand new Maintenance Plan which reorganizes indexes, clears out
> > the MP history and updates DB stats. It refused to save with a schedule of
> > once a week on Sunday at 1:00 a.m., but did save without a schedule (on
> > demand).
> >
> > I have reopened the Maintenance Plan and tried to create a schedule. Every
> > time I try to close out and save (X on the upper right), it gives me the
> > Error: "GUID should contain 32 digits with 4 dashes
> > (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
> > information.
> >
> > What is going on? Does anyone know? Help would be appreciatedd since we're
> > right on top of our official 2000-to-2005 server switch over.
> >
> > Thanks,
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the back?
> > @.=)|||Bob,
I appreciate the link, but this has nothing to do with SSIS or an
importanted maintenance plan. I'm actually creating this plan from scratch
in the GUI of SSMS and getting this error.
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Bob" wrote:
> Check this link out, hopefully it should resolve your issue.
> http://www.kbalertz.com/Feedback_922651.aspx
> Bob
> "Catadmin" wrote:
> > Someone help me please. I'm confused.
> >
> > I've got a brand new Maintenance Plan which reorganizes indexes, clears out
> > the MP history and updates DB stats. It refused to save with a schedule of
> > once a week on Sunday at 1:00 a.m., but did save without a schedule (on
> > demand).
> >
> > I have reopened the Maintenance Plan and tried to create a schedule. Every
> > time I try to close out and save (X on the upper right), it gives me the
> > Error: "GUID should contain 32 digits with 4 dashes
> > (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
> > information.
> >
> > What is going on? Does anyone know? Help would be appreciatedd since we're
> > right on top of our official 2000-to-2005 server switch over.
> >
> > Thanks,
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the back?
> > @.=)|||Bob,
You are correct. I am connected on my desktop with SSMS to a remote server.
So, you're saying I actually have to use a remote connection like VPN/Remote
Desktop to get onto the actual server and create the maintenance plan there?
That stinks. I hope they fix this soon as we only allow one TS connection
to the machine at a time and there are several of us doing different parts of
our upgrade project.
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Bob" wrote:
> No these issues are not related. The second issue you are seeing is probably
> because you are using SQL Server Management studio to connect to a server
> which is not local. If you terminal service to the machine itself and use sa
> account to connect to it from there then you shouldn't see this issue. This
> issue is somehow related to security but haven't found a solution yet.
> Bob
> "Catadmin" wrote:
> > Just an FYI. I tried creating a new job that contained the above 3 steps and
> > the Notify Operator (set with a fail precendence from the other three tasks)
> > for another user db. I hit save, then the X up in the right hand corner and
> > got the following error message:
> >
> > "Apply to target server failed for job 'MyJobName' "
> >
> > I did get this error message on the other job and wonder if maybe there's a
> > connection between this and the GUID message?
> >
> > Thanks,
> > Catadmin
> >
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the back?
> > @.=)
> >
> >
> > "Catadmin" wrote:
> >
> > > Someone help me please. I'm confused.
> > >
> > > I've got a brand new Maintenance Plan which reorganizes indexes, clears out
> > > the MP history and updates DB stats. It refused to save with a schedule of
> > > once a week on Sunday at 1:00 a.m., but did save without a schedule (on
> > > demand).
> > >
> > > I have reopened the Maintenance Plan and tried to create a schedule. Every
> > > time I try to close out and save (X on the upper right), it gives me the
> > > Error: "GUID should contain 32 digits with 4 dashes
> > > (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" with an OK button and no other
> > > information.
> > >
> > > What is going on? Does anyone know? Help would be appreciatedd since we're
> > > right on top of our official 2000-to-2005 server switch over.
> > >
> > > Thanks,
> > >
> > > Catadmin
> > > --
> > > MCDBA, MCSA
> > > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > > Microsoft pays the bills for the funny white jackets that tie in the back?
> > > @.=)

"GUID should contain 32 digits" when saving brand new Maintenance

Thursday, February 9, 2012

"Attempt to repair any minor problems." What is the point?

I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>
My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio

>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>

"Attempt to repair any minor problems." What is the point?

I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio

>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>

Friday, January 27, 2012

error creating maintenance plan

Hello,
I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
includes rebuild indexes, check integrity, update statistics, etc.
I'm using the wizard to create to plan, but at the when I press the finish
button at the end of the wizard there is an error message and I'm unable to
create the plan.
The error message is include at the end of this email.
Does anybody know what could be causing the error?
In advance I appreciate your help and comments.
Edmundo J. Davila
ERROR
TITLE: Maintenance Plan Wizard Progress
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+JobStep&LinkId=20476[/url]
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476[ /url]
BUTTONS:
OK
This question has already been answered.
Ekrem nsoy
"Edmundo J. Davila" <edavila@.monisa.com> wrote in message
news:4F578C0F-8F8A-4371-88B1-C6FDA8C0D4AD@.microsoft.com...
> Hello,
> I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
> includes rebuild indexes, check integrity, update statistics, etc.
> I'm using the wizard to create to plan, but at the when I press the finish
> button at the end of the wizard there is an error message and I'm unable
> to create the plan.
> The error message is include at the end of this email.
> Does anybody know what could be causing the error?
> In advance I appreciate your help and comments.
> Edmundo J. Davila
> ERROR
>
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+JobStep&LinkId=20476[/url]
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476[ /url]
> --
> BUTTONS:
> OK
> --
>

error creating maintenance plan

Hello,
I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
includes rebuild indexes, check integrity, update statistics, etc.
I'm using the wizard to create to plan, but at the when I press the finish
button at the end of the wizard there is an error message and I'm unable to
create the plan.
The error message is include at the end of this email.
Does anybody know what could be causing the error?
In advance I appreciate your help and comments.
Edmundo J. Davila
ERROR
---
TITLE: Maintenance Plan Wizard Progress
--
Create maintenance plan failed.
--
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
--
BUTTONS:
OK
--This question has already been answered.
--
Ekrem Önsoy
"Edmundo J. Davila" <edavila@.monisa.com> wrote in message
news:4F578C0F-8F8A-4371-88B1-C6FDA8C0D4AD@.microsoft.com...
> Hello,
> I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
> includes rebuild indexes, check integrity, update statistics, etc.
> I'm using the wizard to create to plan, but at the when I press the finish
> button at the end of the wizard there is an error message and I'm unable
> to create the plan.
> The error message is include at the end of this email.
> Does anybody know what could be causing the error?
> In advance I appreciate your help and comments.
> Edmundo J. Davila
> ERROR
> ---
>
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
> --
> BUTTONS:
> OK
> --
>

Thursday, March 8, 2012

"Remove files older than" doesn't work

"Remove files older than" does not work

"Remove files older than" does not work

"Remove files older than" does not work

Tuesday, March 6, 2012

"Orphaned" maintenance plan

"Orphaned" maintenance plan

"Orphaned" maintenance plan

Sunday, February 19, 2012

"GUID should contain 32 digits" when saving brand new Maintenance

"GUID should contain 32 digits" when saving brand new Maintenance

Thursday, February 9, 2012

"Attempt to repair any minor problems." What is the point?

"Attempt to repair any minor problems." What is the point?

Friday, January 27, 2012

error creating maintenance plan

error creating maintenance plan

sql error

Blog Archive

About Me