Microsoft (R) SQLMaint Utility (Unicode), Version
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.
Did you remove the BUILTIN\Administrators group or remove
that group from the sysadmin server role?
If so, you can add the login and add it to the sysadmin
server role using:
exec sp_grantlogin N'NT Authority\System'
and
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
-Sue
On Wed, 16 Jun 2004 12:50:32 -0700, "ss"
<anonymous@.discussions.microsoft.com> wrote:
>Microsoft (R) SQLMaint Utility (Unicode), Version
>[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'NT AUTHORITY\SYSTEM'.
Showing posts with label utility. Show all posts
Showing posts with label utility. Show all posts
Friday, March 30, 2012
Maintenance plan error!
Microsoft (R) SQLMaint Utility (Unicode), Version
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.Did you remove the BUILTIN\Administrators group or remove
that group from the sysadmin server role?
If so, you can add the login and add it to the sysadmin
server role using:
exec sp_grantlogin N'NT Authority\System'
and
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
-Sue
On Wed, 16 Jun 2004 12:50:32 -0700, "ss"
<anonymous@.discussions.microsoft.com> wrote:
>Microsoft (R) SQLMaint Utility (Unicode), Version
>[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'NT AUTHORITY\SYSTEM'.sql
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.Did you remove the BUILTIN\Administrators group or remove
that group from the sysadmin server role?
If so, you can add the login and add it to the sysadmin
server role using:
exec sp_grantlogin N'NT Authority\System'
and
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
-Sue
On Wed, 16 Jun 2004 12:50:32 -0700, "ss"
<anonymous@.discussions.microsoft.com> wrote:
>Microsoft (R) SQLMaint Utility (Unicode), Version
>[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'NT AUTHORITY\SYSTEM'.sql
Maintenance plan error!
Microsoft (R) SQLMaint Utility (Unicode), Version
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.Did you remove the BUILTIN\Administrators group or remove
that group from the sysadmin server role?
If so, you can add the login and add it to the sysadmin
server role using:
exec sp_grantlogin N'NT Authority\System'
and
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
-Sue
On Wed, 16 Jun 2004 12:50:32 -0700, "ss"
<anonymous@.discussions.microsoft.com> wrote:
>Microsoft (R) SQLMaint Utility (Unicode), Version
>[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'NT AUTHORITY\SYSTEM'.
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.Did you remove the BUILTIN\Administrators group or remove
that group from the sysadmin server role?
If so, you can add the login and add it to the sysadmin
server role using:
exec sp_grantlogin N'NT Authority\System'
and
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
-Sue
On Wed, 16 Jun 2004 12:50:32 -0700, "ss"
<anonymous@.discussions.microsoft.com> wrote:
>Microsoft (R) SQLMaint Utility (Unicode), Version
>[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'NT AUTHORITY\SYSTEM'.
Wednesday, March 21, 2012
Maintenance Plan Fails
I created a maintenance plan to back up a database. It fails and I get the follow error in the log file.
Microsoft (R) SQLMaint Utility (Unicode), Version [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4064: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed.
What user is it referring to? What user does a Maintenance plan use to login as? SA on the server has full access to all databases. SAs default database is master and I can read and write to it with the enterprise manager and query analyzer.
All replies appreciatedWhat's your security model?
Are you logged on and manually running it, or is it failing during a scheduled run?
That doesn't sound like a maint plan error though...|||It fails during a scheduled run.
In the Enterprise Manager if I right click on the database > All Tasks > Backup Database it works fine.
In the Enterprise Manager if I go into Management > New Maintenance Plans, schedule it. It fails.
The SQL Server use allows Windows Authentication or SQL Server Authentication. The server in question was registered in the Enterprise Manager with SQL Server Authentication. I don't know if that has any bearing on how Maintanence Plans are queued or what login is used when a plan executes.
Maybe I'm looking at a ODBC Driver problem. I just don't know how to get the details on which driver is being so I can compare it to my other servers where all Plans work fine.
Thanks for the reply.
Microsoft (R) SQLMaint Utility (Unicode), Version [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4064: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed.
What user is it referring to? What user does a Maintenance plan use to login as? SA on the server has full access to all databases. SAs default database is master and I can read and write to it with the enterprise manager and query analyzer.
All replies appreciatedWhat's your security model?
Are you logged on and manually running it, or is it failing during a scheduled run?
That doesn't sound like a maint plan error though...|||It fails during a scheduled run.
In the Enterprise Manager if I right click on the database > All Tasks > Backup Database it works fine.
In the Enterprise Manager if I go into Management > New Maintenance Plans, schedule it. It fails.
The SQL Server use allows Windows Authentication or SQL Server Authentication. The server in question was registered in the Enterprise Manager with SQL Server Authentication. I don't know if that has any bearing on how Maintanence Plans are queued or what login is used when a plan executes.
Maybe I'm looking at a ODBC Driver problem. I just don't know how to get the details on which driver is being so I can compare it to my other servers where all Plans work fine.
Thanks for the reply.
Monday, March 12, 2012
Maint not deleting old backups
I use the Maintenance utility to backup the database. I have specified for
it to delete any backup older than 1 day, but it doesn't delete anything.
The old backups end of taking up all the disk space, and then the backup
doesn't complete.
Any suggestions?
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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Gary465" <Gary465@.discussions.microsoft.com> wrote in message
news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>I use the Maintenance utility to backup the database. I have specified for
> it to delete any backup older than 1 day, but it doesn't delete anything.
> The old backups end of taking up all the disk space, and then the backup
> doesn't complete.
> Any suggestions?
|||Make sure the account running the SQLAgent service has delete permissions on
the backup folder
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Gary465" <Gary465@.discussions.microsoft.com> wrote in message
news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>I use the Maintenance utility to backup the database. I have specified for
> it to delete any backup older than 1 day, but it doesn't delete anything.
> The old backups end of taking up all the disk space, and then the backup
> doesn't complete.
> Any suggestions?
|||Thanks guys for the suggestions. It was a more obvious problem, as the
backups had not been completing successfully due to a lack of space. I guess
the utility does not delete the old backups if the job does not complete
successfully.
"Kevin3NF" wrote:
> Make sure the account running the SQLAgent service has delete permissions on
> the backup folder
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
> "Gary465" <Gary465@.discussions.microsoft.com> wrote in message
> news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>
>
it to delete any backup older than 1 day, but it doesn't delete anything.
The old backups end of taking up all the disk space, and then the backup
doesn't complete.
Any suggestions?
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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Gary465" <Gary465@.discussions.microsoft.com> wrote in message
news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>I use the Maintenance utility to backup the database. I have specified for
> it to delete any backup older than 1 day, but it doesn't delete anything.
> The old backups end of taking up all the disk space, and then the backup
> doesn't complete.
> Any suggestions?
|||Make sure the account running the SQLAgent service has delete permissions on
the backup folder
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Gary465" <Gary465@.discussions.microsoft.com> wrote in message
news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>I use the Maintenance utility to backup the database. I have specified for
> it to delete any backup older than 1 day, but it doesn't delete anything.
> The old backups end of taking up all the disk space, and then the backup
> doesn't complete.
> Any suggestions?
|||Thanks guys for the suggestions. It was a more obvious problem, as the
backups had not been completing successfully due to a lack of space. I guess
the utility does not delete the old backups if the job does not complete
successfully.
"Kevin3NF" wrote:
> Make sure the account running the SQLAgent service has delete permissions on
> the backup folder
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
> "Gary465" <Gary465@.discussions.microsoft.com> wrote in message
> news:34112B79-046E-40AB-B489-34A1AD589C45@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)