hexagon logo
Register Sign in
  • Replies 44 replies
  • Subscribers 10 subscribers
  • Views 1083 views
  • Users 0 members are here
Options
Related

External Command Fail

KIRBSTER269
So I finally got my new computer for other machine. Did a fresh new install of PC-DMIS and Datapage +5.2, on windows 10. So a few of us still use the External Command, Listening at the top and End at the bottom. Well if you don't install Datapage 5.0 and install 5.2, this little knickknack don't work. spent all day with Hexagon just to find this out. Now if you put External Command without -END or -E it works which takes a while to record. You have to have Data Importer 5.0 gathering info and Datapage 5.0, and it will still show up in DataPage 5.2. Now it actually seems to work fine on my windows 7 computer, even though I have both Datapages installed, I do use the Data Importer 5.2 gathering the information, results no problem. So I'm kinda guessing this might be a Windows 10 thing. Now Stats update seems to work no problem.

One more thing to add, I'm sure Hexagon will get right on this and fix it Rolling eyes
Parents


  • 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.
Reply


  • 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.
Children
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement