RE: Change Administrator username causes backup to fail

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

NEver use the Administrator account in any service. Create a standard
account which belongs to the administrators group and use this to in your
services.

How are you doing your SQL Server backups? Are you using jobs?
--
MCP MCDBA MCAD MCSD MCT MCTS:SQL Server 2005
"Helping people grow and develop their full potential as God has plan for
them"


"James" wrote:

Hi,

Hopefully a simple question for someone who knows the answer !

Having changed Administrator username to something else - Backup fails.
Change it back it works. So definitley related to a change in username not
being mirrored on a database I think - I just can't find it - full details
below.


New Install of SBS 2003 R2 Premium (with ISA,SQL 2005 and Trend CSM)

All appears to be working OK.
Then I decided to change the Administrator username as recommended in the
tasks.
All appeared OK - even still seemed to get trend updates - until I tried a
backup

Quickly failed with:
==============================================
Volume shadow copy creation: Attempt 1.
"MSDEWriter" has reported an error 0x800423f4. This is part of System State.
The backup cannot continue.

Error returned while creating the volume shadow copy:800423f4
Aborting Backup.
==============================================

And then in the App event log:
==============================================
SQLVDI: Loc=UserAccount::Init(name). Desc=LookupAccountName.
ErrorCode=(1332)No mapping between account names and security IDs was done.
.. Process=9632. Thread=6172. Client. Instance=. VD=.

Setting username back to Administrator causes backup to work - so definitley
related to this.

Can anyone point me at where I should change the Admin name in SQL to allow
backup to work with a changed username.

I've not dug into this in any detail - but presumably I have multiple SQL
installs (MSDE for basic SBS 2003) and then SQL 2005 "proper". I've not
looked at rationalising / migrating anything to SQL 2005 - firm believer
that if it ain't broke ...

Any ideas ?

Many Thanks
James



.

Relevant Pages

  • Re: Group Policy Lofon Script
    ... the next time they can use just USERNAME and they will be able to log in to the domain. ... If you, as the administrator, try to log in to a computer using just the account 'Administrator', the log in will default to the computer name, instead of the SBS domain. ... When you connect the computer to a corporate network, ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup failing at System State
    ... I am using XP SP2 also, using an admin account. ... > administrator account. ... > | For the backup of system state to work you need; ... > |> the backup fails if System State is included, ...
    (microsoft.public.windowsxp.general)
  • Re: Group Policy Lofon Script
    ... admin account. ... 'administrator' account had to be setup, ... added as an administrator on LocalVista, and the jdoe account was deleted. ... with the username in the username@domainname syntax. ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy Lofon Script
    ... corporate LAN, so during initial setup, a network cable was connected. ... After setup was complete, the 'secret' administrator ... account was enabled, the LAN's administrator account was ... with the username in the username@domainname syntax. ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP Authentication problems - via outlook express/2003
    ... In this case, renaming the account shouldn't ... outlook express in same computer, ... Administrator account that cant send emails... ... What ever the username is has ...
    (microsoft.public.windows.server.sbs)