Hotfix for Enterprise Vault for File System Archiving 9.0.2, Build 1061. Issues: Values in the filespecification table can be invalid. And CADODataAccess::AddParameter @Type_0 error during archiving run.

Article:TECH166559  |  Created: 2011-08-05  |  Updated: 2014-03-03  |  Article URL http://www.symantec.com/docs/TECH166559
Article Type
Technical Solution


Issue



Which version of Symantec Enterprise Vault (tm) can this hotfix be applied?
This hotfix can only be applied to the following versions of Enterprise Vault for:

Enterprise Vault for File System Archiving 9.0.2, Build 1061


Error



In the case of the issue corrected in Etrack 2162281, the following will be captured in a dtrace of the FSASummaryMigrator process.

(FSASummaryMigrator) <EVStore1:1172> EV-H {CONSOLEHELPER.EN_US} upgrade failed for vault store: VaultStoreName
 

In the case of the issue corrected in Etrack 2347288, the following will be logged to the event logs.
 

Type:  Error
Date:  2/25/2011
Time:  9:42:15 AM
Event:  13345
Source:  Enterprise Vault
Category: File System Archiving Task
User:  N/A
Computer: Computername.domain.com
Description:
An error was detected while accessing the Vault Database
'Provider=SQLOLEDB;Server=VaultServer;Database=Databasename_1_1;Integrated
Security=SSPI' (Internal reference: CADODataAccess::AddInputParameter @Type_0
.\ADODataAccess.cpp [lines {2148,2165}], built Nov 24 00:04:01 2010), error code
<0x800a0cc1>.

 


Cause



Both issues stem from a problem inserting certain values into the filespecification table.


Solution



What issue(s) does this hotfix resolve?
 

2162281 : The FSASummaryMigrator utility fails because there are some invalid (for xml) characters in the FileSpecification table in directory database.

2347288 : FSA- CADODataAccess::AddParameter @Type_0 during archiving run. Enterprise Vault was storing a large number of strange file extensions in the directory database. When the amount of file extensions reached 32,767 archiving would start failing because no more items could be added to the fingerprint database and the error mentioned in the title of ET 2347288 would occur.
 


Which files does this hotfix replace? 

File Name File Version
FSASummaryMigrator.exe 9.0.2.1130

Additional files included are:

File Name
Directory_Database_fnGetValidFileExtension_1.sql
Directory_Database_fixup_file_extensions_2.sql
Fingerprint_Database_fixup_member_tables_3.sql


How to Install this hotfix:

Before applying the Hotfix kindly go through the points mentioned in note section

1) Stop all the EV services
2) Take a backup of the directory database and all the fingerprint databases on the system
3) Run the sql script Directory_Database_fnGetValidFileExtension_1.sql against the directory database
4) a) Run the sql script Directory_Database_fixup_file_extensions_2.sql against the directory database.(As result, the script will generate .xml file)
     b) Left click on the output to open up the XML file.
     c) Save this XML file.
5) Run the sql script Fingerprint_Database_fixup_member_tables_3.sql against all the fingerprint databases in the system
6) Using the XML file saved in step 4 execute the following fixup stored procedure against all fingerprint databases in the system using the command:

exec dbo.FixUpFileTypeValues '@someXML' (running in CHECK mode)
  (Open up the XML file in notepad, select all, copy and then paste into the query in place of @someXML making sure the single quotes remain at beginning and end)

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) Using the XML file saved in step 4 execute the following command to FIX the entries in fingerprint database

exec dbo.FixUpFileTypeValues '@someXML', 1 (running in FIX UP mode)
 (Open up the XML file in notepad, select all, copy and then paste into the query in place of @someXML making sure the single quotes remain at beginning and end)

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) Take a backup of existing FSASummaryMigrator.exe present in Enterprise Vault installation directory.
9) Copy the new FSASummaryMigrator.exe in Enterprise Vault installation directory.
10) Start the EV services
11) Run FSASummaryMigrator.exe from command prompt.


Note-:

1)For Etrack#2347288 run steps from 1 to 7 and then run only step 10.
2)For Etrack#2162281 run all 1 to 11 steps
3)This hotfix only needs to be applied in instances where a large number of files with unusual file extensions have been archived or where the number of file extensions exceeds 32,767 and FSASummaryMigrator tool or FSAArchiving task fails because of unusual file extension.
4)This is a cumulative hotfix that supersedes HF 2347288, do not apply HF 2347288 after implementing this hotfix
5)The fixup stored procedure must not be run in fixup mode more than once against a fingerprint database.Corruption and data loss can occur

How to Uninstall this hotfix:

 

1) Stop all the EV services
2) Restore the backup of the FSASummaryMigrator.exe present in Enterprise Vault installation directory.
3) Start all the EV services
 

 


Attachments

EV 9.0 SP2 hotfix - Etrack 2162281 - Etrack 2347288.zip
EV 9.0 SP2 hotfix - Etrack 2162281 - Etrack 2347288.zip (27 kBytes)

Supplemental Materials

SourceETrack
Value2162281 and 2347288



Article URL http://www.symantec.com/docs/TECH166559


Terms of use for this information are found in Legal Notices