To train some developers at our office we used the SDK 5.0.12 with CRM2011 Online and Office 365 login approach.
When we downloaded the SDK we found several problems while using the SDK tools mainly with the ExportRibbon utility and the Plugin Registration tool.
All the problems were related to connexion and once we found a way to connect those tools to the CRM everything worked smooth.
I will describe the solutions we found to fix those problems.
Problem 1: Plugin Registration Tool –> The service is unavailable.
We found 3 problems with the PluginRT ,
First of all we hadn´t installed the Windows Identity Foundation tools and we couldn´t build the C# project due to IDentityModel issues.
If you have the same problem please download the right version of Windows Identity Foundation for your system from here .
Second, we had connection problems with the message “service unavailable” or “proxy requires auth”. To fix this issue we just added an app.config file to the Plugin RT with the following code were we specify our proxy settings.
<defaultProxy enabled="true" useDefaultCredentials="true">
<proxy bypassonlocal="True" proxyaddress="http://100.100.300.200:8080" />
Finally we had some problems at one of the machines due to time mismatch between CRM2011 server and the developer machine.
You can change the server time zone in the File/Options menu of CRM and make sure is the same that your clock time zone.
After that using the prompt command “w32tm /resync” you will have your computer synchronized with the internet global time zone setting.
Problem 2: Exported Ribbon XML –> Username and Password must be provided.
When executing the exportRibbonXML project we had some connexion problems with the following message: “username and password must be provided.”.
These message was shown before the tool asked for a username or password. Debugging the tool we manage to jump the step where the connexion was made and
pass to the step where the name and password where input. After that, the connexion was made and the tool created a XML file with the credentials.
If you try to connect again , the tool will check for this file and follow to correct sequence to connect without problems.
If you are experiencing the same problems I suggest you copy this XML, write your organization and username values and save it as Credentials.xml in the
<?xml version="1.0" encoding="utf-8"?>