Jump to content

mavika

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mavika

  • Rank
    Newbie

Recent Profile Visitors

78 profile views
  1. mavika

    RemoteOperator w/Windows 10 Pro

    I installed the Microsoft fix and modified the .config file on another 3 machines, which also had this problem. This solved the issue on all of them. ­čśä
  2. mavika

    RemoteOperator w/Windows 10 Pro

    Hi, Saragani! Thank you very much for the responses! Meanwhile i have done some testing: Without modifying Remote Operator.exe.config or installing any .NET updates, the error message says: So for me, it looks like, Remote Operator is using 2.0 framework libraries. I then uninstalled 3.5 .Net framework (this includes .Net 2.0 and 3.0) Now when i try to start Remote Operator, it opens up a Windows dialog, complaining that the needed 3.5 framework (including 2.0 and 3.0) is missing, and it must be downloaded and installed. This makes sense. After that, i have placed the line that you suggested, in the Remote Operator.exe.config´╗┐ file: So, without installing any .Net framework, i can start Remote Operator, but the "red X" problem is still there, but the error message has also changed: Now its using 4.0 (4.7?) .Net libraries. After that, i installed .NET Framework 4.8 Early Access Build 3707 found here: https://go.microsoft.com/fwlink/?linkid=2032091 Doing so, the "red x" problem is solved! Your workaround is successful! I can now confirm, that to solve this "red x" toolbar problem, it's needed to do 2 things: 1. put the <startup><´╗┐supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup> line in the Remote Operator.exe.config´╗┐ file, AND 2. install the Microsoft fix: .NET Framework 4.8 Early Access Build 3707 https://go.microsoft.com/fwlink/?linkid=2032091 Perhaps, Microsoft will release an update via Windows Update once also. Thank you again Saragani for your help! -------------------------------- Note: this above issue has nothing to do with the other "red x" problem on the plc image, caused by the missing cache files:
  3. mavika

    RemoteOperator w/Windows 10 Pro

    Thank you Ausman, for the quick answer! We do not use Remote Access, but i installed it to try out, and its seems to work, without error messages. (it can show open-file-dialogs, without the above exception occouring). I changed now the Unitronics.RemoteOperator.dll to the one, that Saragani posted (from dll version 1.0.0.62 to 1.0.0.63), but the error message still appears. Saragani wrote: Meanwhile, i found this article: https://blog.jtbworld.com/2018/12/red-x-symbol-error-after-updating-to.html I downloaded the ".NET Framework 4.8 Early Access Build 3707" and installed it, tried out the Remote Operator, but it doesn't solved my problem. I wonder if Remote Operator even uses 4.8 .Net framework, or instead some older, 3.5 or 2.0 version.
  4. mavika

    RemoteOperator w/Windows 10 Pro

    Hello, We also have a problem with the Remote Operator running on a Windows 10 64 bit 1809 System. This error was not present on 1803 version of Windows 10. We tried to run the program on another machine, running this version of Windows, resulting the same error. The Remote Operator program is installed and executed as Admin. As soon as we try to open or save a project, by clicking on the open/saveas icon, the open/saveas dialog shows up, and the following exception error message appears (this exception occours also, when we click on the "Import cache file" menu item): Full error message in hungarian: remote operator hiba.txt After the error message, the program continues to work, but the upper section of its window shows no icons, and has a big red X on it. We tried to reinstall Remote Operator, reinstall .NET framework, run the program in various compatible modes with no success. Is there a more recent version of Remote Operator, or its development has stopped? Does anyone have some idea, what should we try out, to fix this problem? Reverting to older Windows version is not a soulution for us. Thanks: mavika
├Ś