Travelog Helpdesk

...Word 2010, 2007 or 2003 blocks .doc files from being opened

The instructions on this page affect the security of your computer and your network. Some instructions also involve editing your system registry. Mistakes editing the registry can potentially stop Windows from starting and some can only be fixed by reinstalling Windows. We strongly recommend that you consult with your tech support before you make any of the changes suggested below.

The Problem:

When you have MS Office 2010, 2007 or 2003 installed and you are editing a Travel Services document to Word format, the file may be blocked from opening with the message "You are attempting to open a file that was created in an earlier version of Microsoft Office. This file type is blocked from opening in this version by your registry policy setting.". The problem is that administrators have the option of blocking certain file types from being opened when the files are in untrusted locations. Travelog outputs .doc files in Word for Windows 6.0 format, which is the same format as Word 95. To read more about trusted locations, see this page at office.microsoft.com. To read more about blocked file types and how to prevent blocking, see the Microsoft Knowledge base article 922849.

The Solution(s)

The issue has several possible solutions. You can:

You may want to both change Travelog's output file location (from a network share to a folder on the local machine), and add the new location to Word's list of Trusted Locations.

Change Travelog's settings to output the documents to a trusted location

You can edit the Travelog INI files to output documents to a different (trusted) location. Travelog does not create the folder if it doesn't exist, so make sure that the folder you specify does exist. The document output location is stored in the file WINDOWS\TWORLD1.INI (TWORLD2.INI etc), in the [Costing] section, in the "DocumentPath=" setting.

Instead of editing the INI files directly, you can use Travelog's INI File Setup program to accomplish the same thing:

  1. Go to Start, Programs, Travelog World for Windows, click on INI File Setup.
  2. Select the relevant company from the dropdown list and click Modify INI Details.
  3. When asked if you want to make a backup, click No. A new window opens.
  4. Click on the "Setup" folder in the outlook bar at the left hand side.
  5. Click Modify, then change the setting "Document Path" to an appropriate location
  6. Click Save. If you're warned about an Invalid CRS Download Directory, click Yes to continue
  7. Click Close
  8. If necessary, select the next company from the dropdown list and repeat the relevant steps above

If the documents are currently being output to a location on a network share, changing the output location to a folder on the local machine has the disadvantage that backups of the documents are made more difficult. However, if the documents are disposable, this is not a problem.

Adding the Travelog document output folder as a Trusted Location

For information about trusted locations in Word 2007 and 2010, see the article Create, remove, or change a trusted location for your files at office.microsoft.com. For Word 2003 the trusted locations must be added manually by changing the registry (see the MSKB article 922849 for instructions)

It is also possible to create a trusted location using the administrative Group Policy template word12.adm (in the 2007 Office System Administrative Templates package, a free download from Microsoft).

Security Warnings: Making a location trusted means that not only can any file type be opened by Word from that location, but also that macros and code in files in that location can be run without warning. The above linked page at office.microsoft.com has several recommendations about which locations to trust.

Unblock certain file types

NEW: If you have MS Office 2010 you can unblock certain file types from within MS Word. See MSKB article 922849. Scroll down to Word 2010 and click "Click here to view or hide detailed information".

If you have MS Office 2003, you can download and install a .REG file from Microsoft which may solve your problem by allowing all versions of Word documents to be opened. See MSKB article 938810 for information about this file.

These blocks can also be set or unset using the Group Policy administrative template word12.adm, under the category "Block File Formats". If you're editing the registry manually using regedit, the relevant registry locations for blocking files from being opened are:
Office 2003: (MS KB article lists both locations)
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock
Office 2007: (taken from word12.adm)
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

Under the subkey "FileOpenBlock" there can be several DWORD values. The value names which are relevant to us are (from MSKB 922849):

BinaryFiles.doc, .dot
RtfFiles.rtf, .doc (Word 95), .doc (Word 97 original release version)
ConvertersAll file formats that are available by using a text converter (including the Office Compatibility Pack)
InternalFilesAll Word file types that have a non-RTM nFib value
FilesBeforeVersionAll Word files that have an nFib value lower than the minimum nFib value as set by an administrator

For all except FilesBeforeVersion, the value data should be either 1 (block) or 0 (allow). For FilesBeforeVersion, value data of 101 corresponds to Word 6.0 for Windows, which is what we want. There is also a "FileSaveBlock" subkey which prevents particular file types from being saved. Under that subkey the following DWORD value names are allowed:

BinaryFiles.doc, .dot
RtfFiles.rtf, .doc (Word 95), .doc (Word 97 original release version)
ConvertersAll file formats that are available by using a text converter (including the Office Compatibility Pack)
FilesBeforeVersion is specifically not an option in the FileSaveBlock key. I believe that RtfFiles is the relevant key, however if that doesn't work, it is also worth changing the value of FilesBeforeVersion to 101 (or possibly 0) as well.

Security Warnings: Changing these settings overrides restrictions which may have been intentionally put in place by an administrator. Allowing a particular file type to be opened is a 'blanket' option for files in all untrusted locations (presumably WWW as well as files on network drives and shares). Unblocking these file types should be your last resort.