Troubleshooting SQL Server 2000 Virtual Server /Service Pack ...

Troubleshooting SQL Troubleshooting SQL Server 2000 Virtual Server 2000 Virtual Server /Service Pack Setups Server /Service Pack Setups for Failover Clusteringfor Failover Clustering

Uttam ParuiUttam ParuiSQL Server Developer Support EngineerSQL Server Developer Support EngineerProduct Support ServicesProduct Support ServicesMicrosoft CorporationMicrosoft Corporation

2

ObjectivesObjectives

Understand Microsoft® SQL Server™ 2000 Understand Microsoft® SQL Server™ 2000 virtual server setup processvirtual server setup process

Know what logs to review to troubleshoot a Know what logs to review to troubleshoot a failed virtual server /service pack setupfailed virtual server /service pack setup

Troubleshoot virtual server setup failuresTroubleshoot virtual server setup failures Troubleshoot virtual server service pack Troubleshoot virtual server service pack

setup failuressetup failures Discuss SQL Server 2000 Service Pack 3 pre-Discuss SQL Server 2000 Service Pack 3 pre-

installation checklist for SQL Server 2000 installation checklist for SQL Server 2000 virtual servervirtual server

3

Understanding SQL Server 2000 Understanding SQL Server 2000 Virtual Server Setup ProcessVirtual Server Setup Process SQL Server 2000 virtual server setup involves SQL Server 2000 virtual server setup involves

a main setup process that starts one a main setup process that starts one unattended installation for every node that is unattended installation for every node that is part of the virtual server part of the virtual server

The main setup process does the following:The main setup process does the following: Gathers configuration information for the virtual Gathers configuration information for the virtual

server (the information is recorded in the setup server (the information is recorded in the setup initialization file, Setup.iss)initialization file, Setup.iss)

Starts unattended setup process (on every node Starts unattended setup process (on every node that is a part of the virtual server) using the that is a part of the virtual server) using the options specified in Setup.issoptions specified in Setup.iss

Creates virtual server resources and sets the Creates virtual server resources and sets the correct node ownershipcorrect node ownership

4

Understanding SQL Server 2000 Understanding SQL Server 2000 Virtual Server Setup Process Virtual Server Setup Process (2)(2)

Unattended setup processUnattended setup process The number of unattended setup processes is equal to the The number of unattended setup processes is equal to the

number of nodes that are a part of the virtual servernumber of nodes that are a part of the virtual server Each unattended setup is completed by separate threadsEach unattended setup is completed by separate threads An unattended setup process that is running on the node An unattended setup process that is running on the node

where the setup was started (also named primary node):where the setup was started (also named primary node): Copies the required binariesCopies the required binaries Registers the components that are required to run SQL Registers the components that are required to run SQL

Server on that nodeServer on that node Creates databases on the shared driveCreates databases on the shared drive Runs initial configuration scriptsRuns initial configuration scripts

The unattended setup process on other nodes (also named The unattended setup process on other nodes (also named secondary nodes) copies the required binaries and secondary nodes) copies the required binaries and registers the components that you need to run SQL Server registers the components that you need to run SQL Server on that nodeon that node

5

Virtual Server Setup Log FilesVirtual Server Setup Log Files The main setup process creates a The main setup process creates a Sqlstp.logSqlstp.log

file on the node where the virtual server file on the node where the virtual server setup was startedsetup was started

Unattended setup processes create log files Unattended setup processes create log files SqlstpN.logSqlstpN.log (where N is an integer) on each (where N is an integer) on each node where the unattended setup is runnode where the unattended setup is run

After the unattended setup processes After the unattended setup processes complete successfully on all the nodes, the complete successfully on all the nodes, the main setup process creates virtual server main setup process creates virtual server resources and sets the correct node resources and sets the correct node ownershipownership Setup writes detailed messages to the Setup writes detailed messages to the Sqlclstr.logSqlclstr.log

and and Cluster.logCluster.log on the node where the virtual on the node where the virtual server setup was startedserver setup was started

6

Virtual Server Setup Log Files Virtual Server Setup Log Files (2)(2)

Sqlstp.log

SqlstpN.log(primary node)

SqlstpN.log(secondary node)

Configuration Information

Setup is performing required operations on cluster nodes. This may take a few minutes…

#### SQL Server Remote Setup - Start Time

Running '\\NODE1\C$\SQL2000.ENT\x86\setup\setupsql.exe k=Nb k=Rm k=Cl -SMS -s -f "\\NODE1\C$\SQL2000.ENT\x86\setup\setup.ins" -f1 \\NODE1\admin$\NODE1_MSSQLSERVER.iss -f2 "\\NODE1\admin$\setup.log" -e "stpsilnt._ex" -b -x "C:\WINNT\TEMP\"' (NODE1) ...

CProcess::RunUntilComplete [0x94] exit code: 0Remote process exit code was '0' (NODE1).

Running '\\NODE1\C$\SQL2000.ENT\x86\setup\setupsql.exe k=ClSec k=Rm k=Cl -SMS -s -f "\\NODE1\C$\SQL2000.ENT\x86\setup\setup.ins" -f1 \\NODE2\ADMIN$\NODE2_MSSQLSERVER.iss -f2 "\\NODE2\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"' (NODE2) ...

CProcess::RunUntilComplete [0x94] exit code: 0Remote process exit code was '0' (NODE2).

#### SQL Server Remote Setup - Stop Time

CreateVirtualServerResources Sqlclstr.log(primary node)

7


Consider a cluster with the node names Node1, and Consider a cluster with the node names Node1, and Node2. Lets assume that you ran a SQL Server setup Node2. Lets assume that you ran a SQL Server setup program on Node1 to install a virtual server and program on Node1 to install a virtual server and setup completed successfully. setup completed successfully.

Here is a summary of files that will be created on Here is a summary of files that will be created on each node:each node: Node1 (primary node)Node1 (primary node)

Sqlstp.log – created by the main setup processSqlstp.log – created by the main setup process Sqlstp0.log and Setup.log – created by the unattended Sqlstp0.log and Setup.log – created by the unattended

setup process on Node1setup process on Node1 Sqlclstr.log – created by the main setup process when it Sqlclstr.log – created by the main setup process when it

creates the virtual server resourcescreates the virtual server resources Node2 (secondary node)Node2 (secondary node)

Sqlstp0.log and Setup.log – created by the unattended Sqlstp0.log and Setup.log – created by the unattended setup process on Node2setup process on Node2

8


Consider a cluster with the node names Node1, and Consider a cluster with the node names Node1, and Node2. Lets assume that you ran SQL Server setup Node2. Lets assume that you ran SQL Server setup program on Node1 to install a virtual server, and program on Node1 to install a virtual server, and setup failed while running the unattended setup on setup failed while running the unattended setup on Node1 and unattended setup never started on Node2. Node1 and unattended setup never started on Node2.

Here is a summary of files that will be created on Here is a summary of files that will be created on each node:each node: Node1: Sqlstp.log, Sqlstp0.log, and Setup.logNode1: Sqlstp.log, Sqlstp0.log, and Setup.log Node2: No files will be createdNode2: No files will be created

9


Now assume you troubleshoot the issue and then Now assume you troubleshoot the issue and then rerun the setup, and the setup completes rerun the setup, and the setup completes successfullysuccessfully

Here is a summary of files that will be created on Here is a summary of files that will be created on each nodeeach node Node1 Node1

Sqlstp.log – created by the main setup process (this is a Sqlstp.log – created by the main setup process (this is a new file – the main setup process overwrites the new file – the main setup process overwrites the previous Sqlstp.log)previous Sqlstp.log)

Sqlstp1.log and Setup.log – created by the unattended Sqlstp1.log and Setup.log – created by the unattended setup process on Node1 setup process on Node1 Note: The file name is Sqlstp1.log because there is Note: The file name is Sqlstp1.log because there is

already a file named Sqlstp0.log on Node1already a file named Sqlstp0.log on Node1 Sqlclstr.log – created by the main setup process when it Sqlclstr.log – created by the main setup process when it

creates the virtual resourcescreates the virtual resources Node2 (secondary node)Node2 (secondary node)

Sqlstp0.log and Setup.log – created by the unattended Sqlstp0.log and Setup.log – created by the unattended setup process on Node1setup process on Node1

10


Note:Note: Sqlstp.log is overwritten every time the virtual Sqlstp.log is overwritten every time the virtual

server setup is startedserver setup is started Log files (SqlstpN.log) created by unattended Log files (SqlstpN.log) created by unattended

setup are not overwrittensetup are not overwritten The unattended setup process does not create The unattended setup process does not create

log files with the same name on both the nodeslog files with the same name on both the nodes The log file name is dependent on the last SqlstpN.log The log file name is dependent on the last SqlstpN.log

on the nodeon the node

The virtual server setup process creates log files The virtual server setup process creates log files that start with the characters ‘sqlstp’, whereas the that start with the characters ‘sqlstp’, whereas the service pack setup logs start with the characters service pack setup logs start with the characters ‘sqlsp’‘sqlsp’ So, the main service pack setup process will create So, the main service pack setup process will create

Sqlsp.log on the node where the service pack setup was Sqlsp.log on the node where the service pack setup was run, and will create SqlspN.log on other nodes that are run, and will create SqlspN.log on other nodes that are part of the virtual serverpart of the virtual server

11


Primary Node Primary Node (where virtual server setup (where virtual server setup was started)was started)

Secondary Nodes Secondary Nodes (other nodes that are part of (other nodes that are part of the virtual server)the virtual server)

Sqlstp.logSqlstp.log SqlstpN.logSqlstpN.log

SqlstpN.logSqlstpN.log Setup.logSetup.log

Sqlclstr.logSqlclstr.log

Cluster.logCluster.log

Setup.logSetup.log

Note: Note: The default location for SqlstpN.log, Sqlclstr.log and The default location for SqlstpN.log, Sqlclstr.log and

Setup.log is C:\WINNTSetup.log is C:\WINNT The default location for Cluster.log is C:\WINNT\ClusterThe default location for Cluster.log is C:\WINNT\Cluster

