Considerations for automated Office file refresh and Broadcast in Log-Off Mode

Document created by mik1893 Employee on Jul 14, 2017Last modified by ggallo on Jul 20, 2017
Version 4Show Document
  • View in full screen mode
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.


Office applications assume that they are being run under an interactive desktop.

In some circumstances, applications may need to be made visible for certain Automation functions to work correctly. If an unexpected error occurs, or if an unspecified parameter is needed to complete a function, Office is designed to prompt the user with a modal dialog box that asks the user what the user wants to do.


A modal dialog box on a non-interactive desktop cannot be dismissed. Therefore, that thread stops responding (hangs) indefinitely. Although certain coding practices can help reduce the likelihood of this issue, these practices cannot prevent the issue entirely. This fact alone makes running Office Applications from a server-side environment risky and unsupported.


This is also described in a technical Microsoft Article 

As a consequence of those considerations we don't recommend the "Refresh Office File" and "Broadcast" Procedure Commands if executed in User Log-Off Mode.

2 people found this helpful