Publish fails with interruption

Owned by Mattias Löfstrand
Last updated: 04 Mar 2020 by Kenneth Jonsson
1 min read

Problem

Publish fails due to process getting interrupted.

Solution

Publishing process can for larger databases take some time, during which IIS or SQL may get interrupted. If such interrupt occur the process will fail. There can be many reasons for such interruptions but a few may be worth examining.

  • IIS recycling. IIS has typically a default recycling set at installation. If recycling occur during the publishing process the process will get interrupted. Check IIS recycling settings.

  • Memory consumption. Publishing consumes some extra resources and if memory gets low, response times may grow and timeouts may occur. This may interrupt the publishing process and site it self. Check memory usage and ensure there is sufficient extra memory.

  • SQL version. If lower versions of SQL are used, limits on database size and number of connections exist. If limits are reached it may result in interruptions of both publishing process and site it self.

  • Performance on disk where published data is created and updated. Normally a database is generated on a local disk to the editor server, and this is not an issue. When generating file publications; Xml, Pdf etc. the target disk area could be configured to a file server where network may be involved.

  • Network traffic between remote database server and local target database. Publishing a database in this configuration includes linking the source and target database and sending data through the link to the target publication database, If the network should fail, or generate delays, the processing process may be interrupted.