Summary: Setup logs created by SQL Server 2000 virtual server setup

12

Troubleshooting Virtual Server Troubleshooting Virtual Server Setup FailureSetup Failure Basic stepsBasic steps Review the Sqlstp.log file on the node where Review the Sqlstp.log file on the node where

you ran the virtual server setup and identify you ran the virtual server setup and identify where the setup failedwhere the setup failed

After you identify where the setup failed, After you identify where the setup failed, review the appropriate setup files to find the review the appropriate setup files to find the exact error messageexact error message

Use the keywords in the error message to Use the keywords in the error message to perform a search on the Microsoft Knowledge perform a search on the Microsoft Knowledge Base to find more detailed information about Base to find more detailed information about the error, and the solution to the problemthe error, and the solution to the problem

13

Sample Setup.log Created by Sample Setup.log Created by Unattended InstallationUnattended Installation

The meaning of the The meaning of the ResultCode can be found ResultCode can be found by opening an MS-DOS by opening an MS-DOS window and typing net window and typing net helpmsg ResultCodehelpmsg ResultCode

If the result code is –ve If the result code is –ve (for example, -1), net (for example, -1), net helpmsg will not display helpmsg will not display any information. For –ve any information. For –ve result code, refer to SQL result code, refer to SQL Server 2000 Books Online Server 2000 Books Online (BOL) topic “Error Codes (BOL) topic “Error Codes for an Unattended for an Unattended Installation.” The next Installation.” The next slide has the table from slide has the table from BOL.BOL.

[InstallShield Silent][InstallShield Silent]Version=v5.00.000Version=v5.00.000File=Log FileFile=Log File[Application][Application]Name=Microsoft Name=Microsoft SQL ServerSQL ServerVersion=8.00.000Version=8.00.000Company=MicrosoftCompany=MicrosoftLang=0000Lang=0000[Status][Status]Completed=1Completed=1RebootRequired=0RebootRequired=0[ResponseResult][ResponseResult]ResultCode=0ResultCode=0

14

Error Codes for an Error Codes for an Unattended Installation Unattended Installation

Error code numberError code number Error Code DescriptionError Code Description

00 Success.Success.

-1-1 General error.General error.

-2-2 Invalid mode.Invalid mode.

-3-3 Required data not found in the Setup.iss file.Required data not found in the Setup.iss file.

-4-4 Not enough memory available.Not enough memory available.

-5-5 File does not exist.File does not exist.

-6-6 Cannot write to the response file.Cannot write to the response file.

-7-7 Cannot write to the log file.Cannot write to the log file.

-8-8 Invalid path to the InstallShield Silent response file.Invalid path to the InstallShield Silent response file.

-9-9 Not a valid list type (string or number).Not a valid list type (string or number).

-10-10 Data type is invalid.Data type is invalid.

-11-11 Unknown error during setup.Unknown error during setup.

-12-12 Dialog boxes are out of order. This is a common error, caused when a Dialog boxes are out of order. This is a common error, caused when a dialog box appears out of order in the setup initialization file dialog box appears out of order in the setup initialization file (Setup.iss). This can occur due to a system problem during (Setup.iss). This can occur due to a system problem during the creation of Setup.iss. the creation of Setup.iss.

-51-51 Cannot create the specified folder.Cannot create the specified folder.

-52-52 Cannot access the specified file or folder.Cannot access the specified file or folder.

-53-53 Invalid option selected.Invalid option selected.

15

Troubleshooting Virtual Server Troubleshooting Virtual Server Setup Failure Setup Failure (2)(2)

Virtual server setup failed with the following error:Virtual server setup failed with the following error:

Setup failed to perform required operations on the Setup failed to perform required operations on the cluster nodescluster nodes

This is a generic message and all you can conclude This is a generic message and all you can conclude from this message is that the setup failed while from this message is that the setup failed while running unattended setup on one or all the cluster running unattended setup on one or all the cluster nodesnodes

In the following two examples, we will learn how to In the following two examples, we will learn how to start with a generic error message, identify the start with a generic error message, identify the underlying problem, and then with the help of the underlying problem, and then with the help of the exact error message and the Microsoft Knowledge exact error message and the Microsoft Knowledge Base, resolve the issueBase, resolve the issue

16


Example 1Example 1 The first step will be to review the Sqlstp.log on The first step will be to review the Sqlstp.log on

the node where the virtual server setup was the node where the virtual server setup was started and discover where the failure occurredstarted and discover where the failure occurred

In Sqlstp.log, search for the line:In Sqlstp.log, search for the line:“Setup is performing required operations on cluster nodes. This may take a few “Setup is performing required operations on cluster nodes. This may take a few minutes...”minutes...”

Assume this is the error footprint in the Assume this is the error footprint in the Sqlstp.log:Sqlstp.log:

19:18:30 Setup is performing required operations on cluster nodes. 19:18:30 Setup is performing required operations on cluster nodes. This may take a few minutes...This may take a few minutes...

