You’re offline. This is a read only version of the page.
Since the Windows-Server Update 2017-11 from the 1st of December (Azure VM) the NAV Serice Tier (NAV 2017 CU4) is not more starting because of the encrpytion to the Azure SQL Database.
Every 10 seconds there is a message in the Event log: "Unable to encrypt data. The provided string is too Long".
If we want to Mount a tenant at the Service, there is a error message too: "The provided string is too Long".
It is a converted multitendant-database (from NAV 2016)
We read the Article from NAV 2017 CU9 Cumulative Update, where the bug should be fixed. But we can not only Change the NAV Installation from CU4 to CU9 because there are running lots of productive Environments on the Azure VM.
Does anyone has an idea, whats the difference between a NAV 2017 database and a converted database to fix the problem manually which is known since CU9?
*This post is locked for comments
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (