I have 4 SQL Server 2005 production servers that I installed RedGate SQL Bac
k
up on. All but one run fine. The one that doesn't I get the below error.
Executed as user : AD-DomainName\UserName. SQL Backup job failed with
exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step f
ailed.
The back up is backing up to the AD server which is different than the
server the job runs on. It is a shared folder on the AD and the permissions
grant the owner of the job Full Access.
I do not know what else to do with this issue. It mirrors the other 3 that
work fine.
Any and all help is appreciated.
-ChrisChris,
SQL Server caches login information from active directory. The one
troublesome machine has apparently cached out of date AD information. In
David Grey's BLOG he discusses a similar problem (not with Red Gate) that
may help you resolve.
http://www.codefounders.com/communi...entication.aspx
RLF
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2B7A5543-C258-4BA2-8CF4-BF2A7F4F1434@.microsoft.com...
>I have 4 SQL Server 2005 production servers that I installed RedGate SQL
>Back
> up on. All but one run fine. The one that doesn't I get the below error.
> Executed as user : AD-DomainName\UserName. SQL Backup job failed with
> exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step
> failed.
> The back up is backing up to the AD server which is different than the
> server the job runs on. It is a shared folder on the AD and the
> permissions
> grant the owner of the job Full Access.
> I do not know what else to do with this issue. It mirrors the other 3 that
> work fine.
> Any and all help is appreciated.
> -Chris
>
Tuesday, March 27, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment