We realized, that after installing Live Messenger we do not see the Contact/System User icon anymore in our MS CRM system. 

Figure 1: Live Messenger 

Instead we get this IM presence icon. In 99,9 % it is grey because no one has all the CRM contacts in his Messenger and therefore it is uninteresting for our users.

I now tried to find out how we can turn this off and it is not very easy to find information about this presence information.

...

There is one setting in CRM to turn this off/on for Grid Views.

Open the fullname and click on Change Column Properties and you will find the checkbox Enable presence for this column.

Figure 2: Change Column Properties
 

You are not able to turn this off/on for system views and you cannot modify it for lookup fields.

Because these configuration possibilities are very limited, I looked for another possibility to turn this off generally.

What I found out was that the “name.dll”, which comes with Office. So my solution to turn off the presence was to unregister the “name.dll”.

Figure 3: name.dll

At the moment, I do not see any drawbacks of this. I am also sure that if I will upgrade the Messenger or Office, it will register again. But for now this is the solution I use to get rid of this presence information.

I tested this only with Windows 7 and Office 2007.

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

This article contains a detailed guide on how to find out the version number for each mscrm-addons product in CRM 4.0.

…

Activity Tools

First open the Activity Tools Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/ActivityTools for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the Editor.dll-file and click on Properties.

Finally select the version-tab and click on File Version.

Figure 1: ActivityTools editor properties

Alerts:

First open the Alerts Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Alerts for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the Alerts.dll-file and click on Properties.

Finally select the version-tab and click on File Version.

Figure 2: Alerts editor properties

Dashboard:

First open the Dashboard Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Dashboard for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the “Dashboard.deploy.dll”-file (the DashBoard.dll file is obsolete) and click on Properties.

Finally select the version-tab and click on File Version.

Figure 3: Dashboard editor properties

Documents Core Pack Server:

First open the Documents Core Pack Server Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Documents Core Pack Server for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the DocumentsCorePackServer.dll-file and click on Properties.

Finally select the version-tab and click on File Version.

 Figure 4: DocumentsCorePack Server properties

Documents Core Pack Client:

In MS Word, first click on the www.mscrm-addons.com-tab and click on the [WordMailMerge Settings]-button.

Figure 5: [WordMailMerge Settings]-button

In the settings window select the About Documents Core Pack–tab and you will be provided with the version number.

Figure 6: WordMailMerge Settings

Group Calendar:

First open the Group Calendar Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Group Calendar for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the GroupCalendar.dll-file and click on Properties.

Finally, select the version-tab and click on file version.

Figure 7: GroupCalendar properties

Power Search:

First open the Power Search Installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Power Search for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the PowerSearch.dll-file and click on Properties.

Finally select the version-tab and click on file version.

Figure 8: PowerSearch properties

Telephone Integration Server:

First open the Telephone Integration Server installation folder

(C:/Program Files/PTM EDV-Systeme GmbH/Telephone Integration Server for MS CRM 4.0)

and then navigate to the bin-folder. Do a right click on the OutBoundCallConfig.exe-file and click on Properties.

Finally, select the version-tab and click on file version.

Figure 9: OutBoundCallConfig.exe properties  

Telephone Integration Client:

Right click on the TelephoneIntegration icon in the taskbar and then click on Info.

Figure 10: TelephoneIntegration Icon

A License window will pop up and in the lower left corner you can see the version number.

Figure 11: License Info - TelephoneIntegration

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

We once had the problem that some emails with a long text in it were taking ages till they were send. We are using the email router to send and receive emails to our support team.

As we moved some months ago from normal exchange to BPOS my first suggestion was that it has to do with the connection between BPOS and the Emailrouter. ( RU 14)

In the event-viewer I recognized the following entry:

