News.mscrm-addons.com Blog

Resource not found Web API Error for Dynamics 365

Wed, 28 Nov 2018 16:33:01 GMT

This blog article outlines how to proceed if you get the following error message in your web browser: "Resource not found for the segment ‘ptm_......’.

A full error message can look like this:
Error from FetchWebApi: Ressource not found for the segment ‘ptm_mscrmaddons_keies’

We have only experienced this problem for OnPremisse installation so far.

The problem is, that the EntitySet property of our custom entities is not correct. Normally a manual reimport of the correct CRM solution with the option "Overwrite Customizations" can fix this.

How to fix for OnPremise installations

Navigate to the machine on which the Server part of the add-on is installed.
Open the installation directory (per default: "C:\Program Files (x86)\PTM EDV-Systeme GmbH\[PRODUCT NAME] Server for Microsoft Dynamics 365") -> subfolder "essentials"
If your CRM version is 9.0 or higher open the subfolder "9.0", for 8.2 versions stay in the "essentials" folder
Open a web browser: Dynamics 365 -> Settings -> Solution -> hit "Import"
Now select the correct solution from your current directory (depending on the error message):
- MSCRMADDONScomGeneral.zip for
  - “ptm_mscrmaddons_keies”
  - “ptm_mscrmaddons_schedulers”
  - “ptm_mscrmaddons_settingses”
  - “ptm_mscrmaddonscom_debugs”
  - “ptm_mscrmaddonscommetadatas”
  - “ptm_mscrmaddonstemps”
- DocumentsCorePack.zip for
  - “ptm_mscrmaddons_dcptemplateses”
- AutoMergeServerCore.zip for
  - “ptm_automergeworkingitemses”
  - “ptm_mscrmaddonscomamtriggers”
- For different resources please contact our support

The wizard will tell you that the same version of this solution is already installed. If the versions are different it could be possible that you have selected the wrong solution file!

Check "Overwrite customizations" and follow the wizard below.

Figure 2: Overwrite customizations

The problem should be solved now.

Sample
Error message: Resource not found for the segment ‘ptm_mscrmaddons_keies’
CRM version: 8.2
Installed product: DocumentsCorePack

To Solve:
Reimport the solution "MSCRMADDONScomGeneral.zip" of the folder "C:\Program Files (x86)\PTM EDV-Systeme GmbH\DocumentsCorePack Server for Microsoft Dynamics 365\essential".

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

How to check the installation status on Microsoft AppSource

Thu, 15 Nov 2018 15:29:43 GMT

This blog article outlines how to check the installation status on Microsoft AppSource. For example, if you started the installation of GroupCalendar form Microsoft AppSource. At a later time, you want to check if the installation is completed or if there were any problems. This article explains how this can be done.

First, go to the Microsoft 365 Admin Center. Within Dynamics 365 hit on ❶ "Navigate to other applications" and hit ❷ "Admin".

Next, please navigate within Microsoft 365 admin center to the section "Admin centers" as you can see below.

In the so opened management console select the correct ❶ organization and hit on ❷"Solutions".

Next, please select the product for which you want to get more information - in this case, GroupCalendar.

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

GroupCalendar fully supports Dynamics CRM RU12 (Polaris) and cross-browser compatibility

Thu, 28 Feb 2013 12:53:00 GMT

Our GroupCalendar for MS Dynamics CRM 2011 fully supports CRM RU12 (Polaris).
Up to now, the only workaround was to open the GroupCalendar in a new Internet Explorer-window.
Up from v5.45, GroupCalendar opens again directly within CRM. Furthermore, Chrome and Firefox are also fully supported by the GroupCalendar. This release also supports older CRM Rollups!

Supported Browsers

Internet Explorer 8
Internet Explorer 9
Internet Explorer 10
Chrome
Firefox

To benefit from the full support of CRM RU12 and cross-browser compatibility, on-premise customers just have to install the latest GroupCalendar version.
For CRM online-customers the GroupCalendar will be updated automatically, but they have to manually import a solution to their CRM system to view the GroupCalendar embedded in CRM.
Please continue reading for detailed instructions.

GroupCalendar for MS Dynamics CRM On-Premise

If you installed the GroupCalendar in an on-premise environment, you just have to update the GroupCalendar to at least v5.45. This update ensures that the GroupCalendar will load embedded within CRM and that it supports cross-browser compatibility.

