Skip to main content
To homepage To homepage
Solved

Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=12.0.0.0

R
Contributor

hello,

I am upgrading to the latest TX and SQL 2022. When I want to deploy my project I get following error:

 

Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Location: Business Unit 'BU_CRH'.

Details:

Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
Module: TimeXtender.Sql.Engine.2014
System.IO.FileNotFoundException
   at TimeXtender.Sql.Engine.SqlEngineBase.InitializeFromSqlServer(SqlServer sqlServer)
   at TimeXtender.DataManager.DataSource_Sql.GetSqlEngine(Boolean startTransaction, Boolean singleConnection)
   at TimeXtender.DataManager.StepTableStructureRawDeploy.DoAbstractStep(StepSetup stepSetup)

 

Details of the SQL:

Microsoft SQL Server 2022 (RTM-CU13-GDR) (KB5040939) - 16.0.4131.2 (X64) 
  Jun 21 2024 21:57:17 
  Copyright (C) 2022 Microsoft Corporation
  Standard Edition (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor)

 

Any suggestion how to solve this.

Thanks,

Ronny

Best answer by rory.smith

Hi,

there should be more details available for the error that should give you more hints about what is going wrong. The error is an SSIS error: if you are not using (or wanting to use) SSIS, you should change settings to use ADO.Net. These settings can live at the project, BU/DWH, Source level and inherit downwards. If you are usign SSIS you will need to redeploy all packages because you are jumping from 2014 to 2022 SSIS, there could be alot of changes if your original packages were generated in even older versions of SSIS.

The error itself seems to indicate that the source defined for the package (in this case an AX table in source) cannot be reached by SSIS itself. 

View original
    Did this topic help you find an answer to your question?

    12 replies

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 651 replies
    • November 12, 2024

    Hi,

    it is looking for SQL 2014 dlls - I assume you are running 20.10.41 or higher as that is required for SQL Server 2022 support. Could it be that your databases are still running under older compatibility mode or that your settings are hard-setting the target version of SQL for your BU layer? You may need to change those to auto.

    R
    Contributor
    • rluyten
    • Author
    • Contributor
    • 11 replies
    • November 13, 2024

    hello Rory,

    Thanks, we set the compatibility to 2019 and it works.

    Now up to the next error when trying to deploy my first table:

     

    Error creating DTS package for dbo.AX_CRH_A_dbo_DATAAREA
    Exception from HRESULT: 0xC020801C

     

    If you know the solution let me know, in the meantime I will google it.

     

    Regards,

    Ronny

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 651 replies
    • Answer
    • November 13, 2024

    Hi,

    there should be more details available for the error that should give you more hints about what is going wrong. The error is an SSIS error: if you are not using (or wanting to use) SSIS, you should change settings to use ADO.Net. These settings can live at the project, BU/DWH, Source level and inherit downwards. If you are usign SSIS you will need to redeploy all packages because you are jumping from 2014 to 2022 SSIS, there could be alot of changes if your original packages were generated in even older versions of SSIS.

    The error itself seems to indicate that the source defined for the package (in this case an AX table in source) cannot be reached by SSIS itself. 

    Christian Hauggaard
    Community Manager
    Forum|alt.badge.img+5

    @rluyten which version of TimeXtender are you using? Which version of SSIS do you have installed on the application VM? can you please try to synchronize your data source and do a full load of the table by deploying the table and then clicking review tasks and then checking the deploy step and clicking start (please note this will truncate table and require a full load if it is an incremental table)?

     

    Could you please send some screenshots similar to the below, showing SSIS settings and deployment target

     

    Christian Hauggaard
    Community Manager
    Forum|alt.badge.img+5

    Hi ​@rluyten just following up on this - do you have an update on the questions above?

    R
    Contributor
    • rluyten
    • Author
    • Contributor
    • 11 replies
    • November 15, 2024

    hello, I am waiting for the server team to open some connections before I can do further test. I will update next week.

    Thanks,

    Ronny

    R
    Contributor
    • rluyten
    • Author
    • Contributor
    • 11 replies
    • November 19, 2024

    Hello,

    They opened the connection to the data source. Now I was able to deploy the BU, the DWH and the cubes. Currently executing.

    So it seems to work.

    Thanks for the replies.

    Regards,

    Ronny

    E
    Explorer
    • Erwins
    • Explorer
    • 14 replies
    • December 3, 2024
    rluyten wrote:

    Hello,

    They opened the connection to the data source. Now I was able to deploy the BU, the DWH and the cubes. Currently executing.

    So it seems to work.

    Thanks for the replies.

    Regards,

    Ronny

    What kind of connections were openend?

    We're experiencing the same error when deploying to SQL-server 2014.

    We’re not using SSIS, only ado.net and TX is installed on a separate VM.

     

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 651 replies
    • December 3, 2024

    Hi ​@Erwins ,

     

    are you using the default or a named instance in SQL 2014? If the latter, that can influence some of the ports involved? Note, you are also out of extended support with 2014 and should really upgrade.

    E
    Explorer
    • Erwins
    • Explorer
    • 14 replies
    • December 3, 2024

    Hi ​@rory.smith ,

     

    We’re using a named instance in SQL server 2014.

    Could you please specify which ports could be involved with this specific ‘ Could not load file or assembly ‘-error?

     

    p.s. we are aware of the eol of 2014, we’re upgrading next year but now we’re stuck on this version so we really need to get it to work.

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 651 replies
    • December 3, 2024

    Hi ​@Erwins,

    named instances use the dynamic ports by default (49152 - 65535). Each engine restart will trigger a new port potentially. The SQL Browser listens on port 1434 and will tell you which port your instance lives on.

    tl;dr : it depends entirely on your settings

     

    E
    Explorer
    • Erwins
    • Explorer
    • 14 replies
    • December 5, 2024

    Solved:

    The solution was to install the SQL Server 2014 developer edition on the APP VM.

    Only database engine was installed, but for some reason that removed the error.

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings