I am facing a very strange problem, I am executing my project executable in MAC terminal window, the process will halt after some time, but when I remotely access that machine and follow same procedure it will complete the process successfully. I don't know the reason why it can't work when I tried executing directly?
Have you checkt the rights management?
Maybe you're trying to do something that the OS thinks it has to prevent.
Indeed this is strange. Maybe try to "repair" the "access privileges" and "volumes" in the "Disk-Utility".
Often this fixes a lot of problems.
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
I have a Mac with Yosemite on it. Upon downloading SmartCVS 7.1.9 from https://www.syntevo.com/smartcvs/ , I try to run the application and receive an error that states "SmartCVS seems to already be running. Instead of running separate instances you can open multiple project windows in SmartCVS. If you are sure that no SmartCVS instance is running any more you should delete the lock file $FILE_PATH$/_lock_".
I've tried to delete the _lock_ file multiple times and that doesn't help (the lock file is empty. The application hasn't ever successfully run. Rebooting doesn't help. Deleting it from the computer and downloading it again doesn't help. Downloading previous versions has yielded the same error (7.1.3). I've tried running it from the terminal to get the crash log, but it doesn't make much sense.
In case it helps, upon downloading the first time I had a pop up stating that SmartCVS was by an unidentified publisher and couldn't open. I got around this problem found here: http://www.imore.com/how-open-apps-unidentified-developer-os-x-mountain-lion
I know that the program can work on my Mac OS since my boss has it running on her computer. Though, strangely, she did not have to deal with either of the two problems I've had to deal with.
Thanks
so at the time I posted this I also reached out to a SmartCVS community support group. They were able to solve the problem as follows:
My computer is part of a Network. As such, the files are technically stored locally since my User Home is on the Network. SmartCVS can't interact with the lock file since it's not on the local machine. Therefore in the file at "~/Library/Preferences/SmartCVS/7.1/smartcvs.properties", I needed to append the following line to the end of the file:
smartcvs.applock=false
I had a program that starts up a Windows Service when installed and deleted that Windows Service when uninstalled. However it refused to uninstall after I modified the installer by accident (my fault!). I couldn't even remove it from Programs and Features as it kept throwing an error 2715. I found this article that had a FixIt program: https://support.microsoft.com/en-us/mats/program_install_and_uninstall
Using that, I managed to finally remove the program itself. Now however, when I try installing and uninstalling it again (to test my changes), the Windows Service that's attached doesn't get removed. In fact, it continues running. I checked the registry and indeed the key for the service is still there after the uninstall. I would need to manually stop it and do a sc delete to get rid of it. Any idea on how I can solve this?
Edit: I am able to replicate the issue on another computer. What I do is, I install the program there, and use the Fix It tool to remove it. Once this is done, I can easily replicate the issue as the service is never deleted after uninstalling. It works fine prior to this.
Some guesswork here because there's not enough info....
Eroor 2715 is a Windows Installer error, and I suspect it's related to you running a program (as you describe it) to start and stop services. I'm guessing that you run it as a cuatom action, and on uninstall you attempt to run it but it's missing because it's been uininstalled.
So:
That fixit cure is not for a broken MSI (which yours is) - it's for fixing corrupt registry data that prevents uninstall, not fixing a broken MSI uninstall.
You don't need to run code to start and stop and delete services. Most MSI-building tools have support to the the Windows Installer functionalty that does this for you, so stop doing it!
A more specific answer is difficult without knowing what you are using to build your MSI with, and how you're running your program, but the signs point to you running the program after it's been removed, and even if you get the program running properly there's no way to tell whether it is correct without seeing the code. But 2 is what you should be doing anyway.
I have a huge .bat file build script that calls into compilers and what not.
I have until recently been able to run this without any problems (and as I have not made any changes, I suspect there's a Windows update and/or setting at play?)
Using Windows 7
I am logged in as Administrator
I run the command line with "Run as administrator"
My build script then compiles and run my application (shuts down itself which I have confirmed in "Task manager") the first time.
This goes well.
But when it tries to delete the file (the application)
I get "access denied"
This basicly stops me completely because it is a large build system which non-automated takes a very long time and is very error prone to do manually.
The kicker is that if I try delete the file in Windows explorer I get "need admin rights" which is kinda peculiar since... I am already an administrator... and I have also run Windows explorer with "Run as administrator". However, after some time and attempting a rename it seeems to budge and allow the file to be deleted. (I have checked, and there is no process listed in task manager which should be "holding" the file in any way, so I tend to think this is an access rights issue... somehow)
I am... Open to ideas? :)
I have decided to move this question to:
https://superuser.com/questions/493249/windows-file-access-denied
as I think it is my Windows that is messed up somehow :(
I will still monitor this question at SO, but I think this a peculiar Windows issue I am experiencing
I'm fairly new to deploying desktop applications, so this is the first time I'm building an installer for my software. Currently, the first time I run my software after installing it, it crashes. After that, it runs fine. I'm still in the process of debugging this issue, but I've noticed that a reboot immediately after installing and before running the software seems to fix this crash.
What are common reasons that some installers ask you to reboot before running the software?
Also, why do some installers need to restart before finishing the installation?
Thanks in advance!
Generally, reboots between install and running are because you're replacing system DLLs that are locked. The installer sets up a run-once registry entry that copies the DLLs during boot before they're locked by Windows, and then your application can use the new DLL that you laid down.
In general, this is highly discouraged. There should be no reason anymore for anyone other than Windows itself to need to reboot after install anymore.
I'd suggest going back into a debugger to find out more details about why your application is crashing. Hopefully you have enough tracing available in your code to allow that type of debugging.
In general, a reboot is only required if the installer needs to replace files that are currently in use (and locked) by the OS. Sometimes installers will err on the side of reboot-just-in-case, but this is rarer than it used to be.
We've got a case with an installer I maintain where we need to force a reboot for vista only due to UAC and privilege elevation. Once the setup is complete we need to trigger a program as the current user context, not the elevated Vista context.
In your case, I suspect that some files haven't been correctly registered and you just need to stick with the debugging ;)