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.
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 reloading Studio Pro
"It appears that port 8090 is already in use. Please exist the application that uses that port,
of change the port number for this application in the Server tab of the App Settings dialog."
(exiting/reload will not resolve-must reboot system)
Hours later after having enough work around experience encountering anything/everything that can go kaputz: Wahlah, Run Project/View On Your Device finally works again.
By the way, who wants to hear an employee threaten another for saying it like is?
Months were spent on just creating a login process with authentication and password reset, Months were spent on dealing with multiple issues like the above.
Gratitude is given to those that have or have attempted to give solutions to issues that shouldn't exist in the first place. Product is so close to be the Crème de la crème if correctly tested and considerations of errors/ommissions are foreseen.
Reference: https://forum.mendix.com/link/questions/114603