#61042 - An error occurred while the outgoing email message with the subject Re: urgent problem with DCP config PTM CRM00114110 CRM: 0000132293' for ExchangeOnline: http://[servername]/PTMEDVSystemeGmbH for delivery through https://autodiscover-red002.mail.emea.microsoftonline.com/ews/Exchange.asmx The request failed with HTTP status 413: request entity too large,
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) bei Microsoft.Crm.Tools.Email.Providers.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.SendMessage(MessageType mailMessage) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.ProcessMessageInternal(email emailMessage)

...

So I created a case by Microsoft to let them look through this behavior. In this last month I was forwarded 3 times from the CRM team to the BPOS team and back. Today was the big day and the wonderful guy from the BPOS team was able to give the right hint with the following description in his email to me:

For messages to be sent to Exchange Online through the Email Router for CRM, the Secure Sockets Layer certification must be enabled for Exchange Online and your Email Router to communicate. The default size for the buffer in the SQL Server is 48k and every email with more text results in error HTTP status 413: request entity too large.

The solution to this is to logon to your SQL server and follow these instructions:

Increase the size of the UploadReadAheadSize property on your SQL server:
- Click Start, click Run, type cmd, and then click on the [OK]-button.
- At the command prompt, type the following:

cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 500000
Please note: This command changes the UploadReadAheadSize property to 500 KB (500,000 bytes).
- Press the [ENTER]-button.
- By running this command, you update the Microsoft Internet Information Services (IIS) metabase so that you can upload files that are as large as 500 KB.
Please note: In certain situations, you may have to set the UploadReadAheadSize property to even larger than 500 KB.

In my case I had the SQL Server and the CRM Server on one machine and I executed this script and I was not able to reproduce the error. The conclusion is that this had nothing to do with BPOS and everyone also with a normal Exchange can come into this problems.

The dangerous thing is that you do not realize that behavior easily, because you send your email from the web client and the email closes successfully. If you do not explicitly look for the email, you do not see that it was not send or delayed.

If you have the same problem, I hope this will solve your issue too.

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

Before you can upgrade your CRM 4 to 2011, you will need to uninstall all 3rd party addons and check that all buttons have been deleted. After the migration you can then install the latest version of each addon.
 
Should you have not done this, then it will be more complicated to get rid of the buttons and icons before you can install the CRM 2011 addons.

…
 
If you still have NavigationBar items which need to be removed, then you can do this by using the Forms customization option.

If you have Ribbon Buttons we recommend the following blog entries: http://dynamicscrm2011.wordpress.com/2011/04/05/ribbon-customization/

Another possibility to modify the ribbons gives you the Visual Ribbon Editor http://crmvisualribbonedit.codeplex.com/ 
or the Ribbon Workbench http://www.develop1.net/public/page/Ribbon-Workbench-for-Dynamics-CRM-2011.aspx

If you have SiteMap Buttons you want to remove, we can recommend the following blog entry with a description on how to modify the SiteMap in MS CRM 2011:

http://www.powerobjects.com/blog/2011/03/22/sitemap-editing-in-crm-2011/

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

Here are a few troubleshooting steps you can check if the Service Based Printing does not work as expected:

1. Make sure the service is running and configured for both document generation and printing jobs.
    
2. Specify a service user on the first configuration tab (General).
    
3. Make sure that the specified user is the same as the user that is configuring the printer.
    
4. Make sure the printer is added to the server as a local printer and that it has been added by the same user which is running the service.
    
5. Make sure that the printer has been added to the service and that it is possible to print a test page with it from the service.

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

When you try to delete a solution, it will show you an error message if there are any dependencies.

To solve this issue, please follow the steps below.

… 

Copy the GUID from the error log which is retrieved from the error message:

From the Logfile:

openStdWin(“\x2ftools\x2fdependency\x2fdependencyviewdialog.aspx\x3fobjectid\x3d\x25…GUID…\x257d\…)

Now navigate to the following URL:

https://YOUR CRM URL/tools/dependency/dependencyviewdialog.aspx?objectid=GUID&objecttype=7100&operationtype=dependenciesforuninstall

Replace the “YOUR CRM URL” with the your own CRM system's URL and replace the GUID with the GUID retrieved from the above step.

You will be provided with a list of dependencies, which you can manually remove from your system now.

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

This article explains the security roles that must be assigned to users that should be allowed to use our Add-Ons.  

...

The following securityrole is mandatory by all our solutions:

• MSCRM-Addons General Security Role

Next to this, there are Solution-specific security roles that need to be assigned:

DocumentsCorePack:

• DocumentsCorePack Security Role
• MSCRM-ADDONS.com AutoMerge

TelephoneIntegration:

• TelephoneIntegration Security Role

SmartBar:

• MSCRM-ADDONS.com SmartBar

PowerSearch:

• MSCRM-ADDONS.com PowerSearch

ActivityTools:

• MSCRM-ADDONS.com ActivityTools

AttachmentExtractor:

• Solution runs with service user requiring sysadmin rights.

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

When using per User licensing, it is mandatory to enable all users that should be licensed within CRM. It often occurs, that after installing the license via the License Manager, the below screen appears:

Figure 1: License Manager - Preview License 

This is due to the fact, that the user (usually an admin), who is running the license-manager is not a licensed user at this point.

To enable this, specific users you will have to follow the below steps. 

... 

1) Open the User via CRM->Settings->Administration->Users

Figure 2: CRM Settings (User)

2) Set the Per user licensing for [PRODUCT NAME]-bit value to true:
Depending on the installed addons, a Per user licensing-field will be visible on the User form. Here, it is possible to enable users to use our addon (see Figure 3).

Figure 3: Enable user to use addon

When you now restart the licensemanager, you will see that the user-account has changed due to the number of activated users AND, if the admin has been enabled too, the red cross will be gone:

Figure 4: Licensce Manager - Preview License 

Please note: Its possible to install the license, although the red cross appears in the [Number of user licenses]-row. Therefore its not mandatory to set the admin user itself to true.

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

Sometimes it can happen, that you want to execute a fetch simply to see if it works. And also see the results.

With the attached solution, you have the possibility to execute a fetch. Please note that this solution is not designed to generate fetches!

...

1. Download the solution and import it into your CRM System ExecuteFetchXML_1_0_0_0_managed.zip (5.35 kb)

2. Open the solution with a doubleclick.

Figure 1: Open solution
 

3. Then you'll find a simple text box and a [Fetch]-button on this form. Just enter your fetch in the textbox and hit the [Fetch]-button and you'll be presented with the fetch result.

Figure 2: Fetch command window - blank with [Fetch]-button

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

If you have configured your CRM for IFD and also have enabled our FileExplorer Integration, Internet Explorer (IE) will either not load the FileExplorer or show a message about insecure content.

Figure 1: FileExplorer not visible

Figure 2: Internet Explorer shows insecure content warning

If you run into this problem, please follow the steps below to resolve this issue.

...

There are two IE settings you need to modify

