Jeff,
This looks to be a userid and/or AD issue. It looks like
something changed in your environment that caused the
VDI creation functions to fail due to lack of security.
Have a closer look at the userid being used to run the
backup to see if something has changed recently in
regards to security permissions. You should also try
running this backup manually, while logged in. If that fails
as well, try running a backup from within SQL Enterprise Manager.
Doing these may help narrow the problem to a userid issue
and/or a problem internal to SQL Server.
There are a few similar things in the Microsoft Knowledge Base
to also take a look at.
Thanks,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/09/2004
07:30:30 AM:
> Hi all,
>
> We have started getting errors while backing up a SQL server
>
> We have:
> MS SQL 2000
> TDP 2.2.1
> TSM client v5.1.5.0
> TSM Server 5.1.5.2 (z/os 1.3)
>
> Error in logfile:
> ANE4993E Microsoft SQL Server: log backup of database xxxxxx from
server
> yyyyyy failed, rc = 1912.
> On the SQL server, in VDI.LOG
> 2004/08/04 11:00:36 pid(1020) tid(2424)
>
> Error at UserAccount::Init(name): LookupAccountName Status Code: 1332,
x534
> Explanation: No mapping between account names and security IDs was done.
>
> ----------------------------------------------
> 2004/08/04 11:00:36 pid(1020) tid(2424)
>
> Error at IdentifySQLServer: Initialize Status Code: 1332, x534
> Explanation: No mapping between account names and security IDs was done.
>
> ----------------------------------------------
> 2004/08/04 11:00:36 pid(1020) tid(2424)
> Error on TDPSQL-000003FC-0000
> Error at CVDS::Create: Security initialization failed
>
> A transaction log backup ran at 7am that morning (4th August). The
messages
> started to appear when the 11am transaction log backup tried to run.
>
> Has anyone seen this? I tried Richard's site, but could'nt find rc=1912.
>
> Thanks
>
> Jeff White
> jeff.white AT cis.co DOT uk
|
