Post reply

Rename Server and SQL Sever Problem

  • January 28, 2005 at 9:43 am

    #109168

    Hello to everybody!

     

    I have a problem after I renamed my Server (Windows 2003) and then SQL Server.

    Since then I am no more able to schedule Backup jops for databases.

    I always get the message The job failed. Unable to determine if the owner (<Domain\Account Name&gt of job <job name> has server access (reason: Could not obtain information about Windows NT group/user '<Domain\Account Name>'. [SQLSTATE 42000] (Error 8198)).

    I also can't just change the user in the SQL Server Agent for that job.

    When I directly start the backup on the databes without scheduling the job it works.

    Has anybody a solution for my problem?

    PS: The Server is a standalone Server with no Domain.

    Thanks Manfred

     

     

  • January 28, 2005 at 9:52 am

    #539563

    sorry I think I posted my article in the wrong forum because I use SQL Server 2000

    Regards Manfred

  • January 28, 2005 at 9:54 am

    #539564

    Take a look in a table called sysjobs in the msdb database. Look at the field called originating_server. I had to change all the rows to the new server name.

  • February 1, 2005 at 11:00 pm

    #540083

    So another reasen why you never should rename your machine names...

    But, the <Domain\Account Name> error keeps me thinking about the login. Are they ok? Do you have login's that are based on local machine user accounts?

    Maybe SQL is not very happy about renaming. (my policy is never to change a machine name or SQL Server instance. you can use DNS for "changing" host names and cliconfg.exe aliasses for "changing" SQL Server instance connection names)

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply