News.mscrm-addons.com Blog

AttachmentExtractor move email body

Tue, 30 Apr 2019 14:31:48 GMT

NOTE! This feature is still considered BETA and is used at own risk!

Overview

Starting with AE version 2017.26, AE is offering a new feature, allowing you to remove the email body text from within CRM and replace it with a text-only and line break conserving representation of the former email body. The complete email body content is moved to an azure blob storage and streamed into CRM on accessing the email.

CRM Timeline and CRM Activity overview will per default only show the shortened text to allow for more information in less space.

Why?

Emails are often consisting of mostly HTML formatting information. Inlcuding header, footer and maybe an embedded company logo, the content of an EMPTY email can be up to 30 kilobytes in size. In most companies, an email conversation usually consists of several replies and each reply will replicate the full HTML content of the previous emails, adding those 30 kilobytes AGAIN on every answer you write and possibly the same sized formatting information from the recipient of the email.

Asuming the above, a conversation, that contains an email being answered 4 times is generating a total overhead of 550kb. Still not much, but it adds up.

If you have 100.000 emails in your system and only half of them would be part of a conversation as sketched above, those emails add up to 10.000 conversations at 5 emails, occupying up to 5 Gb of space in the ActivityPointerBase table without containing any information yet. Also the actual email text is being replicated in each answer, growing the size even further. Not to mention that nearly all of the one-direction emails will contain a certain amount of HTML information on their own.

Remember, as of Q2 2019, the maximum table size of the WHOLE CRM database (excluding attachments) is 10 GB without additional cost.

How?

AttachmentExtractor is inspecting each email in CRM and looks for known seperators of emails. If any is found, the email is cut and then all HTML tags except linebreaks are removed from the email body. The original body is stored in an AzureBlobStorage and the plaintext representation of the email body is left in CRM. When you are opening an email, a plugin will retrieve the unchanged emailbody from the AzureBlobStorage and replace the stripped down version with the full content.

What is not supported?

AttachmentExtractor preserves both, the original modified by and modified on, therefore not all emails might be processed.

