Hi
I did upgrade MR from CU 11 to CU 14. Upgrade went successful. Then it prompt for MR DB update that also went fine. Now when MR updating MR datamart, its failed.
i checked windows log
The encrypted setting, Password, could not be decrypted. Encryption error occured.
Component: Microsoft.Dynamics.Integration.Common.TraceLog
Then i remove Datamart and try to rebuild. Till configuration it goes fine and when it start integration. I check log again and found the same log. Then i check deployment log from configuration console.
Connecting to a mirrored SQL Server instance using the ApplicationIntent ReadOnly connection option is not supported.
How do i resolve the issues so that my MR start working correctly.
Please reply it promptly as it is urgent.
Thanks
Reyaz Ahamad
*This post is locked for comments
This did NOT work in my case. I am using AAG and I am trying to get MR (CU2016) to use secondary in the AAG but it said " the target database is in an availability group and is currently accessible for connections when the application intent is set to read only. Of course I have configured readonly in AAG
The value is added but seems like it was NOT loaded when I tried to configured DataMart
Really appreciated if you guys have any suggestion
Regards,
Mark
MR CU14+ will require you to change that config value first.
The error this customer is receiving can be workaround by:
1. Open the MRServiceHost.settings.config file in the MR Service folder
2. Add the following key and make sure it’s set to false:
<add key="SetApplicationIntentReadOnly" value="false" />
3. Restart MR services
After these steps are completed they will be able to point the MR integration to a mirrored AX database without that error.
Hi,
I believe that this is a bug in CU14 or it may not compatible for SQL 2008R2 with mirror configuration.
I tried all the solution like i moved my MR DB to a fresh instance instead of Mirror instance but it didn't help.
I tried rebuild of data mart many times .... didn't help
I tried uninstall and install a fresh MR CU14....did't help.
I tried to connect with non mirror DB then it worked and running but in case of Mirror db it failed.
in the last i uninstall CU 14 and install back to CU11, now all is up and running.
Finally i couldn't get CU14 and i had to move back to CU11.
So any one who is planning to go for CU 14 i advise to them please double check the compatibility with DB version and mirror cluster.
Hi Matt,
We are not using SQL AlwaysOn Availability group, this feature is not with SQL Server 2008R2.
Well, my assumption here is that SQL replicates your database using SQL AlwaysOn Availability Group (AG). AG is configured with a Group Listener. The Group Listener redirects incoming connection to whether the primary instance and one of the secondary depending on the application intent.
In this case, it says: ApplicationIntent ReadOnly connection option is not supported
It sounds like MR is establishing a connection to SQL through the Group Listener awith the ApplicationIntent ReadOnly parameter and thus redirected to the secondary database, which is not supported.
Look, I might be plain wrong. But that could help your troubleshooting. First, determine if you are using SQL AlwaysOn Availability Groups or not.
Hi Matt,
I have to check with my data center how do they mirror database.
Is this issue relating anything with database mirror. Could you suggest some possibilities of solution.
How do you mirror your database
Thanks Matt for your response. Please suggest me what could be the reason.
This is SQL Server 2008 r2 and hosted on one of data center using vmware.
My MR DB is on server 2 as described above. Same configuration was working fine before upgrade.
Which technology are you using to replicate your database from Server1 to Server2 ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,113 Super User 2024 Season 2
Martin Dráb 229,918 Most Valuable Professional
nmaenpaa 101,156