FSA upgrade utility (FSASummaryMigrator) fails and reports an 'invalid character' error in its log file and in DTrace

Problem

If certain non-standard characters get inserted into in the FileSpecification table of the Enterprise Vault Directory database, the FSA upgrade utility (FSASummaryMigrator) fails with an error in its log file.

Error Message

The utility generates an error similar to the following in its log file:

Error: '<character>', hexadecimal value <hex_value>, is an invalid character.
upgrade failed for vault store: <vault_store_name>

where <character> is an invalid character for XML, and <hex_value> is the hexadecimal value of the character.


A DTrace of the FSA upgrade utility (FSASummaryMigrator) reveals an error similar to:

hexadecimal value 0xXX is an invalid character

Cause

The utility fails if some characters that are invalid for XML get introduced into the Directory database's FileSpecification table.

Solution

For Enterprise Vault 9.0.3, follow the instructions below to fix this issue. 

Note:

  1. The fixup stored procedure must not be run in fixup mode more than once against a fingerprint database, otherwise corruption and data loss can occur.
  2. The SQL script Directory_Database_fixup_file_extensions_2.sql has been updated to address a Constraint Issue.

 

To apply the fix for Enterprise Vault 9.0.3

 1) Download the attached zip file, which contains two SQL script files as follows:
 

File Name
Directory_Database_fixup_file_extensions_2.sql
Fingerprint_Database_fixup_member_tables_3.sql

2) Stop all the Enterprise Vault services.
3) Take a backup of the Directory database and all the fingerprint databases on the system.
4) Run the SQL script Directory_Database_fixup_file_extensions_2.sql against the Directory database. As result, the script will generate an .xml file.
5) Run the SQL script Fingerprint_Database_fixup_member_tables_3.sql against all the fingerprint databases in the system.
6) Execute the following fixup stored procedure against all fingerprint databases in the system using the command:

    exec dbo.FixUpFileTypeValues '@someXML' (running in CHECK mode)

    where @someXML is the xml generated in step 4.

   This will produce the following output, which details what will be done on a fix up run:

   running in CHECK mode
   xml contains [14] extensions to verify and fix up
   MemberTable_000 has [13] file extensions to verify PRE-fixup
   ...

7) Execute the following command to FIX the entries in fingerprint database:

    exec dbo.FixUpFileTypeValues '@someXML', 1 (running in FIX UP mode)
    
    where @someXML is the xml generated in step 4.

    This will produce the following output:

    running in FIX UP mode
    xml contains [14] extensions to verify and fix up
    MemberTable_000 has [13] file extensions to verify PRE-fixup
    MemberTable_000 updated [13] file extensions during fixup
    ...

8) Start the Enterprise Vault services.
9) Run FSASummaryMigrator.exe from command prompt.
 



This issue has been addressed as part of the following release:

Enterprise Vault 9.0.3 - Release Details
http://www.symantec.com/docs/TECH147782

Enterprise Vault 10.0.1 - Release Details
http://www.symantec.com/docs/TECH147787

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)