Skip to main content
Solved

Not able to deploy after upgrade - System.Runtime.InteropServices.RuntimeInformation error


Forum|alt.badge.img

Hello TimeXtender,

 

Yesterday we've upgraded our PROD environment from 20.10.25 to 20.10.43. Install went fine and upgrading of the repository as well. However, when we went to validate the upgrade by carrying out a deploy and execute of an arbitrary table in the DSA we received the following error message:

 

The type initializer for 'Microsoft.Data.SqlClient.InOutOfProcHelper' threw an exception.
Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
 

Do you have any experience with this error message? Might be good to note that we first carried out the upgrade on our DEV environment and we did not receive the same error message there. We've also tried to rule out that the error was table specific by carrying out a deploy & execute on different tables/layers, but the error persisted.

 

Best regards,

 

Luuk Bouman

Best answer by Christian Hauggaard

Hi @luuk.bouman 

Since 20.10.41 the required version of .NET framework is 4.8 or higher. The article has been updated to reflect this now. Apologies for any inconvenience caused. 

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

9 replies

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

Hi @luuk.bouman 

Which version of .NET framework are you running on DEV and PROD? .NET verification is described in the following article

 


Forum|alt.badge.img
  • Author
  • Participant
  • 17 replies
  • June 26, 2023

Hi Christiaan,

 

There was indeed a difference where DEV was running on 4.7.0 and PROD on 4.6.0. After the installation of TX 20.10.43 we upgraded PROD to .NET 4.7.0 as well, but the error persisted.

 

Would you say that the order would be important in this scenario? So first upgrade .NET and then TX?

 

Best regards,

 

Luuk


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

Hi @luuk.bouman thanks for checking. Have you rebooted the PROD VM after the .NET upgrade?


Forum|alt.badge.img
  • Author
  • Participant
  • 17 replies
  • June 26, 2023

Yes


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

Can you please try to reinstall TX 20.10.43 on PROD now that the .NET framework has been upgraded?


Forum|alt.badge.img
  • Author
  • Participant
  • 17 replies
  • June 26, 2023

We reinstalled TX 20.10.43 but the error persists.


Forum|alt.badge.img
  • Author
  • Participant
  • 17 replies
  • June 26, 2023

Got it working!

We found out that the learn page from Microsoft for the System.Runtime.InteropServices.RuntimeInformation states that it is only incorporated starting .NET Framework 4.7.1. We then doublechecked our versions and found that DEV indeed had 4.7.2, but PROD had 4.7.0. So we went to install 4.7.2 on PROD, restarted and TX is now functioning properly.

 

@Christian Hauggaard the TX prerequisites article states that .NET Framework 4.6.2 is the lowest supported version. Do you know what necessitated a higher version in our case?

 

Best regards,

 

Luuk


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

Hi @luuk.bouman 

Since 20.10.41 the required version of .NET framework is 4.8 or higher. The article has been updated to reflect this now. Apologies for any inconvenience caused. 


Forum|alt.badge.img
  • Author
  • Participant
  • 17 replies
  • June 26, 2023

Hi Christian,

 

No worries. I'm glad we were able to get it to work. Thank you for your assistance!

 

Best regards,

 

Luuk


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