Breaking news from around the world
Get the Bing + MSN extension
Answer forum questions for a chance to win prizesProviding verified answers in the community not only helps your colleagues find solutions, it also earns community members badges and spots on the Top 10 Leaderboards. Starting this month, your verified answers can help you earn a chance to win monthly prizes.
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We got (before the end) a new licence code for the SQL-DB in XAL.The serial number is still the same, therefore we don't have to slize the kernel.If we want to activate the new code, it will temprary accept it, but after reopen the session and form, the old code is still active.We have tried to put in "spaces" as well as a wrong code, nothing works.Because the application version ist 2.7, there is no c_code.sys.The "usr0000.tbl" doesn't have any change date afterwards, neither is it write-protected.
Application version: 2.7Kernel version: 18.104.22.1681
The strange thing is, if we try the same with Kernel 3.55, it works !?
Any idea ?
Unfortunately it is a bug in the 22.214.171.1241 kernel, when you are running with -QXXX < -Q300.
Make sure you are alone on the installation (should always be when you are making maintenance), downgrade the kernel to XAL 3.55, apply the new license codes, reapply the XAL 126.96.36.1991 kernel. Now it should work.
Currently we want to move a XAL native database to a XAL SQL data base. For that we need a special license key. From Microsoft we don't get any Information about this. Does anybody has an idea how to handle it?
Product support for Microsoft XAL ended Janyary 31 2009, please see:
Last date for purchasing license codes was December 31 2011, please see (broken links):
thank you for your reply . We are just looking for a test license just to be possible to move the Clients native XAL to XAL SQL. We know that is not possible to buy any license now but maybe is there a way to help us.
Business Applications communities