Dynamics Community Forum Thread Details

Dynamics 365 Customer Engagement - OrgDBOrgSettingsTool

Hello,

The version of Customer Engagement is
Microsoft Dynamics 365 Version 2104 (9.1.39.4) (DB 9.1.39.4) on-premises

We are using OrgDBOrgSettingsTool that is provided with the version in question.

Prior to trying to updating certain settings we are checking if the retrieve works correctly using the following command
Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe Retrieve /u SALES

We are getting the following error :

Error occurred in OrgDBOrgSettings and the error details are The type initializer for 'Microsoft.Crm.OrgDBOrgSettings' threw an exception.The type initializer for 'Microsoft.Crm.LocatorService' threw an exception.

Can find attached config file (Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe.config) and the user crmadmin has "System Administrator" role. Tried activating Trace using CrmDiagTool2011 but couldn't find anything that's pertinent to the error.
Try restarting IIS

For your information authentication mechanism is classic "Active Directory Authentication".
We are not in an IFD context with claims based authentication.

Many thanks in advance.

Regards

Categories:

Dynamics 365 general

Hi, Thanks for providing the detailed context. The error you're encountering with the `OrgDBOrgSettingsTool`—specifically the type initializer exceptions—often points to issues with environment configuration or missing dependencies. Here are a few suggestions to help troubleshoot: 1. **.NET Framework Compatibility**: Ensure the server is running a compatible version of the .NET Framework required by the tool. Sometimes mismatches can cause type initializer failures. 2. **Tool Location and Permissions**: Run the tool from a local directory with sufficient permissions. Avoid network paths and ensure the executing user has full access to the tool folder. 3. **Assembly Binding Issues**: Check the `Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe.config` file for any incorrect assembly bindings. You might also enable Fusion logging to trace assembly loading issues. 4. **LocatorService Exception**: This may indicate a problem with service discovery. Confirm that the CRM services are running and accessible, and that the tool is pointed to the correct organization and server. 5. **IIS Reset**: As you mentioned, restarting IIS can help if there are stale service references or caching issues. 6. **Trace Logs**: If CrmDiagTool2011 didn’t yield useful logs, consider enabling platform tracing via the registry to capture deeper diagnostics. Please verify if this response helps resolve the issue by marking it as helpful. Thanks and best regards, Daniele *Note: This response was prepared with support from Copilot to ensure clarity and completeness.*

Quick Links