Today I had a bit of fun at a client where we did an insanely quick-and-dirty (totally and absolutely unrecommended) installation of CRM 2011. The tech installing CRM found that SharePoint was using port 80 on the same server and decided to run CRM on port 8500. Yesterday I did a bit of a cleanup of the installation which for me (and my non-IT-pro ways) meant installing Update Rollup 3 and doing a reboot. Today I opened up the server to take a peek at what was going on and found that the webservice wasn’t running and I couldn’t reach my organizations.
Starting up the webservice resulted in an “Error 0×80070020“
The tech article mentioned that it had to do with the port being in use so I did a netstat -aon | find “:8500″ to see which process was running on that port. After adding PID to the task manager processes view I saw that it was the Microsoft.CrmUnzipService.
Stopping the unzip service service from the service management console and starting the CRM website worked just fine… Obviously though the CRM unzip service now didn’t want to start
My suspicions that the unzipservice was running on port 8500, using a VM with the default installation proved me right… So the next step was changing the listening port/binding on the CRM server which now can be done through the IIS service manager only.
So lesson learned don’t run CRM (or anything else) on port 8500 if the zip service runs on the same server.