19:18:30 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\19:18:30 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.iniremsetup.ini19:19:25 Process Exit Code: (2) The system cannot find the file 19:19:25 Process Exit Code: (2) The system cannot find the file specified.specified.19:19:25 Begin Action : GetRemsetupRetCode19:19:25 Begin Action : GetRemsetupRetCode19:19:25 Installation return status on NODE1 : 219:19:25 Installation return status on NODE1 : 219:19:25 Installation return status on NODE2 : 219:19:25 Installation return status on NODE2 : 2

17


Example 1 (continued)Example 1 (continued) Note: Installation return status code on both nodes is 2Note: Installation return status code on both nodes is 2 net helpmsg 2net helpmsg 2

Returns “The system cannot find the file specified”Returns “The system cannot find the file specified” This message is not very helpful. This message is not very helpful. To identify the exact error, we must review the To identify the exact error, we must review the

SqlstpN.log on both nodes (because the failure SqlstpN.log on both nodes (because the failure occurred on both nodes)occurred on both nodes)

Let us assume that SqlstpN.log on both nodes have the Let us assume that SqlstpN.log on both nodes have the following similar error footprintfollowing similar error footprint

19:18:32 [DlgVirtServer]19:18:32 [DlgVirtServer]

19:18:32 Result = 119:18:32 Result = 1

19:18:32 VirtServerName = SQLVirtualName19:18:32 VirtServerName = SQLVirtualName

19:18:32 IpAddresses = X.X.X.X,255.255.255.0, PUBLIC (Upper port)19:18:32 IpAddresses = X.X.X.X,255.255.255.0, PUBLIC (Upper port)

19:18:32 ShowDlgVirtualServer returned: -119:18:32 ShowDlgVirtualServer returned: -1

19:18:32 ShowDlgVirtualServer: GetLastError returned: 8719:18:32 ShowDlgVirtualServer: GetLastError returned: 87

19:18:32 The parameter is incorrect19:18:32 The parameter is incorrect

18


Example 1 (continued)Example 1 (continued) This shows that the unattended setup failed on This shows that the unattended setup failed on

the nodes with error “87 - The parameter is the nodes with error “87 - The parameter is incorrect” incorrect”

This error message occurs if any of the cluster This error message occurs if any of the cluster resources have special charactersresources have special characters

Notice that the name of the public network Notice that the name of the public network connection, “PUBLIC (Upper port)”, has the connection, “PUBLIC (Upper port)”, has the special character ‘(‘ and ‘)’special character ‘(‘ and ‘)’

Removing the special characters will resolve the Removing the special characters will resolve the issueissue

This is also documented in the Microsoft This is also documented in the Microsoft Knowledge Base article:Knowledge Base article:302491, “302491, “Setup May Fail to Perform Required Operations on the ClustSetup May Fail to Perform Required Operations on the Cluster Nodes When Special Characters are Used in the Resourcer Nodes When Special Characters are Used in the Resource Namee Name””

http://support.microsoft.com/?kbid=302491



19


Example 2Example 2 Lets review another virtual server setup that failed with the Lets review another virtual server setup that failed with the

same error message:same error message:”Setup failed to perform required operations on the cluster nodes””Setup failed to perform required operations on the cluster nodes”

As in Example 1, open Sqlstp.log on the node where the As in Example 1, open Sqlstp.log on the node where the virtual server setup was started and search for the line:virtual server setup was started and search for the line:“Setup is performing required operations on cluster nodes. This may take a few “Setup is performing required operations on cluster nodes. This may take a few minutes...”minutes...”

Assume this is the error footprint in Sqlstp.log:Assume this is the error footprint in Sqlstp.log:14:51:37Setup is performing required operations on cluster nodes. This 14:51:37Setup is performing required operations on cluster nodes. This

may take a few minutes...may take a few minutes...14:51:37 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\14:51:37 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\

remsetup.iniremsetup.ini15:04:56 Process Exit Code: (2) The system cannot find the file specified.15:04:56 Process Exit Code: (2) The system cannot find the file specified.15:04:56 Begin Action : GetRemsetupRetCode15:04:56 Begin Action : GetRemsetupRetCode15:04:56 Installation return status on Node1 : 015:04:56 Installation return status on Node1 : 015:04:56 Installation return status on Node2 : 215:04:56 Installation return status on Node2 : 2

Note: Installation return status code on Node1 is 0 (which means success) Note: Installation return status code on Node1 is 0 (which means success) and on Node2 is 2 (indicating failure). To identify the exact error, review the and on Node2 is 2 (indicating failure). To identify the exact error, review the SqlstpN.log on Node2 (because the failure occurred on Node2). SqlstpN.log SqlstpN.log on Node2 (because the failure occurred on Node2). SqlstpN.log on Node1 should indicate “Installation Succeeded.”on Node1 should indicate “Installation Succeeded.”

20


Example 2 (continued)Example 2 (continued) Assume this is the error footprint in SqlstpN.log on Node2:Assume this is the error footprint in SqlstpN.log on Node2:

