Sage 300 crashes after upgrade

I created a new virtual server with sql server.  Then i installed sage 2020 and loaded the sample databases.   Then I ran the sage 2022 installer to upgrade it.   Now when I open Sage it opens and shows my company but when i try to open the company it says connecting to databse in the  bottom left corner and then the program just crashes.  No error message or anything.

How can I go about troubleshooting this?

Thanks

Parents Reply Children
  • in reply to Eva Paterson

    I am pretty sure it is sql related.  Too many tasks today, I will check on it tomorrow and update.

  • in reply to Eva Paterson

    Yeah, so I had some time to get back to this.  I know there is some issue with the sql server developer edition I installed on my test machine bc i could not log in locally to sql server management studio with new users i created.  Sadly, I couldn't find the resolution and gave up and just loaded the test databases to my live sql server and was able to establish the sage connection using the server name / login without any issues.

  • in reply to Eva Paterson

    Thank you for your patience.  I have confirmed directory permissions are ok.  I have confirmed the database connection is ok.  When i start sage 2022 i get the login to company screen.  I put in the user and pass and it says connecting to database in the bottom left and then the program just disappears.   I even tried deleting and recreating the company in Database Setup and that works fine.

    Any ideas?

  • in reply to tcixtulsa

    1. Make sure you don't have references to the old Sage version in your PATH.

    2. Uninstall Sage.  Rename the RUNTIME folder.  Reinstall to ensure RUNTIME is fresh.

  • in reply to Jay Converse Acumen

    So, instead of upgrading (leaving the existing 2020 program)  I should uninstall everything, rename the runtime folder, install sage 2022, run sage the first time as Admin to create the database connection, then run sage as  normal user.

  • in reply to tcixtulsa

    Still no luck with just removing the runtime and DSN's.  Again the only thing that seems to work is to reload the sample data.  So basically I would have to export ALL databases before the upgrade and then use the Sage Loader to load them back in when I am done.

    Is this normal?  Shouldn't I be able to just upload the sage software and run it?

  • in reply to tcixtulsa

    No, it's not normal.  I haven't dumped and loaded for an upgrade in many years.

  • in reply to tcixtulsa

    Hi did you manage to fix this? Because i just had the same issue. i uninstalled , cleaned the registry and renamed the old folder then reinstalled on a new folder