The email must habe a valid state/status combination
(e.g. you cannot have a completed (state) draft (status) email, as CRM does not support this combination
NOTE! As email state/status code pairs can be customized, AttachmentExtractor will only process emails, where those are still defined in CRM!
All activityparties of the email (from, to, cc, bcc) must be resolved to an existing entity in CRM
All activityparties of the email (from, to, cc, bcc) must have the "allow email" property set to allow.
Alternative email body storage options are NOT supported (due to accesstime) (Only AzureBlobStorage)

SharePoint Redirecting

Wed, 20 Mar 2019 14:03:18 GMT

AttachmentExtractor v.2017.21 and newer support redirecting the SharePoint access to a different server.

All Attachments moved to Sharepoint are saved as a link in Dynamics CRM. If you are moving to a new Sharepoint, AE can redirect the Sharepoint access for its AccessOnDemand-plugins to a different server.

To enable this behavior, you need to manually create a setting for the AttachmentExtractor product as described here (Link )

Name: SharepointRedirects

Value: A pipe (|) separated pair of strings defining the original Sharepoint location and the replacement one.

Example: https://old_sharepoint|https:/new_sharepoint

If required, multiple redirects can be defined, separated by semicolons (;)

Example: https://old_sharepoint/account|https:/new_sharepoint/account;https://old_sharepoint/contact|https:/new_sharepoint/other_contact

IMPORTANT:

This does NOT move the actual files on SharePoint, but only redirects the links saved in CRM, when using the retrieve plugins of AttachmentExtractor.

Multiple redirects are evaluated in order of definition and will stop on the first match

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Automerge Workflow MissingMethodException Error

Wed, 13 Dec 2017 12:29:40 GMT

If you are manually updating the latest versions of the AutomergeOnPremise Solution for Dynamics CRM 365 or installing a servicebased DocumentsCorePack for an IFD environment based on Dynamics CRM 365, your server is required to have .net Framework version 4.6.2 installed.

(Using any of our installers will prompt you for the .net framework requirement, if not found on the target machine.)

If you only have .net 4.5.2 your workflows will terminate with the following error :

Unhandled Exception: System.MissingMethodException: Method not found: '!!0[] System.Array.Empty()'.

Due to microsofts mandatory TLS 1.2 communication starting July 2017 for 3rd party applications, all of our products have been moved to use .net 4.6.2

Delete files on SharePoint, when the owning attachment in CRM is deleted

Thu, 02 Nov 2017 13:49:09 GMT

Following the european unions GDPR requirements, AttachmentExtractor version 2017.5 and later are introducing a new plugin/workflow tracing note and email deletion, allowing for removal of the files moved to sharepoint with AttachmentExtractor, when the note or email containting the link file in CRM is being deleted.

Please note, that the deletion tracking is disabled per default.

How to enable the deletion of Sharepoint items:

Download and import AttachmentExtractorCore solution version 2017.5 or later ( Download AttachmentExtractorCore 2017.5)

Create two settings as described in this article : Link

"EnableCascadeDelete"

A value of "true" enables the plugin/workflow in general.

A value of "false" will not remove any file on sharepoint.

"ThrowOnCascadeDeleteFailure"

Value of "true" means, that you will not be able to delete the item in CRM, if the plugin fails to remove the linked file(s) on Sharepoint

Value of "false" means, that the item in CRM will be deleted, regardless if the plugin fails to remove the linked file(s) on Sharepoint.

OrganizationURL provided by DiscoveryService is false

Wed, 04 Dec 2013 13:51:00 GMT

When using our products, the CRM discovery service is contacted to retrieve the service URLs for accessing the CRM WebServices.

In some cases the URL returned by the discovery service is not usable to contact the CRM WebService.

If you have physical access to the server, first check the WebAddress setup of CRM:

Go to your CRM server
Open the Deployment Manager (You need to be deployment administrator to be able to do this)
Select the Microsoft CRM Dynamics node in the tree
Bring up the context menu and select properties
Go to the tab WebAddress

Figure 1: Microsoft Dynamics CRM Deployment Manager

For example, if you changed the CRM port on the IIS, it would not automatically change the web-deployment addresses.

If you do not have server access or cannot change the WebAddresses for another reason please follow our advice below.

For CRM 2011 & CRM 2013:

Our software offers a way to bypass the DiscoveryServices organisation URL by enabling the following option:

Switch to the advanced tab on the connection dialog and enable the Override Organization URL option.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

How to synchronize TelephoneIntegration history with actual phonecalls

Thu, 19 Sep 2013 08:14:00 GMT

Synopsis:

This article explains the steps required to synchronize the actual call duration as recorded in the TelephoneIntegration history with actual phone calls in CRM.

Prerequisite:

This will only work for phone calls, that are created with the always store option enabled in the CTI clients options.

Procedure:

You will need to create a workflow and to trigger the required plugin. You can import the attached workflow to your CRM.

SynchronizationTemplate.zip (4.76 kb)

Or you can create a new workflow as follows:

Start with creating a new workflow and attach it to the entity MSCRM-ADDONS.com CTI CALL History.

Figure 1: Create new workflow

On the next page make sure, the start when-option is set to Record is created.

Add a new step of the type Wait Condition.

Figure 2: Specify the conditions of the process

Make sure all values are set as above BEFORE selecting the Created On-attribute (highlighted in gray).

The timeout suggested with 2 hours should be adapted to your needs. If your processing time for a phonecall is exceeding two hours, you should increase this timeout to a more appropriate value.

Figure 3: Process Information window

Your workflow is now containing a wait condition. You will have to add another step to update the record and trigger the workflow now.

Click on the highlighted row and add an Update Record-step.

Figure 4: Add record

Click on the [Save and Close]-button, then activate the workflow. The duration will be synced to the phonecalls after the set period of timeout.

Please note: The timeout must be sufficiently long to ensure the users are no longer editing the record, as the users saving the record would overwrite the duration again, if the sync has already taken place.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

AttachmentExtractor fails to upload large files

Tue, 20 Aug 2013 10:22:00 GMT

Issue:

AttachmentExtractor fails to upload files exeeding two megabytes of size (The actual size being blockes depends on various parameters and might actually be lower than the set value).

Check, if you see a message similar to the following in the event log or the log overview of the service configuration:

The request message is to big. The server does not allow messages larger than 2097152 bytes.

This is indicating, that the default upload method is not working due to server side message size restrictions.

Solution:

Note your servicename, as you have entered it, when creating the service. (e.g. MyService)

Open the registry editor on the machine, where the AttachmentExtractor service is installed.

Open the following key : HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDV-Systeme\AttachmentExtractorserver\Configurations

Find the key, named euqal to your servicename (e.g. HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDV-Systeme\AttachmentExtractorserver\Configurations\MyService)

Find the following StringValue UseSP15Upload
Change the value to true (Do NOT include the quotes)
Stop and Restart the service

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Addon-Update Behaviour (valid for builds from 1st March 2013 and beyond)

Fri, 01 Mar 2013 11:56:00 GMT

When you launch an upgrade installation of our products, the setup will update existing files and solutions in CRM. The default behaviour of upgrading a product installation has changed with all releases after 1st of March, 2013.

Running an upgrade of our products updates existing solutions in CRM according to the following rules:

When you start an upgrade, you will be prompted with the Connection Dialog. When you select a specific organisation on the Connection Dialog, like alist in the below example (see figure 1), the installer will update the mscrmaddons.com general solution for the selected organization. As this solution is shared between all our products, this update will affect all of our installed products.

Figure 1: CRM connection dialog, opening when running an upgrade

All product-specific solutions will be upgraded for the selected organization only. This behaviour has changed compared to versions built before 1st of March 2013.

Exceptions to the update-behaviour on the selected organization (valid for GroupCalendar and ActivityTools)

In case of an OnPremise- or a Hosted (IFD)-installation, the installer will update all organisations to which the installing user has access to, using the latest versions of the solutions distributed via the release.

This behaviour is mandatory, as the WebApplication is shared between organisations and therefore requires all organizations to use the same solution version.

For all other products, or in case an organisation was not reachable during the installation, you can update specific organisations. You can start the update from within the Installation States-overview (see Figure 2), which has also changed slightly regarding its user interface and functionality as described below:

Per default, the InstallStatus only analyzes the organisation selected in the connection dialog, as analyzing is a rather time consuming process.
Other available organisations have been moved to a dropdown box. Selecting an organization from this menu will start the analysis of the current install-state for the selected organisation only.

Figure 2: Installation States-overview

When you select , the full list of available organizations will be displayed.

Figure 3: Installation States-overview, list of all available organisations displayed

Additional information available in the Install States-overview

We also added three new columns which will be populated during the installation (or when you update an existing installation).

These columns show:

the current product version installed and used by that organization
the version of the currently installed mscrmaddons.com general-solution used by that organization
The product-specific CoreSolution used by that organization.

Please note: Existing installations will not display data in these columns.

To simplify the process of upgrading existing installations, we have added an option to multi-select installed organisations and to run an upgrade on all of them (see Figure 4).

Figure 4: Installation States-overview, multiple organisations selected for upgrade

As of now, only updating is supported for multi-selection.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Telephone Integration Client Unattended Setup

Tue, 23 Oct 2012 11:31:00 GMT

Introduction:

The following article outlines, how TelephoneIntegration Client is installed unattended. This enables installing the CTI client via policy or automatic install scripts.

Procedure:

This procedure basically requires four steps. Please follow each of them carefully!

1) Download necessary files