15:04:21 ShowDlgInstanceName: GetLastError returned: 5004415:04:21 ShowDlgInstanceName: GetLastError returned: 5004415:04:21 End Action DialogShowSdInstanceName15:04:21 End Action DialogShowSdInstanceName15:04:21 End Action ShowDialogs15:04:21 End Action ShowDialogs15:04:21 Action CleanUpInstall:15:04:21 Action CleanUpInstall:15:04:21 StatsGenerate returned: 215:04:21 StatsGenerate returned: 215:04:21 StatsGenerate 15:04:21 StatsGenerate

(0x0,0x1,0xf00000,0x300,1033,0,0x0,0x1000000a,0,0,0(0x0,0x1,0xf00000,0x300,1033,0,0x0,0x1000000a,0,0,015:04:21 StatsGenerate -1,Administrator)15:04:21 StatsGenerate -1,Administrator)15:04:21 Installation Failed.15:04:21 Installation Failed.

Now we know that the unattended setup failed on Node2 Now we know that the unattended setup failed on Node2 with the error 50044. Unlike the last error message, this one with the error 50044. Unlike the last error message, this one is not very intuitive. is not very intuitive.

Next, search for this error in the Microsoft Knowledge BaseNext, search for this error in the Microsoft Knowledge Base Visit Visit http://support.microsoft.comhttp://support.microsoft.com and then click “Search the and then click “Search the

Knowledge Base.” Select “SQL Server” as the Microsoft Knowledge Base.” Select “SQL Server” as the Microsoft product and type “GetLastError returned: 50044” in the Search product and type “GetLastError returned: 50044” in the Search field. This will return the article:field. This will return the article:318672318672, “Error Message: Setup failed to perform the required operation , “Error Message: Setup failed to perform the required operation on the cluster nodes”on the cluster nodes”

http://support.microsoft.com/

http://support.microsoft.com/?scid=318672

21

Troubleshooting Virtual Server Troubleshooting Virtual Server Setup FailureSetup Failure (8) (8)

Example 3Example 3 Lets review a virtual server setup that failed with the Lets review a virtual server setup that failed with the

following error message following error message

An error occurred while creating virtual server resources for clustering. Setup An error occurred while creating virtual server resources for clustering. Setup

could not connect to the database to update cluster-specific information in the could not connect to the database to update cluster-specific information in the

system tables.system tables.

This error indicates that the failure occurred when the virtual This error indicates that the failure occurred when the virtual server resources were createdserver resources were created

Reviewing Sqlstp.log will indicate success (result code 0) on all Reviewing Sqlstp.log will indicate success (result code 0) on all cluster nodescluster nodes

14:54:44 Installation return status on Node1 : 014:54:44 Installation return status on Node1 : 0

14:54:44 Installation return status on Node2 : 014:54:44 Installation return status on Node2 : 0 SqlstpN.log on all nodes will indicate “Installation succeeded”SqlstpN.log on all nodes will indicate “Installation succeeded” Note that the setup failed with error:Note that the setup failed with error:

“Setup could not connect to the database to update cluster-specific information “Setup could not connect to the database to update cluster-specific information in the system tables”in the system tables”

22


Example 3 (continued)Example 3 (continued) After the virtual resources for SQL Server are created, setup After the virtual resources for SQL Server are created, setup

makes an ODBC connection to the SQL Server to update makes an ODBC connection to the SQL Server to update cluster-specific information in the system tablescluster-specific information in the system tables If it cannot make a connection, it fails with this error If it cannot make a connection, it fails with this error

messagemessage The root cause for the above error was The root cause for the above error was improper name improper name

resolutionresolution In all cases, you can run the setup successfully after fixing In all cases, you can run the setup successfully after fixing

the name resolution issuethe name resolution issue

23


Example 3 (continued)Example 3 (continued) Verify the following on Verify the following on bothboth nodes : nodes :

Ping by name (cluster node names, cluster name, and Ping by name (cluster node names, cluster name, and SQL Server virtual name)SQL Server virtual name)

Ping by IP address (node IP addresses, cluster IP Ping by IP address (node IP addresses, cluster IP address, and SQL Server IP address)address, and SQL Server IP address)

Verify the result of the pingVerify the result of the ping Verify that the results are correct and as expectedVerify that the results are correct and as expected For example, when you ping by the cluster name, For example, when you ping by the cluster name,

make sure your reply is from the correct IP addressmake sure your reply is from the correct IP address Verify how much time it takes for the ping to replyVerify how much time it takes for the ping to reply

Sometimes, because of name resolution problems, a Sometimes, because of name resolution problems, a ping takes a long time to return a successful echoping takes a long time to return a successful echo

If the ping takes a long time, you can temporarily If the ping takes a long time, you can temporarily add host file entries on both nodes of the cluster add host file entries on both nodes of the cluster and then see if the ping replies immediatelyand then see if the ping replies immediately

24

Troubleshooting Virtual Server Troubleshooting Virtual Server Service Pack Setup FailuresService Pack Setup Failures The basic steps for troubleshooting a virtual server The basic steps for troubleshooting a virtual server

service pack setup failure are similar to the steps for service pack setup failure are similar to the steps for troubleshooting a virtual server setup failuretroubleshooting a virtual server setup failure

