Question

Studio Pro 9.12.0 Run Local Fails

2

Update:2022/03/21 02:32AM CST It is believed the below log is caused by CPU dedgradation By McAfee Total Protection Version 16.0 Release 16.0 R44 Real Time Scanning causing timeout issues. If this is true, Mendix should be getting together with McAfee and other vendors to recognize the Mendix and projects as not a threat. (Also Norton, Avast, etc, as testing was performed on other systems) If true, no one has a clue that this has wasted 6 months of mine and others time. Enhance error logs to be more direct and comprehensive. It is greatly appreciated the one in the Forum brought up the idea of COMPLETLY disabling/reinstalling anti-virus but appears to be a component, not the anti-virus software suite overall. System.OperationCanceledException: The operation was canceled. at System.Net.HttpWebRequest.GetResponse() at Mendix.Modeler.M2EEConnector.M2EERequest.DoHttpRequest(String json, Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 182 at Mendix.Modeler.M2EEConnector.M2EERequest.Execute(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 72 at Mendix.Modeler.M2EEConnector.M2EEClient.Ping(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EEClient.cs:line 42 at Mendix.Modeler.M2EEConnector.RuntimeLauncher.EnsureStarted(String logFileLocation, Int32 serverPort, M2EEClient client) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 224 at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 56 at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234 at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223 at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29 at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) Once Real Time Scanning was turned off, build completed, and started showing normal console messages. It is still believed the "View Native Mobile App" should be the default tab. **********Now, back to the red screen of death log on device.********** "The development server returned response error code: 500" Overall seems to be complaining about atlas core Deployment Logs Clues: build_core_compile package_log.txt Buildfile: C:\Users\bloye\Documents\Mendix\MyApp-main 9-11-1-40456\deployment\build_core.xml compile: [javac] Compiling 511 source files to C:\Users\bloye\Documents\Mendix\MyApp-main 9-11-1-40456\deployment\run\bin [javac] Note: Some input files use or override a deprecated API. <-Again, Mendix should not be dependant on 3rd party changes. Exactly what was deprecated. Error should have been given before build. [javac] Note: Recompile with -Xlint:deprecation for details. package: [jar] Building jar: C:\Users\bloye\Documents\Mendix\MyApp-main 9-11-1-40456\deployment\model\bundles\project.jar BUILD SUCCESSFUL Total time: 26 seconds On Dismiss: "Something went wrong! Something went wrong when loading the JD bundle." "GO BACK" button does nothing. What the (insert word) went wrong. Very irritated again. Additional information ProcessBundleResult BundleDownloader.java:264 access$200 BundleDownload.java:34 onChunkComplete BundleDownloader.java:193 emitChunk MultipartStreamReader.java:70 readAllParts MultipartStreamReader.java:152 processMultipartResponse BunderDownload.java:177 access$100 BundleDownload.java:34 onResponse BundleDownload.java:147 execute RealCall.java:203 run NamedRunnable.java:32 runWorkder ThreadPoolExecutor.java:1167 run ThreadPoolExecutore.java:641 run Thread.java:923 Note: Cannot find a way to copy text from red screen of death, only can take screen shots. Back to square 0 on another day. ------------------------------------------------------ Update: Upgraded to Studio Pro 9.11.1 Update: Again after trying over and over and over to restore corrupt project ?due to market place modules? I’m back to the same thing over and over. ---------------------------------- After months of diddling around with duplicate jars that mendix doesn’t auto cleanup/handle pre&coReqs, upgrading versions of studiopro/modules/widgets/etc, dealing with file locks (project/log) even with app closed which requires a reboot to access, messing with clean directory/sync app that should be an auto function, now I cannot find a solution for the below. The only posting talks about changing runtime port from 8080 to 8888 which does not resolved the problem. I’m sure the fix is obvious to some, but is not to me. Input appreciated.. System.OperationCanceledException: The operation was canceled. at System.Net.HttpWebRequest.GetResponse() at Mendix.Modeler.M2EEConnector.M2EERequest.DoHttpRequest(String json, Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 182 at Mendix.Modeler.M2EEConnector.M2EERequest.Execute(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 72 at Mendix.Modeler.M2EEConnector.M2EEClient.Ping(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EEClient.cs:line 42 at Mendix.Modeler.M2EEConnector.RuntimeLauncher.EnsureStarted(String logFileLocation, Int32 serverPort, M2EEClient client) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 224 at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 56 at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234 at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223 at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29 at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

asked 2022-03-12

Rosewater Development LLC

8 answers

0

Thank You Robert for taking the time (seriously). I believe you were able to nudge me a little bit further past the road blockSSSSS. It ?appears? that McAfee Antivirus may have gotten in the way (not sure if some update changed how it perceives Mendix), but I am also still having other issues (seems as if I have multiple issues since you were able to simply build and execute). I’m going to place some information here for the next poor sap that might encounter my craziness in case it might help them. Again, Thank You. It take people like you to still make others believe there is something left of humanity and to press on to make this world a little bit better.

Intermittent Insanity ("Results Vary")

McAfee Total Protection v 16.0 R:16.04 "Real Time Scanning"
conflicting with
Mendix Studio Pro v X-9.11.1 40456 "Run Locally"
(after multiple attempts to resolve pre/coreq/dupicate jar issues not being automatically handled by MSP)
ROI: Negative to the Nth degree of the MONTHS of lost development time

Scenario:
McAfee Real Time Scanning is on
Mendix "Run Locally" executed
Result: Error "The server failed to start. See details for the server log."
Details:
System.OperationCanceledException: The operation was canceled.
at System.Net.HttpWebRequest.GetResponse()
at Mendix.Modeler.M2EEConnector.M2EERequest.DoHttpRequest(String json, Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 182
at Mendix.Modeler.M2EEConnector.M2EERequest.Execute(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 72
at Mendix.Modeler.M2EEConnector.M2EEClient.Ping(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EEClient.cs:line 42
at Mendix.Modeler.M2EEConnector.RuntimeLauncher.EnsureStarted(String logFileLocation, Int32 serverPort, M2EEClient client) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 224
at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 56
at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234
at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223
at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Scenario continued:
McAfee Real Time Scanning turned off
Mendix "Run Locally" executed
Result: (Immediate as no server actions appear to be happening) Error "The server failed to start. See details for the server log."
Details:
System.IO.IOException: The process cannot access the file 'C:\Users\bloye\Documents\Mendix\Project-main 9-11-1-40456\deployment\log\m2ee_log.txt' because it is being used by another process.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
at Mendix.Modeler.Utility.FileSystem.OpenNewTextFileForWriting(String filePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\FileSystem.cs:line 231
at Mendix.Modeler.M2EEConnector.RuntimeLauncher.SetLogWriter(Process process, String logFileLocation) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 162
at Mendix.Modeler.M2EEConnector.RuntimeLauncher.StartM2EEServer(LaunchConfig launchConfig, String logFileLocation) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 73
at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 53
at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234
at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223
at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Scenario continued:
Mendix close Studio Pro/Reopen/"Run Locally"
"Your app ist starting, we will let you know when....."
Results: Warning
"It appears that port 8090 is already in use.
Please exit the application that uses that port, or change the port number for this application in the Server tab of the App Settings dialog.
?Should one be phsychic to know which "port" to use? Why should one have to muck with this when they haven't had to for years? ??????

Scenario continued:
Mendix close Studio
Reboot
Note: McAfee tuned real time scanning back on, violating request to wait 60 minutes (before reboot was executed)
Turn McAffee Real Time Scanning off AGAIN
Reopen
"Run Locally"
Console messages finally start happening
(Note: Another previous issue. Must reboot and manually delete deployment directory and then Sync project as Mendix holds a lock on project.jar)
Scenerio continued:
Have got to this point before while attemptimg to load mobile app via "Make It Native" which results in the red screen of death everytime starting with error code 500.
This round, going to use a different mobile device. (Android Samsung S20)
Thought: Device space issue not monitored by Mendix?
"View On You Device"
"View Native Mobile App"<-Issue: This tab should be first
On Mobile open Make it Native and scan QR code
Connect to you app Via local IP address: http://192.168.154:8080/ (Wireless)
Load with orange status bar
Mobile Red Screen of Death AGAIN
Note: Can only be captured by mobile screen shot, actual text cannot be copied for analysis.

Console shows: (see attached)

--------

com.mendix.systemwideinterfaces.MendixRuntimeException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30015/30000 ms
at com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:23)

Caused by: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30015/30000 ms
   at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:257)
   at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:639)
   at java.base/sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:341)
   at java.base/sun.nio.cs.StreamEncoder.close(StreamEncoder.java:161)
   at java.base/java.io.OutputStreamWriter.close(OutputStreamWriter.java:258)
   at com.mendix.util.using.Using$.using(Using.scala:8)
   at com.mendix.modules.debugger.internal.DebuggerHandler.doProcessRequest(DebuggerHandler.scala:66)
   at com.mendix.external.connector.MxRuntimeConnector.$anonfun$processRequest$1(MxRuntimeConnector.scala:50)
   at com.mendix.external.connector.MxRuntimeConnector.$anonfun$processRequest$1$adapted(MxRuntimeConnector.scala:50)
   at com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:20)
   at com.mendix.external.connector.MxRuntimeConnector.processRequest(MxRuntimeConnector.scala:50)
   at com.mendix.basis.impl.MxRuntimeImpl.processRequest(MxRuntimeImpl.scala:213)
   at com.mendix.m2ee.appcontainer.server.handler.RuntimeServlet.service(RuntimeServlet.scala:25)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
   at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
   at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1631)
   at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:228)
   at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
   at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
   at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:548)
   at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
   at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
   at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
   at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434)
   at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
   at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
   at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
   at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
   at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349)
   at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
   at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
   at org.eclipse.jetty.server.Server.handle(Server.java:516)
   at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:400)
   at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:645)
   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:392)
   at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
   at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
   at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
   at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
   at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
   at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
   at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
   at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
   at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
   at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
   at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
   at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.util.concurrent.TimeoutException: Idle timeout expired: 30015/30000 ms
   at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
   at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
   at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
   at java.base/java.lang.Thread.run(Thread.java:834)

