| Author |
Topic |
|
kwilliams
194 Posts |
 Posted - 2003-08-05 : 12:49:27
|
| Hello, and thanks in advance,I'm REALLY hoping that someone can help me out here. Our Network Administrator changed something on our server having to do with the firewall, and ever since I've been getting this error message when a replication is attempted:The job failed. Unable to determine if the owner (SERVERNAME\kwilliams) of job INTERNALSERVERNAME-DB-Jobs-21 has server access (reason: Could not obtain information about Windows NT group/user 'dgcodmn1\kwilliams'. [SQLSTATE 42000] (Error 8198)).(NOTE: I've replaced both the internal & enternal server names in the error message above with generic names for security reasons.)Can anyone help me to figure out what's going on with it? Thanks!KWilliams |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 12:57:54
|
| If your server allows SQL authentication, try changing the owner of the jobs to sa.Tara |
 |
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 14:21:06
|
| Tara,About the post in the other forum, I didn't realize that the exact same people view and reply to posts in all of the forums, so that's why I posted it there too. About changing the owner to sa, that takes the error away, and says the job's successful, but it's really not. It doesn't change the subscription DB table at all. And changing it to sa wouldn't solve to problem of what's going on with my access rights. This only started when I switched from SQL Server 7 to 2000. Any suggestions?KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 14:23:36
|
| Should your account have system administrative privileges? If so, check to see if your account is a member of the system administrators role in SQL Server. To do that, go to your server in EM, then to security, then to server roles. If you add your account to the administrators group on the server (through Computer Management), this will also give you system administrative privileges.If your account isn't supposed to have this access, then the DBA will need to provide appropriate permissions.Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 14:30:36
|
| Tara,I checked this, and I'm already listed in the "System Administrators" list. This is what's confusing. All 4 replications worked fine until 2 things happened: the firewall was changed somehow by the NA, and I upgraded to SQL Server 2000 from SQL Server 7. The replications worked fine until I had to do some maintenance to a table. So when I took down the replication, and redid it after my maintenance, it started acting like this. Changing the owner to sa doesn't solve the problem in 2 ways: First, Em says that the job was successful even though it actually wasn't. I somehow doesn't see the new record entry. Second, I don't want to have to switch everything from me to sa when it should logically work for me as one of the System Administrators.Any other suggestions are appreciated. Thanks.KWilliams |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 14:51:05
|
| Tara,I forgot to mention that for some reason, SQL Server drops the DB table completely on the external server when the internal server's replication job fails. I have no idea why this is happening, and I'm seriously thinking of switching back to SQL Server 7 to maybe solve these problems. Have you ever seen these kinds of thngs happen in SQL Server 2k before? I'm completely lost!KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 15:35:20
|
| Well, what changed on the firewall? Did the NA keep the required firewall rules? I don't think that the firewall has anything to do with this problem, but it needs to be ruled out anyway. Is SERVERNAME\kwilliams a local account or an active directory account? If it is an active directory account, what side of the firewall is SQL Server located and what side of the firewall is the active directory server on?Have you tried dropping and recreating replication yet? Maybe something was missed in the configuration.Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 15:38:03
|
| Tara,I'm actually just starting with completely deleting the 4 replications, deleting the distribution, and redoing it all in SQL Server 2000. I think that it has something to do with the change from SQL Server 7 to 2000 personally. I thought that when I uninstalled 7, and installed 2000, everything would still work properly. Anyway, I'll let you know what happens. Thanks for your help.KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 15:42:26
|
| Oh I didn't realize that you just uninstalled SQL 7 and then installed SQL 2000. How did you handle the upgrading of the databases? Did you perform a BACKUP/RESTORE or DETACH/ATTACH? Replication should definitely be recreated after an upgrade.Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 15:48:56
|
| Tara,No I didn't. I never was told that you have to do those things. I just upgraded from 7 to 2000 on my own machine, and since I'm the only one using replication, these issues would only affect me. So I guess I'm on the right track now...hopefully!KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 15:52:43
|
| I would think that your databases are orphaned. Are they working in SQL 2000, meaning can you access the data in them using Query Analyzer? If not, then do you have database backups for them from SQL 7.0? The databases need to be upgraded in order for this to work. For replication, which server is the source server and which is the destination?Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 16:12:42
|
| Tara,Well, I deleted all of the replications, and tried to redo the first merge replication, and it's still having one of the same problems. It says that the job was successful, but nothing was changed on the subscription. Do you know why this might happen in SQL Server 2k?KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 16:13:54
|
| It's not SQL 2000 that is the problem. Have you checked if the databases are available? You can not just uninstall SQL 7.0 and then install SQL 2000. You have to upgrade the databases. Please answer the questions in my previous post.Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 16:18:17
|
Tara,quote:
I would think that your databases are orphaned. Are they working in SQL 2000, meaning can you access the data in them using Query Analyzer? If not, then do you have database backups for them from SQL 7.0? The databases need to be upgraded in order for this to work. For replication, which server is the source server and which is the destination?
The databases are working fine in SQL Server 2000, until replication is set up. I've done several queries using the Query Analyzer on both servers. There are 2 servers: the internal server is the source server, and the external server is the destination server.KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 16:21:19
|
| Did the NA setup a firewall rule to allow the two SQL Servers to communicate with each other? Can the SQL Servers see each other? Was the other server upgraded to SQL 2000 as well? Do you have the database backups from SQL 7.0 so that you can do the upgrade the right way from scratch?Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 16:27:24
|
| I forwarded all of your questions to the NA, and I'll let you know what he says.KWilliams |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 17:03:58
|
| Tara,Ok...it's still not replicating at all, even though the message says the job was successful. We're trying to figure out why the 2 servers don't seem to be connecting when replication's set up. Both work fine until I set up the replication, which leads me to a question that I hope you can help me out with. If the 2 servers are not connecting correctly, then how is it that I can successfully import & export DB tables from one server to the other, but replication from one server to the other doesn't work?? Thanks Tara.KWilliams |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 17:06:41
|
| If you can import/export tables from one server to the next, then the server can communicate so replication should work. I still think that something is wrong with your databases since you did not upgrade them. I'm surprised that they are accessible. Have you checked the SQL Server Error Log for errors? How about the replication monitor?Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 17:11:56
|
quote:
If you can import/export tables from one server to the next, then the server can communicate so replication should work. I still think that something is wrong with your databases since you did not upgrade them. I'm surprised that they are accessible. Have you checked the SQL Server Error Log for errors? How about the replication monitor?
I've been checking the Replication Moniter, and it's been also saying that everything is working. On the specific replication that I have set up, it gives this message: "No Replicated Transactions Are Available" next to "Successful" under the "Status". That's why it's so confusing. I've been in and out of DB tables on both servers for days, and everything's been fine until I tried to edit the properties of a replicated DB table. Any other suggestions? I'm stumped! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-05 : 17:14:30
|
| I'm stumped as well.Just as a recommendation, if you upgrade from SQL 7.0 to SQL 2000, do not do it the way that you did it this time, which could be the problem. You should read the articles here at SQLTeam that discuss the best practices for upgrading.Tara |
|
|
|
kwilliams
194 Posts |
Posted - 2003-08-05 : 17:23:08
|
| I realize that now, but even my NA had never heard of this process you're supposed to follow for upgrading to 2k. Several other employees here have upgraded in the past from 7 to 2k, and none of them had any problems with their DB's. One other comment is that the external server has SQL Server 7, and the EM's SQL Server 7. But the internal server has SQL Server 7, but the EM is 2000. I don't know if that makes a difference or not. But like I've said before, there are 2 main problems. First, even though I have the proper access rights, I have to set the owner to sa for anything to work. The other problem is when I try to set up any kind of replication from the internal server to the external server, and vice-versa, it says that the job was successful even though it actually wasn't. I really need these problems solved, but I have no idea of what else I can do. KWilliams |
|
|
|
Next Page
|
Error msg when attempting replication??