Your Products have been synced, click here to refresh
VinniUSMC
Yea, I actually fixed that error at one point. Something to do with Microsoft.sqlserver.types being pointed at the wrong assembly.
I had to add this to dataimporter.exe.config and to another datapage config file.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
This forces SQL to use version 10 of sql types. But It's been about 3 years since I actually had to do it so I don't recall the actual info.
VinniUSMC
Yea, I actually fixed that error at one point. Something to do with Microsoft.sqlserver.types being pointed at the wrong assembly.
I had to add this to dataimporter.exe.config and to another datapage config file.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
This forces SQL to use version 10 of sql types. But It's been about 3 years since I actually had to do it so I don't recall the actual info.
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |