Monthly Archives: August 2014

How to Disable the CRM 2013 Welcome Screen Popup

CRM 2013 has an annoying CRM 2013 Welcome Popup (First Things First)

CRM 2013 Welcome Popup

Not exactly sure why they did not predict the need to turn of this popup Organisation by organisation, however the solution is to just turn it off for good.

The Solution

On the CRM server, run “Regedit.exe” as an administrator.

  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRMAdd  and right click to new 32 Bit DWord

CRM Stop Popup


  • Name the new Dword: DisableNavTour


  • Set the Data Value to 1

Screenshot 2014 08 29 18 18 17

  • Restart IIS

Screenshot 2014 08 29 18 20 11

That’s it, your CRM server should never show the Popup again.

adfs/services/trust/mex Returns 503 on CRM 2013 Windows 2012 IFD – MEX EndPoint Fix

When browsing to your CRM server: /adfs/services/trust/mex  you receive an 503 Error.

In our case this was to “” and we received the 503 Error. This became evident as we were testing the importing and upgrading of custom JS scripts from CRM 4.0 and CRM 2011 to use the new SDK in CRM 2013 (also applicable to CRM 2015). When we used fiddler to look at why the test environment failed we noticed a call to the ADFS mex endpoint.

Screenshot 2014 08 29 00 54 30

Looking at the ADFS Logs for the server will show a 102 Error:

There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service.

Additional Data
Exception details:
System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. —> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
— End of inner exception stack trace —
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
at System.ServiceModel.Channels.ConnectionAcceptor.StartAccepting()
at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at Microsoft.IdentityServer.ServiceHost.STSService.StartSTSService(ServiceHostManager serviceHostManager, ServiceState serviceState)

The Cause

This is caused because the CRM Sandbox service is using port 808.  As you can read here:

The Fix

The fox for this is very easy. We need to use a PowerShell command to set the nettcpport port to 809 for ADFS.

1. Open PowerShell

2. Type: Set-ADFSProperties –nettcpport 809

3. Hit enter

Screenshot 2014 08 29 00 57 21

4. Use the Services to restart ADFS or restart the entire server. 

Now browsing to the URL will give a result looking more like this:

Screenshot 2014 08 29 00 58 16

CRM 2013 Warning Data encryption will be active after the install or upgrade.

When importing a database from CRM 2011 to CRM 2013, you may receive an error:

Screenshot 2014 08 21 16 27 06

Data encryption will be active after the install or upgrade. We strongly recommend that you copy the organization encryption key and store it in a safe place. For more information, see

Understanding This

Microsoft Dynamics CRM 2013 uses standard SQL Server cell level encryption for a set of default entity attributes that contain sensitive information, such as user names and email passwords for Server-Side Sync and authentication tokens for Yammer integration capabilities.  This feature can help organizations meet FIPS 140-2 compliance by ensuring that the data is encrypted “at rest” so that local database admins cannot read the data in the database tables directly.  For Microsoft Dynamics CRM Online, all new and upgraded organizations use data encryption.  For on-premise versions of Microsoft Dynamics CRM 2013, users who have the system administrator security role (and in the PrivUserGroup) can activate data encryption or change the encryption key after data encryption is enabled in the Settings > Data Management > Data Encryption area.  After you activate data encryption, you cannot turn it off. NB: For on-premises versions of Microsoft Dynamics CRM:

  • Changing the encryption key requires SSL configured on the Microsoft Dynamics CRM website. (This requirement can be averted by a work-around described herein, which should only be used for testing purposes.  The point of having data encryption is to have data be encrypted both in transit and at rest.)
  • It is a best practice is to change the encryption key once every year.
  • The encryption key is required to activate data encryption when you import an organization database into a new deployment or a deployment that has had the configuration database (MSCRM_CONFIG) re-created after the organization was encrypted.  You can copy the original encryption key to Notepad and paste it into the Settings > Data Management > Data Encryption dialog box after the organization import is completed.
  • When you re-enter the data encryption key, we recommend that you run the Microsoft Dynamics CRM web application using Internet Explorer to paste the encryption key into the Data Encryption dialog box.

Copy your organization data encryption key.  It is strongly recommend that you make a copy of your data encryption key.  This is particularly important for on-premise deployments that may need to reactivate data encryption after a redeployment or failure recovery.