Instead of reviewing Sqlstp.log for service pack Instead of reviewing Sqlstp.log for service pack failures on virtual SQL Server, review Sqlsp.log file failures on virtual SQL Server, review Sqlsp.log file on the node where the service pack installation was on the node where the service pack installation was startedstarted

After you identify where the service pack setup After you identify where the service pack setup failed, review the appropriate service pack setup file failed, review the appropriate service pack setup file (SqlspN.log) to find the exact error message(SqlspN.log) to find the exact error message

Use the keywords in the error message to perform a Use the keywords in the error message to perform a search in the Microsoft Knowledge Base to find more search in the Microsoft Knowledge Base to find more detailed information about the error, and the solution detailed information about the error, and the solution to the problemto the problem

25

Troubleshooting Virtual Server Troubleshooting Virtual Server Service Pack Setup Failures Service Pack Setup Failures (2)(2)

Example 4Example 4 Lets review a virtual server service pack setup Lets review a virtual server service pack setup

that failed with the following error message:that failed with the following error message:

Setup failed to perform required operations on the cluster nodesSetup failed to perform required operations on the cluster nodes

Notice that this is the same error message that Notice that this is the same error message that we saw in Examples 1 and 2we saw in Examples 1 and 2

As before, open the file Sqlsp.log on the node As before, open the file Sqlsp.log on the node where you ran the service pack setup and where you ran the service pack setup and

search for the line:search for the line: “Setup is performing required operations on cluster nodes. This “Setup is performing required operations on cluster nodes. This may take a few minutes...”may take a few minutes...”

26


Example 4 (continued)Example 4 (continued) Lets assume this is the error footprint in Lets assume this is the error footprint in

Sqlsp.log:Sqlsp.log:12:54:42 Setup is performing required operations on cluster nodes. 12:54:42 Setup is performing required operations on cluster nodes.

This may take a few minutes...This may take a few minutes...

12:54:42 "C:\DOCUME~1\SQLExec\LOCALS~1\Temp\1\SqlSetup\12:54:42 "C:\DOCUME~1\SQLExec\LOCALS~1\Temp\1\SqlSetup\Bin\remsetup.exe" C:\WINNT\remsetup.iniBin\remsetup.exe" C:\WINNT\remsetup.ini

13:03:08 Process Exit Code: (3010) The requested operation is 13:03:08 Process Exit Code: (3010) The requested operation is successful. Changes will not be effective until the system is successful. Changes will not be effective until the system is rebooted.rebooted.

13:03:08 Begin Action : GetRemsetupRetCode13:03:08 Begin Action : GetRemsetupRetCode

13:03:08 Installation return status on Node1 : 301013:03:08 Installation return status on Node1 : 3010

13:03:08 Installation return status on Node2 : -113:03:08 Installation return status on Node2 : -1

13:03:08 End Action : GetRemsetupRetCode13:03:08 End Action : GetRemsetupRetCode

13:03:08 End Action : GetRemsetupRetCode13:03:08 End Action : GetRemsetupRetCode

#### SQL Server Remote Setup - Start Time mm/dd/yy 12:54:42 ######## SQL Server Remote Setup - Start Time mm/dd/yy 12:54:42 ####

Server ‘Node2' not found on the network (53).Server ‘Node2' not found on the network (53).

27


Example 4 (continued)Example 4 (continued) Note : Installation return status code on Node1 is 3010 (The Note : Installation return status code on Node1 is 3010 (The

requested operation is successful. Changes will not be effective requested operation is successful. Changes will not be effective until the system is rebooted) and result code on Node2 is -1 until the system is rebooted) and result code on Node2 is -1 (general failure). sqlspN.log on Node1 will indicate “Installation (general failure). sqlspN.log on Node1 will indicate “Installation Succeeded - Reboot Required”.Succeeded - Reboot Required”.

In this case, no setup files were created on Node2In this case, no setup files were created on Node2 Notice the error Notice the error “Server ‘Node2' not found on the network (53).” “Server ‘Node2' not found on the network (53).” in the Sqlsp.log in the Sqlsp.log

filefile

net helpmsg 53net helpmsg 53

returns “The network path was not found.”returns “The network path was not found.”

This indicates network issuesThis indicates network issues To resolve this, fix the network issue first, and then review the To resolve this, fix the network issue first, and then review the

Windows NT® event logs and cluster logs to make sure there are Windows NT® event logs and cluster logs to make sure there are no errorsno errors

Make sure that you can:Make sure that you can: Ping each node by names and IP addressPing each node by names and IP address Connect to the ADMIN$ share on node2 from node1 and vice-versaConnect to the ADMIN$ share on node2 from node1 and vice-versa

After you fix the network issues, re-run the service pack setupAfter you fix the network issues, re-run the service pack setup

28


Example 5Example 5 Lets review a virtual server service pack setup that failed with the Lets review a virtual server service pack setup that failed with the

following error message:following error message:An error occurred while creating virtual server resources for clustering. An error occurred while creating virtual server resources for clustering.

Cannot create a file when that file already exists.Cannot create a file when that file already exists. This error indicates that the failure occurred when the virtual This error indicates that the failure occurred when the virtual

