Failed To Write Sector 12 Error 170
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Windows 2003 Cluster service not starting Windows Server > High Availability (Clustering) Question 0 Sign in to vote I have a 2 node active/Passive cluster. Unfortunately active node rebooted unexpectedly and it is not coming up due to some hardware issues. I cannot start the cluster service on node2 it is showing below event error. I understand the quorum disk is not started in node2, that creating this issue. Please help on this. Thanks in advance. Event Type: Error Event Source: ClusDisk Event Category: None Event ID: 1209 Date: 11/7/2011 Time: 11:17:51 PM User: N/A Computer: CLNODE2 Description: Cluster service is requesting a bus reset for device \Device\ClusDisk0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Monday, November 07, 2011 5:58 PM Reply | Quote Answers 0 Sign in to vote The error 170 means "The requested resource is in use." This suggests that the other node has a reservation on the quorum disk. If this issue is occurring, it suggests that you have a network communications issue between the cluster nodes as the nodes are fighting with each other to gain access to the quorum. This quorum arbitration should only occur in the event of a network communications failure between the nodes. If all cluster resources are healthy and online on Node1, Iwould suggest disabling cluster service on the Node2 and investigate the network communications problems between the nodes. If your Node1 is dead/dying, I would disable cluster service on this node and reboot it so it stops arbitrating for the quorum. Hope this helps.Visit my blog about multi-site clustering - http://msmvps.com/blogs/jtoner Proposed as answer by JohnTonerModerator Wednesday, November 09, 2011 2:16 PM Marked as answer by Vincent HuModerator Friday, December 09, 2011 10:42 AM Tuesday, November 08, 2011 2:01 PM Reply | Qu
doesn't agree with the solution, but I believe with the info below we're safe tell what's going on. In this particular scenario we've a Cluster Windows Server 2003 SP environment (2 nodes) and one of these servers cannot start up the service "Cluster Service" . When we try startup the following message is displayed: If we check the Event Viewer we will see the ID 1209: Event Type: Error Event Source: ClusDisk Event Category: None Event ID: 1209 Date: 8/5/2011 Time: 4:02:44 PM Computer: SRVNAME Description: Cluster service is requesting a https://social.technet.microsoft.com/Forums/windowsserver/en-US/2e8ab7e6-344c-4723-b4fe-e9ef76486949/windows-2003-cluster-service-not-starting?forum=winserverClustering bus reset for device \Device\ClusDisk0.Let's staring take a look under Cluster Environment:OS Version and SP: Windows Server 2003 SP2 R2 ENTHostname: SRVNAME01 / SRVNAME02Is Virtual (Y/N): NRoles: Cluster Print ServerDomain: cro.local Additional Features:==================Antivirus: SEP 11.0.6200The Cluster environment contains 3 LUNs (Disk Quorum, Disk S: e Disk P: )For more tests we've added a LUN number 4 (named disk N:)Important TIP: The Disks Q: http://panerarichang.blogspot.com/2011/08/cannot-startup-cluster-service.html , S: , P: were online under Disk Management, however unavailable through Explorer or Command Prompt. However the Disk N: was totally perfect. We could read and write the information on the disk.Solution========== We tested startup the cluster service on both nodes, but it's doesn't worked. For troubleshooting we requested to customer shutdown the node2 - SRVNAME02. Based on Logs and symptom it's likely be a Storage Issue. Analyzing Cluster.log: 598:7f8.08/05[16:52:39.256](6522675) WARN [NM] Network 4e1a3d12-269a-4f33-a3f0-bf0393bf6d10 (Public) is up.598:3c8.08/05[16:52:39.256](6522676) WARN [NM] Network 88798bd5-4cef-4f45-a6a0-d6631a0e4fd3 (Private) is up.a68:dfc.08/05[16:54:31.912](000008) ERR Physical Disk
NOT come up! Discussion in 'SQL Server Clustering' started by pbertuzzi, Jul 1, 2004. pbertuzzi New Member Hi guys! I have the following scenario. 2 http://www.sql-server-performance.com/forum/threads/cluster-service-does-not-come-up.17273/ win2k adv servers with patches and a scsi storage connected to node1 and node2. All of the interfaces are properly configured and i can ping the other interefaces. There is an Active Directory server http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description installed in the network to work with the cluster only. Node1 and Node2 log ok to the Active Directory. To do that i created two accounts, node1 and node2 in the Active Directory failed to and put them in group Domain Users only. I also created the service account cluster in the Active Directory server and put it in groups Administrators and Domain Users. I turned off node 2 and installed cluster services in node1. The wizard does not finish succesfully. It opens up an error window with the message "The Clustering Service could not join an existing cluster and could not form failed to write a new cluster. The Clustering Service has terminated" What could be wrong? Note: after installing the Active Directory server I changed the ip address and noted that the server is a little bit slower when creating accounts or consulting them. thanks a lot for your help. Pablo pbertuzzi, Jul 1, 2004 #2 bradmcgehee New Member That's not a lot of information to go on. Have you checked the NT logs, and the clustering install log? These might provide better information. Did you follow all the steps in my article on clustering on this website? Is all of the hardware on the Microsoft HCL? Are all of the hardware drivers the most current? From node one, can you see the shared array? ----------------------------- Brad M. McGehee, MVP Webmaster SQL-Server-Performance.Com bradmcgehee, Jul 1, 2004 #2 pbertuzzi New Member Yeap, the hardware is in the HCL. The servers are DELL 2650 with Cluster SE400 and the array is DELL Powervault 200S. I can see the array from node1 and from node2 (with node1 turned off). I follow this linkhttp://www.microsoft.com/windows2000/techinfo/planning/server/clustersteps.asp and I also have read your documentation. Where can I find the logs you mention? Pablo. pbertuzzi, Jul 1, 2004 #2 bradmcgehee New Member
Français Deutsch 日本語 Español Help Video Screencast Help Windows System Error Codes (exit codes) Description Created: 28 Jan 2009 • Updated: 20 Dec 2010 | 9 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 Sidd +19 19 Votes Login to vote Tweet Application installation (legacy setup applications or Windows installer applications) sometimes fails without any error message. These tasks will return exit/error codes when log file is generated. The following script will help in getting the Exit/Error code of Application installation else on can get it from log file. Dim oShell, MyApp, i Set oShell = CreateObject("WScript.Shell") MyApp = """C:\MyApplication\Setup.exe"" /Q" i = 0 i = oShell.Run(MyApp, 1 ,True) WScript.Echo "Exit Code is: " & (i) Set oShell = Nothing Note: Use Silent switches according to the application. The table below describes system Exit/Error codes when a task is executed. The description of codes may help in identifying and troublshooting the issues. Code Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 Th