You can download the latest version of GroupCalendar here.

GroupCalendar for MS Dynamics CRM Online

If you use the GroupCalendar for CRM Online, we will update your GroupCalendar installation automatically.

In the previous versions, the GroupCalendar was opened in a new Internet Explorer window due to a workaround.

With the latest version of GroupCalendar, you are able to use the GroupCalendar embedded in CRM again.

For being able to use and see the GroupCalendar embedded in CRM, you have to import and apply a solution to your CRM system.

Please note: If you don't update the solution, the updated GroupCalendar version will work but will continue to open the GroupCalendar in a new window!

How to import the solution to your CRM system

To import the solution to your CRM system, you need to download the following file:

MSCRMADDONScomGeneral.zip (440.50 kb)

After you have downloaded the file, please open your CRM system, go to Settings, click on Solutions and on Import.

Figure 1: CRM Settings > Solutions

This will bring up a dialog. Please select the downloaded MSCRMADDONScomGeneral.zip file and click on the [Next]-button.

Figure 2: Solution Import Dialog

Click on the [Next]-button in the following dialog in order to proceed.

Figure 3: Solution Information

Afterwards, please select Overwrite Customizations and Activate any processes.

Figure 4: Import Options

It could take some minutes until the solution is imported. After the import has finished, you will be noticed and you can close the window then.

Figure 5: Solution Import finished

After refreshing your CRM browser window, GroupCalendar will load embedded within your CRM system.

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.

Installing GroupCalendar and ActivityTools in an IFD/Claims-Based-Environment

Mon, 28 Nov 2011 20:09:00 GMT

This blog article will walk you through the required steps on how to install GroupCalendar and ActivityTools in a claims-based environment.

This article is valid for GroupCalendar for CRM 2011, 2013, 2015 and 2016 but only for CRM 2013 and older versions of ActivityTools. From CRM 2015 onwards ActivityTools does not have to be configured for IFD anymore!

The steps are the same for both products, so instead of an explicit product name, we will use the term the addon in this guide.

The IFD configuration for the GroupCalendar is as follows:

IFD-Tool -> Download Link you must have a login on our web site
For installing GroupCalendar you need at least version 5.12 from our Download Section
For installing ActivityTools you need at least version 5.13 from our Download Section

Before you start the installation, make sure that MS CRM is working correctly in IFD/Claims-Mode, including your ADFS, which should be installed correctly and configured to work with MS CRM.

More details on how to configure MSCRM for IFD/Claims can be found in the Microsoft Guide Configuring Claims-based Authentication for Microsoft Dynamics CRM 2011 Download

The following system configuration is the base for our guide.
Your setup will differ in these URLs, make sure you are replacing the URLs with your own URLs when following the guide.

Internal Url used to access Microsoft Dynamics CRM:
https://internalcrm.rc1ifd.ptm-edv.at

External Url used to access Microsoft Dynamics CRM:
https://[orgname].rc1ifd.ptm-edv.at

AD FS Server:
https://win2008domain.ptm-edv.at

The addon itself also requires a dns name:

https://activitytoolsserver.rc1ifd.ptm-edv.at (for ActivityTools)

https://groupcalendarserver.rc1ifd.ptm-edv.at (for GroupCalendar)

Basic installation/configuration of the addon:

Install the addon on the CRM Server.
You will be asked for the Logon Information. Fill in the internal IFD name of your CRM. In our case it is internalcrm.rc1ifd.ptm-edv.at
Now select the organization on which you want to install the addon and click on the [OK]-button.

Figure 1: Connection dialog
After the installation has finished, you have to open the IIS ( inetmgr.exe ) and go to Sites > the addon WebSite. Right click the ActivityToolsserver or GroupCalendarserver - WebSite and select Edit Bindings...

Figure 2: Select Edit Bindings...

On the Bindings, click on the [Add...]-button and select in the Add Site Binding the type https.
You also have to specify the port. In our example we use 4446

Figure 3: Add Bindings

