Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Application unable to connect Sql Server 2005

Hi,

We recently installed Sql 2005 server and it was working fine. But today one of our user reported that they could not able to connect the sql server 2005 from the application. When I checked the error log, I found the following error for every one minute. We restarted the sql service on this sql 2005 instance but still we are getting the same error.

SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed.

Could any one help us on that?

Regards,

Sankar

Hello Sankar. There appears to be several possibilities as to what is going on so i will provide the links that I think are the most relevant.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

http://support.microsoft.com/kb/247931/en-us

OJ has suggested this as a possible means for tracing it - I am not sure of your setup so it may or may not be useful.

0x80090311 error refers to "No authority could be contacted for authentication" which means the user cannot contact AD to get a ticket. I suggest turning on Kerberos logging and using Netmon to trace the authentication routes. You can find detailed info on how to troubleshoot Kerberos here.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

Let us know if you have any further questions or if this helps. If you do have further questions/problems please try specifying more details about your setup, e.g. are db and web server on same server? what os? what update revisions, etc.

|||

Hi, SanKar

Is your computer in a Domain? If so, it seems the problem that no KDC can be contacted. Suggest:

1) Disjoin the domain and rejoin your computer to the domain.

2) nslookup

type " <FQDN> of your client computer " see which DC returned.

3) ping <KDCname> if you know the hostname of your DC.

ping -a <ipaddress of your DC>, see whether FQDN returned.

4) Try use "SetSpn.exe" to manually register SPN, see whether it succeeds.

5) Or restart your client computer, try to use a domain account to log on, see what happens.

Good Luck!

Ming.

|||

Thanks all for your reply.

We rebooted the sql server. The error is not getting displayed after the server reboot.

App server unable to connect to SQL Server 2000 developer edition on localhost.

Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?

FAILS
--
Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db

Error: "com.inet.tds.SQLException: Connection refused"

When app server on Machine_A attempts to connect to database on
Machine_A the conenction is refused.

SUCCEEDS
---
Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db

When app server on Machine_A attempts to connect to database on
Machine_B the conenction succeeds and the app server runs normally.

JDBC driver: com.inet.tds.TdsDriver

jdbc:inetdae7:locahost:1433

I don't believe the app server is exhausting the 10-connection max on
SQL2K developer edition (there is a 10-connection limit imposed on the
developer edition, correct?)

LBlbunet@.hotmail.com (LB) wrote in message news:<35e1fa55.0404062027.3635b8b9@.posting.google.com>...
> Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?
> FAILS
> --
> Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db
> Error: "com.inet.tds.SQLException: Connection refused"
> When app server on Machine_A attempts to connect to database on
> Machine_A the conenction is refused.
>
> SUCCEEDS
> ---
> Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db
>
> When app server on Machine_A attempts to connect to database on
> Machine_B the conenction succeeds and the app server runs normally.
> JDBC driver: com.inet.tds.TdsDriver
> jdbc:inetdae7:locahost:1433
> I don't believe the app server is exhausting the 10-connection max on
> SQL2K developer edition (there is a 10-connection limit imposed on the
> developer edition, correct?)
> LB

There is no connection limit in Developer Edition - it's Enterprise
Edition with a different licence.

I don't know exactly what "Connection refused" means, but you might
want to check the SQL Server logs for failed logins, and also test
your username/password combination with osql.exe or whatever, just to
make sure it works correctly. You could also check the authentication
modes on the two servers (Windows or Mixed), to see if they are the
same - username/password works only in Mixed mode, if that's what
you're using.

Simon|||sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0404070120.39c31661@.posting.google.com>...

... [See first post for text that appeared here]

> There is no connection limit in Developer Edition - it's Enterprise
> Edition with a different licence.
> I don't know exactly what "Connection refused" means, but you might
> want to check the SQL Server logs for failed logins, and also test
> your username/password combination with osql.exe or whatever, just to
> make sure it works correctly. You could also check the authentication
> modes on the two servers (Windows or Mixed), to see if they are the
> same - username/password works only in Mixed mode, if that's what
> you're using.
> Simon

Thanks for the feedback.

LB