CRM in-line search fails with SQL error

After upgrading Microsoft CRM from earlier versions we found that the global search function when enabled failed to return any results, and once the index for the global search had run over a 24-hour period, the in-line search function for any entity would cause a crash and SQL error message to be displayed on page.

The problem

In our particular instance this CRM environment had been upgraded from much earlier versions of CRM and included an attempt to solve some upgrade issues by dropping indexes. Initially our thoughts were that the dropping of the indexes were responsible for the problems. However it appears retrospectively that was a fragmentation of indexes that cause the issue. I cannot be exactly sure why the maintenance procedure that is run on the SQL Server did not rebuild and reorganise the indexes sufficiently that the global social function. However the following solution did work for us.

After doing this, we were then able to turn on the global search and weight the relevant period of time for it to complete the indexing. It appears to have fixed our problem with both global search returning valid results, and in-line search no longer broken when global search was unable.

if you are to upgrade or change the password that you utilise in your ZenDesk system for the account that has been set to synchronise data with the Microsoft CRM platform, you will notice that the synchronisation may not function correctly or may only perform a one-way synchronisation.

In the Users page, click New if you need to add new users. If you are editing a list of existing users, select the user you want to modify and click on the Manage Roles button.

In the Add Users dialog box, select the role for the group you want to configure. The two new roles created by the Zendesk integration are at the bottom. Click Next to select and assign the users to a particular role and to send email invitations. Make sure you give yourself the Zendesk administrator role for now so you can complete the setup.

Users are now configured to use the Z endesk for Microsoft Dynamics CRM integration! If you have pre-existing users, you can simply add the appropriate roles to each of your uses.

Note: For users with the Zendesk – Read configuration settings permission, they can individually add their own credentials by navigating to Settings->ZD Personal Settings in Microsoft Dynamics and clicking the New button to add credentials. Enter the Zendesk User ID andPassword then save the record and it will be applied when they access Zendesk tickets. The password will be encrypted so others cannot see the value.

Mac Mail using Exchange Connection to SmarterMail InteractiveWebs

To Set up your mac mail with and Exchange Connection using Mac Mail you will need to follow these instructions carefully.

On your Mac, open System Preferences.

Click Internet accounts.

Click Exchange.

Complete the display name, full email address and password fields.

Click Sign In.

Ensure that you’re email address is et for your User Name, and Type the internal and external URL to read: https://mail.interactivewebs.com/ews/exchange.asmx

Click Sign In.

An account summary screen will display. You can select or unselect any features that you do not wish to sync.

Click Done.

Click Add Account.

To Hide a DNN Page from the Menu

Note: This page will still be available to those who know the URL of that page (if for example you had put the page in a news letter).

Select Edit / Page Settings

Page Details / Unselect the Include in Menu Option

Update Page

The Page will no longer appear in the menu system. It can still be hit with the permissions that have previously been set.

Alternatively – To Change Permissions on the page to hide and stop access: http://www.interactivewebs.com/blog/index.php/general-tips/dnn-change-permissions-on-a-page-to-stop-users-being-able-to-access-the-page/

To Stop users (Either members or visitors) from being able to access a page on the DNN Site.

Select Edit / Page Settings

Select the Permissions Tab

Uptick the All users View Settings. With no view pages permissions set. No users other than the Default Administrator settings will be able to visit the page.

Update Page

Note This hides the page from users in the menu too. Alternatively you can just hide the page from the menu, but still allow people how know where the page exists to still access it by following this post:http://www.interactivewebs.com/blog/index.php/general-tips/dnn-hide-a-page-from-the-menu/

Problem

How to enable TLS 1.2 on Windows Server 2008 R2?

Resolution

QuoVadis recommends enabling and using the TLS 1.2 protocol on your server. TLS 1.2 has improvements over previous versions of the TLS and SSL protocol which will improve your level of security. By default, Windows Server 2008 R2 does not have this feature enabled. This KB article will describe the process to enable this.

Start the registry editor by clicking on Start and Run. Type in “regedit” into the Run field (without quotations).

Highlight Computer at the top of the registry tree. Backup the registry first by clicking on File and then on Export. Select a file location to save the registry file.

Note:

You will be editing the registry. This could have detrimental effects on your computer if done incorrectly, so it is strongly advised to make a backup.

Browse to the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

Right click on the Protocols folder and select New and then Key from the drop-down menu. This will create new folder. Rename this folder to TLS 1.2.

Right click on the TLS 1.2 key and add two new keys underneath it.

Rename the two new keys as:

Client

Server

Right click on the Client key and select New and then DWORD (32-bit) Value from the drop-down list.

Rename the DWORD to DisabledByDefault.

Right-click the name DisabledByDefault and select Modify… from the drop-down menu.

Ensure that the Value data field is set to 0 and the Base is Hexadecimal. Click on OK.

Create another DWORD for the Client key as you did in Step 7.

Rename this second DWORD to Enabled.

Right-click the name Enabled and select Modify… from the drop-down menu.

Ensure that the Value data field is set to 1 and the Base is Hexadecimal. Click on OK.

Repeat steps 7 to 14 for the Server key (by creating two DWORDs, DisabledByDefault and Enabled, and their values underneath the Server key).

Reboot the server.

Your server should now support TLS 1.2.

Note: This article cannot be used on a Windows Server 2003 (IIS 6). Windows Server 2003 does not support the TLS 1.2 protocol.

Reverting Back

If you make a mistake or something just isn’t right, you can revert back to your previous registry settings by opening the Registry Editor and importing the backup you made in step x.

When upgrading from CRM 2013 to CRM 2015 you get an error: Microsoft.Crm.CrmException: Database having version 7.0.1.129 is not supported for upgraded.

Cause:

This is usually because there is already a database that exists with the same ID. You will need to delete that Organisation in CRM deployment manager before upgrading the new organisation from the same name.

CRM 2016 Import Upgrade from CRM 2015 Failure: Timeout expired

On attempting to upgrade a Microsoft CRM Dynamics 2015 Database to CRM 2016 (without service pack) you receive a Failure: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding..

This happens at the System Check stage.

There are a bunch of suggestions online from earlier releases of CRM like 4.0 etc suggesting that you may need to change the timeout settings on the settings with some DWord changes in the registry. In this case it is not the cause.

Cause

Microsoft has again released an initial version of their software with some significant bugs. The biggest of these being that you cannot import your CRM 2015 database to upgrade to CRM 2016 if it has a Full Text Catalogue. Something that is likely if you have been using the improved searching functions of CRM 2015.

The Fix

All care and no responsibility with this one. The prudent process would be to either upgrade an existing CRM 2015 environment in place, which form all reports will correctly update the CRM database in question to CRM 2016 without error. Alternatively you can wait the months that are likely required for Microsoft to get around to releasing a patch for this problem.

Skip through the steps here as you normally would Noticing that it no longer stalls on the recheck before upgrade.

11. Once the upgrade has finished and you have your database imported and upgraded to CRM 2016, Open the SQL manager for the database in question again, and run a new query against the database as we did in step 3 above.

This time however we are going to paste the output we captured to clipboard in step 4 above, and run that output as a script.

Click Execute again. And you should be rebuilding the database indexes to a state that will function with the new CRM upgraded database.