[VisiLogic Run-Ttime error, Out of memory]

It seems, our problem is solved.

I uninstalled VisiLogic, i runned the Revo Uninstaller, and tried Wise Registry Cleaner too, deleted manually all VisiLogic remaining files,
and after some restarts, i installed the most recent VisiLogic_9.8.91 version as Administrator.
Running VisiLogic as Administrator no longer throws "Out of memory" errors.

A system restore would have been painful (despite we have frequent full backups), as many files are constantly changing,
and i also didn't looked into antivirus settings, as the reinstall solved our problem.

Thank you very much for all the suggestions!

[VisiLogic Run-Ttime error, Out of memory]

Hi AlexUT,  Ausman! Thank you for the answers!  

18 hours ago, AlexUT said:

Q1. What is a VisiLogic version you use.

The VisiLogic version we use is: 9.8.90

 

18 hours ago, AlexUT said:

- Run VisiLogic as administrator and test.

We will do a couple of tests, reinstalls and then I will report the results.

 

7 hours ago, Ausman said:

I'd also run Revo unistaller or similar to completely delete the previous installation before trying again.  Lastly, check what classification your A/V has Visilogic in, perhaps do some changes

The external uninstaller to clean all the things sounds good, we will try it.
What do you mean, that we should check our A/V classification? Antivirus?

[VisiLogic Run-Ttime error, Out of memory]

Hello!

We have "Out of memory" errors. It's not the PLC-s memory, it's the VisiLogic executable having this error.

This error has been common (once in every 2 hour) in the last month when using VisiLogic.

It occurs randomly while working, but mostly when using the clipboard, to Ctrl+C / Ctrl+V things.

The used VisiLogic version is: 9.8.90
Windows version: Windows 10 Pro 64 bit 10.0.18363.900
System memory: 8 GB (free memory 53%)

Since the VisiLogic binary is 32 bit, 8 GB of system memory (half of it free) should be enough for it to run.

With no luck, i have searched the Internet for this particular error, and have also found this thread: 

 

 

Does anyone else experience this kind of error? What can we try to solve this?

Thanks in advance:

mavika

 

[RemoteOperator w/Windows 10 Pro]

I can confirm, that with the recent Windows version the red-X-toolbar .NET problem is fixed.

Yesterday, i made a clean install of Windows 10 Pro 64 bit Build 1903 ,with Microsoft Media Creator Tool made USB stick.
(Full reinstall, not just update, i choose at install, to delete all partition and recreate them.)

After drivers and windows updates installed, i tried to install Remote Operator 1.0.71.

It shows up a dialog, it requires the .NET Framework version 3.5, clicking yes opens browser at dotnet.microsoft.com.

I do not downloaded anything, instead opened program-components in Windows, clicked the 3.5 Framework checkbox, and let Windows to install it.

After that, restarting the Remote Operator installer runs succesfully, and the program works normally,
it can connect to V130, V570, V1040 PLCs.

The open and saveas dialogs also works, the big-red-toolbar problem is not present.

[UniOPCThreadNode and processor load]

Thank you Isakovic for your reply!

I know this problem is there long ago, because of this,
in the past years we have also switched to Modbus/TCP from OPC wherever we can.

Sadly in these particular case we can not modify the PLC's installed.

I hope some developer at Unitronics can make a fixed version of the UniOPC Server,
or at least explain, why it uses all of the CPU even if there are no or very few OPC transactions performed.

[UniOPCThreadNode and processor load]

Hello!

Unfortunately, this high CPU problem is still present in UniOpcServer (2.0.14).

We use it to communicate with 4 PLCs (2x V1040 , V120 and V130),
and read 273 tags total, at 1 sec refresh rate.

As soon as the visualization software starts (Provicon VisionX9),
the CPU load goes to 100%, UniOpcNodeThread.exe uses 70-80%.

The PC which runs OPC server and the SCADA software has a i5-2400 CPU @3.1GHz.

The OS is Windows 10 64 bit 1903.

Is there a newer version of UniOpcServer available, or are there some settings to tweak?

Thanks in advance:

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. 😄

[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:

Quote

...
mscorlib
    Szerelvény verziója: 2.0.0.0
    Win32-verzió: 2.0.50727.9035 (WinRelRS5.050727-9000)
    Kódbázis: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
System.Windows.Forms
    Szerelvény verziója: 2.0.0.0
    Win32-verzió: 2.0.50727.9031 (WinRelRS5.050727-9000)
    Kódbázis: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
mscorlib.resources
    Szerelvény verziója: 2.0.0.0
    Win32-verzió: 2.0.50727.9035 (WinRelRS5.050727-9000)
    Kódbázis: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
...

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:

Quote

The line that was added to the config is just after the </userSettings> and before the </configuration>.

It's the: <startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup>    which tells it to target .Net framework 4.

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:
 

Quote

...
mscorlib
    Szerelvény verziója: 4.0.0.0
    Win32-verzió: 4.7.3260.0 built by: NET472REL1LAST_C
    Kódbázis: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
System
    Szerelvény verziója: 4.0.0.0
    Win32-verzió: 4.7.3314.0 built by: NET472REL1LAST_B
    Kódbázis: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Szerelvény verziója: 4.0.0.0
    Win32-verzió: 4.7.3260.0 built by: NET472REL1LAST_C
    Kódbázis: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
...

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:

 

[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:

Quote

No, it is being used by Remote Operator only, and it fixes just the trend issue.

 

Meanwhile, i found this article:

https://blog.jtbworld.com/2018/12/red-x-symbol-error-after-updating-to.html

Quote

“WinForms applications may have problems rendering the application UI and instead may render a white screen with a red ‘X’ symbol. The issue is caused by a change in Windows 10 October 2018 Update that exposed a bug in .NET Framework 4.7.2. The issue is caused by a change in Windows 10 October 2018 Update that exposed a bug in .NET Framework 4.7.2. The Windows 10 October 2018 Update adds a new flag to VisualStyle state when the application UI launches a child dialog (i.e., a FileSaveDialog or PrintpreviewDialog) that causes .NET Framework to fail its VisualStyleState check and thus throw an exception while rendering the application UI.”

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.

[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):

Quote

Visual Styles-related operation resulted in an error because no visual style is currently active.

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