Dynamics Community Forum Thread Details

GP2010 Web Service - Config Wizard Loader Error on Load Security for Metadata step - Databases migrated and upgraded from GP 10 onto new Server - switching from ADAM to SQL security

1) After upgrade and unsuccessful Web Services Configuration: Used Configuration to Remove Web Services - Uninstalled Web Services - Reinstalled Web Services - SQL Option creating new security database - Used Configuration to Add Companies

2) Configuration successfully checked ISO and Functional Currency - Succeeded through steps: System Status Objects, System Exception Objects, System User Assignment Objects, and System Web Service Objects.

3) On the System Security Metadata step, the process immediately failed with the following:

Loader Errors: - Microsoft.Dynamics.Security.InvalidSecurityContextException: Microsoft.Dynamics.Security.NonExistentSecurityObjectException : The security object does not exist. Key = 25cc1a21-2cc4-4b13-a1c8-eea186fb688a at Microsoft.Dynamics.Security.ValidationHelper.ValidateContext(SecurityContext context) at Microsoft.Dynamics.Security.SecurityService.Get(SecurityContext context, Key key) at Microsoft.Dynamics.Security.AzManOperationServiceImplementation.GetOperation(SecurityContext context, OperationKey operationKey) at Microsoft.Dynamics.GP.GPSecurityMetadataSystemLoader.PerformActionForCustomSecurityOperation(Action action, String operationKey, Keyword keyword, String nameResXId, String descriptionResXId, String resXAssemblyName) at Microsoft.Dynamics.GP.GPSecurityMetadataSystemLoader.PerformActionForStandardSecurityOperations(Action action, Type businessObjectType, Keyword keyword, Operation[] serviceOperations) at Microsoft.Dynamics.GP.GPSecurityMetadataSystemLoader.PerformActionOnOperationsUpgradeVersion105ToVersion11(Action action) at Microsoft.Dynamics.GP.GPSecurityMetadataSystemLoader.b__6() at Microsoft.Dynamics.InstallData.Loader.Process(String[] args)

The DYNAMICS and company databases were upgraded from GP 10.0, which had ADAM security on an older server, to GP 2010 on a Windows 2008 server where we wish to use SQL security. Apparently the company databases themselves are not getting refreshed so the dependency on ADAM is not being removed. Therefore, I can successfully Remove security data using the Configuration Wizard, but I cannot add the companies.

As a result, the Dynamics Security Console shows no applications to select and of course no companies. I have spent nearly a week reading all the posts on this issue and taking all the suggestions I have found.

The idea of leaving the old GP 10 server alone is to provide a fail-safe for the delays caused by upgrade. My current test system is intended to be the new production system. All upgrades have gone successfully except Web Services, which is crucial to the client's business. The old server is still running GP 10.0 SP4, and I do not want to risk corrupting data by attempting to install Web Services 2010 (depends on everything else, including the server, being upgraded).

I cannot help but notice the questions regarding this error are officially "unanswered." My question is "How do I safely remove the memory of ADAM security objects from the DYNAMICS database and (if needed) the company databases I have upgraded so I can use SQL security?

Or, is there some secret when reinstalling Web Services which will actually create the correct metadata? How do I prevent the Configuration Wizard from looking for this non-existent key?

Thanks.

Lin

Follow-up:

Reference entitled, MDGP2010_HOWTO_UninstallWebServices which appears to be a standard document. After running uninstall, I checked for each of the items mentioned in the white-paper.

I have discovered that, once I had removed web services objects and uninstalled web services and econnect, while the objects had been removed from the company databases, the tables starting with WS had not been dropped from the DYNAMICS database. I used the script provided in the MDGP2010 document which applied to the DYNAMICS database.

The WS tables contained references to the older version of GP and what steps had been completed on Web Services installation (from the old system).

Continued:

After having used the Wizards to remove security objects (removed from Companies) and to uninstall Web Services (removed services, registry entry etc.), running the DYNAMICS database script to drop the procedures and tables from the prior system was the only thing I needed to do manually.

After this, the Web Services installed cleanly against the migrated/upgraded databases.

Quick Links

Leaderboard