With that we have made the website available for https. Now click on the [OK]-button.
Reselect the addon website and double click on the Authentication-item in the right side details pane.
Verify that the options Anonymous and ASP.Net Impersonation settings are enabled. ( Anonymous must be disabled with non IFD systems).
The addon URL must be added to your DNS Server.
Your DNS-Servers have to resolve the activitytoolsserver.[your-domain] or groupcalendarserver.[yourdomain] names correctly. That means, they should resolve it with the same IP-address your CRM Server has.
Please note: IF you are have an external DNS, make sure that both external and internal DNS are able to resolve the URL.
Extract the IFD-Tool (.zip-File), that you have downloaded before and execute the IFDSetupWizard.exe.
Follow the steps in the IFD Setup carefully.
Open your CRM in Internet Explorer and go to Settings > MSCRM-ADDONS.com Products > Open the addon. In the MSCRM-ADDONS.com Products form, select the MSCRM-ADDONS.com Settingskeys and search for the WebApplicationPort entry.

Figure 4: mscrm-addons.com Settingskeys
Open the WebApplicationPort and replace the existing KeyValue with the following:
[httpsPort]|[httpPort]|[claimsbased]|[addonname]|[debugging]

e.g.:
4446|5557|true|activitytoolsserver|false

We have finished the configuration of the CRM part and now need to configure the AD FS.

Please logon your AD FS Server and start AD FS 2.0 Management.
On the Actions menu located in the right column, click Add Relying Party Trust.
In the Add Relying Party Trust Wizard, click on the [Start]-button.
On the Select Data Source page, click on Import data about the relying party published online or on a local network, and then type in the URL to locate the federationmetadata.xml file.

This federation metadata is created with the IFD-Tool on the CRM Server. For example:
https://activitytoolsserver.rc1ifd.ptm-edv.at:4446/FederationMetadata/2007-06/FederationMetadata.xml

Type this URL in your browser and verify that no certificate-related warnings appear.
Click on the [Next]-button.
On the Specify Display Name page, type a display name, such as ActivityTools IFD, and click on the [Next]-button.
On the Choose Issuance Authorization Rules page, leave the Permit all users to access this relying party option selected, and then click on the [Next]-button.
On the Ready to Add Trust page, click on the [Next]-button, and then click on the [Close]-button.
If the Rules Editor appears, click on Add Rule. Otherwise, in the Relying Party Trusts list, right-click the relying party object that you created, click Edit Claims Rules, and then click on Add Rule.
Please note: Make sure the Issuance Transform Rules tab is selected.
In the Claim rule template list, select the Pass Through or Filter an Incoming Claim template, and then click on the [Next]-button.
Create the following rule:
• Claim rule name: Pass Through UPN (or something descriptive)

Add the following mapping:
i. Incoming claim type: UPN
ii. Pass through all claim values
Click on the [Finish]-button.
In the Rules Editor, click on Add Rule, and in the Claim rule template list, select the Pass Through or Filter an Incoming Claim template. Then click on the [Next]-button.
Create the following rule:
• Claim rule name: Pass Through Primary SID (or something descriptive)

• Add the following mapping:
i. Incoming claim type: Primary SID
ii. Pass through all claim values
Click on the [Finish]-button.
In the Rules Editor, click on Add Rule.
In the Claim rule template list, select the Transform an Incoming Claim template, and then click on the [Next]-button.
Create the following rule:
• Claim rule name: Transform Windows Account Name to Name (or something descriptive)

• Add the following mapping:
i. Incoming claim type: Windows account name
ii. Outgoing claim type: Name
iii. Pass through all claim values
Click on the [Finish]-button and when you have created all three rules, click the [OK]-button to close the Rules Editor.

You have finished the configuration and you should be able to use the addon in your IFD/Claims Environment now.

Troubleshooting:

Error message:

Figure 5: Error Message

Reason:

This indicates you are using a wrong certificate for the ADFS signing.

Solution:
Make sure the thumbprint in the web.config matches the one the token signing certificate in ADFS.

Error message:

Figure 6: Error Message

Reason:

This error could (also) indicate access rights problems with the certificates private key (mainly an issue for self signed certificates).

Solution:

Open your certificate store on the server (MMC, add certificate snapin for local computer) and find your HTTPS certificate. In the context menu, under all tasks select the manage private keys option and grant access to everyone.

Checklist for general troubleshooting:

Is the Setting WebApplicationPort still intact?
Are there any not http/https bindings in CRM?
Are there any not http/https bindings in the product website?
Is the DNS correctly resolving the products link?
Has the ConnectionProfile been created with IFD as connection type?

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