This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

M-Files Web stops working after every automatic update.

It happens in two different servers, .Net 4.7.2/4.8, M-Files 23.1/23.2 at this moment.

Every time an automatic update occurs, the customer needs to reconfigure IIS, the "Physical path..." does not match the "Application Group". I've tried using %MFILESVERSION% but the behavior is the same:

(Above configuration is OK, just an example).

Is there a permanent solution for this behavior?

Is it a "normal" post update behavior?

Regards,

Erick

Parents
  • Is it a separate IIS-server from the M-Files server?
    Because in that case, both servers need to be updated simultaneously.
    If it is not working, what do you need to change in the configuration exactly? The application group or the physical path?

Reply
  • Is it a separate IIS-server from the M-Files server?
    Because in that case, both servers need to be updated simultaneously.
    If it is not working, what do you need to change in the configuration exactly? The application group or the physical path?

Children