It is believed this red screen of death was dealt with a long time ago but do not recall the solution.
Hmmmmmmm, the Idle timeout expired looks familiar with a function needed to monitor a particular situation regularily.

I'd really like to interject a Masty Gram right now, however I know it would just be called abuse.
How much more abuse must I take as a "Citizen Develper"? There are no cheecks left to turn.
Tik Tok!

answered 2022-03-19

Rosewater Development LLC

0

Screen Shots

answered 2022-03-19

Rosewater Development LLC

0

More screen shots

answered 2022-03-19

Rosewater Development LLC

0

More relative screen shots of unit testing.

answered 2022-03-19

Rosewater Development LLC

0

It does feel that your antivirus software may be at the heart of the problem. Is it possible to disable all the antivirus functionality and scanning it may have in place. Reboot, then reinstall Mendix. Reboot again, and try you project. My hope would be with it disabled it will allow an error free install of Mendix Studio Pro, and being still disabled, it will allow your application to compile and run as expected.

Good luck!

answered 2022-03-19

Robert Price

0

Please mark as resolved.

Mobile Development-Informational Only To Benefit Others of What Not and To Do

After 3 YEARS of performing proof of concept for 5 standard functionalities, After MONTHS (not kidding-calculate that ROI) of trying to fix a corrupt project even when reverting to prior working versionS, incredibly irritated and frustrated of having to use 3 different resources (web vs Studio Pro), no prereq/coreq handling and/or automagic upgrading of EVERYTHING i.e. Marketplace Modules/Widgets/Atlas/etc. Also including, file locks after exiting Studio Pro (including 9.12.1), issues caused by timeout issues due to other system resources being used, issues requiring Studio Pro reload, issues requiring System Reboot, issues with high availability/outages. One has to guess when what things needs to be done.

