| Author |
Topic |
|
dhw
Constraint Violating Yak Guru
332 Posts |
 Posted - 2004-04-14 : 12:52:14
|
| Hello...Recently, our sql server was changed to a domain controller. After that, I completely removed/disabled Replication and then set it up again. I also changed the accounts that MSSQL and the Sql Agent run under to a domain account. I can create a publication, but when I try to start it....it appears that nothing happens. There are no agent errors or history to view. When I look at the Event Log for the machine, I see the following description that seems to indicate that the old machine admin account (HANTA\Administrators) is somehow causing a problem.SQL Server Scheduled Job 'Replication agents checkup' (0x8AF4673734EB3A4B83312D63B02C654C)Status: Failed - Invoked on: 2004-04-14 09:40:01Message: The job failed. Unable to determine if the owner (HANTA\Administrator) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'HANTA\Administrator'. [SQLSTATE 42000] (Error 8198)).Does anyone know of a way to fix this problem? Or, if there are any articles that I can research?Thanks, - dw |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-04-14 : 12:55:54
|
quote:
Originally posted by dhw
Recently, our sql server was changed to a domain controller.
Bad idea.quote:
Originally posted by dhw
Message: The job failed. Unable to determine if the owner (HANTA\Administrator) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'HANTA\Administrator'. [SQLSTATE 42000] (Error 8198)).Does anyone know of a way to fix this problem? Or, if there are any articles that I can research?
Just change the owner of the replication jobs to sa. Or you can see if any of these will work for you:http://support.microsoft.com/?kbid=834124Tara |
 |
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2004-04-14 : 13:08:39
|
| Tara....Thanks for the suggestions and link. I'll try them out. It wasn't my idea to change the sql server to a domain controller. In fact, this morning I ran the MS Base Line Security Analyzer tool and it even reported that sql server shouldn't be running on a domain controller. ... douglas |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2004-04-14 : 13:16:13
|
| Tara...Changing the owner of the replication job to the "sa" account, seems to start the job...but it immediately errors out. When I look at the details, I see the message: "The process could not create file \\Server\Repl\unc" Access is denied, Source (OS); Error number 5.Is this because the "sa" account isn't a real account and therefore doesn't have access to the share I am writing the replication to?...douglas |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-04-14 : 13:19:24
|
| Why isn't sa a real account?The account that owns the replication jobs here is distributor_admin. I kept the defaults when I setup replication, so see if that account works for you. If it doesn't, try using a Windows account.Tara |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2004-04-15 : 05:56:42
|
| Well....after re-formatting the server and re-installing the OS and Sql Server, my problem still persists. I can only get my publications created when I leave the file path to the default of //ServerName/C$/Program Files/MSSql Server.../Repl. If I change the publication to a share like //ServerName/Repl it just doesn't work. I keep getting an error that the process cannot create the UNC file. I searched on this error and the only solutions state that I need to make sure I am using a domain account that has rights to the share. In my case, both of these are true. I am using a domain account, that I even placed in the Administrators group. Further, I have verified that the security on the Share is set to all my domain account Full Control. About the only thing that is truly different from when this was working is that the OS has changed from Windows 2000 Server to Windows 2003. Has anyone experienced similar problems with Win 2003 server?thanks...dw |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-04-15 : 12:13:13
|
| Do you have sp3a installed?Tara |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2004-04-15 : 12:31:02
|
| Yes...we installed SP3a right after the Sql Server install. |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2004-04-15 : 13:31:49
|
| I just figured it out....The problem is that Windows 2003 seems to have an extra layer of security on shared folder access. Even though the Sql Agent's account had Full Control of the share when viewed from the Security Tab property sheet of the share....there was another set of permissions that you can set on the Sharing property sheet. Once I added my Sql Agent there...it worked. Seems redundant to me...but as long as it works I am happy. - dw |
|
|
|
|
Replication won't start anymore....