I just moved a database from one sql server to another. Both use Windows
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:
Showing posts with label windows2000. Show all posts
Showing posts with label windows2000. Show all posts
Saturday, February 25, 2012
Cannot connect to subscriber
Setup:
- SQL2000 SP3 running on Windows2000 servers.
I have a merge replication running between three identical servers. Two of
the servers, the publisher and subscriber1, receive data from different
sources and are synced every day at 4am. Subscriber2 is a query server only
and is updated by the publisher at 5am.
Replication has been running flawlessly since we upgraded everything nearly
a year ago. This morning the merge agent for Subscriber1 failed with the
following error (XXXX is the server name):
"The process could not connect to Subscriber 'XXXX'.
(Source: XXXX (Agent); Error number: 20084)"
"Cannot generate SSPI context
(Source: XXXX (Data source); Error number: 11004)"
Subscriber2 succeeded. Nothing has changed on the servers, and the logon
credential are the same for each.
I'm at a loss here. Anyone have any idea what might be happening and how to
fix it?
Thanks,
John Steen
There are some patches which seem to be causing this problem. The first
thing I would do is try to connect to the problem machine using SQL
Authentication. This might indicate that someone has changed the server from
mixed authentication to windows. Then try Windows - do you get the SSPI
error there too?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> Setup:
> - SQL2000 SP3 running on Windows2000 servers.
> I have a merge replication running between three identical servers. Two
of
> the servers, the publisher and subscriber1, receive data from different
> sources and are synced every day at 4am. Subscriber2 is a query server
only
> and is updated by the publisher at 5am.
> Replication has been running flawlessly since we upgraded everything
nearly
> a year ago. This morning the merge agent for Subscriber1 failed with the
> following error (XXXX is the server name):
> "The process could not connect to Subscriber 'XXXX'.
> (Source: XXXX (Agent); Error number: 20084)"
> "Cannot generate SSPI context
> (Source: XXXX (Data source); Error number: 11004)"
> Subscriber2 succeeded. Nothing has changed on the servers, and the logon
> credential are the same for each.
> I'm at a loss here. Anyone have any idea what might be happening and how
to
> fix it?
> Thanks,
> John Steen
>
|||Thanks for getting back to me so quickly, Hilary.
All three servers are using mixed authentication and identical credentials,
and there have been no patches or updates applied. I ran the merge agent for
Subscriber1 this morning manually and it succeeded. I did the same thing for
Subscriber2 but it failed. A second attempt succeeded. So it doesn't seem
to be an authentication issue.
We have a BU Exec SQL agent that does a differential backup at the same time
the merge agents run, so I'm going to to change the time that the agents run
to see if there's a conflict of some sort. If not, then I'll push it off to
our telecom people.
Thanks,
John
John Steen
remove (nospam) from e-mail address to send me a message
"Hilary Cotter" wrote:
> There are some patches which seem to be causing this problem. The first
> thing I would do is try to connect to the problem machine using SQL
> Authentication. This might indicate that someone has changed the server from
> mixed authentication to windows. Then try Windows - do you get the SSPI
> error there too?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
> news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> of
> only
> nearly
> to
>
>
- SQL2000 SP3 running on Windows2000 servers.
I have a merge replication running between three identical servers. Two of
the servers, the publisher and subscriber1, receive data from different
sources and are synced every day at 4am. Subscriber2 is a query server only
and is updated by the publisher at 5am.
Replication has been running flawlessly since we upgraded everything nearly
a year ago. This morning the merge agent for Subscriber1 failed with the
following error (XXXX is the server name):
"The process could not connect to Subscriber 'XXXX'.
(Source: XXXX (Agent); Error number: 20084)"
"Cannot generate SSPI context
(Source: XXXX (Data source); Error number: 11004)"
Subscriber2 succeeded. Nothing has changed on the servers, and the logon
credential are the same for each.
I'm at a loss here. Anyone have any idea what might be happening and how to
fix it?
Thanks,
John Steen
There are some patches which seem to be causing this problem. The first
thing I would do is try to connect to the problem machine using SQL
Authentication. This might indicate that someone has changed the server from
mixed authentication to windows. Then try Windows - do you get the SSPI
error there too?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> Setup:
> - SQL2000 SP3 running on Windows2000 servers.
> I have a merge replication running between three identical servers. Two
of
> the servers, the publisher and subscriber1, receive data from different
> sources and are synced every day at 4am. Subscriber2 is a query server
only
> and is updated by the publisher at 5am.
> Replication has been running flawlessly since we upgraded everything
nearly
> a year ago. This morning the merge agent for Subscriber1 failed with the
> following error (XXXX is the server name):
> "The process could not connect to Subscriber 'XXXX'.
> (Source: XXXX (Agent); Error number: 20084)"
> "Cannot generate SSPI context
> (Source: XXXX (Data source); Error number: 11004)"
> Subscriber2 succeeded. Nothing has changed on the servers, and the logon
> credential are the same for each.
> I'm at a loss here. Anyone have any idea what might be happening and how
to
> fix it?
> Thanks,
> John Steen
>
|||Thanks for getting back to me so quickly, Hilary.
All three servers are using mixed authentication and identical credentials,
and there have been no patches or updates applied. I ran the merge agent for
Subscriber1 this morning manually and it succeeded. I did the same thing for
Subscriber2 but it failed. A second attempt succeeded. So it doesn't seem
to be an authentication issue.
We have a BU Exec SQL agent that does a differential backup at the same time
the merge agents run, so I'm going to to change the time that the agents run
to see if there's a conflict of some sort. If not, then I'll push it off to
our telecom people.
Thanks,
John
John Steen
remove (nospam) from e-mail address to send me a message
"Hilary Cotter" wrote:
> There are some patches which seem to be causing this problem. The first
> thing I would do is try to connect to the problem machine using SQL
> Authentication. This might indicate that someone has changed the server from
> mixed authentication to windows. Then try Windows - do you get the SSPI
> error there too?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
> news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> of
> only
> nearly
> to
>
>
Subscribe to:
Posts (Atom)