Skip to main content
To homepage To homepage
Solved

Not able to deploy after upgrade - Failed to connect (Azure Managed Instance) - Method Not found Exception

M
Starter

Hi,

We have upgraded our TXT environment from 20.10.14 to 20.10.43 last week.

Install and repository/existing projects upgrade went well.

We can save the project. The new scheduler service runs correctly. Execute action is ok. 

However, we encounter an exception during table deployment task (BU/STAGE or DWH table):

Failed to connect to server XXX (Azure Managed Instance)
Method not found: 'System.Net.Http.Headers.HttpResponseHeaders Microsoft.Identity.Client.MsalServiceException.get_Headers()'.

 

The connection settings (Repository/STAGE/DWH) seem correct (positive test connection): same Azure Managed Instance.

We have checked the .NET framework version - it seems recent 4.8.03761

Thanks for your help.

 

Best regards

Matthieu

Best answer by Thomas Lind

Hi @EelcoH 

We have a workaround, but not a release with a fix for this currently. I will send the method to you. A fix is currently being tested and will be released.

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

    5 replies

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1017 replies
    • July 4, 2023

    Hi @matthieu.carrat 

    We will try to figure out what is going on.

    M
    Starter

    Hi Thomas,

    Thank you for your message. 

     

    Indeed the error is on all the tables (stage and dwh). The databases are specifically on an Azure Manage Instance (same instance for all db including repository).

     

    Time: 2023-07-04 14:39:58
    UTC: 2023-07-04 12:39:58
    Title: xxx - TimeXtender 20.10.43.64
    Application: 20.10.43.64
    Repository: 20.10.43.64 (in Azure Managed Instance)
    SQL Server: Microsoft SQL Azure (RTM) - 12.0.2000.8 
        Apr 27 2023 03:47:17 
        Copyright (C) 2022 Microsoft Corporation

     

    It is strange, it seems a problem with the connection settings but we don’t find a missing param. We don’t know if it is linked to the MethodNotFound exception or if this last one is just a consequence of the connection problem.

     

    Thanks.

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

    Hi @matthieu.carrat I have created a support ticket for this, let’s keep the communication in the support ticket

    M
    1 person likes this
    • M
      matthieu.carrat
    E
    Explorer
    • EelcoH
    • Explorer
    • 5 replies
    • July 19, 2023

    Any outcome on this connection issue?
    We're encountering the same (upgraded from 20.10.26 to 20.10.43).

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1017 replies
    • Answer
    • July 31, 2023

    Hi @EelcoH 

    We have a workaround, but not a release with a fix for this currently. I will send the method to you. A fix is currently being tested and will be released.

    E
    1 person likes this
    • E
      EelcoH

    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