Skip to main content
  • EN

Hi,

 

We are with the 2017 version of FME Server and we would like to modify the database connection string in the “FMEServer\\Server\\fmeCommonConfig.txt” file. It's the same database (same provider, same version, same content), with just an update of the connection string. We have already done the test by modifying this file and restarting the server, but FME Server has stopped working. The home page was then presented without the "Use Windows Credentials" button (which is not normal according to our configuration) and if we manually entered a credential, a page informed that FME Server was unavailable.

 

What is the procedure for making this type of change?

If this type of update is possible, would the procedure be the same with the FMEServer2019 version?

 

Thanks in advance,

@sper2,

I'm sorry you are experiencing this problem.

I'm not 100% certain I understand the problem. But if I am here's my response.

If you are attempting to have the new FME Server 2019 connect to the old database of FME Server 2017, then that isn't correct. It will not work. You must use the SQL scripts (click here for steps) that come with FME Server 2019 to create a new schema. (there are lots of changes to the objects in the fmeserver schema as well as new objects). Once you have the new schema created, use the Backup tool in the FME Server 2017 Web UI to make a back up of the FME Server 2017 system and then restore to the new system using the Restore Tool in the FME Server 2019 Web UI. (see the Backup and Restore instructions: 2017 version and 2019 version)

In summary, it would appear to me that the FME Server Core is not connecting to the database after the change. The connection to the FME Server System Database is the first hurdle FME Server Core needs to get over to come to life. So it seems to indicate that FME Server doesn't like the database you are attempting to connect to. Please review the fmeserver.log for errors when you do a restart of the FME Server Core service.

If this isn't the issue please expand with more details or may I suggest if this is related to a production upgrade or is blocking you from upgrading to FME Server 2019, that you create a case at www.safe.com/support (report a problem).

Please do escalate this if it is related to production by contacting your Account Executive.

Look forward to hearing from you.

@sper2,

I'm sorry you are experiencing this problem.

I'm not 100% certain I understand the problem. But if I am here's my response.

If you are attempting to have the new FME Server 2019 connect to the old database of FME Server 2017, then that isn't correct. It will not work. You must use the SQL scripts (click here for steps) that come with FME Server 2019 to create a new schema. (there are lots of changes to the objects in the fmeserver schema as well as new objects). Once you have the new schema created, use the Backup tool in the FME Server 2017 Web UI to make a back up of the FME Server 2017 system and then restore to the new system using the Restore Tool in the FME Server 2019 Web UI. (see the Backup and Restore instructions: 2017 version and 2019 version)

In summary, it would appear to me that the FME Server Core is not connecting to the database after the change. The connection to the FME Server System Database is the first hurdle FME Server Core needs to get over to come to life. So it seems to indicate that FME Server doesn't like the database you are attempting to connect to. Please review the fmeserver.log for errors when you do a restart of the FME Server Core service.

If this isn't the issue please expand with more details or may I suggest if this is related to a production upgrade or is blocking you from upgrading to FME Server 2019, that you create a case at www.safe.com/support (report a problem).

Please do escalate this if it is related to production by contacting your Account Executive.

Look forward to hearing from you.

Hello,

 

Thanks for your response,

 

The problem is not the one you describe.

We just want to change the SQLServer database connection string for FMEServer2017, in order to connect to the same database. The reason is only that the connection string refers to a CName alias and that our DBAs want this alias to be changed. So it's really the same database. When we updated the connection string by referring to the new alias, FMEServer2017 stopped working.

 

After doing some research, we read about a post-installation file: FMEServer\\Utilities\\runPostInstall.bat. Do we also need to execute this script if we update the connection string? If so, can it have any impacts on running this script?

 

Thanks for your help,

Reply


Community Stats

30,159
Posts
114,479
Replies
37,803
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.