TelephoneIntegration client Versions 5.46 and above: available in the Download area on www.mscrm-addons.com
Batch/Reg-Files: attached to this article

2) Configure tiuai.reg- file:

This file contains the whole registry-setting of TelephoneIntegration Client.

Please note: you need to replace the placeholder values/dummy values of the registry file with your real values.

3) Modify the invoke_uai.bat - file:

Basically, it consists of two path-parameters:

Path of the Telephone Integration-client installation package
Path of the tiuaix(64/86).reg file

"PATHTOMSIFILE" /V"/qb /lvx* C:\instlog.txt UAIREGFILE=PATHTOREGFILE"

Example:"C:\tmp\UAI\Telephone Integration Client for MS CRM 2011.exe" /V"/qb /lvx* C:\instlog.txt UAIREGFILE=C:\tmp\UAI\tiuaix64.reg"

Please note: These paths must not include any kind of blanks in the values.

4) Run the batch-file:

Run the modified.bat file to start the installation routine.

Possible errors are logged in C:\instlog.txt, process information is written to your temp folder and to the installation directory of Telephone Integration Client.

Please send these files and, if possible, a screenshot of the error message to support@mscrm-addons.com in case of troubles.

To uninstall, you may try the follwoing command:

wmic product where "name = 'Telephone Integration Client for MS CRM'" call uninstall /nointeractive