1. Add the DocumentsCorePack (DCP) Server FQDN DNS name to the trusted sites.
Open the IE Settings and on the Security-tab page, switch to Trusted Sites and click on Sites to add the fully domain name of DocumentsCorePack (e.g. https://documentscorepackserver.c3.ptm-edv.at)

Figure 3: IE Settings showing how to add DocumentsCorePack to the trusted sites

2. Modify the Local Intranet zone to allow mixed content
Open the IE Settings and on the Security-tab page, switch to Local Intranet and click on Custom Level to modify the settings.

Figure 4: IE Settings showing Local Intranet options

Then you have to scroll down to Miscellaneous and enable Display Mixed Content

Figure 5: Enable Display Mixed content

After you have applied these settings, please restart Internet Explorer.
Hereafter, the FileExplorer documents will be shown without any prompt in the an IFD environment.

Figure 6: FileExplorer Documents in IFD

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

This article provides a step-by-step upgrade path of our solutions to the new MS CRM 2015 release!

...

From MS CRM 2013

1. Request License: To run our addons on MS CRM 2015, you need to request a license for the CRM 2015 version of our solution.
   Upgrades of MS CRM are covered with our support & maintenance.
   Thus, every customer with a valid support contract can go ahead and request a license by sending an email including the unique CRM organization unit name
to support@mscrm-addons.com

How to get the unique CRM organization unit name? 
Link:Get Unique Organization unit name


2. Check currently installed version
   DocumentsCorePack: If you are using DocumentsCorePack please ensure that the server component is on v 6.8 or higher.
   How to check the version number?
   Link: Version number guide
   You can download the most current version for CRM 2013 from Downloads 
   
   All other addons are fine to upgrade from any CRM 2013 version! 
3. Upgrade your CRM instance to MS CRM 2015!
   
   
4. Download the CRM 2015 version of our solution
   You can download the version for CRM 2015 from our Download – center (Login required)
    http://www.mscrm-addons.com/Downloads.aspx
   
   
5. Install CRM 2015 version of our solution
   Once you start the installer it will detect the currently installed version and perform an upgrade automatically. You will not loose any configuration during this process!
   
   
6. Install new License
   Finally you will need to install the new license using the LicenseManager that comes with the installation of our solution (accessible via the Start Menu or Installation folder)

FROM CRM 2011

Microsoft requires to upgrade to CRM 2013 prior to being able to upgrade to CRM 2015. This being said, you will need to upgrade our solutions to CRM 2013 too before you can proceed with your Upgrade to CRM 2015 as above described.

Upgrade paths from MS CRM 2011 to MS CRM 2013

• DocumentsCorePack
• GroupCalendar
• TelephoneIntegration
• PowerSearch
• AttachmentExtractor
• ActivityTools
• AutoMerge

SmartBar is THE exception when it comes to upgrades previous to CRM 2013, because SmartBar was known as RecordCounter before. RecordCounter did not have as many functionalities as SmartBar, thus, it does not work with Microsoft Dynamics CRM 2013!
This means, if you want to upgrade the RecordCounter to SmartBar (CRM 2013), you simply have to deinstall it. Click here to get an overview how to deinstall RecordCounter. 

After the deinstallation you can install SmartBar for CRM 2013. Up from that version, the update for SmartBar is similar to the above described process. 

FAQ

• How do I upgrade form CRM 4.0?
  Upgrading from CRM 4.0 requires to uninstall our solutions and reinstall the solutions for CRM 2015 after performing the upgrade. If you need assistance – please contact support@mscrm-addons.com
  
  
• What if my CRM Online instance was upgraded without checking the current version of our addon?
  Please send an email to support@mscrm-addons.com– we will check the status and help you get going asap!

That’s it!  
We appreciate your feedback about the upgrade path and your CRM 2015 user experience. Please share your thoughts by sending an email to office@mscrm-addons.com

Sometimes, you may be asked to create a new settingskey for one of our products. This article outlines how to do so. 

...

1. Open your CRM in the InternetExplorer.

2. Navigate to Settings in the CRM sitemap.

3. Within the settings, navigate to MSCRM-ADDONS.com Products in the Extensions-area of the sitemap. 


Figure 1: MSCRM-ADDONS.com Products in CRM settings

4. Activate the checkbox in front of the product (1) for which you need to create a new settingskey (in this example TelephoneIntegration) and click on the [Edit]-button.

Figure 2: View and edit MSCRM-ADDONS.com Products

5. A new window opens. Within this new window, navigate to the MSCRM-ADDONS.com settingskeys of the product in the menu on the left (1) and click on the [Add New MSCRM-ADDONS.com Settingskeys]-button (2).

Figure 3: View/add settingskeys of/to a MSCRM-ADDONS.com product

6. A new window opens. In this window, you have to define the name of the settingskey in the Name-field and its value (true) in the KeyValue-field. Once you have created the new key do not forget to save your settings by clicking on the [Save and Close]-button.

Figure 4: Create a new settingskey for a MSCRM-ADDONS.com product

Please note: If the new key is intended for a Client application like DocumentsCorePack or TelephoneIntegration, you need to restart the Client application.
(Otherwise, the changes will not be applied to the client.)

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

· MS Dynamics CRM 2011 On-Premise/Hosted (IFD)/Online
· RollUp 12
· MS Sharepoint 2010/2013/Online
· MS Office (x86, x64) 2007/2010/2013
· and which of them support cross-browsing.

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 useable to contact the CRM WebService. 

...

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

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

Figure 1: Microsoft Dynamics CRM Deployment Manager

e.g.: If you changed the CRM port on the IIS, it would not automatically change the webdeplayoment 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.

+++++++++++++++++++++++++++++++++++++++++++++++++++

   Please note: This article applies to CRM 2013 as well as to CRM 2015/2016

+++++++++++++++++++++++++++++++++++++++++++++++++++

When ordering licenses, you will be asked for the organisation unit name of your CRM system.
This information is mandatory in order to create a license.
Below, you will find a short description on how to get the necessary information for CRM 2013 and CRM 2015/2016.

...

Open you CRM in your preferred browser and navigate to Settings.

Figure 1: Navgate to the CRM Settings. 

Navigate to Customizations and Developer Resources.

Figure 2: Developer Resources

Here you will find the unique organisation name.

Please note: For CRM 2013 as well as CRM 2015/2016, the Unique Organisation Name is required.
Besides, our key is case sensitive and does not work if the names do not fit.

This is where you find the unique name in CRM 2013:

Figure 3: Unique name in CRM 2013

This is how it looks like in CRM 2015/2016: 

Figure 4: Unique name in CRM 2015/16

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

To facilitate and to speed up the issuing process of a new license, we kindly ask you to
send us a short e-Mail including answers to the following questions.

…

Which product do you need the license for?

- DocumentsCorePack Client Based
- DocumentsCorePack Server Based
- TelephoneIntegration
- AttachmentExtractor
- GroupCalendar
- ActivityTools
- PowerSearch
- SmartBar

Which CRM version do you use at the moment?

- CRM 2011
- CRM 2013
- CRM 2015
- CRM 2016

What kind of CRM do you use?

- CRM Online
- CRM OnPremise
- CRM with ADFS Authentication (IFD)

How many active CRM users are there in your company?

What is the unique organization name of your CRM Organization?
(If you need more information on the unique organization name, please click here)

Additionally, we provide a license requirements form in order to facilitate the response. 
Please find the form here:
mscrm-addons.com_license_requirements.docx (41.26 kb)

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

A valid license key is the key to a smoothly running mscrm-addons.com product. Having an invalid license stops the whole product from working. An invalid license will never have any impact on your CRM, it only limits the addon itself.

…

Reasons for an invalid license:

• Wrong license Organization Unit
• Usercount has execeeded the granted licenses
  (Stops whole product, not only for the excessive users on all license models)
• Upgrading the product after having the support contract expired
• Trial license has expired
• License was created for a different CRM version

If your license has expired because of one of the above reasons, you must renew it. This can be done by installing a new license key.
This article provides you with an overview of the 3 main ways to install a new license key to your product.

Option 1) Install the license key via the On Premise License Manager
               The license manager provides you with an overview of your license. 
              (Applies to all products that have been uploaded via .msi-file)

