New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have successfully completed an upgrade from GP2013R2 to GP2015R2 but the users get an error on their initial login to a company.
Has any one come across this before, all companies have updated and data and forms are all correct.
Install is on a Terminal Server no client workstations.
I have resolved this issue by restoring the GP2013R2 Databases in SQL and re-running the GP2015 Utilities and updating the databases. This is the only way that I could get rid of this random message when logged into a company.
Looks like something did not upgrade properly from your previous GP versions... I'd have bet on the company access security tables, but it could be anything.
I had same issue. Realised that it was due to "Remember this company" option that the user had selected. The company that he had chosen as default was not part of the upgrade, therefore the message.
I am not sure if this would resolve your issue, but in my case it did.
I know this is old, but I thought I'd answer it just in case someone else had the problem. If you are experiencing this problem, you need to modify your SY01402 table. syDefaultType 70 stores the companyID number of the company the system is trying to launch. If that company isn't there anymore, the dialog will appear and will not close until you close it. If you edit the SY01402 table in the DYNAMICS database, you can fix it. You can remove the syDefaultType =70 records or change the SYUSERDFSTR value to a company ID that exists in your current installation.
Business Applications communities