Posts Tagged ‘CRM 4.0’

MS CRM 4.0 Can Not Go Online

PROBLEM:

·        MS CRM 4.0 Outlook 07 Client cannot go online, throwing error “Microsoft Dynamics CRM cannot go online. The Microsoft Dynamics server was not found”.

·        You can successfully use the web client.

·         None of the rollups fix the problem.

·         Client is running Windows Vista.

·         Server is running Windows 2003 family, including SBS2003.

SOLUTION THAT WORKED FOR ME:

If a user changes their domain password, this might not properly propagate to CRM. Change domain password back to the previous one (using either the client computer or the server) then try again.

OTHER POSSIBLE SOLUTIONS:

·         Ensure the user has been assigned an appropriate security role. If the user has not been assigned a role, CRM will not connect.

·         Programs such as Content Protect (Content Watch) can also interfere with the connection between the client and the server. Try either adding the CRM website URL (don’t forget the IFD, or internet facing deployment address as well as the internal address) as an allowed website to the web exceptions sites list and / or choose to allow secure content under the “Secure Internet Content (HTTPS)” section in settings.

·         Try re-setting the organisation settings by clicking on the CRM menu in Outlook 2007 and choosing Change Organization.

·         Stop or unload any anti-virus programs or firewalls and try to go online

·         In Internet Options, ensure the URL for CRM is in the trusted sites zone and making Internet Explorer the default browser.

·        If the message you are getting is more like the following: “Unable to connect. Still unable to connect to Microsoft Dynamics CRM. Microsoft Dynamics CRM will restore the connection when possible. To stop retrying, right-click and select Sign Out”, it could be that anonymous access to the _imgs folder in the Microsoft Dynamics CRM Web site in IIS on the server has been disabled. Try the following article if that is the case: http://support.microsoft.com/default.aspx/kb/951146

·       Try installing the latest rollup. Information on all the latest hotfixes and rollups is located here http://support.microsoft.com/kb/949256

·      Common troubleshooting steps now located here: http://blogs.msdn.com/crm/archive/2009/05/29/troubleshooting-the-microsoft-dynamics-crm-client-for-outlook.aspx

·         If you are feeling masochistic, uninstall/reinstall CRM Client:

·         Easy instructions found here http://social.microsoft.com/Forums/en-US/crmdeployment/thread/27bfe765-09a6-4cf1-bc00-e51f811baab0,

·         Which might have come from here (may require subscription, but either way the info is the same): http://www.experts-exchange.com/Database/Software/CRM/Q_23119039.html

·         Something more official here (relates to CRM 3.0, but largely the same as for 4.0) http://www.microsoft.com/dynamics/crm/using/deploy/removeclient.mspx

·         If none of these work, call Microsoft Support, as it could be some hitherto unknown thing that will commit you to an insane asylum if you try to figure it out alone.

MS CRM 4.0 Unable to Publish Workflows

PROBLEM:

• You cannot publish a workflow in CRM, with the following error appearing “An error occurred when the workflow was being created. Try to save the workflow again.”

• None of the rollups fix the problem – or, one of the rollups caused the problem.

• Client is running Windows Vista.

• Server is running Windows 2003 family, including SBS2003.

SOLUTION THAT WORKED FOR ME:

Various rollups over time have modified the web.config file to include various configuration lines. Some of these modifications can fail.

The solution to this one’s all over the internet, but the solution isn’t consistent. The best and quickest one seems to be:

Take a backup of your web.config file, then modify it to add the following under the <authorizedTypes> tag at the end before the </authorizedTypes> tag:

<authorizedType Assembly=”mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.Globalization” TypeName=”CultureInfo” Authorized=”True”/>

However, I would suggest you also look at the following three lines and see if any of these are missing from the file also. If you, add these in too:

<authorizedType Assembly=”mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System”  TypeName=”Void” Authorized=”True”/>

<authorizedType Assembly=”mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.Reflection”  TypeName=”AssemblyFileVersionAttribute” Authorized=”True”/>

<authorizedType Assembly=”mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.Reflection”  TypeName=”AssemblyVersionAttribute” Authorized=”True”/>

After making the changes above, restart IIS.

The above three lines came from http://www.msexperts.org/blogs/mark/archive/2009/06/19/error-while-publishing-crm-4-0-workflow.aspx

The reason for differences in opinion over which lines to add back in relates firstly to the different rollups everyone has installed and secondly to comparisons some people have made between a backup version of the web.config file they have retained and the current appearance of their file. A definitive list of changes to the web.config file can be found here: http://support.microsoft.com/kb/968793

OTHER POSSIBLE SOLUTIONS:

• Uninstall the latest rollup to revert to previous one. If this works try to re-install the rollup again.

• Try installing the latest rollup. Information on all the latest hotfixes and rollups is located here http://support.microsoft.com/kb/949256

• If none of these work, call Microsoft Support, as it could be some hitherto unknown thing that will commit you to an insane asylum if you try to figure it out alone.

MS CRM 4.0 Reports Fail to Display

PROBLEM:

·        Reports fail to display in MS CRM 4.0, with the following error shown “Reporting Error. The report cannot be displayed”.

·        If you have DevErrors turned on – which you should – (use CRM diagnostics tool on the server or modify the Web.Config file directly), the user might see one of the following errors under the Full Stack section: “[MissingParameterException: The 'CRM_Full_Name' parameter is missing a value]” or “[MissingParameterException: The 'CRM_CalendarType' parameter is missing a value]” or even “[ReportServerException: The permissions granted to user ‘<user>’ are insufficient for performing this operation.”

·        This can happen when using either the web client or the Outlook 2007 client.

·         None of the rollups fix the problem.

·         Server is running Windows 2003 family, including SBS2003.

SOLUTION THAT WORKED FOR ME:

This can occur when the Domain Logon Name field in CRM does not match the user’s actual domain account name. It might be because the name in CRM has been misspelled or the domain account name was changed on the server but not updated or fails to propagate correctly in CRM.

Check that the Domain Logon Name in CRM matches the user’s domain account name exactly. If it already does, change it to another user’s name then back to the original user’s logon name.

If you can’t change the name in CRM because it throws the following error: “You are attempting to create a user with a domain logon that is already used by another user. Select another domain logon and try again.”, change the Domain Logon Name field to another user who is not currently a CRM user. If you have none, create a temporary user on the server, change the Domain Logon Name to this user, then change back to the original user. This tip comes from http://navintmicrosoftcrm.blogspot.com/2008/12/how-to-correct-microsoft-dynamics-crm.html

A user should theoretically be blocked from accessing CRM if their Domain Logon Name does not match their actual domain name however Microsoft CRM seems to be the reason the word “theoretically” was conceived. Users can sometimes access CRM when the domain names don’t match but any reports would fail because reporting services produces the reports, not CRM.

OTHER POSSIBLE SOLUTIONS:

·         Check the authentication mode in the datasource for the report(s) and in IIS. It should be set to Windows Integrated Authentication.

·        Check the affected users have been assigned a security role in CRM.

·         Try installing the latest rollup. Information on all the latest hotfixes and rollups is located here http://support.microsoft.com/kb/949256/en-us

·      If none of these work, call Microsoft Support, as it could be some hitherto unknown thing that will commit you to an insane asylum if you try to figure it out alone.