Option 2) Install the license key via the Web License Manager   
               (Applies to PowerSearch and ActivityTools at the moment, does not work with DocumentsCorePack Client)

Option 3) Our support team installs the license key for you.
              Please contact our support-team via support@mscrm-addons.com 
               This applies to DocumentsCorePack and Group Calendar, but only
               in the subscription mode. (CRM Online ONLY!)

Please click on the option that matches your product. You will be provided with further information on how to install the license key properly.

For additional information, have a look at How to install your license key. 

(Blog still being reviewed)

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

Thank you for using our mscrm-addon!

The following overview was created to support you when it comes to the installation of a new license key. 

...

There are many reasons why a license key has to be installed, but there are only three main possibilities how to install your license key. They depend on the addon you would like to install:

Option 1– Install the license key via the On Premise License Manager

Option 2– Install the license key via the Web License Manager

Option 3 – Our support team installs the license key for you.

The following table contains all our products and license key installation options.
Please click on the x that matches your product. You will be provided with further information on how to install the license key properly.

(Blog still being reviewed)

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

This blog explains how to change your subscription Credit Card details on our homepage.

…

(1) Please go to www.mscrm-addons.com and click on the [LOGIN]-button placed in the upper right corner. Insert your credentials.

Figure 1: mscrm-addons.com Login
 

