Problems Encountered in Deployment of Microsoft Lync server 2010.
Recently I had a chance to deploy Microsoft Lync Server 2010.
I encountered some errors during its installation.
I will list them down below.
With the topology published, and Local Configuration Store installed, I proceeded towards "Install or Update Lync Server System" => "Setup or Remove Lync Components"
The Setup or Remove Lync Components Makes necessary changes towards the deployment, as define them and publish them in Topology Builder.
As I ran the Setup or Remove Lync Components, It proceeded and came up with following.
Command execution failed: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
It is a problem that is caused by a port number that is being used by server and preventing Lync Server Websites to start.
In order to get past this error you must be able to start both the Lync Server Internal Website and Lync Server External Website.
So when providing ports in Topology Builder, always make sure that those ports are unique and not used by any other process. Conflicting of these ports causes Lync server websites prevent from starting.
Following command may help you if you want to find out if any of the ports are being used or not :
netstat -aon | find ":portnumber"
Also check information and bindings in inetmgr, if any of the websites are using that port.
Another error was caused while "Requesting and Assigning new certificates" from my internal CA(Certificate Authority).
System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
This is a problem caused by firewall, in my case.
Disable firewall, if any and then try connecting again, it will work for sure.
We have Microsoft Forefront Threat Management Gateway installed.
What I did was :
1. Open Forefront TMG.
2. Right Click Access Rule that deals with internal network traffic.
3. Configure RPC Protocol
4. Uncheck "Enforce strict RPC Compliance."
5. Click "Firewall Policy" then click "Edit system policy" in right hand pane.
6. Under Authentication Services, Click Active directory and uncheck "Enforce strict RPC Comliance."
7. Apply changes.
The above procedure must almost be same for Microsoft ISA Server too.
I encountered some errors during its installation.
I will list them down below.
With the topology published, and Local Configuration Store installed, I proceeded towards "Install or Update Lync Server System" => "Setup or Remove Lync Components"
The Setup or Remove Lync Components Makes necessary changes towards the deployment, as define them and publish them in Topology Builder.
As I ran the Setup or Remove Lync Components, It proceeded and came up with following.
Command execution failed: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
It is a problem that is caused by a port number that is being used by server and preventing Lync Server Websites to start.
In order to get past this error you must be able to start both the Lync Server Internal Website and Lync Server External Website.
So when providing ports in Topology Builder, always make sure that those ports are unique and not used by any other process. Conflicting of these ports causes Lync server websites prevent from starting.
Following command may help you if you want to find out if any of the ports are being used or not :
netstat -aon | find ":portnumber"
Also check information and bindings in inetmgr, if any of the websites are using that port.
Another error was caused while "Requesting and Assigning new certificates" from my internal CA(Certificate Authority).
System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
This is a problem caused by firewall, in my case.
Disable firewall, if any and then try connecting again, it will work for sure.
We have Microsoft Forefront Threat Management Gateway installed.
What I did was :
1. Open Forefront TMG.
2. Right Click Access Rule that deals with internal network traffic.
3. Configure RPC Protocol
4. Uncheck "Enforce strict RPC Compliance."
5. Click "Firewall Policy" then click "Edit system policy" in right hand pane.
6. Under Authentication Services, Click Active directory and uncheck "Enforce strict RPC Comliance."
7. Apply changes.
The above procedure must almost be same for Microsoft ISA Server too.
Labels: Microsoft
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home