- You cannot configure MS CRM 4.0 Outlook 07 Client with Offline Access, with the Configuration Wizard on the client throwing error "The request failed with HTTP status 401: Unauthorized", followed by "Mandatory updates for Microsoft Dynamics CRM could not be applied successfully. Try running the application again." when trying to enter the CRM server name.
- You may be able access CRM from the client computer using the web client, although depending on how the username/password was entered, you may also get "HTTP Error 401.1 - Unauthorised: Access is denied"
- None of the rollups fix the problem
- Client is running Windows Vista
- Server is running Windows Server 2003 family, including SBS2003.
SOLUTION THAT WORKED FOR ME:
Our CRMAppPool in IIS had been set to identify using specific account (not Network Service) per https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb$en-us$954045 to fix another issue we were having.
Changing the App Pool to use Network Service again fixed the issue. We were able to change the identity from Network Service back to the other account after configuring the client.
To change the identity account:
Our CRMAppPool in IIS had been set to identify using specific account (not Network Service) per https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb$en-us$954045 to fix another issue we were having.
Changing the App Pool to use Network Service again fixed the issue. We were able to change the identity from Network Service back to the other account after configuring the client.
To change the identity account:
- Go into Internet Information Services (IIS) Manager on the server
- Under <servername> / Application Pools, right click on CRMAppPool, and click Properties.
- Click on the Identity Tab, click the Predefined radio button and if not already selected, choose Network Service from the drop down list.
- Click OK
- Open up a command prompt and type iisreset
Others have mentioned changing the server address in the Configuration Wizard to either ServerIP:port or FQDN:port instead of computername:port can fix the issue. For instance, if your CRM server name is http://hellokitty:5555 and your local domain is catsanddogs.local, using catsanddogs.local:5555 or the IP address of the server (eg: 192.192.1.1:5555) instead of the server name can fix the issue. That is a long shot though.
OTHER POSSIBLE SOLUTIONS:
The following describe similar problems to the above but have different solutions:
- Enable only Basic HTTP Authentication on the Web Listener in ISA http://social.microsoft.com/Forums/en-US/crmdeployment/thread/10589b30-bf9b-4d88-b1c8-3cfd43337ae3
- Modifying the Default_Client_Config.xml file http://social.microsoft.com/Forums/en-US/crmdeployment/thread/4986242d-6cc1-4377-aa40-026a486099db
- If your client is in a different domain to the server, the following could help: http://www.crmwatcher.com/2006/01/outlook-client-connecting-from-other.html and also,
- The following also has useful information if you have an internet facing deployment (subscription may be required - you can sign up for 15 day trial) http://www.experts-exchange.com/Microsoft/Applications/Microsoft_Dynamics/Q_23316120.html however the crux of the useful information at this site is from http://www.microsoft.com/downloads/details.aspx?FamilyID=3861e56d-b5ed-4f7f-b2fd-5a53bc71dafc&displaylang=en
- http://social.microsoft.com/Forums/en-US/crm/thread/12933ee1-a3d0-4e7a-8a98-c0569582f62c
- http://microsoftdynamicscrm.blogspot.com/2007/12/solved-http-status-401-unauthorized.html
- Common CRM troubleshooting steps are also located here: http://blogs.msdn.com/crm/archive/2009/05/29/troubleshooting-the-microsoft-dynamics-crm-client-for-outlook.aspx
