Installation of Exchange Rules 2003, 2007, 2010 or 2013 in non-default location

Problem:

CodeTwo Exchange Rules 2003, 2007, 2010 or 2013 has no access to files and libraries after installation in non-default location.

Solution:

When CodeTwo Exchange Rules 2003, 2007, 2010 or 2013 is installed in a non-default location (e.g. on a different physical disk rather on the C: drive of the server machine) it may have problems with access to its files and libraries. This solution is based on CodeTwo Exchange Rules 2010, but it looks similarly in all versions.

The following issues might occur:

  • Wrong position or no signatures at all
  • Wrong operation of the Sent Items Update module
  • Emails being held in the queue for processing and not being sent to recipients (queuing)

To prevent the above issues, make sure that the NETWORK SERVICE user has the Full control access to the installation folder of Exchange Rules 2010.

To check this setting and if necessary to give the required access right to the folder specified, follow these steps:

  1.  Locate the installation folder of CodeTwo Exchange Rules 2010.
  2.  Click on it with the right mouse button and from the context menu select Properties.
  3.  Select the Security tab (Fig. 1.) and check whether the NETWORK SERVICE user has Full control rights.

    Security tab in folder properties
    Fig. 1. Security tab in folder properties.

  4. If the user does not have such rights, click the Edit button below the list of users and then change the setting accordingly.
  5. If the user is not on the list then he should be added to it - click the Edit button under the list of users and then in a new window (Fig. 2.) click the Add… button. Search for the NETWORK SERVICE user (Fig. 3.).

    Window with the folder access rights for selected user
    Fig. 2. Window with the folder access rights for selected users.

    User search window 
    Fig. 3. User search window.

  6. Add the user to the list giving him Full control access right.

These steps will help fix the problem with the lack of access to the program's libraries, because of their location in a custom location.