This is the second section of dealing with errors running the Windows 2008 cluster validation test with an EMC Symmetrix. The next errors is: -
Validate SCSI-3 Persistent Reservation
Validate that storage supports the SCSI-3 Persistent Reservation commands.
Validating Cluster Disk 0 for Persistent Reservation support
Registering PR key for cluster disk 0 from node servername.domain.com
Failed to Register PR key for cluster disk 0 from node servername.domain.com status 1
Cluster Disk 0 does not support Persistent Reservation
This post has moved - http://iunite.com.au/wp/blog/index.php/2011/09/cluster-disk-0-does-not-support-persistent-reservation-error-with-windows-2008-and-symmetrix/
Thursday, October 15, 2009
Cluster Disk 0 does not support Persistent Reservation error with Windows 2008 and Symmetrix
Posted at
12:04 PM
0
comments
Labels: Windows
Saturday, October 10, 2009
MPIO errors, Windows 2008 cluster validation test failing and EMC Symmetrix
If you have ever tried to configure a Windows 2008 cluster using an EMC Symmetrix then you have probably come across this issue. If not then you might want to read on.
Windows 2008 uses Persistent SCSI reservations. The SCSI Reserve command and the SCSI Persistent Reserve command are specified by the SCSI standards. Servers can use these commands to prevent HBA ports in other servers from accessing the LUN.
This post has moved - http://iunite.com.au/wp/blog/index.php/2011/09/mpio-errors-windows-2008-cluster-validation-test-failing-and-emc-symmetrix/
Posted at
11:14 AM
0
comments
Labels: Windows
Thursday, October 8, 2009
How to Create an ODBC Connection for 32-bit application on 64-bit Windows
Just a reminder post really. Had a colleague today that was installing a 32-bit application on Windows 2008 x64 that required an ODBC connection. The trouble with this is that the default ODBC (Data Sources) under Administrative Tools opens the 64-bit driver version of the ODBC tool.
Therefore even though he had created the connections correctly the 32-bit application could not see them. To make things a little confusing 64-bit Windows versions install the 64-bit ODBC tool under C:\Windows\System32.
The 64-bit version is installed under C:\Windows\Syswow64\. Therefore this fix was to run the following command at the Run line: -
c:\windows\syswow64\odbcad32.exe
Posted at
10:25 PM
0
comments
Thursday, July 17, 2008
Video: Debugging a Windows Blue Screen of Death
Just came across this video today. Daniel talks about why BSOD (Blue screen of death) occur and shows a real world debugging example showing how to diagnose and debug issues. It's a good addition to my other blogs on Windows troubleshooting.
http://channel9.msdn.com/posts/Dan/Daniel-Pearson-Debugging-a-Windows-Blue-Screen-of-Death/
Posted at
2:01 PM
0
comments
Labels: Windows
Thursday, July 10, 2008
Windows System Hang Troubleshooting – Bits and pieces
So what do you do when a Windows system hangs? Well let’s be honest. Normally a reboot will fix this. However what do you do if the reboot is only a temporary solution?
This post has moved - http://iunite.com.au/wp/blog/index.php/2011/09/windows-system-hang-troubleshooting-bits-and-pieces-2/
Posted at
2:46 PM
0
comments
Wednesday, July 9, 2008
Cannot open Local or Group Security Policy Console
However, when navigating to Security Options under Local Computer Policy >Windows Settings > Security Settings > Local Policies, the following error was generated: -
"The Group Policy security settings that apply to this machine could not be determined. The error returned when trying to retrieve these settings from the local security policy database (%windir%\security\database\secedit.sdb) was: The parameter is incorrect."
We also had the application vendor contact us stating that the Windows Sharepoint Services sites were down. Checking the event log showed many errors. The vendor and my colleague thought that the vendor had corrupted to WSS database and were considering a re-install.
Using standard troubleshooting techniques I started by checking what was last changed. So I opened the Local Security Policy Console via Administrative Tools and wow I received the security policy database error.
I opened a command prompt and browsed to C:\Windows\Security\database. I then backed up the C:\Windows\Security folder. I then tried to check the SDB file state using esentutl.exe. Those familiar with Exchange will understand this fully.
i.e. esentutl.exe /mh C:\Windows\Security\database\secedit.sdb
This showed that the database was in a clean shutdown state. I thought ok lets try to repair : -
i.e. esentutl /p secedit.sdb
esentutl /d secedit.sdb
After this I still had the same error. So I restored the backup copy of the C:\Windows\Security folder I made before I changed anything. I was then able to find mention of a registry key that could cause this issue. According to MS PSS when you change the NTLM setting this can write extra entries to the following registry key. If any entries other than “Default” and “Auth2” exist in this key it can generate this error. I there exported this key and deleted the extra two entries.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
Further Information
You cannot determine Group Policy security settings on a Windows Server 2003, Enterprise Edition-based computer
http://support.microsoft.com/kb/932461
Posted at
1:19 PM
1 comments
Labels: Windows
Friday, December 14, 2007
Analyse a Windows Blue Screen of Death!
This post has moved - http://iunite.com.au/wp/blog/index.php/2011/09/analyse-a-windows-blue-screen-of-death/
Posted at
1:56 PM
0
comments
Labels: Windows
Wednesday, December 12, 2007
How to use Subinacl.exe to assign permissions to manage services
This post has moved - http://iunite.com.au/wp/blog/index.php/2011/09/how-to-use-subinacl-exe-to-assign-permissions-to-manage-services/
Posted at
10:23 PM
3
comments
Labels: Windows