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

  • Open database setup and see if you can open up the system database and the company database and save them. Start there and see what might be wrong.

  • 1. Create a test ODBC DSN to make sure connection fine.
    2. Please try to remove old ODBC DSNs and try again.

  • in reply to Marius Yung

    I tested the ODBC DSN and they tested fine.  I even deleted them and recreated them using server name and localhost and same issue.  It shows connecting to datbase and then just disappears.

  • in reply to Django

    I dumped the database and reloaded it and that didnt work.   Then i reloaded the original sample databases and it loads.   The problem is it concerns me what will happen on my live production system.  What if I had made some changes to the sample data I needed to keep?  In my live scenario I will have only the one database I can use.

  • in reply to tcixtulsa

    Delete ALL of your ODBC DSNs, then run Sage "As administrator" one time so that Sage creates them using Native Client 11.  Don't create them manually.

  • in reply to Jay Converse Acumen

    Hey jay, I am not sure how Sage will create the DSN?  when I try to run sage without the databases set up it pops up the message saying to set up your databases.   I was able to get it to open by loading the original database again from the sample data.  I will try it again by taking a database backup before the upgrade and trying to reload that backup since that is more like the scenario for when I do the live system upgrade.

  • in reply to tcixtulsa

    Run Sage "As administrator" 

  • in reply to Jay Converse Acumen

    When I delete all the DSN adn run sage (I always open it as administrator)  i get the message Cannot access database(Error=49153. See help for more information.

    I am sure I am missing something you are trying to tell me.   I deleted the databases from database setup but that requires the setup when you start Sage.   So I have to add the database info and it will not accept using server it wants a DSN and since the DSN has not been created I have to back out and create it.   I must be missing some order or step in the process you are thinking of.

  • in reply to tcixtulsa

    First of all, you should not be running Sage as Administrator every time, you only need to do it once on a new install.

    Second, error 49153 means your client can't connect to the SQL server, which in turn means:

    1. That's not the correct server name, or 

    2. The firewall on the server is blocking SQL port 1433

  • in reply to Jay Converse Acumen

    Interesting, I have inherited managing the Sage server.  When i came on board the users always ran it as Administrator.  I am not sure if Sage or the support vendor told them to do that.

    I have the firewall turned off and when I try to connect I get "Login ID is not valid or password is not correct"

    • I am not running this from a client machine but direct on the server
    • I know the server name is correct
    • I created a local admin account, SageTstSA,  on the DB and verified the password.
    • I made sure that the SageTstSA account is dbo owner on the two sage databases

    It is odd because it happens so quick that it seems it is not even looking at the database server, it just pops up right away. When I try to save the DB connection and get the above message it does create a 32 bit.

    Upon further testing I can see that something is wrong with the user that was created.  So it appears the culprit is the user on the SQL server.  Once I get that sorted I will post back.   thanks for helping out with this.  I will report back soon.  

    I really do appreciate your guys help.  Trying to learn a production system without messing it up can be a challenge.

  • in reply to tcixtulsa

    So I have created a user that is a local sql login, serveradmin, and db owner of the SAMSYS databse and when I try to create the database with the sage utiliyt it says "Login is not valid or password is incorrect"  However, I know them to both be correct.

    I am using

    • Description: SAMSYS
    • Server: SAGETEST (the name of the server running sql, same machine sage is on)
    • login: SageSA
    • Password: password I have set
    • Database: SAMSYS

    I have create the SageSA user in SQL Server management studio, selected all the server rolls, and set set it to be db owner of the SAMSYS database. 

    What could i be doing wrong here??

  • Do you have the correct rights for the shared data directory? Can you read and  write to it

  • in reply to tcixtulsa

    Try logging into SQL with the new user.  Rule out that the user you setup actually works to log into SQL.

  • 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