Cannot reinstall MSDE on XP after uninstall it

I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
Some of the component in an application did not work well so I had to
uninstall the MSDE 2000 SP3a completely. I removed all folders and even
registry entries. I kept getting this message, "Setup failed to configure the
server. Refer to the server error logs and setup logs for more information".
Unfortunately, those error and setup logs were useless. So, I used the /L*v
parameter to generate the setup log but it did not pinpoint why it failed. It
always fail at the last 4 seconds install period.
I ran the same setup on another XP machine. After uninstalled MSDE, removed
folders and registry entries, I was able to reinstall MSDE 2000 again.
Any help will be greatly appreciated.
Thank you.
KC
Here's a Knowledge Base article with instructions on how to manually
uninstall MSDE 2000.
http://support.microsoft.com/default...b;en-us;320873
Good luck,
Tony Sebion
"KC" <KC@.discussions.microsoft.com> wrote in message
news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:

> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
|||Thank you for the reply. First, I looked for those registry entries mentioned
in the article. None of them exists. So, I installed Windows Support Tools
for XP on the machine, ran the msizap with GUID, it found nothing.
The setup still fails with the same error message. What's next?
Thank you for the article though.
"Tony Sebion" wrote:

> Here's a Knowledge Base article with instructions on how to manually
> uninstall MSDE 2000.
> http://support.microsoft.com/default...b;en-us;320873
>
> Good luck,
> Tony Sebion
>
> "KC" <KC@.discussions.microsoft.com> wrote in message
> news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:
>
>
|||hi
KC wrote:
> Thank you for the reply. First, I looked for those registry entries
> mentioned in the article. None of them exists. So, I installed
> Windows Support Tools for XP on the machine, ran the msizap with
> GUID, it found nothing.
> The setup still fails with the same error message. What's next?
>
sometimes this is due to MDAC mess, so you have to fix it...
you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
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
|||KC wrote:
> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
Hi,
A had the same problem. I found that there isn't uninstalled
MSSQLServerADHelper service. I searched in registry and deletet
(almost;-) everything which contained MSSQL. That works (at least at my
PC). Maybe it'll work at yours too.
ukasz
|||Okay...Finally, I got it to reinstall after many tries. Thank you all for
your helps. First, MDAC was messed up. It was sqlsrv32.dll. Because I
upgraded my initial MSDE installed to SP3a, that DLL file got upgraded. I
replaced that DLL file from a good known XP machine. Then, re-registered all
MDAC using MDAC Repair Util. That didn't work. Later, I found out that there
were three DLLs missing from the System32 folder: sqlsrv32.rll, SQLWID.DLL &
SQLWOA.DLL. I copied them from a known good XP machine. Reinstalled MDAC 2.8
completely. After that, it installed just fine...Thank you.
"Andrea Montanari" wrote:

> hi
> KC wrote:
> sometimes this is due to MDAC mess, so you have to fix it...
> you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
> it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> 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
>
>

Cannot open database requested in login

Hi there i'm having a bit of trouble with my asp.net authorisations and was wondering
if anyone would have any idea how I can solve it - as it's driving me nuts!.

On my local machine (I've MDSN) running with Web Matrix - my connection works fine.

However since i've uploaded it to my Hoster - Forms and DB - I get the error

Cannot open database requested in login 'TestDB'. Login fails. Login failed for user AUTHORITY\NET SERVICE'.

Can anyone give me any pointers on where I should be going?

I've been told by my Hosting co. that the server should be set to localhost (as shown)
but thats about it!

My Web.config file looks like:-

<configuration>
<!-- application specific settings -->
<appSettings>
<add key="ConnectionString" value="server=localhost;Trusted_Connection=true;database=TestDB" />
</appSettings
<!-- forms based authentication --
<system.web>
<!-- enable custom errors for the application -->
<customErrors mode="Off"/>
<!--RemoteOnly" defaultRedirect="ErrorPage.aspx" -->
<!-- disable session state for application -->
<sessionState mode="Off" />
</system.web>
</configuration
Thanks in advance for any help.

Dave.Did the host say whether you should use NT Authorization or Sql Authorization? You are using NT Authorization now but perhaps it should be Sql Authorization. If so you'll have to change your connection string to something like:

data source=localhost;initial catalog=TestDb;password=whatever;user id=whatever;packet size=4096

Of course you'll need to find out what username and password to use.|||I know netiquete etc but had to thank you!

Just like to say thanks for that invaluable piece of information!

If anyone else has the problem i've been getting then the solution proposed by McMurdoStation was absolutly spot on.

Thanks again.

Dave|||Your welcome.

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.

>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
Dan
Hi Dan
"dan@.wagers.net" wrote:

> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#disablenetworkprotocols
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
http://msdn2.microsoft.com/en-us/library/ms173748.aspx
John

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.
>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
DanHi Dan
"dan@.wagers.net" wrote:
> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
> >From the remote machine, the same .udl is set up, but with a Data
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#disablenetworkprotocols
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
http://msdn2.microsoft.com/en-us/library/ms173748.aspx
John

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.

>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
DanHi Dan
"dan@.wagers.net" wrote:

> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
>
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
l]
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
[url]http://msdn2.microsoft.com/en-us/library/ms173748.aspx" target="_blank">http://msdn2.microsoft.com/en-us/li...y/ms173748.aspx
John

Cannot generate SSPI context

Hi,
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that
I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with m
y
network account from within an RDP session.
"Anatoli" wrote:

> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server tha
t I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I kee
p
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have a
ny
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to othe
r
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:

> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
[vbcol=seagreen]
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to m
y
> domain account. That is that I can connect remotely to the SQL server usin
g
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logg
ed
> onto that PC and still I got the same error. Again, when I logged in local
ly
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to ot
her
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
>

Cannot generate SSPI context

Hi,
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with my
network account from within an RDP session.
"Anatoli" wrote:
> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server that I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I keep
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have any
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to other
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:
> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to my
> domain account. That is that I can connect remotely to the SQL server using
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logged
> onto that PC and still I got the same error. Again, when I logged in locally
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to other
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
> > Anatoli,
> >
> > check these links.
> > http://support.microsoft.com/kb/811889/
> >
> > http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> > http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> >
> > Hope this helps
> >
> > Markus
> >
> >