server resources were createdserver resources were created For more details, review Sqlsp.log and Sqlclstr.log on the For more details, review Sqlsp.log and Sqlclstr.log on the

node where the service pack setup was startednode where the service pack setup was started Assume that Sqlsp.log has the following error footprint:Assume that Sqlsp.log has the following error footprint:

20:22:25 Begin Action : CreateVirtualServerResources20:22:25 Begin Action : CreateVirtualServerResources

20:22:25 Begin: BeforeFTS()20:22:25 Begin: BeforeFTS()

20:22:25 Begin Action : EnumerateNodes20:22:25 Begin Action : EnumerateNodes

20:22:25 End Action : EnumerateNodes20:22:25 End Action : EnumerateNodes

20:22:25 End: AfterFTS()20:22:25 End: AfterFTS()

20:22:35 End Action : CreateVirtualServerResources20:22:35 End Action : CreateVirtualServerResources

20:22:35 CreateVirtualServerResources returned: 18320:22:35 CreateVirtualServerResources returned: 183

20:28:38 Begin Action : ClusterErrorCleanup20:28:38 Begin Action : ClusterErrorCleanup

29


Example 5 (continued)Example 5 (continued) Assume that Sqlclstr.log has the following error footprint:Assume that Sqlclstr.log has the following error footprint:

cConnectString="ODBC;DSN='';DRIVER={SQL cConnectString="ODBC;DSN='';DRIVER={SQL Server};SERVER=VSQL;DATABASE=master;Trusted_Connection=yes"Server};SERVER=VSQL;DATABASE=master;Trusted_Connection=yes"

Database 'pubs' cannot be opened because it is offlineDatabase 'pubs' cannot be opened because it is offline

[sqlclusterSetup.cpp:1295] : 183 (0xb7): ~~~ DoClusterSetupWork[sqlclusterSetup.cpp:1295] : 183 (0xb7): ~~~ DoClusterSetupWork

During the virtual server service pack installation, setup During the virtual server service pack installation, setup queries the databases to make sure that all the database files queries the databases to make sure that all the database files are on disk resources that have the correct dependencies, are on disk resources that have the correct dependencies, and the virtual SQL Server resource, which is necessary for and the virtual SQL Server resource, which is necessary for the failover supportthe failover support When a database is offline, setup cannot access the When a database is offline, setup cannot access the

database and fails with the above messagedatabase and fails with the above message To work around this problem, bring the inaccessible database To work around this problem, bring the inaccessible database

online, and then rerun the service pack setuponline, and then rerun the service pack setup For more details, in the Knowledge base, search for For more details, in the Knowledge base, search for

“[sqlclusterSetup.cpp:1295] : 183” to return the article:“[sqlclusterSetup.cpp:1295] : 183” to return the article:320524320524, “SQL Server Service Pack 2 Setup May Stop Responding in a , “SQL Server Service Pack 2 Setup May Stop Responding in a Windows Clustering Environment If There Is an Offline Database”Windows Clustering Environment If There Is an Offline Database”


30

SQL Server 2000 Service Pack 3 SQL Server 2000 Service Pack 3 Pre-Installation Checklist for SQL Pre-Installation Checklist for SQL Server 2000 Virtual ServerServer 2000 Virtual Server Service Pack 3 (SP3) for SQL Server 2000 is a major service Service Pack 3 (SP3) for SQL Server 2000 is a major service

pack and it should be thoroughly tested in a test environment pack and it should be thoroughly tested in a test environment firstfirst The basic testing goal is to make sure your applications are The basic testing goal is to make sure your applications are

working correctly with the changes introduced by SP3working correctly with the changes introduced by SP3 To make sure your SP3 setup is successful, complete the To make sure your SP3 setup is successful, complete the

following pre-installation checklistfollowing pre-installation checklist

ChecklistChecklist

1.1. Review the Readme file for SP3 and note any areas Review the Readme file for SP3 and note any areas that could affect your production environment, and that could affect your production environment, and then test these before proceedingthen test these before proceeding

2.2. Run DBCC checkdb against all your databases Run DBCC checkdb against all your databases (system and user databases)(system and user databases) Resolve any unexpected errors before continuingResolve any unexpected errors before continuing

31

SQL Server 2000 Service Pack 3 SQL Server 2000 Service Pack 3 Pre-Installation Checklist for SQL Pre-Installation Checklist for SQL Server 2000 Virtual Server Server 2000 Virtual Server (2)(2)

3.3. Make sure that you have a recent and accurate Make sure that you have a recent and accurate backup of your system and user databases, and your backup of your system and user databases, and your full text catalogsfull text catalogs

4.4. Stop all monitoring software services (on all nodes Stop all monitoring software services (on all nodes that are part of the virtual SQL Server) such as that are part of the virtual SQL Server) such as Microsoft Operation Manager (MOM) and any third-Microsoft Operation Manager (MOM) and any third-party products that provide similar functionalityparty products that provide similar functionality Set this type of software for manual startup and restart the Set this type of software for manual startup and restart the

servers before you install SQL Server 2000 SP3 servers before you install SQL Server 2000 SP3

