
Dears, we are trying to install and environment containing Widows server 2012 r2 , SQL 2014, Dynamics GP 2013 R2 , SharePoint 2010 and installing Business portal 6.0
all setup regarding the GP2013 r2 with e connect , web services and Sharepoint 2010 worked fine but when installing the business portal 6.0 it generates the following error:
-----------------------------------------------------------------------
Feature Id: 93dfb004-5724-4a4b-850b-6e0cb99c83c0
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPWcfConnectorModel
Action: Install
Exception: Cannot delete BDC Model 'MicrosoftDynamicsGPModel' as it exclusively references LobSystem (External System) with Name 'MicrosoftDynamicsGP', and you do not have Edit permissions for that LobSystem.
Stack Trace: at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.Execute[T](String operationName, UInt32 maxRunningTime, ExecuteDelegate`1 operation, Boolean performCanaryCheck, Boolean isChannelThatDelegatesIdentity)
at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.Delete(MetadataObjectStruct metadataObjectStruct)
at Microsoft.SharePoint.BusinessData.Administration.MetadataObject.Delete()
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.DeleteModel(Model model, Boolean deleteNoCascade)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.ImportBdcArtifacts(String featureFolder, String modelFilePath, String[] resourceFilesPaths, Dictionary`2 lobSystemAssemblies, Boolean incrementalUpdate)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)
at Microsoft.SharePoint.SPAdminFeatureCollection.Add(Guid featid, Version version, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddCore(SPFeatureDefinition featdef, SPSite site, String solutionHash, Boolean fForce, Boolean fDoValidation)
at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddInternal(String relativePathToFeatureManifest, Guid solutionId, String solutionHash, SPSite site, Boolean force, Boolean fDoValidation, SPFeatureDefinitionContext featureDefinitionContext)
at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.Add(String relativePathToFeatureManifest, Guid solutionId, Boolean force)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Install(String manifest, Boolean force)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointInstallFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------
we tried different options that didn't work and even uninstalled the Sharepoint , e connect and web services and re installed and it came out with the same error!
*This post is locked for comments
I have the same question (0)Hello kassab,
We've seen this error caused by an ISO currency value not being correct. Web Services, when it is installed, looks at the ISOCURRC values for each currency, in the MC40200 system table, in the DYNAMICS database.
This ISOCURRC value must be 3 characters and unique for each listed currency, otherwise it can cause errors related to Web Services.
It also could be related to SharePoint permissions:
In SharePoint 2010 Central Administration:
1) Go to "Security"
2) Click on "Configure managed accounts"
3) Make sure the account performing the Business Portal installation is listed there.
Also, make sure the account you're using is in the following for SharePoint:
1. Administrator on the server.
2. Farm Administrators group
3. BDC Administrators group.
4. Site collection administrator.
If none of the above resolves this error, we'd probably need a support case opened to look at it further, if you're still running into this issue.
Thank you,