How to copy a CRM 2013 Data Encryption Key for an Organization

  1. Sign in to Microsoft Dynamics CRM as a user with the system administrator security role.
  2. Go to Settings > Data Management > Data Encryption.
  3. In the Data Encryption dialog box, select Show Encryption Key, in the Current encryption key box select the encryption key, and copy it to the clipboard.

CRM 2013 Data Encryption https errorHowever, if the Microsoft Dynamics CRM website is not configured for HTTPS/SSL, the Data Encryption dialog box will not be displayed.  Instead, you’ll get the error noted at the right.  For a more secure deployment, we recommend that you configure the website for HTTPS/SSL.  As a work-around, it is possible to get at the CRM 2013 Data Encryption settings even if the website is not configured for HTTP/SSL.  To do so, use a tool that can be used to modify CRM database tables, such as Microsoft SQL Server Management Studio and open the configuration database (MSCRM_CONFIG); in the DeploymentProperties table, set DisableSSLCheckForEncryption to 1.  In order to set the property use the following SELECT and UPDATE statements:

<span style="color: #000000;">SELECT [ColumnName],[BitColumn]
FROM [MSCRM_CONFIG].[dbo].[DeploymentProperties]
WHERE ColumnName='DisableSSLCheckForEncryption'
UPDATE [MSCRM_CONFIG].[dbo].[DeploymentProperties]
SET [BitColumn]=1
WHERE ColumnName='DisableSSLCheckForEncryption'</span>

CRM 2013 Data Encryption KeySaving CRM 2013 Data Encryption w Unicode

After performing an IISReset on the CRM Server, you’ll be able to see the encryption screen.  Paste the encryption key in to a text editor, such as Notepad. As a best practice, save the text file that contains the encryption key on a computer in a secure location on an encrypted hard drive.  Also note that if you keep the default encryption key with all the special hieroglyphic characters, you’ll need to save the file with Unicode encoding — see screenshot below.  Also, note, there is one data encryption key per organization.

Testing our system, I backed-up our test Adventure Works CRM organization database, and restored it as AdvWrks2.  I imported (re-deployed) the AdvWrks2 database to create a new CRM org.  I browsed to Settings => Admin => Users, and selected my User.  I changed the Primary E-mail address and hit save.  Here’s where I got a “Data Encryption error — There are encrypted fields in the organization database, but the data encryption feature isn’t activated.” What this means is that the org that I originally backed-up had encryption enabled, and we copied and re-deployed that org to the new org — which is now requiring data encryption be activated with the Encryption Key from the original org. I went ahead and activated using the Encryption Key that I had previously saved, and got the good news that the Encryption Key was activated successfully.
CRM 2013 Data Encryption - encryption not activated error

So we’ve seen CRM 2013 Data Encryption be activated automatically, by simply installing CRM, as noted in the highlighted paragraph at the top of this post. We also know that Data Encryption will be enabled on all CRM Online deployments.

We’ve further seen that when an encrypted CRM database is restored and redeployed it requires that data encryption be activated with the appropriate encryption key. If you ever think you may want to restore your CRM organization database for disaster recovery or redeploy your CRM system for testing or operational reasons, you simply must save off the encryption key of your existing CRM system. 


CRM 2011 to 2013 “Database cannot be started in this edition of SQL Server” error when restoring a Microsoft Dynamics CRM database.

When restoring a database that is a backup of a CRM 2011 database and you are restoring it to a CRM 2013 server running SQL 2012 but not Enterprise, you may receive an error: 

“Database cannot be started in this edition of SQL Server” error when restoring a Microsoft Dynamics CRM database.

This error only happens when the original SQL instance was running an enterprise version and the destination server is not.

Screenshot 2014 08 21 15 45 58

The Cause

When Microsoft Dynamics CRM 2011 is installed using a Microsoft SQL Server Enterprise edition, a partition is created for the auditing functionality of Dynamics CRM 2011. The AuditBase table uses partitioning which is only available for Microsoft SQL Server Enterprise.

The Solution

Use the following Steps and Script to remove the partitioning. The following script recreates all the indexes on the Primary partition and then drops the partition.

Be sure to have a database backup of the ‘Org_MSCRM’ before performing the following steps. 

1. Restore the ‘Org_MSCRM’ database to a Microsoft SQL Server Enterprise edition. It is recommended to backup and restore the database instead of running the script on the production database.

2. Run the following script against the restored database.

