When loggining into SSMS there does not appear to be a way to connect to the
ALIAS remote servers names like you could with SQL Server 2000. Does any one
know how to use the Alias names at the SQL Server 2005 connection dialog?D. Haber (DHaber@.discussions.microsoft.com) writes:
> When loggining into SSMS there does not appear to be a way to connect to
> the ALIAS remote servers names like you could with SQL Server 2000. Does
> any one know how to use the Alias names at the SQL Server 2005
> connection dialog?
What aliases? Those you defined in the Client Network Utility? I guess you
need to use the SQL Configuration Manager to set up aliaes for the SQL 2005
tools. It's under SQL Native Client configuration, which is a little
misleading, but I did a very quick test, and it seemed to work.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Tuesday, March 27, 2012
Alias with XP
Why is it necessary to create an alias in the Client Network Utility to be able to connect to SQL Server if you are running Windows XP?To clarify a little, it seems it is only necessary in XP. We don't have to create an alias when the client is running NT or 2000, only XP. Also, if the network connection goes down, we occasionally lose the alias and have to re-create it. Any ideas?sql
Alias for a database name?
Hi there,
I'm using SQL Server 2000.
I've created a database that has the name "SworderNet.ProductAnalysis."
Various applications connect to this database using this name. Well, it
turns out that certain programs like Excel have a problem accessing SQL
databases that have a "." in the name. The simplest solution is obviously to
just rename the database but it would be a major hassle to try to track down
all of the various clients that use this database and change the
appropriate config files to reflect the new name. Is there a way to create
an "alias" name for this database (similar to a CNAME record in dns)? For
example, I'd like to create an alias called "ProductAnalysis"... The
original name would still work, but clients that have problems with "."
embedded in the database name can just use the alias name instead.
Is it possible?
Sincerely,
David SworderI'm afraid not. The closest would be to create a new database and for each
table create a view inside that database. Not a nice solution...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"David Sworder" <GilGrissom@.CSILasVegas.com> wrote in message
news:unJfw9IDEHA.1600@.tk2msftngp13.phx.gbl...
> Hi there,
> I'm using SQL Server 2000.
> I've created a database that has the name
"SworderNet.ProductAnalysis."
> Various applications connect to this database using this name. Well, it
> turns out that certain programs like Excel have a problem accessing SQL
> databases that have a "." in the name. The simplest solution is obviously
to
> just rename the database but it would be a major hassle to try to track
down
> all of the various clients that use this database and change the
> appropriate config files to reflect the new name. Is there a way to create
> an "alias" name for this database (similar to a CNAME record in dns)? For
> example, I'd like to create an alias called "ProductAnalysis"... The
> original name would still work, but clients that have problems with "."
> embedded in the database name can just use the alias name instead.
> Is it possible?
> --
> Sincerely,
> David Sworder
>|||Hi,
I have a workaround.
The overhead of this workaround might be large depending upon the database
size and the number of users accessing it.
I tried to replicate the database to the same server with a different name.
If the application, that is facing problem, accessing the database with "."
in its name, does not update the data, then the replication can be
transactional and a frequency can be set for updating the new database.
But again as I said, the overhead may be big. But this workaround would
eliminate the requirement of renaming the database and changing it in the
various clients.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm using SQL Server 2000.
I've created a database that has the name "SworderNet.ProductAnalysis."
Various applications connect to this database using this name. Well, it
turns out that certain programs like Excel have a problem accessing SQL
databases that have a "." in the name. The simplest solution is obviously to
just rename the database but it would be a major hassle to try to track down
all of the various clients that use this database and change the
appropriate config files to reflect the new name. Is there a way to create
an "alias" name for this database (similar to a CNAME record in dns)? For
example, I'd like to create an alias called "ProductAnalysis"... The
original name would still work, but clients that have problems with "."
embedded in the database name can just use the alias name instead.
Is it possible?
Sincerely,
David SworderI'm afraid not. The closest would be to create a new database and for each
table create a view inside that database. Not a nice solution...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"David Sworder" <GilGrissom@.CSILasVegas.com> wrote in message
news:unJfw9IDEHA.1600@.tk2msftngp13.phx.gbl...
> Hi there,
> I'm using SQL Server 2000.
> I've created a database that has the name
"SworderNet.ProductAnalysis."
> Various applications connect to this database using this name. Well, it
> turns out that certain programs like Excel have a problem accessing SQL
> databases that have a "." in the name. The simplest solution is obviously
to
> just rename the database but it would be a major hassle to try to track
down
> all of the various clients that use this database and change the
> appropriate config files to reflect the new name. Is there a way to create
> an "alias" name for this database (similar to a CNAME record in dns)? For
> example, I'd like to create an alias called "ProductAnalysis"... The
> original name would still work, but clients that have problems with "."
> embedded in the database name can just use the alias name instead.
> Is it possible?
> --
> Sincerely,
> David Sworder
>|||Hi,
I have a workaround.
The overhead of this workaround might be large depending upon the database
size and the number of users accessing it.
I tried to replicate the database to the same server with a different name.
If the application, that is facing problem, accessing the database with "."
in its name, does not update the data, then the replication can be
transactional and a frequency can be set for updating the new database.
But again as I said, the overhead may be big. But this workaround would
eliminate the requirement of renaming the database and changing it in the
various clients.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 24, 2012
After upgrade MSDE Sp4 Can't connect it through Enterprise Manager
Hi,
I have upgrade MSDE to SP4, but can't connect it throught enterprise manager
after upgrade.
How can I fix it?
Thanks,
Tiger
hi Tiger (Oracle user? :D ),
Tiger wrote:
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
actually you shoud have no technical problem (but legal)...
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||No, I'm not use Oracle
I just use SQL Server Enterprise Manager to connect client PC MSDE, but
after upgrade MSDE to SP4, then fail to connect.
Tiger
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngm9cF1ecmrU1@.individual.net...
> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
> what kind of exception are you reported with when trying connection to
> MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Tiger,
Tiger wrote:
> No, I'm not use Oracle
>
that was a joke, as Scott / Tiger are the "default" sample credentials for
accessing Oracle
> I just use SQL Server Enterprise Manager to connect client PC MSDE,
> but after upgrade MSDE to SP4, then fail to connect.
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Mon, 29 Aug 2005 17:01:01 +0200, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:
> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
Legal problem?
I thought a SQL Server Developer Edition license ($39 or free with MSDN)
allows you to use Enterprise Manager to configure your development copies
of MSDE.
Managing production copies is another matter, but Tiger never mentioned
that.
|||hi,
Lucvdv wrote:
> Legal problem?
> I thought a SQL Server Developer Edition license ($39 or free with
> MSDN) allows you to use Enterprise Manager to configure your
> development copies of MSDE.
> Managing production copies is another matter, but Tiger never
> mentioned that.
if you install SQL Server Dev Edition (for dev and test) you already have a
full SQL Server instance and should not require MSDE at all, but I must
confess as well I've both installed on the same dev pc for my own tests/dev
tasks...
as regard the "legal" problem, I always refer to http://tinyurl.com/ac3v2 ,
where Steve presents a good metaphor about using SQL Server Client Tools
against MSDE in production...
then it's all up to you...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi!
I had the same problem - it seems that SP4 changes the server port ... check
this in server network utility.
greeting
Lukas
"Tiger" <tigerwong666@.hotmail.com> schrieb im Newsbeitrag
news:OBwjydHrFHA.3216@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
> How can I fix it?
> Thanks,
> Tiger
>
I have upgrade MSDE to SP4, but can't connect it throught enterprise manager
after upgrade.
How can I fix it?
Thanks,
Tiger
hi Tiger (Oracle user? :D ),
Tiger wrote:
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
actually you shoud have no technical problem (but legal)...
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||No, I'm not use Oracle
I just use SQL Server Enterprise Manager to connect client PC MSDE, but
after upgrade MSDE to SP4, then fail to connect.
Tiger
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngm9cF1ecmrU1@.individual.net...
> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
> what kind of exception are you reported with when trying connection to
> MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Tiger,
Tiger wrote:
> No, I'm not use Oracle
>
that was a joke, as Scott / Tiger are the "default" sample credentials for
accessing Oracle
> I just use SQL Server Enterprise Manager to connect client PC MSDE,
> but after upgrade MSDE to SP4, then fail to connect.
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Mon, 29 Aug 2005 17:01:01 +0200, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:
> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
Legal problem?
I thought a SQL Server Developer Edition license ($39 or free with MSDN)
allows you to use Enterprise Manager to configure your development copies
of MSDE.
Managing production copies is another matter, but Tiger never mentioned
that.
|||hi,
Lucvdv wrote:
> Legal problem?
> I thought a SQL Server Developer Edition license ($39 or free with
> MSDN) allows you to use Enterprise Manager to configure your
> development copies of MSDE.
> Managing production copies is another matter, but Tiger never
> mentioned that.
if you install SQL Server Dev Edition (for dev and test) you already have a
full SQL Server instance and should not require MSDE at all, but I must
confess as well I've both installed on the same dev pc for my own tests/dev
tasks...
as regard the "legal" problem, I always refer to http://tinyurl.com/ac3v2 ,
where Steve presents a good metaphor about using SQL Server Client Tools
against MSDE in production...
then it's all up to you...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi!
I had the same problem - it seems that SP4 changes the server port ... check
this in server network utility.
greeting
Lukas
"Tiger" <tigerwong666@.hotmail.com> schrieb im Newsbeitrag
news:OBwjydHrFHA.3216@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
> How can I fix it?
> Thanks,
> Tiger
>
Thursday, February 16, 2012
After password change, cannot connect to SQL servers.
We have 4 instances of SQL running on 4 different servers. We recently
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?
Check this article and see if it helps.
http://support.microsoft.com/default...b;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?
Check this article and see if it helps.
http://support.microsoft.com/default...b;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
After password change, cannot connect to SQL servers.
We have 4 instances of SQL running on 4 different servers. We recently
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Could be an issue with your SPN - you can find more info and
troubleshooting steps for the error in the following
article:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On 17 Jan 2006 05:43:12 -0800, "jgrubbs@.pgsd.org"
<jgrubbs@.pgsd.org> wrote:
>We have 4 instances of SQL running on 4 different servers. We recently
>had to change our administrator password. After doing that, we cannot
>connect from our computers (Windows XP SP2) to any of our SQL servers
>(1 Windows Server 2000, 3 Windows Server 2003). We see the following
>error:
>A connection could not be established to "servername"
>Reason: Cannot generate SSPI context.
>Please verify that SQL Server is running and check your SQL Server
>registration properties and try again.
>Any Ideas?|||Thanks, we figured out the issue. The SQLSERVER and the SQLSERVERAGENT
service were set to use the old password. Once we changed this, we
were able to connect.
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Could be an issue with your SPN - you can find more info and
troubleshooting steps for the error in the following
article:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On 17 Jan 2006 05:43:12 -0800, "jgrubbs@.pgsd.org"
<jgrubbs@.pgsd.org> wrote:
>We have 4 instances of SQL running on 4 different servers. We recently
>had to change our administrator password. After doing that, we cannot
>connect from our computers (Windows XP SP2) to any of our SQL servers
>(1 Windows Server 2000, 3 Windows Server 2003). We see the following
>error:
>A connection could not be established to "servername"
>Reason: Cannot generate SSPI context.
>Please verify that SQL Server is running and check your SQL Server
>registration properties and try again.
>Any Ideas?|||Thanks, we figured out the issue. The SQLSERVER and the SQLSERVERAGENT
service were set to use the old password. Once we changed this, we
were able to connect.
After password change, cannot connect to SQL servers.
We have 4 instances of SQL running on 4 different servers. We recently
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?
Could be an issue with your SPN - you can find more info and
troubleshooting steps for the error in the following
article:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On 17 Jan 2006 05:43:12 -0800, "jgrubbs@.pgsd.org"
<jgrubbs@.pgsd.org> wrote:
>We have 4 instances of SQL running on 4 different servers. We recently
>had to change our administrator password. After doing that, we cannot
>connect from our computers (Windows XP SP2) to any of our SQL servers
>(1 Windows Server 2000, 3 Windows Server 2003). We see the following
>error:
>A connection could not be established to "servername"
>Reason: Cannot generate SSPI context.
>Please verify that SQL Server is running and check your SQL Server
>registration properties and try again.
>Any Ideas?
|||Thanks, we figured out the issue. The SQLSERVER and the SQLSERVERAGENT
service were set to use the old password. Once we changed this, we
were able to connect.
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?
Could be an issue with your SPN - you can find more info and
troubleshooting steps for the error in the following
article:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On 17 Jan 2006 05:43:12 -0800, "jgrubbs@.pgsd.org"
<jgrubbs@.pgsd.org> wrote:
>We have 4 instances of SQL running on 4 different servers. We recently
>had to change our administrator password. After doing that, we cannot
>connect from our computers (Windows XP SP2) to any of our SQL servers
>(1 Windows Server 2000, 3 Windows Server 2003). We see the following
>error:
>A connection could not be established to "servername"
>Reason: Cannot generate SSPI context.
>Please verify that SQL Server is running and check your SQL Server
>registration properties and try again.
>Any Ideas?
|||Thanks, we figured out the issue. The SQLSERVER and the SQLSERVERAGENT
service were set to use the old password. Once we changed this, we
were able to connect.
After password change, cannot connect to SQL servers.
We have 4 instances of SQL running on 4 different servers. We recently
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Check this article and see if it helps.
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Check this article and see if it helps.
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
After password change, cannot connect to SQL servers.
We have 4 instances of SQL running on 4 different servers. We recently
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Check this article and see if it helps.
http://support.microsoft.com/defaul...kb;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
had to change our administrator password. After doing that, we cannot
connect from our computers (Windows XP SP2) to any of our SQL servers
(1 Windows Server 2000, 3 Windows Server 2003). We see the following
error:
A connection could not be established to "servername"
Reason: Cannot generate SSPI context.
Please verify that SQL Server is running and check your SQL Server
registration properties and try again.
Any Ideas?Check this article and see if it helps.
http://support.microsoft.com/defaul...kb;en-us;811889
VM
"jgrubbs@.pgsd.org" wrote:
> We have 4 instances of SQL running on 4 different servers. We recently
> had to change our administrator password. After doing that, we cannot
> connect from our computers (Windows XP SP2) to any of our SQL servers
> (1 Windows Server 2000, 3 Windows Server 2003). We see the following
> error:
> A connection could not be established to "servername"
> Reason: Cannot generate SSPI context.
> Please verify that SQL Server is running and check your SQL Server
> registration properties and try again.
> Any Ideas?
>
Monday, February 13, 2012
After installing SQL 2000 SP3, error DB Library : Unexpected EOF from SQL Server
After I installed SP3 to MS SQL 2000 Server, client are not able to connect.
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks
"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>
|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks
"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>
|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>
After installing SQL 2000 SP3, error DB Library : Unexpected EOF from SQL Server
After I installed SP3 to MS SQL 2000 Server, client are not able to connect.
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a crit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>
After installing SQL 2000 SP3, error DB Library : Unexpected EOF from SQL Server
After I installed SP3 to MS SQL 2000 Server, client are not able to connect.
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks"Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>> After I installed SP3 to MS SQL 2000 Server, client are not able to
>> connect.
>> client receive this error :
>> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
>> Client are old application in ObjectView, bat all was Ok before this
>> upgrade.
>> Can anyone advice solution ?
>>
>> Thanks
>
client receive this error :
DB-LIBRARY Error ; Unexpected EOF from SQL Server.
Client are old application in ObjectView, bat all was Ok before this
upgrade.
Can anyone advice solution ?
Thanks"Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
> After I installed SP3 to MS SQL 2000 Server, client are not able to
> connect.
> client receive this error :
> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
> Client are old application in ObjectView, bat all was Ok before this
> upgrade.
> Can anyone advice solution ?
>
> Thanks
>|||"Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
news: OlGdQJ44FHA.1476@.TK2MSFTNGP10.phx.gbl...
> "Laurent CLAUDEL" <laurent.claudel@.steria.com> a écrit dans le message de
> news: e3YKkuS4FHA.2676@.TK2MSFTNGP15.phx.gbl...
>> After I installed SP3 to MS SQL 2000 Server, client are not able to
>> connect.
>> client receive this error :
>> DB-LIBRARY Error ; Unexpected EOF from SQL Server.
>> Client are old application in ObjectView, bat all was Ok before this
>> upgrade.
>> Can anyone advice solution ?
>>
>> Thanks
>
After installing active directory I failed to connect SQL server 2000
After installing active directory I failed to connect SQL server 2000 with
eather with Active directory user accont and sa.
It's showing a messege unable to connect sql server Mainserver\SQL2000DB
server msg 17, level16 state 1
server does not exist or access denied.
Please helpOn Nov 6, 5:26 am, "asif"<jossy...@.nospam.com> wrote:
> After installing active directory I failed to connect SQL server 2000 with
> eather with Active directory user accont and sa.
> It's showing a messege unable to connect sql server Mainserver\SQL2000DB
> server msg 17, level16 state 1
> server does not exist or access denied.
> Please help
first make sure sql server service is started. If the service does
not start you can not connect
second pay attention to servername when you're trying to connect. If
you created default instance then just the servername needed if named
instance created then the server name above should work.
eather with Active directory user accont and sa.
It's showing a messege unable to connect sql server Mainserver\SQL2000DB
server msg 17, level16 state 1
server does not exist or access denied.
Please helpOn Nov 6, 5:26 am, "asif"<jossy...@.nospam.com> wrote:
> After installing active directory I failed to connect SQL server 2000 with
> eather with Active directory user accont and sa.
> It's showing a messege unable to connect sql server Mainserver\SQL2000DB
> server msg 17, level16 state 1
> server does not exist or access denied.
> Please help
first make sure sql server service is started. If the service does
not start you can not connect
second pay attention to servername when you're trying to connect. If
you created default instance then just the servername needed if named
instance created then the server name above should work.
Sunday, February 12, 2012
After enabling named pipes and disabling again, not able to start engine
I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:
TITLE: Connect to Server
Cannot connect to ****** (replaced my servername with stars here for privacy).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
BUTTONS:
OK
BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159
I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.
After enabling named pipes and disabling again, not able to start engine
I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:
TITLE: Connect to Server
Cannot connect to ****** (replaced my servername with stars here for privacy).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
BUTTONS:
OK
BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159
I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.
Subscribe to:
Posts (Atom)