Getting black dlalog box wipe off screen, scroll back and message visible

Question

0.00/5 (No votes)

See more:

, +

Hi,

This is a weird one affecting some Win2016 VM Servers that I have some applications on.

So, we have a small farm setup Hyper-V Vms with 2016 servers. A couple of the servers running my .NET apps and seems to crash during the early hours of the mornings. Prior to December this was fine, but all of a sudden I am getting a black dialog box in which I cannot read the error message.

Once I grab the dialog box, move it off-screen with the mouse then back to the screen, the message is visible.

More times than not, it has "Memory Exception,""Low Memory," or "Insufficient Storage" in the error.

The Windows Logs that I have looked at don't seem to indicate anything in particular happening or Hyper-V picking up anything wrong either. Looking at Task Manager on the VM itself reveals nothing, no excess memory being used or low resources.

This is happening to VB6 apps as well as .NET apps that connect to "old" Windows2003 servers running SQL Server 2000 (we're still upgrading!) However, applications running on Windows2003 seem unaffected, as do the SQL Servers themselves.

The problem only seems to be happening from Win2016 servers using VB6 or .NET apps that are connected to the old SQL Server servers. Other .NET apps running on Win2016, that are running on SQLite with local databases with low memory usage are not having the issue.

Can anyone suggest anything that might be able to do, to track or specific logs that I might be able to take a look at? Any ideas thrown at me to look at would be great. Banging heads on wall at the moment with pressure from my boss.

Server RAM is quite large, being 16GB, barely ever touching more than 30% of it, CPU usage is extremely low too, under 20%. Though - if something is happening in the middle of the night, it's not being reported via alerts that have been set up on low resource.

Just at our wits end at moment with it.

What I have tried:

We have even rolled back December's patch update from MS, just in case that had affected, but it seems to have made no difference.

Posted 26-Jan-22 1:19am

Member 12561559

Updated 31-Jan-22 22:54pm

Sean Ewington

v2

Add a Solution

Comments

[no name] 26-Jan-22 13:25pm

VM's use memory too. Have too many or use the wrong memory settings. You need to use Task Manager / Performance Monitor to look harder at where the actual problem is. The logs won't tell you that.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 12561559 · Answer 1 · 2022-01-31T22:54:00

We found the issue - although our host VM gets rebooted during updates, the VM's themselves havent been and our ancient SQL Server 2000 servers hadn't been rebooted in over 600 days. No wonder ! Anyway - 3 days in from fresh reboots and no sign of the issue. Considering the applications we not even on the same server as the SQL Servers, I can only imagine the drivers (.net OLEDB) were getting overloaded with data from them - even though sometimes the issue was falling over bringing back one piece of text (10 chars max). Strange. Our engineer also did disable on-the-fly NGEN which may have also been part of the issue. The apps seem to run fine without it enabled. Thanks for taking a look anyway - it might be useful to someone in a similar situation.