Following on from our very popular IFD configuration for Microsoft CRM.
The time will come around where you need to renew the SSL certificate for your CRM IFD configuration.
This will include the renewal of the SSL certificate as used by IIS and and ADFS. Couple of steps we followed based exactly on the configuration outlined in our above linked blog post.
1. Open IIS Manager and click on server certificates.
2. Create certificate request
3. Fill in the data:
4. Change to 2048 Bit
5. Give it a name:
Finish and you are done.
Now Open the certificate text file and copy the text to your clip board, or use this with your certificate authority to issue you a new Wild Card Certificate. *.interactivewebs.com is what we use.
To get the certificate we use a service called “startssl.com” who allow you to issue certificates like this for 2 years for free once you are validated as a user.
Once the new certificate has been issued to you you need to complete the request on IIS.
1. In IIS Manager click on Complete Certificate Request
2. Browse to the certificate from your issuer provider and give it a friendly name. We like to use a year in the name to help distinguish from the old one.
Finish the import.
1. Expand the two sites on the CRM server and click on Default Website first then Bindings / https
2. Select the new certificate that you just imported and click on OK
3. Repeat this process fro the Microsoft Dynamics CRM website
selecting the new certificate here and OK.
4. Restart IIS
1. Click Start, and then click Run.
2. Type MMC.
3. On the File menu, click Add/Remove Snap-in.
4. In the Available snap-ins list, select Certificates, and then click Add. The Certificates Snap-in Wizard starts.
5. Select Computer account, and then click Next.
6. Select Local computer: (the computer this console is running on), and then click Finish.
7. Click OK.
8. Expand Console Root\Certificates (Local Computer)\Personal\Certificates.
9. Right-click Certificates, click All Tasks, and then click Import.
Step 2: Add to the ADFS service account the permissions to access the private key of the new certificate. To do this, follow these steps:
1. With the local computer certificate store still open, select the certificate that was just imported.
2. Right-click the certificate, click All Tasks, and then click Manage Private Keys.
3. Add the account that is running the ADFS Service, and then give the account at least read permissions. (for us this is the Network Service)
1. Run the CRM deployment manager:
2. Run the Configure Claims-based Authentication
Select the default settings.
Which should be the default from your IFD setup
But when you get to the Certificate, you need to select the new certificate.
Which should be visible from the list after importing it in the steps above.
3. Run the Configure Internet Facing Deployment action and just step though it with the default settings.
4. Restart the AD FS 2.0 Windows Service
1. Start AD FS 2.0 Management
2. Expand certificates and select Set Service Communications Certificate
3. Select the new certificate that will be listed here.
Update Relying Party Trusts
1. From the AD FS 2.0 Management, Select your replying party trusts and update from the federation metadata one by one.
Update both listed. They will likely have a red cross before you do this.
Restart AD FS Service:
and restart IIS the usual way.
And you should be done. Login to your CRM IFD again and enjoy.
Please feel free to link to / reference this blog. Comments welcome below.
Often with the setup of CRM 2011. Users experience messages about Pending e-mail warning and sometimes email messages are not sending.
This can be especially frustrating as both the CRM email queuing and tracking system and the Email router application are terrible to help you understand exactly what is going on with your CRM e-mail.
We mentioned some of the issues we have experience here:
1. Out of the box, CRM does not send email messages. You need to configure an application known as CRM 2011 Email Router to have email messages send.
2. You also need a working SMTP (email server) that is configured to allow the relay of email messages from email accounts at your domain name. This can be achieved with Amazon SES message service or your own servers. We can assist you setup Amazon SES if you need assistance with this.
3. You should install and configure your Email Router. Some notes to help you may include these: http://www.interactivewebs.com/blog//?s=email+router
1. Out of the box. CRM will only be able to send email messages to leads, contacts, and accounts. Until you change this setting found in the Admin / System Settings in CRM.
2. Avoid delayed email messages in CRM by Approve Email Address. In the Administration / Users. Go into each user and approve the configured email address.
There is a view of users who are Pending Email address approval to help identify who is needing approval.
Also uncheck the option for Process emails only for approved users and process email only for approved queues. Administration / System Settings.
3. Configure users email settings to use the email router for outbound email messages. (optionally inbound configuration too).
Our recommendation is to set the outbound processing for the email router. This will allow emails generated by the crm system to be delivered right away via the email router. This also means that you do need to install and configure the email router.
The above settings can be set automatically for all users by the use of a simpler out of the box workflow that runs on create of new users.
4. The next setting is recommended. Knowing that email can be tracked in CRM with the outlook client:
Email messages can automatically be tracked too.
5. The all powerful features of creating contacts in CRM when and email address is not known.
This is a great way to automatically get more leads or contacts (depending on your business) in crm. And depending on your business can also be a great way to pollute your crm full of contacts or leads that you don’t want.
To troubleshoot an E-mail Router outgoing profile configuration, follow these steps:
Test Access error
If there is a problem with your outgoing e-mail configuration, you may receive the following error message when you click Test Access on the E-mail Router Configuration Manager:
“Outgoing status: Failure – An error occurred while checking the connection to e-mail server EXSERVERNAME. The requested address is not valid in its context”
If you receive this message, follow these steps to troubleshoot the problem:
E-mail error when message sent from the Web application
Symptom: When a user sends an e-mail message by using the Web application, the user might receive one of the following messages:
This message has not yet been submitted for delivery. 1 attempts have been made so far.
The message delivery failed. It must be resubmitted for any further processing.
Resolution: For information about how to resolve this issue, see KB article 915827.
Load Data error
When you click Load Data in the E-mail Router Configuration Manager, you receive the following error:
The E-mail Router Configuration Manager was unable to retrieve user and queue information from the Microsoft Dynamics CRM server. This may indicate that the Microsoft Dynamics CRM server is busy. Verify that URL ‘http://OrganizationName‘ is correct. Additionally, this problem can occur if the specified access credentials are insufficient. To try again, click Load Data. (The request failed with HTTP status 404: Not Found.)
To resolve this problem, follow these steps:
On the Email Router, configure:
1. Check event view for Email Router related errros
2. Change the send email
3. Restart CRM email Router service
4. Reduce the pooling time and conneciton timeout
The Advanced find can be used to find email messages that have not sent. A workflow can also be created to resend messages automatically. However constant failures is going to indicate a problem some other place. So the use of this automatic workflow should not be introduced in place of fixing your sending issues.
Steps to create the workflow to re-send failed e-mails:
1. Create a new Workflow in CRM | Processes on the E-mail entity
2. Set the workflow to be Available to Run “As an on-demand process”, Change the scope to Organization and uncheck “Record is created”. This will make the workflow available to run On-Demand, function for all e-mails in the organization and also not run when every time a new e-mail is created as we just want to use this when needed on specific e-mails.
3. Click “Add Step” and choose “Change Status”
4. Set the E-mail to a status of “Pending Send”
5. Click Save and then Activate in the toolbar. Click ”OK” to the message to confirm you want to Activate the workflow and then click “Close” on the workflow.
Advanced Find to see how many e-mails are in a failed status:
1. Open Advanced Find by clicking the “Advanced Find” button in the CRM ribbon
2. Select “E-mail Messages” in the Look For option set and then select “Status Reason” and set it equal to “Failed”. Then click the Results button in the Advanced Find ribbon.
3. You can refine the results using the filter criteria from here as well in case you do not want to re-send all of the e-mails. Once you are done, multi-select the e-mails you want to re-send and then click the “Run Workflow” button in the CRM ribbon.
4. Select the e-mail workflow that you created using the steps above and click OK.
The workflow will then run and change the status of all the e-mails you had selected back to “Pending Send”. This is an asynchronous process, so it may take a few minutes depending on your current asynchronous workload in CRM. Then the CRM e-mail router will process them again and send them out through SMTP as expected.
Here at InteractiveWebs we know how terrible this component of Microsoft CRM is. Actually, in our opinion, it is difficulties like these that really shows Microsoft is not at all interested in giving it’s customers a good experience. Much of the multitude of steps and better monitoring could be fixed with very little effort from Microsoft, yet after years of CRM, much remains the same.
In any case, if you need paid administration assistance to get your email working on your CRM system, be it Cloud Microsoft Hosted, IFD, or On Premises, we are available. Please contact us at: http://www.interactivewebs.com by submitting a support ticket.
Reposted: Today the update Rollup 12 for Microsoft CRM 2011 (CRM 2011 Polaris on premises) is available for download at this location:
This update is the long awaited one that is doing the UI update that will add the support for multiple browsers apart from Internet Explorer.
The image above depicts the functionality included in Polaris. I will now touch upon some of the key ones in a little more detail, hopefully in plain English!
Microsoft Dynamics CRM 2011 Update Rollup 12 (UR12), which was readied for availability on January 10 and made available on January 12, has been withdrawn by Microsoft, citing ” an issue that could potentially impact a customer’s database”.
Writing in a blog post on the Microsoft Dynamics community site, CVP for Dynamics CRM Bob Stutz explained that an issue discovered in the “UR12 Server bits” could impact customer databases, so the software download was removed from the Microsoft Download Center.
A new version of UR12 will be made available within the week, according to Stutz.
Dynamics CRM forum members discussed the missing server software for UR 12 on Friday, January 11. One person notes that she downloaded it on the 9th, discovered issues, and saw that it had been pulled down soon after:
“I grabbed the server component around 10:00 PM eastern on the 9th, and they pulled it down about an hour later. I installed it in my environment and it had a few bugs, maybe MS pulled it down and are frantically fixing?”
Another forum member puzzled over the lack of communication on the missing software:
“Seems wierd [sic] that they were there one moment and gone the next. Always amazes me that there’s multiple posts when it’s released, but nothing but silence when it gets pulled. SImilar to UR 10 and UR 11 which both had V2′s (and niether [sic] of which were really fixed).”
This is not the first update rollup to be withdrawn because of undiscovered issues. UR10 had to be re-released in October 2012 due to several issues. UR11 was similarly re-released several days after the original due to user-reported issues.
Stutz’s blog post does not elaborate on the problems, but Stutz acknowledges that another consecutive withdrawn update to Dynamics CRM hurts the product’s QA and release processes. He concludes with an assurance: “We have taken measures to improve our engineering processes and methodologies going forward, and we take your feedback very seriously. We apologize for any inconvenience this has caused.”
We have created a tool that allows the importing of Microsoft CRM (IFD) into your Zendesk setup.
The simple tool will look at your Microsoft CRM 2011 Articles (also known as KB articles) and draw them into your Zendesk support portal.
This is powerful if you have an existing CRM system with useful client data that you wish to expose to your support portal as a way of helping your customers find answers to their questions before they directly lodge a support ticket.
Additionally, the tool is smart enough to remove duplications. So if you run it against more than one instance of CRM, you can import KB articles without the fear of duplicating up on KB articles.
At the Zendesk end, the KB articles import something like this:
From original articles in CRM like this:
We have at this stage only release a version that runs as a Windows installable program, and connects to an IFD deployment of CRM. This is because we don’t anticipate a huge demand for the tool, and the only need we had was for this type of setup.
We are releasing the Source Code for the program, so that others can update it to their needs. Alternatively we would be happy charge a small amount to customize it to other particular needs.
In the near future we are going to update the tool to convert WordPress posts into Zendesk Knowledge Base Articles.
Please feel free to give feedback and or ask questions on what you would like to see in this too.
After installing CRM 2011 Rollup 10 (not 9 as that is MIA) you receive an Invalid Argument messages as per the image above. This happens after you login to an IFD deployment.
For all we know it may happen on the CRM on premises but we have not managed to test that.
You may also have a CRM Platform Trace Error:
Crm Exception: Message: A non valid page number was received: 0, ErrorCode: –2147220989
Crm Exception: Message: A non valid page number was received: 0, ErrorCode: –2147220989
CRM’s Fetch Throttling abilities have been disabled or modified from the default values. Re-enable CRM’s default Fetch Throttling settings.
1. START | RUN | “regedit” | OK
2. Locate and select the registry subkey: HKEY_LOCAL_MACHINESoftwareMicrosoftMSCRM
Change the value on: TurnOffFetchThrottling
In fact if you find either MaxRowsPerPage or the TurnOffFetchThrottling registry keys set them both to 0 or delete them.
3. START | RUN | “iisreset” | OK
(This will restart IIS)
Login to CRM and you should be good to go.