Yes, you CAN do that with CRM : MSCRM 1.2

SBS SP1 Installation Woes

crm — Fri, 22 Jul 2005 14:28:00 GMT

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.

Installing MSCRM 1.2 on SBS 2003

crm — Sun, 10 Jul 2005 21:56:00 GMT

As some of you may know, I was working with Harry Brelsford to add some Microsoft CRM content to the “Extending SBS 2003” book. My hope was that I could help my peers in the SMB consulting space avoid some of the pot holes and dead ends that I encountered with MSCRM on SBS. The planned timing of the book release relative to Microsoft's (now) official announcement of the release of Microsoft CRM 3.0 pretty much made the chapter I penned on installing MSCRM on SBS 2003 obsolete so I've decided (with Harry's concurrence) to release the chapter to the public domain in hopes that it will help. This was my first crack on writing a chapter for a technical book. I'd appreciate any feedback that might help me as I start working on the new chapters for the “Extending SBS 2003” that will focus on CRM 3.0.

Check back here shortly for a link to my recipe for a successful CRM implementation on top of SBS 2003 .....

Prescribed MSCRM Pacthes and Hot Fixes (From my CRM Knowledge Base)

crm — Wed, 20 Oct 2004 19:23:00 GMT

I install the following patches and hot fixes on all the Microsoft CRM implementations we manage. This article also demostrates the functionality of the CRM Knowlege Base and is infact a copy of the KB I maintain for my company. As I update my internal KB I'll post the update here.

Prescribed Patches for a Microsoft CRM Server Installation

KBA-02024

Purpose & Scope

The following Updates and HotFixes should be applied to all Microsoft CRM V1.2 installations.

Prerequisites & Initial Conditions

Microsoft CRM v1.2 is installed.

Procedure

Install the following Updates and Hotfixes in the order listed.

(2005-03-28) KB870635 - Microsoft Business Solutions CRM update for Windows XP Service Pack 2
(2005-03-28) KB837059 - Update to Microsoft Business Solutions CRM 1.2 to add Coordinated Universal Time +1200 to timezone list
(2005-03-28) KB840934 - Microsoft Business Solutions CRM version 1.2 update for 839153, 839159, and 839162
(2005-03-28) KB841562 - Microsoft Business Solutions CRM 1.2 hotfix for 839163 and 835306
(2005-03-28) KB886355 - Microsoft CRM 1.2 Hotfix Rollup for 840058, 841648, 843172, 870575, 888004, 888005, and 888006
(2005-04-19) KB892949 - Microsoft CRM Update Rollup 1 for Microsoft CRM Sales for Outlook 1.2 (Note this role up addresses a lot of server side bugs too.)

Additional Comments

Last updated 4/22/2005