(2) Click on the [MY ACCOUNT]-button in order to proceed.

Figure 2: My Account 

At the bottom of the overview, you will find an overview of your subscriptions including Credit Card data etc. If you haven't 

made any subscriptions yet, your overview looks like the below screenshot: 


Figure 3: Overview if no subscriptions were made yet

If you have already made subscriptions, the summary will look like the below screenshot:

Figure 4: Overview if subscriptions have already been made 

Please use the blue buttons in Figure 4 in order to configure your subscriptions 

The [Cancel Subscription]-button allows you to cancel your subscription

The [Update payment]-button enables you to update your payment details.

The [Modify package size]-button enables you to change the size of your package.  

In the above example, the service will stop working automatically at 2016-12-22 if the information will not be changed. 

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

This article provides step-by-step instructions regarding to the upgrade of our addons to Microsoft Dynamics CRM 2016.

Our addons provide a wide range of helpful features! But before you will be able to enjoy the various benefits of or addons for MS CRM 2016 there is some work (at least let us call it like that) waiting for you:

The upgrade.

...

Do you know Murphy’s 4th Law of Computing? You do, don’t you? No?*

Anyway, we are not here to make jokes (seriously!), but to make sure that your product works impeccably. Having that in mind, let us start:

There are three possible scenarios from which you could start your upgrade.

1) The ideal case

You are the delighted owner of one of the following addon versions:

DocumentsCorePack (DCP) Client > 7.103 
TelephoneIntegration Client > 7.100
DocumentsCorePack (DCP) Server > 2015.109  
TelephoneIntegration Server > 2015.100
AttachmentExtractor, SmartBar Server, ActivityTools > 2015.200

In this case, an upgrade from MS CRM 2015 to 2016 is possible without extra work.

2) The semi-ideal case:

Your current version is none of the versions mentioned before, but you have not tried to upgrade your CRM to the 2016 version yet. No problem – simply upgrade to one of the versions mentioned above and then upgrade to MS CRM 2016.

3) The – well, we are going to work it out together – case:

Your addon's version is none of the versions mentioned before, but you have already upgraded your MS CRM to the 2016 version. If so, simply upgrade to one of the versions mentioned in the first case.
Probably you will stumble over the following failure notice:

Figure 1: Upgrade failure notice 

Yes. We know. You also wanted to be one of the ideal case–users. But imagine – in that case you would not be able to read that wonderful blog and I wouldn’t have a job. So let’s focus on the positive aspects.

What is more: We have the perfect solution for your issue. Simply click on the [OK]-button, then press the [Cancel]-button and finally, click on the [Yes]-button (the short version of "Did you turn it on and off again?" ;) ).

Figure 2: Cancel setup 

After a few seconds, a new CRM connection setup-dialog appears. For further information on the CRM connection dialog, please have a look at our documentation of the same name. 

Figure 3: CRM Connection setup dialog 

Select your preferred organization and click on the [OK]-button. Follow the upgrade instructions as usual…

Figure 4: Upgrade (example addon: TelephoneIntegration Server)

… and the upgrade will work out perfectly!

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

* Murphy’s 4th Law of Computing: When the going gets tough, upgrade.