EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB428974: Error message "Filter Unit-Filter Unit-COM interface error" appears when attempting to update schema in MicroStrategy Developer 10.5


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article shows one known issue that error message "Filter Unit-Filter Unit-COM interface error" appears when attempting to update schema in MicroStrategy Developer 10.5. This is due to some inconsistency of filter object associated with one metadata partition mapping table. Contact MicroStrategy Technical Support to identify this table and the problem filter. 

SUMMARY:
This document shows one known issue that error message "Filter Unit-Filter Unit-COM interface error" appears when attempting to update schema in Strategy Developer 10.5. This is due to some inconsistency of filter object associated with one metadata partition mapping table. Contact Strategy Technical Support to identify this table and the problem filter. 
 
SYMPTOM:
The following error message appears when attempting to update schema in Strategy Developer 10.5:

ka02R000000kV3QQAU_0EM440000002Wz3.jpeg


Error(s) occurred while loading schema: DSSSQL Eingine: Schema loading error: Filter (XXX). -Filter Unit-Filter Unit-COM interface error.

 
Searching the filter name shown in error message but it could not be found in Developer. 
 
CAUSE:
There is some inconsistency on one filter object which is associated with one metadata partition mapping table. 
 
ACTION:
In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.
 
WORKAROUND:
Contact Strategy Technical Support to identify the metadata partition mapping table and the problem filter. Once it is found, follow steps below:
1. Remove the attribute elements selected in this filter, change qualification to ID form and save this filter and partition mapping table. 
2. Update schema.
3. Edit partition mapping table and filter, change qualification back to element and add original selected elements. 
 
This issue has been logged as Scopus ID: 174846 and  KB428974


Comment

0 comments

Details

Knowledge Article

Published:

July 17, 2017

Last Updated:

December 12, 2018