Setup encountered an error during deployment of the Role Center and Enterprise Portal framework

(0) Share

Report

Posted on by Community Member

We have updated from AX 2012 to AX 2012R2 CU6.

When trying to deploy the EP from the AOS we get this error in the event viewer:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Setup encountered an error during deployment of the Role Center and Enterprise Portal framework.

at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at Microsoft.Dynamics.Framework.Deployment.Services.EPDeploymentService.DeployWebComponent(String treeNodePath, String virtualServer, String webSite)

at AxUpdatePortal.Program.UpdateWebComponent(String operationName, String treenodePath, String webSiteUrl)

at AxUpdatePortal.Program.Main(String[] args)

And the Source is the Dynamics .NET Business Connector 6.0

I have tried to install a whole new server for the EP and it won't work.

So i'm suspecting the AOS to be malfunctioning but how the hell do I troubleshoot it.

I have looked into web.config files and tried to figure out why the .Net business connector 6.0 is not named 6.2

I had consultants looking at this problem but they don't know what to do.

Any bright ideas?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

Enterprise needs to be fully uninstalled after the upgrade and reinstalled. You will probably have to use the AX2012 Setup to uninstall the 6.0/6.1 bits. If the 6.2 Setup is already installed, use Programs and Features in the control panel to remove it.

I'm assuming the entire application is fully compiled without any errors and CIL is generated successfully. You will most likely need to ensure WCF configurations are updated correctly in the used client configurations.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The wierd thing is that even on a totally new installed server, when we install the enterprise portal (R2) we can see in the event log that it's try to use business connector 6.0.

We need to go throug the WCF configuration. Is it on the EP server or the AOS server?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Looks like the development environment is running 6.0 while the AOS is running 6.2.

So for some reason the development environment is not updated while the reset of the system is updated to 6.2.

Was this reply helpful? Yes No
Uzair Saleem 131 on at

Like (0)

Report

I am facing the same issue.. anyone have solution?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I no longer work in the IT department so I don't know how it was fixed. I'm Sorry.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (4)

Report

Try the following:

Open regedit and find this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions

On SharePoint 2010 environments you can have both 14.0 and 15.0 keys, and the 15.0 key typically has a single "Csom" sybkey.

If this is true for your machine rename the 15.0 key to 15.0_newname and try to rerun EP install

To avoid any issues revert the key rename after EP install.

Please mark as answer for other folks if this fixed your issue.

Was this reply helpful? Yes No
Uzair Saleem 131 on at

Like (1)

Report

Thanks Shah. By follow mention steps my problem had been resolved.

Was this reply helpful? Yes No
Zain Bokhari 3,208 Moderator on at

Like (1)

Report

Since the suggestion from Mohd Shah worked for him plus one other member, and the author has recused himself from a position to verify. I am marking his suggested answer as verified.

Was this reply helpful? Yes No