ti_uai.zip (3.40 kb)

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Windows 8 WIF Framework installation (WindowsIdentityFoundation)

Mon, 03 Sep 2012 09:19:00 GMT

Windows 8 has the WIF Framework built in, therefore our installers will fail for now trying to update the WIF on windows 8 clients.

To activate WIF on Widnows 8 run Control Panel > Programs and Features > Turn Windows Features on or off.

Then check the Windows Identity Foundation 3.5 check box in the Windows Features dialogue box and click on the [OK]-button:

Figure 1: Windows features - Windows Identity Foundation 3.5

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Display Issues with ActivityTools pre 5.26 and RU8

Fri, 20 Jul 2012 11:02:00 GMT

As a preparation of the now rescheduled cross browser compatiblity for RU8, older versions of ActivityTools already had preparations built in, which will cause the Activity & Queue preview to fail. Please update to the latest Version to fix this issue.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Change Default settings for ActivityTool

Fri, 20 Jul 2012 10:23:00 GMT

ActivityTools default user settings can be predefined as follows:

Define the default settings for EmailPreview

Create a new settingskey called DefaultViewEmail as described here.

The Value should look similar to this :

"203;50;eListView;127;30000;30;false;350;300;0"

Explanation of values:

Value 203 (First option): 
A flag collection of email states to display: 

Draft = 1,            
Completed = 2,             
Sent = 4,             
Received = 8,             
Canceled = 16,             
PendingSend = 32,             
Sending = 64,             
Failed = 128

Calculate the sum of the states you want to display and change the 
value accordingly (e.g. 255 for all states)

Value 50 (Second option)
Items displayed per page, available values are 10, 25, 50, 100

Value eListView (Third option)
Selects the default view. 

Available options are :

eThreadedBySubject: Group by Subject
eThreadedByRegarding: Group By Regarding
eGroupByDate: Group By Date
eListView: ListView
eThreadedByRegardingNameAsc: Group By Regarding, Ascending by name
eThreadedByRegardingNameDesc: Group By Regarding, Decending by name
eThreadedBySubjectAsc: Group By Subject, Ascending by name
eThreadedBySubjectDesc: Group By Subject, Decending by name
eThreadedBySenderAsc: Group By Sender, Ascending by name
eThreadedBySenderDesc: Group By Sender, Decending by name
eThreadedByRegardingRestrictive:
Group By Regarding, exclude items with no regarding

Value 127 (Fourth option):
A flag collection of email fields to search :

From = 1,
To = 2,
Subject = 4,
Detail = 8,
Regarding = 16,
CC = 32,
BCC = 64

Calculate the sum of the states you want to search and change the
value accordingly (e.g. 127 for all fields)

Value 30000 (Fifth Option):
Do not change

Value 30 (Sixth option):
TimeRange to show:

All = 0,
Today = 1
Week = 7
30 Days = 30
90 Days = 90
6 Month = 180
Year = 365

Other options:
Do not change

Define the default settings for ActivtyPreview

Create a new settingskey DefaultViewActivity

The Value should look similar to this:

"4202|4212|4206|4214|4210|4207|4208|4201|4204|4209|4406|4411|4402;50;
eListView;127;30000;30;false;350;300;0;false"

Value "4202|4212|4206|4214|4210|4207|4208|4201|4204|4209|4406|4411|4402"

First option:

Pipe seperated Value List of activtyentitytypecodes to display, see CRM Documentation
for details on the typecodes.

