If you are migrating to, or have imported emails into FileSite, you may not have the header information imported from the email. This can include the To, From, Sent Time, and Received Time. Luckily, Autonomy has a utility to open the emails and import the header information, but it requires a decent amount of setup and testing prior to running. You will need full access to SQL and the WorkSite server for this task. You will also have to download and install the Resource Kit from Autonomy (available from their support site with login).
Determining Documents to be Fixed:
The first step is to isolate the range of emails that need to be fixed. To do this, we will query against the FileSite database to find which documents have NULL fields.
select docnum, docname, t_alias, c13alias, entrywhen from mhgroup.docmaster
where c13alias IS NULL and t_alias = ‘mime’ order by entrywhen
This will result in all emails that have c13alias (From) as NULL, and order them by date. Make a note of first and last emails “Entry When” date, as well as one document number we can use to test
Installing the Resource Kit:
Once you download and install, there are many components as part of the kit, but we need to make sure at least the MSGFIX utility gets installed.
Registry Keys: The application will reference registry keys that you must manually create to map the header fields to their respective custom fields in FileSite. The following are the default values, but if you have customized your system please verify and update as needed:
Reg keys for 64bit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Interwoven\Worksite\Server Common\Custom Fields Map]
“From”=dword:0000000d
“To”=dword:0000000e
“Sent”=dword:00000000
“Receive Time”=dword:00000016
“Send Time”=dword:00000015
“CC”=dword:00000000
“BCC”=dword:00000000
Reg keys for 32bit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Interwoven\Worksite\Server Common\Custom Fields Map]
“From”=dword:0000000d
“To”=dword:0000000e
“Sent”=dword:00000000
“Receive Time”=dword:00000016
“Send Time”=dword:00000015
“CC”=dword:00000000
“BCC”=dword:00000000
XML configuration: There will be a CONFIG.XML file in the installation location that needs to be edited. 32 Bit: C:\Program Files\Interwoven\WorkSite\Server, or 64 bit: C:\Program Files (x86)\Interwoven\WorkSite\Server. Open this in your XML editor or simply notepad. We have two sections to edit, the first is the DB connection and the second is the filter for which emails will be affected.
DB Connection: find the <DBConnection dsn=”database name” user=”user” pwd=”password” /> and replace the quoted information with your server information
Filter: There are MANY different ways to filter the information. This will cover two methods, the first will run against a specific document number for testing purposes, and the second will run against a date range (full update). The red text represents what should be edited.
Specific Document Number:
<DocFilters>
<Filter column=”DOCMASTER.DOCNUM” value=”123456” opp=”E” type=”numeric” />
</DocFilters>
Date Range:
<DocFilters>
<Filter column=”DOCMASTER.ENTRYWHEN” value=”CONVERT(datetime, ‘4/1/2003 0:00:00‘)” opp=”GE” type=”date” />
<Filter column=”DOCMASTER.ENTRYWHEN” value=”CONVERT(datetime, ‘1/26/2011 0:00:00‘)” opp=”LE” type=”date” />
</DocFilters>
Running the MSGFIX utility:
Once the application is installed, the registry keys are created, and the XML file has been updated, we are ready to run the utility. When running agianst the full data set, the WorkSite Server should be stopped. When this is running against one document, it should be okay to leave it running.
In the installation directory, create a batch file with the following contents. This is what you will use to actually run the utility:
32 bit: “C:\Program Files\Interwoven\WorkSite\Server\MsgFix.exe” -mod e -cnfg “C:\Program Files\Interwoven\WorkSite\Server\config.xml”
64 bit: “C:\Program Files (x86)\Interwoven\WorkSite\Server\MsgFix.exe” -mod e -cnfg “C:\Program Files (x86)\Interwoven\WorkSite\Server\config.xml”
BACKUP YOUR WORKSITE DATABASE BEFORE YOU RUN ANYTHING!
Test on one document first:
First, we want to run the utility against a single email with missing information to confirm it will run correctly. To do this, adjust the xml with the single identified document number from earlier.
Run the batch file. Review the imMsgFix.log file in the same directory for errors. This looks good for one document:
Mon 11/07 13:35:47.229 : 573:Info2 [10292] START: MsgFix in execution mode.
Mon 11/07 13:35:47.402 :1209:Info2 [10292] updateProfile is successful for docnum :220881 and version: 1
Mon 11/07 13:35:47.435 :1229:Info2 [10292] FINISH: 1 MIME-type Documents fixed
Mon 11/07 13:35:47.435 :1238:Info2 [10292] No Errors found.
Mon 11/07 13:35:47.436 : 79:Info2 [10292] MSG Fix Successful
Mon 11/07 13:35:47.436 : 88:Info2 [10292] **** Ended MsgFix ***********
Run against entire data set:
If after updating the single document, it looks correct in FileSite, you can assume the rest will be the same. Adjust your dataset in the config.xml, stop the WorkSite server, and run the utility. Monitor until the log shows its complete, restart the server, and verify in Outlook.