Extracting Sql: failover

Monday, March 19, 2012

Failed on installation of SQL Server SP3a on Failover Cluster

Platform: Windows 2003 ent failover cluster
SQL Server 2k ent
Process: apply SQL server 2k SP3a
We did installation of SQL Server 2k ent successfully. We are using Mixed
mode which allow both NT and SQL authentication. We assigned sa password.
We are able to start/stop/start SQL servrices.
Right after SQL Server 2k ent installation, we started to apply SP3a. But we
got error in middle of serivce pack: Setup was unable to verify the state of
the server for an upgrade. Verify the server is able to start and that you
provide a valid sa password and restart setup.
We foolowed the instruction on article ID 330022 and readme come with CD but
it still doesn't work
Thanks.
Check for:
PRB: Error Message: "Setup was unable to validate the logged user..."
Occurs When You Install SQL Server 2000 Service Pack 3 (SP3)
http://support.microsoft.com/?id=814844
PRB: "Setup Was Unable to Verify the State of the Server for an Upgrade"
Error Message When SQL Server Service Pack 2 Setup Stops Responding
http://support.microsoft.com/?id=328290
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||I referenced both articles but they are not really applied to our case. Our
platform is on WINDOWS 2003. We are implementing Failover Clustering. Our
MDAC is 2.8 version above. We didn't have any problem to install sql sp3a on
any other win2k or win2k3 ent platform. Only this time is Windows 2003 ent
FAILOVER CLUSTERING. We got SQL server 2k ent ed installed and we tried to
apply sql sp3a immediately after installation base on the recommendation.
But we got error in middle of serivce pack: Setup was unable to verify the
state of the server for an upgrade. Verify the server is able to start and
that you provide a valid sa password and restart setup.
"Fany Vargas [MSFT]" wrote:

> Check for:
> PRB: Error Message: "Setup was unable to validate the logged user..."
> Occurs When You Install SQL Server 2000 Service Pack 3 (SP3)
> http://support.microsoft.com/?id=814844
>
> PRB: "Setup Was Unable to Verify the State of the Server for an Upgrade"
> Error Message When SQL Server Service Pack 2 Setup Stops Responding
> http://support.microsoft.com/?id=328290
>
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
|||1. Ensure that all NON-essential services are stopped. You can reference KB
for a list of services which need to stay running: INF: Order of
Installation for SQL Server 7.0 Clustering Setup - ID: 219264 (I realize
this is a 7.0 article). Also stop any antivirus or backup software in case
this is interfering with setup.
It is possible some other service is taking hold of the single user
conenction sql server starts with while applying the service pack. Also,
check any *.out files created by setup especially cnfsvr.out - they may
have more detailed errors.
2. If necessary, you can post your SQLSP.log file ( this is the setup log
file - fyi, it will contain your machine name, user name, virtual
servername,etc - it should not have any passwords though)
Thanks,
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Also check that in "Environment Variables" (Right click on
My Computer -> Advanced) the variable TEMP has an actual
physycal path like c:\Temp and is not like %vari...%
Works for me every time

Friday, March 9, 2012

Fail over - DNS change

Hi,

In case of failover to standby server, what is theest way to redirect
client applications to new server?
1) DNS name change -- not viable due to Caching issue.

IS there any alternate like Oracle's onames/LDAP for resolving name
with sql server?

Can use Sever alias?

Thanksbarbara_2003@.hotmail.com (barbara) wrote in message news:<5cd01256.0408221348.259e22d1@.posting.google.com>...
> Hi,
> In case of failover to standby server, what is theest way to redirect
> client applications to new server?
> 1) DNS name change -- not viable due to Caching issue.
> IS there any alternate like Oracle's onames/LDAP for resolving name
> with sql server?
> Can use Sever alias?
> Thanks

There's no equivalent to Oracle's naming solutions, since MSSQL uses
the operating system for name resolution. If you can't use DNS, then
you would have to look at modifying connection strings or ODBC DSNs in
your applications. This is easier for some types of applications than
others, of course.

Simon|||Please share any other recommendations.

sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0408230548.39882eda@.posting.google.com>...
> barbara_2003@.hotmail.com (barbara) wrote in message news:<5cd01256.0408221348.259e22d1@.posting.google.com>...
> > Hi,
> > In case of failover to standby server, what is theest way to redirect
> > client applications to new server?
> > 1) DNS name change -- not viable due to Caching issue.
> > IS there any alternate like Oracle's onames/LDAP for resolving name
> > with sql server?
> > Can use Sever alias?
> > Thanks
> There's no equivalent to Oracle's naming solutions, since MSSQL uses
> the operating system for name resolution. If you can't use DNS, then
> you would have to look at modifying connection strings or ODBC DSNs in
> your applications. This is easier for some types of applications than
> others, of course.
> Simon|||Sinon,

Thanks for reply. How does it uses OS for name resolution in case of
multiple instances? Could we use multiple IP address feature of sql
2000 for fail over purpose? Using virtual IP, but without using
clustering.

<snip
The client resolves the server part of the instance name, then
connects to port 1434 to get back a list of instances and the ports
they listen on; it can then connect to the correct port for the
instance you requested. You can specify these ports explicitly using
the MSSQL Server Network Utility if you want to.

Clustering is the standard way to implement failover with MSSQL -
multiple instances aren't useful for high availability. You can check
these resources for more details:

http://www.microsoft.com/sql/techin...vailability.asp
http://www.microsoft.com/technet/pr...oy/sqlhalp.mspx

I'm not sure why you want to avoid clustering - if you have a business
need for any sort of high availability solution, then you have to make
sure you get the correct resources you need for that.

Simon|||Our vendor application (web based) doesn't support clustering. What
are the disadvantages of using NLB for failover? I've read it is not
advisable to use NLB for critical DB failovers. Is it true?

sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0408240605.2c289511@.posting.google.com>...
> barbara_2003@.hotmail.com (barbara) wrote in message news:<5cd01256.0408240202.7bb670e8@.posting.google.com>...
> > Sinon,
> > Thanks for reply. How does it uses OS for name resolution in case of
> > multiple instances? Could we use multiple IP address feature of sql
> > 2000 for fail over purpose? Using virtual IP, but without using
> > clustering.
> <snip>
> The client resolves the server part of the instance name, then
> connects to port 1434 to get back a list of instances and the ports
> they listen on; it can then connect to the correct port for the
> instance you requested. You can specify these ports explicitly using
> the MSSQL Server Network Utility if you want to.
> Clustering is the standard way to implement failover with MSSQL -
> multiple instances aren't useful for high availability. You can check
> these resources for more details:
> http://www.microsoft.com/sql/techin...vailability.asp
> http://www.microsoft.com/technet/pr...oy/sqlhalp.mspx
> I'm not sure why you want to avoid clustering - if you have a business
> need for any sort of high availability solution, then you have to make
> sure you get the correct resources you need for that.
> Simon|||barbara_2003@.hotmail.com (barbara) wrote in message news:<5cd01256.0408241352.44eb3992@.posting.google.com>...
> Our vendor application (web based) doesn't support clustering. What
> are the disadvantages of using NLB for failover? I've read it is not
> advisable to use NLB for critical DB failovers. Is it true?

<snip
I have no idea, since I've never used NLB myself. See here:

http://www.microsoft.com/technet/pr...oy/hasog04.mspx

Simon

Monday, March 19, 2012

Failed on installation of SQL Server SP3a on Failover Cluster

Friday, March 9, 2012

Fail over - DNS change

Extracting Sql

Blog Archive

About Me