Pugazhnetwork

 A specified authentication package is unknown reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v AllowCustomSSPsAPs 0 Blocks custom SSPs/APs from loading 1 Allows custom SSPs/APs to load  

If a new cluster is being created, and multiple nodes are specified in the Create Cluster Wizard, the creation process fails due to a timeout. Creation of a single node cluster, on the other hand, using any of the servers that will participate in the cluster will succeed. If you try to then add an additional node using the Add Node Wizard, the process will time out. If the Create Cluster Wizard is used to create the cluster, the following output is displayed: Configuring node ‘name’ ---------------------------------------  12% Validating cluster state on node ‘name’.  25% Getting current node membership of cluster ‘name’.  37% Adding node ‘name’ to Cluster configuration data.  50% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node ‘name’.  62% Validating installation of the Cluster Disk Driver on node ‘name’.  75% Configuring Cluster Service on node ‘name’.  87% Starting Cluster Service on node ‘name...

Windows Server Failover Cluster Log Generating the Cluster.log   Get-ClusterLog   =>  The output looks like for all node in the cluster:   The Cluster.log files can be found in the  \cluster\reports  directory (usually c:\windows\cluster\Reports) on each node.  You can use the  –Destination  parameter to cause the files to be copied to a specified directory with the Server’s name The time stamps default to UTC (which some people call GMT) For instance, if you are in that time zone and a problem occurred at 1:38pm (13:38), UTC time stamp in the cluster log would be (21:38) The  –UseLocalTime  parameter for  Get-ClusterLog  causes the cluster.log to write timestamps that are already adjusted for the server’s time zone instead of using UTC Tip:  The sections of the cluster.log are encased in [===   ===], which makes it easy to navigate down the log to each...

The List Running Processes test fails when you run the Failover Cluster Validation Wizard on a Windows 7-based or Windows Server 2008 R2-based cluster node Symptoms Assume that you configure a Windows Server 2008 R2-based computer as a failover cluster node locally, or you configure it from a Windows 7-based computer by using the Remote Server Administration Tools feature. You run the Failover Cluster Validation Wizard on the computer. In this situation, the List Running Processes test fails. Additionally, you receive the following error message:  Gathering Running Processes for  node name An error occurred while executing the test. There was an error getting information about the running processes on the nodes. There was an error retrieving information about the Processes from node ' node name '. Not found Cause This issue occurs because some running processes are ended on the cluster node during the List Running Processes test. Res...

Quick cheat sheet for port numbers used by SQL Server services or services that SQL Server may depend on: 21 TCP FTP (replication) 80 TCP HTTP endpoints, Reporting Services, HTTP replication 135 TCP & UDP RPC, WMI, MSDTC, SQL Agent file copy, and TSQL Debugger (RPC used for multiple purposes including SSIS and clustering.) 137 UDP File & Print Sharing (replication) and Cluster Admin 138 UDP File & Print Sharing (replication) 139 TCP FileStream and NetBIOS Session Service (clustering) 443 TCP HTTPS endpoints and Reporting Services 445 TCP & UDP FileStream, SMB (clustering), and File & Print Sharing 500 UDP IPSec 860 TCP iSCSI 1024-5000 TCP Original dynamic ports for named instances. (WinSock standard.)(See ports 49152-65535.) The DoD Database STIG requires static ports. 1433 TCP SQL Server database engine 1434 TCP & UDP SQL Server database engine, DAC, and SQL Server's "Browse" button. 2382 UDP Analysis Serviceswhen using dynamic po...