IF EXISTS (SELECT name FROM sys.partition_schemes WHERE name='AuditPScheme')
  CASE WHEN ind.type != 1 
    'DROP INDEX [dbo].[AuditBase].' + QUOTENAME( + ' ' 
   ELSE ' ' 
  END + 
  'CREATE ' + CASE is_unique WHEN 1 THEN 'UNIQUE ' ELSE '' END  +
  ind.type_desc + ' INDEX ' + QUOTENAME(  COLLATE SQL_Latin1_General_CP1_CI_AS )  + ' ON [dbo].' +  QUOTENAME(OBJECT_NAME(object_id)) + ' (' +
   SELECT name + CASE WHEN sc.is_descending_key = 1 THEN ' DESC' ELSE ' ASC' END + ','
    sys.index_columns sc
    JOIN sys.columns c ON sc.object_id = c.object_id AND sc.column_id = c.column_id
    OBJECT_NAME(sc.object_id) = 'AuditBase' AND
    sc.object_id = ind.object_id AND
    sc.index_id = ind.index_id
   ORDER BY index_column_id ASC
        )), 2, 8000)) + ')' +
  CASE WHEN ind.type = 1 
    ' ' 
  END  as Script 
 INTO #indexesScript
 FROM sys.indexes ind
 JOIN sys.partition_schemes ps on ind.data_space_id=ps.data_space_id 
  OBJECT_NAME(object_id) = 'AuditBase'
  AND = 'AuditPScheme' 
  AND is_unique_constraint = 0 
 SELECT * FROM #indexesScript 
 DECLARE @recreateScript nvarchar(max)
 SELECT Script FROM #indexesScript
 OPEN indScript
 FETCH NEXT FROM indScript INTO @recreateScript
  Execute sp_executesql @recreateScript
  IF @@ERROR > 0
   declare @message varchar(max)
   set @message = 'Audit history recreate index failed. SQL: ' + @recreateScript 
      RAISERROR (@message, 10,1)
  FETCH NEXT FROM indScript INTO @recreateScript   
 CLOSE indScript   
 DEALLOCATE indScript 
 DROP TABLE #indexesScript

3. Once the script is complete you can backup the database and now you should be able to restore the database to a Microsoft SQL Server Standard edition.

Editing (Without Word) and Deleting Content

You’ve got this website and you want to change some of your wording because it just doesn’t feel right, it’s only a quick change and you’re not on your computer so you don’t have Word. Not a problem! Step 1, log in to your website using the login link in the top right.


Now the magic can happen. Go to the section of the page you’re not happy with, put your mouse over it and a border will appear around it, in the bottom left of this newly bordered box you’ll see those 2 wonderful words “Edit Content”, click them.


A new page will load displaying your content, go in and change whatever wording you’d like then scroll down a little and click Save.


Undoing Changes

Crisis! You’ve accidentally rid of something you really needed and you can’t remember what it was! Crisis averted. Go back into “Edit Content” scroll all the way down to the bottom. You will see “Version History” with an arrow next to it, click it and it will expand down with the last few changes.


Select the last version you know was safe and click the little green button to the right of it. When you scroll up your content will be back how it was, (now you can make more changes if you want), click “Save”. Done!

Maybe you’ve decided it’s all wrong! It has to go! Very carefully put your mouse over the gear symbol next to the edit pencil, hover over it and a menu will appear. In there you’ll see “Delete”, click to remove it, but only if you’re sure!


Editing Websites With Word 365

It is time! Your website is up and running, but you’ve got some information burning away that needs to go on the website. Step 1: Log in to the website (top right hand corner of the site).


Now you’re logged in, you’ll see a bit black bar at the top of the screen, we need to edit the page, so click on “Edit Page” to the top right hand side of the page. Then in the menu that opens, click “Edit this Page”.


Next, in the top right of the area you want to edit you’ll see 3 icons, hover over the pencil to show a menu. Click “Edit in Word” (To see how to do it without Microsoft Word check out our post on “Editing (Without Word) and Deleting Content”).


If this is your first time, something strange will happen, a box will open and tell you that you need to install something. Lets get briefly technical for those who care, but you can skip to the next paragraph if you just want to get on with it. We’ve installed something called a “module” that will allow the website to open Word 365 and Accept information from Word 365 because we built it to suit Microsoft’s software. They however did not build Word with us in mind (rude right?), so this software install lets Word know how to send your content to the website.


We now need to install this bit of software so click “Download Word Addin” Then follow the install prompts to get Word 365 comfortable with our software.

When complete we can open our content in Word 365 and edit the  content in the same way we would edit any other document, then it’s just a matter of clicking the big orange “Publish” and your website gets updated!