Who the (insert word-s) is doing Unit/Component/System/GA (General Availability Testing)/UAT (User Acceptance Testing)? Green horns fresh out of University with no Fortune 500 experience? It appears that few are doing mobile development from experiences and the number of job offerings that are not specifically mobile.

Opinion/Warning: If you have a working project SERIOUSLY consider NOT upgrading Studio Pro,

Market Place Components, Widgets, Atlas, etc. etc. Thinking upgrading will make your project better

by attempting to fix bugs you may not have encountered yet may not produce the same results as upgrading/being current with the latest operating system/virus software/etc versions to be current.

Even if you stay a few versions behind to be sure any bugs have been shaken out by the updates/fixes.

i.e.

~3:14 AM Thursday, April 14, 2022 (CDT)

After continuing development the following day having left Studio Pro open "The server failed to start. See details for the server log."

Details>>

System.IO.IOException: The process cannot access the file 'C:\Users\bloye\Documents\Mendix\MyProject-main\deployment\log\m2ee_log.txt' because it is being used by another process.

at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)

at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)

at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)

at Mendix.Modeler.Utility.FileSystem.OpenNewTextFileForWriting(String filePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\FileSystem.cs:line 231

at Mendix.Modeler.M2EEConnector.RuntimeLauncher.SetLogWriter(Process process, String logFileLocation) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 162

at Mendix.Modeler.M2EEConnector.RuntimeLauncher.StartM2EEServer(LaunchConfig launchConfig, String logFileLocation) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 73

at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 53

at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234

at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223

at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

After reboot

System.OperationCanceledException: The operation was canceled.

at System.Net.HttpWebRequest.GetResponse()

at Mendix.Modeler.M2EEConnector.M2EERequest.DoHttpRequest(String json, Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 182

at Mendix.Modeler.M2EEConnector.M2EERequest.Execute(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EERequest.cs:line 72

at Mendix.Modeler.M2EEConnector.M2EEClient.Ping(Int32 timeout) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\M2EEClient.cs:line 42

at Mendix.Modeler.M2EEConnector.RuntimeLauncher.EnsureStarted(String logFileLocation, Int32 serverPort, M2EEClient client) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 224

at Mendix.Modeler.M2EEConnector.RuntimeLauncher.LaunchRuntime(LaunchConfig launchConfig) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.M2EEConnector\RuntimeLauncher.cs:line 56

at Mendix.Modeler.Deployment.Local.LocalRunner.DoLaunchRuntime(IConfiguration config, String javaExePath) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 234

at Mendix.Modeler.Deployment.Local.LocalRunner.<>c__DisplayClass63_0.<LaunchRuntime>b__0() in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Deployment\Local\LocalRunner.cs:line 223

at Mendix.Modeler.Utility.BackgroundUtil.<>c__DisplayClass1_0`1.<Do>b__0(Object s, DoWorkEventArgs e) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.Utility\BackgroundUtil.cs:line 29

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

After disabling McAfee Total Protection V16R45 Real Time Scanning

making system vulnerable to attacks.

(Issues are also with other products such as Avast

System.IO.IOException: The process cannot access the file 'C:\Users\bloye\Documents\Mendix\MyBeverageBuddy-main\deployment\log\m2ee_log.txt' because it is being used by another process.