5.5. Verify that all the resources in the SQL Server group Verify that all the resources in the SQL Server group that contain the instance of SQL Server come online that contain the instance of SQL Server come online on all nodes of the clusteron all nodes of the cluster If any resource does not come online, fix that before you If any resource does not come online, fix that before you

upgrade to SP3upgrade to SP3

32

SQL Server 2000 Service Pack 3 Pre-SQL Server 2000 Service Pack 3 Pre-Installation Checklist for SQL Server Installation Checklist for SQL Server 2000 Virtual Server 2000 Virtual Server (3)(3)

6.6. Verify that there are no dependencies other than Verify that there are no dependencies other than those created by the SQL Server setup on any SQL those created by the SQL Server setup on any SQL Server cluster resourcesServer cluster resources Resources such as file shares, FTP servers, and Microsoft Resources such as file shares, FTP servers, and Microsoft

Internet Information Services (IIS) servers must always have Internet Information Services (IIS) servers must always have a unique network name and an IP address resourcea unique network name and an IP address resource

Remove any such non-default dependencies before you Remove any such non-default dependencies before you install SQL Server 2000 SP3install SQL Server 2000 SP3

7.7. While performing the cluster portion of SQL Server While performing the cluster portion of SQL Server 2000 SP3, the setup will reset all cluster resources to 2000 SP3, the setup will reset all cluster resources to the default properties for all resources in the group, the default properties for all resources in the group, whether they are related to SQL Server or notwhether they are related to SQL Server or not Make sure to note all settings before you install SQL Server Make sure to note all settings before you install SQL Server

2000 SP32000 SP3

33

SQL Server 2000 Service Pack 3 SQL Server 2000 Service Pack 3 Pre-Installation Checklist for SQL Pre-Installation Checklist for SQL Server 2000 Virtual Server Server 2000 Virtual Server (4)(4)

8.8. SP3 installation will fail if the “Unsigned non-driver installation SP3 installation will fail if the “Unsigned non-driver installation behavior local security policy for Windows 2000” was set to "Do behavior local security policy for Windows 2000” was set to "Do not allow installation”not allow installation” Review the Readme file for more informationReview the Readme file for more information

9.9. Set unnecessary services for manual startup on all nodes of Set unnecessary services for manual startup on all nodes of cluster and restart nodes before upgradingcluster and restart nodes before upgrading For a list of services that should be left running, see the For a list of services that should be left running, see the

“Prerequisites” section of the Microsoft white paper “SQL Server “Prerequisites” section of the Microsoft white paper “SQL Server 2000 Failover Clustering”2000 Failover Clustering”

Log on all nodes of the cluster using the startup account of the Log on all nodes of the cluster using the startup account of the virtual SQL Server servicevirtual SQL Server service

10.10. Set MASTER, MODEL, and MSDB databases to auto grow on Set MASTER, MODEL, and MSDB databases to auto grow on Data and log fileData and log file

11.11. Remove Read Only option from user databases and restrict Remove Read Only option from user databases and restrict access to DBOaccess to DBO

12.12. Disable any agent jobs that might interfere with the upgradeDisable any agent jobs that might interfere with the upgrade

34

Additional ResourcesAdditional Resources Microsoft White Paper - SQL Server 2000 Failover Microsoft White Paper - SQL Server 2000 Failover

Clustering Clustering http://www.microsoft.com/SQL/techinfo/administration/2000/failovercluster.ahttp://www.microsoft.com/SQL/techinfo/administration/2000/failovercluster.aspsp

Microsoft Knowledge Base ArticlesMicrosoft Knowledge Base Articles302491302491, “Setup May Fail to Perform Required Operations on the Cluster , “Setup May Fail to Perform Required Operations on the Cluster

Nodes When Special Characters are Used in the Resource Name”Nodes When Special Characters are Used in the Resource Name”

318672318672, “Error Message: "Setup failed to perform the required operation on , “Error Message: "Setup failed to perform the required operation on the cluster nodes“”the cluster nodes“”

320524320524, “SQL Server Service Pack 2 Setup May Stop Responding in a , “SQL Server Service Pack 2 Setup May Stop Responding in a Windows Clustering Environment If There Is an Offline Database”Windows Clustering Environment If There Is an Offline Database”

254321254321, “INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings”, “INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings”

811168811168, “INF: SQL Server 2000 Service Pack 3 Pre-Installation Checklist for , “INF: SQL Server 2000 Service Pack 3 Pre-Installation Checklist for SQL Server 2000 Virtual Server for Failover Clustering”SQL Server 2000 Virtual Server for Failover Clustering”

SQL Server 2000 Books Online topic "Failover SQL Server 2000 Books Online topic "Failover Clustering”Clustering”

http://www.microsoft.com/SQL/techinfo/administration/2000/failovercluster.asp

http://www.microsoft.com/SQL/techinfo/administration/2000/failovercluster.asp






Troubleshooting SQL Server 2000 Virtual Server /Service Pack ...

Documents

Transcript of Troubleshooting SQL Server 2000 Virtual Server /Service Pack ...