Update the config file - point Forecast 5 to a new server or database.

Update the config file - point Forecast 5 to a new server or database.

If you have a network license and you wish to store the Forecast 5 database on a server, you will need to update the config file to point to the correct server and database.

  1. On the server, go to this path: C:\ProgramData\Forecast 5 Ltd
  2. Edit the file Forecast5Config.xml in notepad.
  3. Find the line below:

<ConnectionString>Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFileName=C:\ProgramData\Forecast 5 Ltd\Data\Forecast5V3_2015.mdf;Initial Catalog=Forecast5V3_2015;Integrated Security=True;</ConnectionString>

4. Replace with the line below and enter the correct database name by changing the coloured lines below to your server or computer name and the database name (it is new database, you can create any name that has no spaces or odd characters, e.g. $, % '):

Note: below is an example of a default SQLExpress instance. DESKTOP-MHDPC00 should be renamed to the PC/Server you are connecting to. SQLExpress is the instance you are connecting to.

<ConnectionString>Data Source=DESKTOP-MHDPC00\SQLEXPRESS;Initial Catalog=Forecast5v3_2015;Persist Security Info=True;Integrated Security=SSPI;</ConnectionString>

Or you can add the SA username and password:

<ConnectionString>Data Source=DESKTOP-MHDPC00\SQLEXPRESS;Initial Catalog=Forecast5v3_2015;User Id=myUsername;Password=myPassword;</ConnectionString>

4. Save the config and reopen Forecast 5.

Note: you can find the server name by opening SQL Server Management Studio:

    • Related Articles

    • Version Control: Unable to access Forecast 5 after update

      Issue: After running the update, Forecast 5 begins to load, the error below flashes and it closes down: "The Forecast 5 Client you are running has a newer version than the database you are connecting to. Ensure that the db user you are connecting ...
    • Update: Could not connect to Forecast 5 Auto-Update Server.

      Issue: Could not connect to Forecast 5 Auto-Update Server. Next try in 1 day. You may receive this error when launching Forecast 5. As the error suggests, Forecast 5 is being blocked from connecting to the F5 update server.   To resolve this add the ...
    • SQLException: Failed to update database... because the database is read-only

      Issue/Error: When opening Forecast 5, you are receiving an error: Forecast5 cannot continue because of an exception occured: SqlException. Failed to update database "[database name]" because the database is read-only. Forecast 5 will fail to open. ...
    • Can I change the recovery model on my Forecast 5 database .log file from Full to Simple?

      Question: My .log file for the Forecast 5 database has grown to a significantly large file. Can I change the recovery model from Full to Simple? Solution: Forecast 5 uses Full recovery model by default to allow you to be able to restore from the log ...
    • Database creation: NullReferenceException

      Issue: When trying to create a new database, you are receiving the following error but the database is still created in SQL:  NullReferenceException Object reference not set to an instance of an object. Cause: This is caused by attempting to connect ...