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 Role with vb

I use Application role with vb.
I connect to sql server by windows authentication.
I setup each login to public role of database.
In Database , i add application role and set permission via application
role.
When VB App connect to database , it use windows authentication.
Before It connectd , i call stored procedure (sp_setapprole) to database.
It work fine except that if i use boundcolumn to control in form.
it's occure error for consequent code try to select data from table.
It warn that "permission denied".
Thanks in advanceIt's not work yet.
But i close recordset of bound column, it can select data but bound column
can not see data.
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:eH6bONNeDHA.1832@.TK2MSFTNGP09.phx.gbl...
> It may be that connection pooling is resetting the connection so you
> lose the app role security context. Assuming you're using SQLOLEDB, try
> disabling connection pooling by including ';OLE DB Services=-2' in your
> connection string. For example:
> Provider=SQLOLEDB;Data Source=MyServer;Integrated Security=SSPI;Persist
> Security Info=False;;OLE DB Services=-2
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> --
> SQL FAQ links (courtesy Neil Pike):
> http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> http://www.sqlserverfaq.com
> http://www.mssqlserver.com/faq
> --
> "ton" <barameek@.inglife.co.th> wrote in message
> news:e5ydwCNeDHA.3204@.TK2MSFTNGP11.phx.gbl...
> > I use Application role with vb.
> > I connect to sql server by windows authentication.
> > I setup each login to public role of database.
> > In Database , i add application role and set permission via
> application
> > role.
> > When VB App connect to database , it use windows authentication.
> > Before It connectd , i call stored procedure (sp_setapprole) to
> database.
> > It work fine except that if i use boundcolumn to control in form.
> > it's occure error for consequent code try to select data from table.
> > It warn that "permission denied".
> >
> > Thanks in advance
> >
> >
> >
>

Application not connecting to DB on restart of PC?

Hi,

i am stuck in a strange situation.
I

have successfully built my application setup through InstallSheild 12.

Which first installs SQL Express user define instance as a

pre-requisite and then install my application files. First time when i

run my application (without restarting the pc), it connects

successfully with user define instance.
But as i restart my PC and try to open my application, it is not connecting with database.
i am using the following command line to install SQL Express 2005 user define instance:

"/qn ADDLOCAL=SQL_Engine INSTANCENAME=MyInstance SECURITYMODE=SQL SAPWD="test" AUTOSTART=1"

if

i change Remote connection to "using both TCP/IP and named pipes"

through "SQL Server Surface Area Configuration" and then restart my pc

again. My application connects successfully with Database.

Please

guide me where i am getting wrong in building setup. do i have to add

something in my command line to not get this error

Please provide more information...

What error are you getting?

How are you connecting to SQL Express? (i.e. connection string)

What is different from the first time you connect at installation and the second time you connect after re-boot?

Are you using ODBC, OLEDB or Shared Memory to connect?

Mike

|||Hi,
thanks for the reply.
i am installing my installer on WinXP machine.
i am using the following connection string to connect with database.

Connection String:
--
Connection.ConnectionString = "packet size=4096;user id=sa;pwd=test; data source = (local)\\MyInstance;initial catalog = MyDB";

Error getting when connecting to SQL Mangmnt Studio:
-
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: Shared Memory Provider, error: 40 -
Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

when first time i install , In "SQL Server Surface Area Configuration" it is checked on "Local Connection Only" and connects successfully.
When i restart my pc and open application it doesnt connect .I open "SQL Server Surface Area Configuration", still "Local Connection Only" is checked but when i check on "using both TCP/IP and named pipes".
and then start my applicaion it connects successfully.|||Hi,
i am using following namespace for connection object.
using System.Data.SqlClient;

application failed. when clicked on the sqlexpr.exe file.

Hello

I have the sql server 2005 express edition. the software stops during the setup and gives me a "failed" message. All other software of express edition are working fine. I am getting the problem only when I am dealing with sql server 2005 express edition. I made sure to deleate all the old version of sql server. uninstalled all the sql server files which were in my computer prior to download the new one. However I am still in troulbe.

As someone suggested that one should uninstale the sqlmsi file so I did that too. Still samething. Any help please......

Hi,

The event log should give you a clue what happened, eventually during the initial startup of the service.

Make sure that the SQL Server Service could start up properly. In the near püast a often and common error was that the rights provided within the SQL Server service was not priviledged to aquire the sufficient permissions for starting. So either make sure that you are using a account for starting the service which is priviledged to start as a service. Normally, Local System should be enough to start (commonly used), a (for me) better way is (if you have a domain context) is to use a domain account.

Some of the advantages are:

-There is much more security granularity over a domain account than over a system account
-If you later need network ressources you won′t get them with a Local System Account and have to switch to a domain account.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Thank you very much sir thanks a lot its working now. :) i appreciated your support

Anyway to Stop DSN & DSNless connections to SQL Server?

I'm trying to setup a new server but need to stop people accessing the database via Access, Excel etc

Is there any way to set SQL server up to stop connections from such applications?

Is there any way to allow only certain users to connect via a DSN

We are not using windows authentication on the server

Cheers

No, you cannot restrict connections based on the application that made them. But you can restrict connections based on the account they were made with. You can try to have your application connect to SQL Server using a specific account and not grant any connection rights to the users - then they would only be able to access the database through the application. Of course, if they would debug the application, they could figure out how it connects to SQL Server (the account and the password), but this would at least prevent accidental connections from other applications.

Thanks
Laurentiu