Problem:
In the Free Plotting function, a rectangle cannot be drawn for the plot area. In the Line Trace Plot function, the calculation of the entered line trace leads to an error message.
In the log file (with DEBUG setting) and in the error message, a reference is made in each case to an assembly that was not found, e.g.:
- AedSicad.UT.Gis.Baselib, Version=10.2.1.5714
- AedSicad.UT.Gis.Framework, Version=10.2.1.5718
Impact:
This issue exists only in the UT Asset Manager. Both functions work correctly in the UT Editor. Without countermeasures, both functions are not usable in the UT Asset Manager. The problem cannot be fixed by the customer. However, there are workarounds (see Workaround).
Affected UT versions:
The problem has existed since the first build >6000 of UT 10.2.1 R3 (May 2020). The issue still exists in the current build 6310.
Workaround:
Option 1:
Check if the task can be done alternatively by the remaining plot functions in UT Asset Manager.
Option 2:
Check if the task can be done alternatively in the UT Editor.
Option 3:
Redirecting the wrong assembly version to the correct assembly version in the program config circumvents the problem.
To do this, edit the <installation path UT>\bin\AedSicad.UT.Applications.AssetManager.exe.config file. Note: <installation path UT> is usually C:\Program Files (x86)\AED-SICAD\ArcFM_UT.
In this file you will find the block <runtime> to </runtime>. Here the customization must be inserted.
At newVersion the build number of your current UT release must be entered.
Here is the customization for build 6310:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="AedSicad.UT.Cocolib" culture="" publicKeyToken="22d7f4664f141cba" />
<bindingRedirect oldVersion="10.2.1.5000-10.2.1.5999" newVersion="10.2.1.6310" />
</dependentAssembly>
</assemblyBinding>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="AedSicad.UT.Foundation" culture="" publicKeyToken="22d7f4664f141cba" />
<bindingRedirect oldVersion="10.2.1.5000-10.2.1.5999" newVersion="10.2.1.6310" />
</dependentAssembly>
</assemblyBinding>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="AedSicad.UT.Gis.Baselib" culture="" publicKeyToken="22d7f4664f141cba" />
<bindingRedirect oldVersion="10.2.1.5000-10.2.1.5999" newVersion="10.2.1.6310" />
</dependentAssembly>
</assemblyBinding>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="AedSicad.UT.Gis.CoreRuntime" culture="" publicKeyToken="22d7f4664f141cba" />
<bindingRedirect oldVersion="10.2.1.5000-10.2.1.5999" newVersion="10.2.1.6310" />
</dependentAssembly>
</assemblyBinding>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="AedSicad.UT.Gis.Framework" culture="" publicKeyToken="22d7f4664f141cba" />
<bindingRedirect oldVersion="10.2.1.5000-10.2.1.5999" newVersion="10.2.1.6310" />
</dependentAssembly>
</assemblyBinding>
Note: If the UT installation is executed again (repairing or modifying the installed components), the program config must be adjusted again! |
Solution:
The issue is solved in Build 6408
Comments
0 comments
Please sign in to leave a comment.