Hello,
Recently, when working in a Visual COBOL 4.0 Visual Studio 2017 environment, if we leave Visual Studio 2017 up for a length of time, we get the following Visual Studio 2017 error. We then have to kill Visual Studio 2017 via Task Manager.
Has anyone else experienced this? Could this have been caused by a Microsoft update?

Are you on Patch Update 29, which is the latest one, with Visual COBOL 4.0?
What is the version (15.9.x) of Visual Studio 2017 you are on?
Are you on Patch Update 29, which is the latest one, with Visual COBOL 4.0?
What is the version (15.9.x) of Visual Studio 2017 you are on?
Hello,
sorry for the late reply.
Patch update 29 was installed with VC 4.0.
Still experiencing the same problem after the VC 4.0 patch 29 update.
Posted a ticket to Microsoft thinking that this may be an issue on Microsoft side. After their review, they believe this is an error caused by Visual COBOL and not Visual Studio.
We continue to receive the error, if we leave Visual Studio 2017 open for a period of time.

Microsoft Visual Studio Professional 2017
Version 15.9.53
VisualStudio.15.Release/15.9.53+33423.255
Microsoft .NET Framework
Version 4.8.04084
Any help on this would be greatly appreciated.
Thank you,
Doug
Hello,
sorry for the late reply.
Patch update 29 was installed with VC 4.0.
Still experiencing the same problem after the VC 4.0 patch 29 update.
Posted a ticket to Microsoft thinking that this may be an issue on Microsoft side. After their review, they believe this is an error caused by Visual COBOL and not Visual Studio.
We continue to receive the error, if we leave Visual Studio 2017 open for a period of time.

Microsoft Visual Studio Professional 2017
Version 15.9.53
VisualStudio.15.Release/15.9.53+33423.255
Microsoft .NET Framework
Version 4.8.04084
Any help on this would be greatly appreciated.
Thank you,
Doug
Hi Doug,
We are not really sure what is causing the problem but Visual COBOL 4.0 for Visual Studio 2017 is unsupported. I would suggest upgrading to the latest Visual COBOL 8.0 for Visual Studio 2022 and then if you have a problem we can actually research it.