Powershell 4.0 - Mixed mode assembly issue

Question

Morning,

Since updating Adaxes to the latest version that uses Powershell 4.0 we are unable to query SQL 2008 R2 database in a scheduled task.

The Activity History provides the following error:
Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. Stack trace: at <ScriptBlock>, <No file>: line 20

This is a sample of the script we are trying to run:

1: Import-Module Adaxes
2: add-pssnapin sqlserverprovidersnapin100
3: add-pssnapin sqlservercmdletsnapin100
...
20: $list= invoke-sqlcmd -query "SELECT ..." -Database 'DB' -ServerInstance 'Server' -Username 'User' -Password 'Pass'

Seems like we should be able to update a .config file to support mixed mode?
https://stackoverflow.com/questions/642 ... he-runtime

Any assistance would be appreciated.

Regards, Ben

Answer 1

After trial and error the solution for us was the following.

Edit the Softerra.Adaxes.Service.exe.config file on the server (e.g. C:\Program Files\Softerra\Adaxes 3\Service\Softerra.Adaxes.Service.exe.config).

At the bottom of the file before the closing configuration tag add the highlighted section:

<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>

Save and restart the Softerra Adaxes Service.

Comments

Hello,

Thank you for sharing the solution.

The issue occurs because of a bug with the Invoke-Sqlcmd cmdlet in .NET framework 4.5.2 which Adaxes 2018.1 targets. Details can be found in the following post on Microsoft blogs: https://blogs.msdn.microsoft.com/aseemb ... formation/.

---

This also fixed my Related Problem with the current Microsoft.Online.SharePoint.PowerShell Module.

under Adaxes you got -

Import-Module : Could not load type 'Microsoft.SharePoint.Administration.DesignPackageType' from assembly 'Microsoft.SharePoint.Client, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.

running it under a normal Powershell it worked fine. (Adaxes 2019.2)