web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Installation error ADX Studio Portals for Dynamics 365 (On-Premises)

(0) ShareShare
ReportReport
Posted on by 390

Hi, 

We have a fresh installed Dynamics 365 On-Premises server up and running and working as it should and want to install ADX Studio Portals, however upon installing the different components like the Adxstudio Portals Base

I get Solution import failed. with the following error:

[pluginassembly] Adxstudio.Xrm.Workflow.AssignWebRole, Version=1.0.1.0, Culture=neutral, PublicKeyToken=d3ebcae416f78f44 - Plugin Types import: FAILURE. Error: Plugin: Adxstudio.Xrm.Workflow.AssignWebRole, Version=1.0.1.0, Culture=neutral, PublicKeyToken=d3ebcae416f78f44 of PluginTypeName: Microsoft.Crm.Entities.PluginType and PluginTypeNode: System.Xml.XmlElement caused an exception.

Any ideas on how to solve the issue?

thanks for any help on this

regards

Martin

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Shan McArthur Profile Picture
    on at

    Is this a solution upgrade issue?  I have only seen that in upgrade scenarios.  For upgrade scenarios this is a known bug that will be resolved in the next update.  That said, please do not install new deployments of legacy Adxstudio 7 portals as that product is going to reach its end-of-life support date on Aug 1, 2018 and no new licenses are being sold.  You should consider moving to our online portal service or the source code distribution.  See https://blogs.msdn.microsoft.com/crm/2017/09/14/changes-coming-for-legacy-adxstudio-portals-v7/  for more information

  • icimasa Profile Picture
    390 on at

    Hi,

    this is actually not an upgrade, but a clean install. But I have seen the road map today that support will end for this product and I see your point and we have go back to the project manager with this information and see what options we have to move forward.

    Thanks for the information and URL link.. much appreciated.

    best regards

    Martin

  • Community Member Profile Picture
    on at

    I am also getting this same error, but using the actual source code release with on premise dynamics 365 update 2.1.

    I have two identical deployments, it worked just fine in the first environment, but then fails with this error in the second environment.  I cannot find any differences between our two environments.  Any ideas on what may cause this issue?

    Thank you,

    Blair

  • Community Member Profile Picture
    on at

    Hi Blair,

    Did you manage to solve this issue?..

    Thanks,

    Moshiko.

  • Suggested answer
    Community Member Profile Picture
    on at

    We were able to resolve this issue on Premise by opening up port 808 on our back-end CRM servers.  Our deployment has two FE's, two BE's, and two SQL Servers (SQL Always On DAG).  The issue was with the web server not being able to communicate with the Async service via port 808 on the back end servers.  Once this was opened up the portal installation worked.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans