Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
One of my companies child companies was on Axapta 3.0 SP4 KR1 about 5 years ago and has since changed ERP's and is now on NAV. The server that use to have Axapta is on the way out and right now it's only on for this company to log into Axapta when a customer needs sales history more than 5 years old, so it's not used very often. We would like to get Axapta off this server and on to another server so we can get rid of the old server that is on it's way out.
I tracked down a disc with Axapta 3.0 SP4 and installed everything on to the new server. Created a back up of the sql database and restored it to the new server. i was getting some errors at first about kernels not matching (31/30) and i figured out that i need to install kernel rollup 1 but can't find it so i changed the SYSTABVERSION to 30 in the database to bypass this just to see if i could log in. Once I did that i could get the log in screen to pop up and i'm able to use my credentials to log just like the old system. Then the menu pops up for our default company but i can't click on anything and then i get a not responding/check online for solutions box and it crashes.
We have a RDS setup with the Axapta client installed (3.0 SP4 KR1) so i changed the SYSTABVERSION back to 31 and tried logging in from there after creating a new config to point at the new server and i get the same thing. I noticed that in the lower right corner of the Axapta window it shows PC icon and a database icon and a green arrow constantly going back and forth between the 2 which i assume means it's trying to talk to the database but it's not happening? When i change the config back to the original config pointing to the old server the pc/greenarrow/database thing happens for a second and then it's done.
i figured that i should put on a trace to see what it's trying to do and from what i can tell it's constantly trying to run some stored procedures over and over. i did the trace on the working version and it only does this once.
I have zero knowledge on installing Axapta as it was installed before i worked here and at the time they hired a consultanting firm that we no longer use to install it. If you need more information i will try my best to retrieve it for you.
Thanks for any help.
Would it be easier if you virtualize these old servers? (Try disk2vhd: technet.microsoft.com/.../ee656415.aspx)
If you manage to Virtualize them, then you can turn them on only when the historical data is needed. The resources can be put into other use.
Do you run Axapta in 2-tier or 3-tier (with AOS) configuration? If 3-tier then have you updated the AOS kernel to KR1 before trying to connect with KR1 client? Have you set up necessary SQL Server permissions for the migrated database?
You don't have to install KR1 update - it's ok just to copy KR1 kernel files (bin directory) from the old server location where KR1 was installed. Try to restore the database from the backup and run KR1 kernel with the database again, without changing SYSTABLEVERSION or something like that. Note also that in 3-tier configuration AOS and client kernel build numbers should match, so better don't try to run KR1 client with SP4 AOS.
Thank you both for you replies. Dominic i have passed your suggestion on to my manager as that's his call. I think a while back when this server first started flaking out they threw that idea around but chose not to do it, but might change their minds now.
Gl00mie, i think we run 2-tier. As i mentioned i'm not well versed in Axapta but when we install the client we select 2-tier and point it to the application folder on the server. I will try and move the bin folder from the old server to the new server today. As of right now i can connect with our KR1 client (that is currently connected to our "live" server) but once i log in to the restored database it thinks for a bit and then kicks me out. I'll try the bin thing and also look at sql rights. right now i think i have BMSSA as a db_owner and sys_admin. is that correct?
EDIT: i just copied bin file to the new server's client install and that now allows me to connect to the restored database unlike before. thank you for the help on that. below is a screen shot of what it looks like after i log in. the arrow in the lower right just keeps bouncing back and forth between pc icon and db icon and then kicks me out after about 15 seconds. maybe it's timing out? This is after i can successfully log in as myself to Axapta.
Stop the AOS
Delete the AOI file
restart the AOS
and then try if you have any improvement.
Thank you for the reply Nitesh. I stopped the service and removed axapd.aoi from application/appl/standard and then when i restarted the service and launched Axapta it said it was rebuilding it. once it was done i still had same issue. Did i delete the correct file?
It is fine, aoi file gets rebuild once AOS is started
Can you please review the Windows Event viewer and check if you have any specific error when AOS crashes
please verify and update us with your findings
i just tried to log in and this was the error in the event log:
Faulting application name: ax32.exe, version: 3.0.1951.6710, time stamp: 0x43c6d945
Faulting module name: ax32.exe, version: 3.0.1951.6710, time stamp: 0x43c6d945
Exception code: 0xc0000005
Fault offset: 0x000058f3
Faulting process id: 0x1074
Faulting application start time: 0x01cfe87bfd244cb7
Faulting application path: D:\Program Files\AX30SP4\AxClient\Bin\ax32.exe
Faulting module path: D:\Program Files\AX30SP4\AxClient\Bin\ax32.exe
Report Id: 500e6d51-546f-11e4-a1a2-0024e8508e73
Business Applications communities