If I try to run a program in debugging mode I get "Cannot create process: cannot find the specified file", while it works without problems in released mode. I found the same problem discussed here several years ago. Carefully I followed all the suggestions of that old case but without any good result. Of course I checked all the security staff and compatibilities. I run the Delphi 10.4.2 on a Dell 9510 with windows 11 and Microsoft defender only. I checked also the firewall and open ports.
Can someone give me an hint. Thankyou
More of what I wrote before I have reinstalled Delphi and made a run of Dell diagnostics for what the Laptop OS and HW is concerned.
The program, in the present and actual version works without problem but I need to modify it and I cannot do that if I cannot get debugging info and step by step running.
Related
I've been a happy user of MobaXterm for years, this is a great terminal and X-window manager on Windows to access Linux machine and others. Recently, possibly since I upgraded to Windows 11 or changed laptop, I sometimes get the following error window:
An error occurred while starting the following MobaXterm subprocess:
"%APPDATA%\MobaXterm\slash\bin\MobaSCPRinew.exe"
Access is denied
I could not figure out which action is triggering this error but it is pretty rare and seems to happen either when I switch from one tab to another or when I unlock my computer after a while but I can't reproduce it systematically. I'm using MobaXterm Personal Edition v22.0 Build 4858.
This executable exists on my system and the file properties mention that this is a "Command-line SCP/SFTP client". However, even after the error, the SSH Browser available in the side bar (provided you only show one tab) is still visible and working.
Does anybody know what could be causing this?
Thanks
[EDIT]
I contacted the support of MobaXterm:
they told me it is a known bug related to the "Remote Monitoring" feature, which can display stats about memory, disk usage, connected users,...
advised me to test the preview version 22.2 since the bug seems fixed in that release
I used it for a few days and the issue never happened. I will download the latest official release 22.1 and, if it happens also in that one, will wait for the official 22.2. I will close this issue once the bug is fixed in an official release.
Same issue here, with some slight differences:
Location seems to be the "Documents" folder of my "Onedrive":
E:\OneDrive - xyz\Documents\MobaXterm\slash\bin\MobaSCPRinew.exe"
I use the "professional edition" with the same license ID, so I suppose technically it is the same software.
Issue only popped up till now after a reboot of my system, launching the MobaXterm and subsequently starting an ssh session.
Restarting MobaXterm only (once) didn't produce the issue.
I now upgraded to 22.1. Since the release notes do not mention anything concerning this issue, I can't know for sure the problem will be solved. I'll report back when it reoccurs.
Johan
Alright StackOverflowians, this is a strange one, so bear with me and be kind. Also, this may be more of a question for ServerFault, but I'm hoping other developers out there may have seen this behavior and / or have some insight.
I have a VB6 application (custom built but the source code is long gone) which is running on a Windows Server 2012 R2 VM. When I connect to the VM using an RMM utility (ConnectWise) I can run the application as expected and everything is happy and good. However, when I connect to the VM over traditional RDP, the application crashes on startup and cites the error as COMCTL32.DLL, Exception Code: c0000005. I login as the same user in both scenarios.
I believe that this did work over RDP once-upon-a-time, but it's been probably 6 - 8 years since I've done this.
I've been finding information about the exception code listed above as an "Access Violation" and have followed some steps to disable Data Execution Prevention, but this had no effect. If I wasn't seeing this with my own eyes, I would not believe it is happening. Would welcome any tips or information, especially if you've seen similar behavior before.
I'm having a very strange problem with an application in windows 10. It consists of several .exe in the same computer communicating between them with sockets using system.net.sockets library.
The problem I have is that after installing Windows 10 in a new computer, install all windows updates and then installing that application, connection to sockets doesn't work correctly and the application fails. The strangest thing is that if you leave the computer alone for 1-2 days the applications starts working just fine. The same has happened after installing version 1803 update, it stops working and then works one or two days later.
Any idea of what can it be? Has anyone seen something similar?
It really seems to be related to the 1803 update you mentioned.
Symptoms:
Running an application from a network share will fail when creating a socket;
Copying the very same application to a local drive/path will work just fine, without any further modification.
We are also struggling with this while connecting to an Oracle database (both ODBC and ODP.NET) and it seems the issue has recently been acknowledged:
https://support.oracle.com/knowledge/Oracle%20Database%20Products/2399465_1.html
It also seems this is a recurrent Windows bug:
Win Socket Creation fails with Error code 10022 if non super user
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/3076a9cd-57a0-418d-8de1-07adc3b486bb/socket-fails-with-error-10022-when-application-is-run-from-certain-network-shares-on-vista-and?forum=wsk
Sorry, no effective solution at the time (other than copying the app binaries to a local folder). I'll update this answer once we get a better solution.
OK, looking a little further I found here in SO that this might be related to a SMBv1 network share, which describes the environment we had here (the network share was disabled because of another bug we faced - thanks MSFT).
Re-enabling SMBv2 / SMBv3 on the server solved the issue.
Related post:
After Windows 10 update 1803 my program can't open a socket when running from network share
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
I am trying to run an old Clipper application. It runs fine on Win 7 32bit but when I try using the DOSBox 0.74 it crashes with the following error:
Exit to error: CPU_SetSegGeneral: Stack segment zero
Are there some settings I forget to set when running the DOSBox?
I need to be able to run this app in DOSBox as it appears to be only portable solution that would work on any Win 7, being it 32 or 64bit.
If no apparent solution is known for this problem maybe you can tell me what alternatives I have to run a Clipper 5.3 application on a Win 7 64-bit Home edition?
EDIT:
I tried it on Win 7 Home 64 bit with the very same result. What can I do?
I used clipper many years ago, clipper does cause problems because incorrect config.sys configuration, specially the setting "FILES" must be big enough (let´s say 200) for your application, but "original" dosbox does not provide a way to adjust this setting.
Try the patch from http://www.shdon.com/blog/2009/09/05/adjustable-files-setting-in-dosbox
This patch allows to configure FILES adding a new setting on dosbox options file
Steps:
Backup dosbox.exe and replace it with the patched version
Edit the dosbox options file and add FILES=200 to the [DOS] section
Try it and post the results since i don't have clipper 5.3 to test.
Wanting to close this question I will write what was the only solution thanks to which I was able to run that aged application on Win7 64bit.
It was VMLite XP Mode.
I simply followed the steps described in their how to guide and it was up and running then I copied my application into the VMLite XP Mode, and it was running fine.
Finally I created, after some googling, a shortcut to my desktop and now I can easily start the application from my Win7 64bit desktop which then lunches the VMLite XP Mode which starts the application :) or something along this lines anyway, so far, it works great.