Visio related errors on a server

 This article is suitable for an IT Adminstrator

Ref: 201101271539
Last Edited: April 26th, 2016
 


Introduction

If automated publications persistently report Visio-related errors, then stability can be improved by using these methods.  We recommend trying the first method first, and should that not succeed in improving Visio stability, then move on to implement the second method.
 
Such errors can be COM errors reported in the Triaster Server publication logs, which will usually mean a failure to export maps to HTML, and/or errors related to Visio automation in the Windows Application Event Log.
 

Creating a SystemProfile "Desktop" folder

This is applicable to Windows Server 2008 and later (and Windows 7 and later).
  1. In Windows Explorer, go to this location:
    32-bit Windows: 
    "C:\Windows\System32\config\systemprofile"

    64-bit Windows:
    "C:\Windows\System32\config\systemprofile"
    "C:\Windows\SysWOW64\config\systemprofile"
     
  2. If there is not already a folder call "Desktop" in this location, then create it.
     
  3. If problems persist after making this change, proceed to make the DCOM changes as specified below.
     

Configuring DCOM to associate Visio with the publication user 

Procedure

This has sometimes been found not to be necessary on some 64-bit Windows Server 2008 systems, usually where a 'Microsoft Office Visio Drawing' setting hasn't been found. In those cases, the creation of the 'Desktop' folder described earlier has been sufficient. Elsewhere, this should be done on the publication server.

Configuring DCOM configuration

  1. Start > Administrative Tools > Component Services.
     
  2. Expand Console Root > Component Services > Computers > My Computer > DCOM Config.
     
  3. If there is no 'Microsoft Office Visio Drawing' (or similar) item, check the DCOM configuration by running Microsoft Management Console in 32-bit mode.
    1. Open the 'Run' dialog.
      (Commonly, Start > Run)
    2. Type 'mmc -32' (without quotes) > click OK.
    3. In the console window, click 'File' > 'Add/Remove Snap-in...'.
    4. In the 'Add or Remove Snap-ins' dialog, in the left-hand pane, click 'Component Services' > click 'Add >'.
    5. Click OK to close the 'Add or Remove Snap-ins' dialog.
    6. Expand Console Root > Component Services > Computers > My Computer > DCOM Config.
       
  4. Right-click 'Microsoft Office Visio Drawing' (or similar) > Properties.
     
  5. In the Properties window, click the Identity tab.
     
  6. Select the 'This user' option, and enter the credentials of the Triaster publication user (i.e. the user account that runs, for example, the 'PN Publication Wrapper' service).
     
    Note: It's very important that the user specified is the Triaster publication user. The syntax should be '<Domain Name>\<User Name>' or '<Computer Name>\<User Name>', depending on the nature of the account. You can ensure this by selecting the user through the 'Browse...' button.
     
  7. Click OK.
     

Ending inactive Visio.exe processes

When the DCOM configuration is applied, Visio may not be closed following an automated publication. Inactive Visio.exe processes can be ended using  a scheduled script and additional commands within the Publication Command file, as described here.

Comments

Running Visio

When this configuration is applied, if Visio is run through automation, it will run invisibly, even when logged on as the user specified in the DCOM configuration. Such circumstances are:
  • Creating a new Visio process through the Start menu.
  • Exporting to HTML through Process Navigator.
  • Running a publication by running the publish CMD file.
Visio can still be run interactively by:
  • Double-clicking on a Visio drawing file, e.g. a map VDX file.
  • Running Visio from its own Start menu shortcut, and either creating a new drawing or opening an existing one from its File menu.

User account to run Visio

If an account other than the Triaster publication user is specified to run Visio, Visio will not run properly when launched from an automated publication. Indeed, it won't run properly if launched from an interactive session of Process Navigator that is being run by a different user account.
 
 

Applies to

  • Windows Server 2003, Windows Server 2008, Windows Server 2012
  • All versions of Triaster software

Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on 0870 402 1234.

                    Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk 
Comments