Skip to main content
Question

FSM6u32, Application Server reboot and SQL reconnnection

  • October 15, 2026
  • 1 reply
  • 10 views

Forum|alt.badge.img+8

Our IT/IS team has change after a business acquisition, as a result a new process is in place for Server Policy updates. 

On occasion, after the server updates the server may be restarted. It appears that the application server does not always reconnect to the SQL Database server..~


What should the excepted behavior be? How many attempts and and at what frequency (e.g, every 60 seconds). Is this managed via app params or a config file?

 

Result is that on occasion, the users lose connection and cannot log in until the services are restated or the application server is restarted.

1 reply

roklde
Superhero (Employee)
Forum|alt.badge.img+27
  • Superhero (Employee)
  • October 15, 2026

Hi Angelo,

nice to hear from you again - hope you are doing fine!?

I’d recommend first determining whether the FSM service / IIS Application Pool itself has stopped, remains running but cannot reconnect to SQL, or whether SQL/network connectivity is still unavailable after the server maintenance. Further, did you check FSM Server Log? Does it indicate that the Application Server has lost SQL connection? Checking Windows Events Web Role Events could also provide some additional information about the IIS health after the reboot.


If the FSM application service remains running and SQL connectivity has already recovered but FSM nevertheless does not restore the database connection, the FSM logs from the outage should be reviewed and the behaviour raised with Product Support to confirm the product's connection-recovery logic.


I’d also recommend ensuring that SQL Server is fully available before FSM services are started, and implementing a post-maintenance health check to verify both SQL connectivity from the application server and FSM application availability before releasing the environment after such policy updates.

​​​​​​​
Best regards
Roman