DCOM was unable to communicate with the computer X.X.X.X using any of the configured protocols; requested by PID
The above issue occurs when one server is not able to communicate with the other server using hostname or improper DNS settings . I was able to solve the issue by editing the hosts file and adding the below entry
“X.X.X.X HOSTNAME of Other Server”
Where X.X.X.X is the IP address of the other server
a) Minimum three servers required, one will be Active Directory and the other two acting as failover Cluster nodes.
b) Two NICs are required on both the database nodes one for Cluster and other for heartbeat
c) Activate OS license on the Active Directory Server before Active directory is installed as active directory does not allow activating license once it is installed.
d) Apply windows updates on all the three servers. Try keeping the windows updates level same on both the nodes as it can cause some issues while validating the failover cluster
e) 2 LUNS should be assigned on both the Nodes; the LUN with lower size is used as the Quorum Disk automatically by the failover Cluster.
f) Format the LUNs and make it Online only on one Server.
g) Install the failover over Cluster feature from add/remove roles and features on both the nodes
h) Install donet framework 3.5 on both the nodes. Without Dotnet framework 3.5, SQL Installation gives error.
1) Install Active Directory on One Server. Set the Hostname.
2) On the Active Directory Server , In Active Directory Users and Computers , Right Click Computers , New computer, and Create New Computer. View Advanced , Features , Right Click Computers, Security Tab and give administrator create Computer Rights.
3) Rename the NICs on both the database nodes as Public and Private
4) On the two database nodes in Public LAN , For DNS Server , Add the IP of Active Directory Server , Enable NetBIOS Over TCP/IP , In Private LAN Disable “Enable NetBIOS Over TCP/IP”
5) On both the Nodes in hosts file add ” ACTIVE DIRECTORY HOSTNAME IP ADD of AD ”
6) Make both the servers member of domain controllers, reboot both the servers and Active Directory server.
7) ON both the Database Servers Install Failover Cluster Service Role .
8) Login to one DB Server with Administrator user as a member of domain controller , goto failover cluster manager => validate a configuration => Next => Browse => advanced => find now and select DB1 and DB2 => next and run the test with “Run all the tests ( recommended ) option “ .
9) Once the test passes, Click create a cluster, Next , Access Point for Administering the Cluster , and set the Virtual hostname and Virtual IP of OS Cluster and complete the cluster wizard . That’s it you have completed the OS cluster. Now next you need to install the MSSQL cluster.
10) Run the MSSQL 2014 setup on DB1 node and select the option “ New SQL Server Failover Cluster Installation” and complete the setup on one node
11) Run the MSSQL 2014 setup on DB2 Node and select the option “Add node to a SQL Server Failover Cluster” and complete the setup on the second node. That’s it you have completed MSSQL 2014 failover Cluster setup. Happy Learning
Add binding for the PleskControlPanel site 127.0.0.1:8443. Open IIS->PleskControlPanel->Bindings and add: https 8443 127.0.0.1
go to following directory
run the following command
-uadmin -pMYSQL_ADMIN_PASSWORD -V
Unable to access Webadmin tool for MSSQL: Could not load type ‘ASPEnterpriseManager.ConnectionString
Bin folder is missing in the
- Download the
- Repair the mssql-webadmin.msi installation. Run Windows command line as Administrator and launch the command:
msiexec /fvocmus C:\mssql-webadmin.msi /L*V "c:\mssql-webadmin.log"
c:\mssql-webadmin.log if the installation fails.
Please refer the following URL to find out the correct Gold rate in Nasik
Copy the folder “SXS” from the OS installation Disk to the server drive “C or D”
Open server manager >> select feature “asp.net3.5” >> click next >> select the alter native source file “C:\sxs” >> click next.
Asp.net 3.5 will be installed.
Stop the VM >> open .vmx file of the VM and add following links at the end of vmx file.
Hypervisor.cpuid.v0 = “FALSE”
mce.enable = “TRUE”
save the vmx file and star the VM
add the following entry is host file