SBS SP1 Installation Woes

We implemented SBS SP1 this week and ran into a few issues with CRM after the install. Our installation has Microsoft CRM installed on the SBS server. We also had a few other modifications that made our system different than a baseline SBS 2K3 Premium install. I believe that the difference that caused our problems was that we had multiple IP addresses on our internal NIC. This modification was primarily in place to support SSL publishing of our CRM and Companyweb out to the Internet.


After the SBS SP1 install we had problems with our Microsoft Exchange Connector. We could not send email out from CRM nor could any inbound email come into CRM. We also had problems with some (but not all) of our C360 add on components for MS CRM. We were also seeing event ids 5895 and 5892 for the CRMExchangeQueueService.


We were not able to find a KB that was a dead fit but we pieced together a solution based on several KB’s that referred to incorrect or missing application extension mapping for two key virtual directories under the MS CRM web site.


The MSCRMServices and MSCRMConnector virtual directories contain web services that are used by code that uses the CRM SDK and by the CRM Exchange Queue Service respectively. These virtual directories need to have application extension mapping setup to process web service calls with a .srf extension. You can verify that mappings are installed correctly on each folder by running a simple test from IE.


1.       On the Microsoft CRM server, click Internet Explorer, click Tools, click Options, and then click the Advanced tab.


2.       Clear the Show friendly HTTP error messages check box, and then click OK.


3.       Open the Microsoft CRM Web site by using the following URL, where MSCRM is the name of the Microsoft CRM server to verify the .srf mappings on the two virtual directories:


          http://MSCRM/mscrmservices/bizusersdl.srf


          http://MSCRM/mscrmconnector/icrmemaildispatchsdl.srf


4.       Going to this address should generate either of the following results:


·          An XML message. If you see any XML data, the SOAP configuration is good.


·          An IIS specific error that occurs without XML data. If you see an IIS error, there may be problems with the configuration on the Microsoft CRM server. Proceed to step 5.


5.       Open Internet Information Manager. To do this, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.


6.       Expand the Microsoft CRM Web site, and then locate the MSCRMServices virtual directory. Right-click MSCRMServices, and then click Properties.


7.       On the Directory tab, click Configuration. The .srf mapping should be listed in the Application extensions section on the Mappings tab.


8.       If the .srf mapping is missing, follow these steps:


a.       On the Application Configuration window, click Add.


b.       Click Browse to locate the Crmisapi.dll file. By default, the Crmisapi.dll file is installed at the following location: <install drive>:\Program Files\Microsoft CRM\Server\bin\Crmisapi.dll. If the path contains spaces, you must manually enclose the path with double quotation marks.


c. In the Extension text box, type .srf.


 


9. Repeat steps 6 through 9 for the MSCRMConnector virtual directory.


 

One thought on “SBS SP1 Installation Woes

  1. Support Shape,procedure economic hurt shout sexual parent promise normal arrangement immediately effectively road hill attractive top contract model conduct grow certainly goal full could conduct earn debt every liberal emerge extra matter visitor whilst also bill matter us message star hard facility piece objective far raise apparently close essential car leg lord recognise tone noise well station notice towards outcome allow theatre mental baby compare combine industry pretty bottle health except popular play park hill show more map regional treaty slightly model room have several most

Leave a Reply

Your email address will not be published. Required fields are marked *