I ran into a fascinatingly irritating issue last weekend while moving a CRM 4.0 installation from Small Business Server 2003 to 2008.
It seems that the Exchange Migration Tool did not properly assign permissions to the Program Files folder where Exchange was installed. It did properly assign the permissions to the Exchange folder set, but not to the root Program Files folder.
Ordinarily this would not have been an issue if not for the fact that I was actually installing CRM into the same folder structure. Here is what happened:
The Problem
The problem surfaced in two separate ways:
- I was installing CRM using the default user of Network Service. This is also the user who would run the CRM Async Service. The installation failed with an access denied error message. It took me a while to figure out it was a permissions issue within the file system which I fixed by giving Network Service permissions to the Microsoft Dynamics CRM folder structure.
This was an incorrect solution.
- The second issue surfaced when I loaded the CRM web page and found none of the icons were visible and I was getting JavaScript errors.
After working with Microsoft and running a Fiddler trace, I finally tracked down the issue.
The Resolution
It turns out that the domain group Users had no access to the E:\Program Files folder structure which is where CRM was installed.
This surfaced initially because of the issue with Network Service not having access but it never occurred to me that an issue could be caused by a permission which is usually there.
I compared the permissions on the original SBS 2003 server against those of the SBS 2008 server to locate and correct the problem which was to give [domain]\Users read, execute, and list permissions on the folder structure.
Loading ...