All other options are identical to emailPreview, except value 4,
which is ignoring all fields but subject and detail.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

CRM entities created during the installation

Wed, 18 Jul 2012 16:18:00 GMT

Each product installs the following entities in CRM:

ptm_mscrmaddonstemp

Containing pre-user & temporary settings

ptm_mscrmaddons_settings

Container for ProductSpecific settings

ptm_mscrmaddonscommetadata

Containing metadata of CRM for products

ptm_mscrmaddons_key

Sepcific Key/value pairs for product settings

ptm_mscrmaddonscom_debug

Entity storing debug information for actions where no file access is allowed.

Also, each product installs a new Security Role, mscrm-addons general security role.
This security role is covering the required access rights for the entities listed above.

Product specific entites for DocumentsCorePack (DCP):

ptm_dcpspssiteconfig2011

Saves information about Sharepoint Storage of documents

ptm_mscrmaddons_dcptemplates

Contains the DCP Templates required for creating the documents.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

CTI Client Version expiring when only support expires

Tue, 17 Jul 2012 07:47:00 GMT

This is a known issue with versions previous to 5.28.

Please upgrade to at least this version : http://62.99.232.162/ti2011/tic530.zip to fix the problem.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

How to add NavBar entries manually

Thu, 26 Apr 2012 12:06:00 GMT

On some occasions, unmanaged customizations to forms might prevent the setup to correctly configure the navbar section of entities.

You would see an error similar to this one, telling about a transition of an unmanaged solution being impossible.

Figure 1: Error message (unmanaged solution)

The first step to solve this issue is to identify the causing entity.

You need to find the errortext highlighted in purple in the XML tree.

Figure 2: XML tree with errortext

Follow the tree up till you find the formXML node.
The localized name will tell you which entity is failing.
You need to uncheck this entity from all locations in the configuration.
You can process all other entities as normal.

How to add the NavBar entry manually

Please note: You need to be an administrator to be able to complete the following steps.

1) Open up any record of the entity you want to customize (Account for this example) and open the form designer.

Figure 3: Open entity and the form designer

2) Enable the NavBar editing...

Figure 4: Click on the [Navigation]-button

3) ...and insert a new item

Figure 5: Insert new item

4) On the following dialog enter a name (i.e. EmailPreview or ActivityPreview) and select the ptm_Icon16x16 webresource for the icon

Figure 6: Select ptm webresource

5) Select the ptm_webApplicationPreloaderActivityPreview to add the ActivityPreview functionality or select the ptm_webApplicationPreloaderEmailPreview to add the EmailPreview.

If you want to enable both, you need to repeat the same steps for each item.

Figure 7: Add the ptm_webpplicationPreloaderEmailPreview

6) Close all forms, and do not forget to save & publish the changes! (Or the changes will not show).

Figure 8: Save and publish changes

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Disable ribbon buttons for non-licensed users

Wed, 18 Jan 2012 11:56:00 GMT

Starting with version 5.23 / TI and version 5.19 / DCP in combination with LicenseManager 5.2, the ribbon buttons will be disabled on perUser licensing, if the user is having the acccess flag for the product set to no.

Licensemanager 5.2 creates a new setting, IsPerUserLicense with value true|false when importing a licensekey.

Based on this setting being true and the Users access flag (perUserLicensing[Product]), the button will be disabled.

The functionality is requiring general solution v46.0.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

WindowsXP and WIF (WindowsIdentityFoundation)

Mon, 12 Sep 2011 14:33:00 GMT

!! Please note: This only applies to CTI Versions 5.30 and below !!
!! Since Microsoft has changed the EULA of their WIF SDK we are now allowed to include all required files into our setups !!

All of our client products (Telephone Integration and DocumentsCorePack Client) need the WindowsIdentityFoundation Framework to be able to connect to CRM 2011.

Unfortunately the WIF Framework is not officially supported on WindowsXP by Microsoft, but there are 2 ways to make this work on a WindowsXP OS.

Requirements:

Microsoft .Net Framework 3.5 & prerequisites installed on the Windows XP Client.

You need one machine that is supported for having the WIF Framework. (Vista or higher)

Locate the Microsoft.IdentityModel.dll.

