Skip to main content

Hi All,

If you ever come across an error with an error as below when opening the Astea Browser we could look if the Database connection string is being using the current version of SQL with Azure which is SQL2019 version.

Astea Browser Alert

To find the version used in Connection String you should first navigate to Configuration Editor -> Profiles -> Database and open Data Link Properties window. If the Connection String is directing to a different version of SQL you should edit the values as shown below.

Data Link Properties

Select the database name and test the connection.

After saving the changes on Configuration Editor and perform an “IISRESET” command the error should not be displayed anymore.

Hope this finds useful for anyone having the issue. Please feel free to add more of your inputs.

Hi Akila,

Your suggestion is valid for a specific scenario though there are other reasons why you may get an Astea Server is not available error message when trying to use the Astea Browser.

Other reasons include:

  • Network connectivity is not possible (firewall or network down or something blocking the connection from the client to the server)
  • IIS is not running or the server has not been started in Azure (in your specific case)
  • The URL defined in the configuration for the Astea Browser connection is not correct.

Hope this helps others as well.

Phil

Thanks for sharing @Akila Kariyawasam.

As you mentioned the reason for the application unable to connect to server is due to an invalid database connection string in Configuration Editor. 

In your case was due to database migration from SQL 2016 to SQL 2019, and the string was referring to an old connection path.

Another instance this could happen is during alliance version upgrades, where if you change the  connection string during the setup process (For DB Update Scripts). It is unlikely that existing connection string in Global.xml file (that the configuration Editor refers to) will get updated and you will face a similar issue. 

Therefore always check the database string for your configuration profile after performing upgrades.

Terms & ConditionsCookie settingsAccessibility statement