none
Can't see DQS knowledge base in SSIS DQS Cleansing component

    Question

  • I have created a knowledge base and published it.  But when I go to my SSIS package on the same SQL server and add a DQS Cleansing step I cannot see the knowledge base I have created.  I create a new data quality connection manager to the localhost and the test is successful but it doesn't show my knowledgebase.

    Why?  How can I get the knowledgebase to appear

    Tuesday, July 02, 2013 4:29 AM

All replies

  • Please see if this troubleshooting guide helps you:

    http://social.technet.microsoft.com/wiki/contents/articles/3777.troubleshoot-operational-issues-in-data-quality-services-dqs.aspx


    Arthur My Blog

    Tuesday, July 02, 2013 6:02 PM
  • Hi Arthur,  Thanks for your response.  I have checked this wiki and there are no answers there. 
    Tuesday, July 02, 2013 8:51 PM
  • Hi MMort,

    Please check whether the DQS Knowledge Base is published properly. To do so, click Open knowledge base in the home screen of Data Quality Client, and then check the Date Published column. Alternately, you can also check the PUBLISH_DATE column in the DQS_MAIN.dbo.A_KNOWLEDGEBASE table.

    Here are documents about creating a Knowledge Base and opening an existing Knowledge Base:

    Regards,
    Mike Yin

    If you have any feedback on our support, please click here


    Mike Yin
    TechNet Community Support

    • Proposed as answer by ArthurZMVP, Moderator Wednesday, July 03, 2013 5:24 PM
    • Unproposed as answer by MMort Wednesday, July 03, 2013 9:31 PM
    Wednesday, July 03, 2013 6:54 AM
  • When I select Open Knowledge Base from within the Data Quality Client the Date Published for my knowledge base is 7/2/2013 2:07:23PM.  The State column is empty.

    I can connect to the knowledge base fine using the client and re-publish but it's not visible from the SSIS package.  Everything, DQS, the SSIS package and the Data Tools and Data Quality client are all running on the same server.  I don't understand why I can't see my knowledge base from SSIS.  I can't see the default DQS Data knowledge base either. 

    Wednesday, July 03, 2013 9:41 PM
  • is that possible your SSIS install and SQL Server at different builds?

    Arthur My Blog

    Thursday, July 04, 2013 1:13 AM
  • No the software versions are the same.  See below

    Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report          
    Product Instance Instance ID Feature Language Edition Version Clustered
    Microsoft SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 Management Tools - Complete 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Microsoft SQL Server 2012 Integration Services 1033 Enterprise Edition: Core-based Licensing 11.0.2100.60 No
    Thursday, July 04, 2013 4:09 AM
  • Perhaps if you continue to have issues you need to repair/re-install SQL server

    Arthur My Blog

    Friday, July 05, 2013 1:44 AM
  • A suggestion made to me offline was that this maybe is a security issue of some sort?  I have checked my account is in the dqs_administrator, dqs_kb_editor and dqs_kb_operator roles on the DQS_MAIN database.

    I have aslo made sure I am running SQL data tools as administrator but still no luck. 

    Is there anywhere else I can check where an error may be being written when it queries for published KBs and finds nothing?

    Monday, July 08, 2013 1:25 AM
  • I'd start with inspecting the Windows Logs on both the target and source machines. I am also curious if you get any visual error messages.

    Arthur My Blog

    Monday, July 08, 2013 2:18 AM
  • No visual error messages at all.  Target and Source machine are the same. 
    Monday, July 08, 2013 2:29 AM
  • Do you see any errors in the Windows Logs?

    Also ensure you start SSMS as Admin.


    Arthur My Blog

    Monday, July 08, 2013 2:44 AM
  • Thanks.  yes I am seeing a whole lot of Unsafe Assembly errors like below

    07/08/2013 12:53:12,spid56,Unknown,Unsafe assembly 'system.serviceprocess<c/> version=4.0.0.0<c/> culture=neutral<c/> publickeytoken=b03f5f7f11d50a3a<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:12,spid56,Unknown,Unsafe assembly 'system.serviceprocess<c/> version=4.0.0.0<c/> culture=neutral<c/> publickeytoken=b03f5f7f11d50a3a<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.matching<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.matching<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.flow<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.flow<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.association<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.association<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.cleansing<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.cleansing<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.domainrules<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.domainrules<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.datavalueservice<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.datavalueservice<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.associationrules<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.associationrules<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).
    07/08/2013 12:53:09,spid56,Unknown,Unsafe assembly 'microsoft.ssdqs.index<c/> version=11.0.0.0<c/> culture=neutral<c/> publickeytoken=89845dcd8080cc91<c/> processorarchitecture=msil' loaded into appdomain 592 (DQS_MAIN.dbo[runtime].592).

    Monday, July 08, 2013 3:02 AM
  • Does the error occur when you try to connect to DQS?

    I'd clear the log up and then check for event triggers this error.


    Arthur My Blog

    Tuesday, July 09, 2013 12:20 AM
  • Yes these errors occur when I try to connect to DQS.  These are the errors in the log straight after.
    Tuesday, July 09, 2013 11:06 AM
  • I'd re-install as much as I can, may be even the OS.

    Arthur My Blog

    Tuesday, July 30, 2013 7:40 PM