Office 365 Website for Business

Small Business Website that Integrates with Office 365

Screenshot 2014 08 19 08 46 43

Today we are please at announce the launch of the Microsoft Office 365 Website for business site. This website is aimed to help small business (and large) get ready access to web technologies that are designed to work directly with the Microsoft Office 365 suite of products.

With the Office 365 Website product, you will receive a website ready to promote your small business, but still be able to interact with the website users, and data directly from your Office 365 tools.

Some of the Stand out Office 365 Website integrations:

  • Using Outlook to link to the website registered users.
  • Using Outlook to track the social activity of users on the site
  • Using MS Word to edit content of the site
  • Linking Outlook Contacts to your Bulk Email marketing

Creating a Website using Office 365 

Creating a Website Using Office 365 has never been easier. You simply pick from one of our many templates, and provide us with the basics of your business website content. We will then configure the site for you and setup the necessary components to connect your website to your Office 365 subscription suite. We do all the initial setup and hold your hand while you walk through the site.

Creating Office 365 Website

To get started creating an Office 365 Website all you need to do is contact us.

Proudly created and supported by InteractiveWebs.

CRM 2013 Reporting is not enabled Message in CRM Deployment Manager

You Receive the Message “Reporting is not enabled”

And as the name suggests, this is because you have not installed the CRM Reporting feature. To Install the CRM 2013 Reporting Extension

Screenshot 2014 08 03 00 27 58

Add the SQL Server Data Tools option to the SQL 2012 server.

Screenshot 2014 08 03 00 29 19

Add features

Screenshot 2014 08 03 00 31 02

Select SQL Server Data Tools

Screenshot 2014 08 03 00 31 33

Next Next Install Etc till you are all done.

Install the CRM Report Authoring Extensions


Following the standard setup process, then..

Install the Reporting Extensions


That’s it. You now will have the message from the Deployment Manager removed, and the necessary reporting Extensions installed.

CRM 2013 splash screen crash on Setup DVD / ISO

CRM 2013 splash screen crash on Setup DVD / ISO

After so many years, with the Splash screen crash of CRM 2011, the boys at Microsoft have not bothered to fix that problem. You start the screen

Screenshot 2014 08 03 00 16 22

Then before long you see this.

Screenshot 2014 08 03 00 17 03

Search around the net, and you find a bunch of old data relating to CRM 2011 and the same problem. Some suggestions are to uninstall various version of IE (The worlds Words Browser) or other similar crap. Not really much help when you are on a Windows 2012 R2 server with the newest release of CRM install ISO. Note: This is the sort of stuff I hope the new CEO will fix one day!

Other Solutions incorrectly reference the files to install from.

The Solution

These are the correct locations for CRM 2013:

  • Install Microsoft Dynamics CRM Server[Drive]:\Server\amd64\SetupServer.exe
  • Install Microsoft Dynamics CRM Report Authoring Extension[Drive]:\BIDSExtensions\i386\SetupBIGSExtensions.exe
  • Install Microsoft Dynamics CRM Reporting Extensions[Drive]:\Server\amd64\SrsDataConnector\SetupSrsDataConnector.exe
  • Install Microsoft Dynamics CRM for Outlookx86: [Drive]:\Client\i386\SetupClient.exex64: [Drive]:\Client\amd64\SetupClient.exe
  • Install Microsoft Dynamics CRM Email Routerx86: [Drive]:\EmailRouter\i386\SetupEmailRouter.exex64: [Drive]:\EmailRouter\amd64\SetupEmailRouter.exe

The trust relationship between this workstation and the primary domain failed Windows 2012 R2 Hyper-V snapshot

The trust relationship between this workstation and the primary domain failed Windows 2012 R2 Hyper-V

Screenshot 2014 08 02 23 22 38

After working with Hyper-V and Snap shots, you may find that a previously working domain member machine gets this error message. This is because the Domain Controller will automatically update passwords of Machine Accounts every 30 days, and a restored snapshot may not match the new pass.

The solution

  1. On the effected client machine open PowerShell
  2. Run the following command “Reset-ComputerMachinePassword” or specify the credentials switch if the account your running PowerShell with doesn’t have the correct AD perms for the CMDlet “Reset-ComputerMachinePassword –credential Domain\Adaccount” (You will be prompted for the domain password).
  3. After running this give the client machine a restart

After Reboot, the server will function correctly.