All around NAV dev and test
So today I sat down to get things prepared for my session at Directions EMEA 2014, next week. Not in the least because this week I had to install a new laptop, hence having to let go of everything that was there and proofed working alright at Directions US. Indeed somewhat tricky.
Luckily everything got installed well and working, earlier on this week. Nothing really to worry about. NAV 2015 RTM NL was running and now I wanted to get a W1 database to put my things in. Having the W1 DVD at hand only a matter of restoring the Demo Database NAV (8-0).bak file, and renaming the database name and file names. This in order to discriminate between the various country versions (which MS be default always name Demo Database NAV (version)) and projects I am using c.q. working on. Therefor I decided to call my database: Demo Database NAV (8-0) - Directions EMEA, likewise I had done for Directions US.
Connected my NAV 2015 Development client and service tier to this database. And ... couldn't get the the windows client work. Quite fast I realised I had to get some things set on the account that is running my service tier: NT AUTHORITY\NETWORK SERVICE.
Restart the service and ...
... open the windows client again, I wanted to say.
Holy cow. My license not compatible? My mind started running, trying to unnerve myself.
Upload the license to the database? Nope, no use. Ask MS for a license update? Might, but will take too much time. Would it work with the other NAV 2015 databases on my SQL Server (see screen shot)? Yes, it does! With the same license!
Am I being fooled somehow? Well, it seems to be.
I recon that, when I named my database Demo Database NAV (8-0) - Directions EMEA, your mind was triggered. Mine was somehow, but I decided to disregard it. I shouldn't.
Once I had changed the name to Demo Database NAV (8-0) D-EMEA everything worked fine.
What the ****, "this license is not compatible with this version of Microsoft Dynamics NAV"?
A to-the-point message would have made it surely easier for me, mister MS.
BTW: Should the name be less than 30 characters? Is that the rule? No, time to figure that out now.
For those who would like NAV to be enhanced to get a meaningful message, please vote on msconnect: go here.
thanks for sharing. The default names are dangerously close to this limit already... and they keep growing, at least on developer setups.
with best regards
it should be possible after october 1st to download a new dev license with support for NAV2015 from Voice
True, Kasper, but I didn't have to. As I described it didn't have anything to do with my license,i t was the database name. The message was very misleading.
I dont think it is with size of the database name.
I faced same issue today and our database name is DynamicsNAV_PSA13.
It started working after changing it to DynamicsNAV-PSA13.
Do we have to rename database after converting it to NAV2015?
or some characters are not supported in database name?
I also got the same error. But in my case I am using the standard Demo database "Demo Database NAV (8-0)". It used to work yesterday but it is not working now. I even tried to rename the database as "Demo Database NAV 80" but no success. Please suggest.
Ravi Prakash Goyal
I got this error message following the restart of the Microsoft Dynamics NAV Server Service. After looking for an answer on the web, I couldn't find one so I remembered that I read somewhere that the license file for NAV 2013 or 2013 R2 were not compatible with NAV 2015. To fix the issue, you need to upload the Cronus license file provided in the DVD setup (located in this area "RoleTailoredClient\program files\Microsoft Dynamics NAV\80\RoleTailored Client\Cronus.flf"). After uploading the license file, restart the service. It should work then. It worked for me.
Thanx for sharing Hassan.
I encountered the same prolem today.
Your post gave me the idea to try around with the length of the service instance.
As far as I got, there is a problem with the maximum length of CompanyName + InstanceName.
If I have a short(er) CompanyName, e.g. the Demo Database, I can have longer InstanceNames.
If I have some really long CompanyName (mine was 26 characters), then I can only use a short InstanceName.
Hope this helps anyone ;)
Thanx for sharing Jonatan.
Just restart the service that is being used.
I encountered this problem today after restoring the 2015 Cronus database, when I tried to access the server I received this error.
The problem was that the server was using a default license which was 2013. I connected via the development environment and uploaded the 2015 license. Worked straight away
Hope this helps someone, as none of the above responses matched my issues
I encountered this error too. In my case, I tried to convert our NAV 2013 dev DB named Vychozi2015 to NAV 2015. In my case, I had old NAV 2015 development license created in year 2014. I created new license file and restarted service, this helped.
Thanx for sharing Andy and Martin!