Option 1:

Register the Microsoft.IdentityModel.dll in the GAC (GlobalAssemblyCache) of the Client you want to install it on.

This makes the DLL available to any application on the specific Client.

A detailed How-To can be found here : http://mkonrad.blogspot.com/2010/11/crm-2011-filenotfoundexception-when.html

Option 2:

Copy the DLL to the desired target installation folder BEFORE installing the product.

You will manually have to create the folder at first.

This will enable the WIF only for the product targeted, narrowing down the possibilities of side effects.

Please note: Both ways are not supported by Microsoft.

It is not guaranteed, that this method will still work with further updates to the WIF Framework.

If Microsoft chooses to udpate the WIF Framework you might also have to replace the DLL with a newer version.

MSCRM-Addons can also not guarantee for the functionality or any possible side effects.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

How to install DocumensCorePack Client unattended

Mon, 18 Jul 2011 11:24:00 GMT

To install DocumentsCorePack Client for MS CRM 2011/2013/2015/2016/D365 unattended, you need to supply a registry file with the required registry settings.

Unattended install is available for DocumentsCorePack Client Version 5.18 and Version 6.5 or above.

Below, you can download templates to perform the unattended install.

The below files are set up for x86 and x64 systems.

The templates contain inline documentation regarding the possible settings that can be set for the Client application.

The below described keys and place holder have to be replaced to have a valid registry file for the installation process.

Please note: The current examples are set up for http. If you are using https you also have to adjust the protocol in these files!

uai_ RegCRM2013_x86_x64.reg (8.90 kb)

uai_ RegCRM2011_x86_x64.reg (8.88 kb)

This is a blank registry file containing all required keys. You need to replace the following tags with your actual CRM data:

YOURCRMSERVER:PORT: The URL of the CRM server without any protocol information, e.g crm:5555

UNIQUEORGANISATIONNAME: The unique name of the organization you want to connect to

These both keys also have to be applied to the

DiscoveryCrmServiceUrl=[PROTOCOL]:
//[YOURCRMSERVER:PORT]/[UNIQUEORGANISATIONNAME]
/XRMServices/2011/Organization.svc.

PROTOCOL: Either http or https.

ORGANISATIONFRIENDLYNAME: The display name of the organization.

OrganisationFriendlyName contains the Organization name.

While not vital, it should be changed to reflect the correct Organizsation name.

The path variable in the templates has to be adjusted as well depending on the achritecture of the client

(Program Files (x86) or Program Files)

If your discoveryservice is using Https (Usually its the same protocol as your CRM), the entry

HttpsDiscovery

needs to be set to true.

You can then launch the setup with the prepared registry file similar to the batch file launch.bat (116.00 bytes)

"[DocumentsCorePackInstallFolderAndFile]" /V"/qb /lvx* C:\instlog.txt UAIREGFILE=[RegFileLocation]\[RegistryFileName].reg"

The tags DocumentsCorePackInstallFolderAndFile needs to point to the correct installation source folder and filename.

RegFileLocation needs to point to the folder of the prepared registryfile.

If you have changed the registry filename previously, you need to adapt this change in the command as well.

RegistryFileName: the filename has to be adjusted depending on the file you are going to use for the install process.

That's it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Connection dialog retrieves organizations, but refuses to connect

Mon, 30 May 2011 09:47:00 GMT

Check the log textbox if the following statement is present (might be accomodated by a 401 exception).

The HTTP request is unauthorized with client authentication scheme Anonymous. The authentication header received from the server was NTLM, Negotiate

Make sure CRM website is supporting anonymous authentication on ROOT level.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Service Unavailable after error in upgrade process

Sun, 29 May 2011 08:28:00 GMT

Receiving a service unavailable response on a website usually indicates, that the application pool of the site is not running.

To solve this issue, open your InternetInformation Management and verify all required app pools are started.

The page content would look like this:

Service Unavailable

HTTP Error 503. The service is unavailable.

Embedded in CRM the error would look like

Figure 1: Service Unavailable error message

The issue can be caused by problems during the upgrade, because upgrading stops the app pool in order to avoid issues with files in use.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.