Kapow ManagementConsole could not start - kofax

An error message pops out when I try to connect to the management console. The version is Kapow 10.1.0 master nightly 2370 x64.
The Error message is:
Unable to register to the default cluster: ManagementConsole failed to start: Spring subsystem failed to load.. Retrying

I had to delete the folder on Kapow Appdata User Profile folder, for example:
C:\users\<user>\appdata\local\Kapow
And then restart the RoboServer/Management Console.
This will create a new configuration and from there you can continue the installation (bring up the management console, enter the license, etc)

Please Delete Appdata and open localhost:50080 Management console and delete and then add Cluster settings again.
Now restart the Design studio and open it up again. Make sure you are using same objectdb.

You only need to rename the folder:
C:\Users\<user>\AppData\Local\Kapow\10.ur.version\Data
Then rerun the Management console as Administrator.
If you are still facing the same issue, please uninstall Kapow and install it again (also make sure you renamed the Data folder).

Related

How to uninstall mongodb from Windows

I saw a tutorial that said to run this:
C:\mongodb\bin\mongod.exe --config C:\mongodb\mongod.conf --remove
but that command does not work since there is no mongod.conf file in the mongodb folder in my Windows. Besides, I don't want to only stop the service, but to remove everythin, including files, services, etc. Is that possible?
I am using Windows 8.1.
The command...
C:\MongoDB\bin\mongod.exe --config C:\MongoDB\mongod.conf --remove
Is used to just remove the service.
If you don't have a mongod.conf and/or no longer have the .msi installer (who keeps that stuff?) then:
win-key + r and run regedit
Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MongoDB (or just cut and paste this path)
Once there right click on MongoDb and click Delete. Service is now gone.
Goto C:\mongodb (or where you installed it) and delete directory. Mongodb is now gone.
Check your system environment variables to see if it's in your path (It will not exist unless you put it there).
Alternatively you may be able to re-download the msi and try using that.
EDIT: If you forgot to stop the service first or if it left dead orphan in services then open CMD or other shell as administrator and run the command: sc.exe delete MongoDB ... you should see: [SC] DeleteService SUCCESS
Use the command below to delete the service:
run cmd as Administrator
sc delete MongoDB
Since you're using Windows, just run the same .msi file that you installed it with.
It should be in your downloads folder, i'm guessing.
Once you opened the file, press next and there you will have the complete access to remove your MongoDB installation.
Run the mongo-db installation file that ends with .msi.
You'll see the remove option there, click on it.
Then you could delete the mongo-db files that are in your computer.
Go to services.msc and stop MongoDb service .
Delete all the folders in C: drive where MongoDb Folders exists.
Remove data folder if you created previously.
Type cmd in start and ryt click on cmd and select run as
administrator and type below Command.
sc delete MongoDB
If it throws some error like service not exists then open properties of the service and check whether you are giving the proper service name.
net stop MongoDB : This will stop your mongo server(in case of windows) then simply delete that MongoDb folder.

Node fs Error: EPERM: operation not permitted, open

I get this error in my app:
Error: EPERM: operation not permitted, open 'C:\Program Files
(x86)\Full Menu\db\main.json'
The app I have is built with electron-boilerplate. I am using this function to get the path to the root of the app:
path.dirname(process.execPath)
And this is the script that writes the file:
fs.writeFile(apath + '/db/' + elem + '.json', JSON.stringify(results)
I know what the problem is: permissions. But how could I get this working without running the app as an administrator?
For the benefit of searchers; I has this error. I added full permissions for Everyone as a test, but that didn't fix it. The issue was that the file was set to readonly (by source control).
Unchecking the readonly option in the file properties fixed the issue.
On my Windows 10 machine, I encountered this error when running an old Node JS project. I think Node version 10.16.
In any case, it was trying to modify a dotfile in my project. Be sure that the file isn't hidden on Windows. After unchecking the hidden option in the file properties pop up. Everything worked.
So to fix:
Right click file in Windows Explorer
Select properties
Uncheck Hidden
Click Ok
Re-run your command.
If you have the file that you can't open or modify mounted as a volume in docker restarting docker should fix the issue.
i had to run the node command prompt as administrator and that fixed the issue.
I face this issue when I was deleting a file/folder.
Solution:
Just restart your code editor/ terminal
Or
Restart your computer
If you are facing this issue on Windows 10, then please try the following:
Uncheck readonly options for the folder (if read-only reverts, login as administrator)
Open terminal as administrator (if you are facing this issue on terminal)
Switch off ransomware folder protection
Change chmod of the folder
Check if the folder is hidden or not
Disable antivirus protection (temporarily) and try this
Or move your project folder somewhere else, where antivirus ransomware protection is disable.
If nothing above works, then try the following:
https://appuals.com/how-to-fix-folder-keeps-reverting-to-read-only-on-windows-10/.
Hope this would of help.
I think that you must change the permissions recursively to the file so the user executing your script can read / write this file.
https://fr.wikipedia.org/wiki/Chmod
Restarting my computer fixed this problem for me.
I had this issue too. I'm using TFS (or VSO, Azure DevOps, etc.) for source control. I was trying to compile from .scss to .css and it couldn't open my .css. I just needed to right-click on my .css file and Check Out for Edit...
I had the error because i have already open the file before
var stream = fs.createWriteStream(outputFileName, {flags:'a'})
var output = fs.createWriteStream(outputFileName, {flags:'a'})
this is not an exact answer but may help:
i think if you want to read or readSync a file that doesn't exist you will encounter an EPERM error...
in many programming languages, any permission related error may not
directly means an actual permission issue
for example in PHP Folders (not files) must delete by php rmdir() method but if you want to do that with unlink() , u will encountered with a wrong Warning message that says "permission denied"
I was facing the same problem using the following software:
Windows 10
GitBash
Node v19
I was able to solve it opening GitBash as admin
I had the same problem, when i tried to create and write to a file using NodeJS. I thought it had to do with my windows file/folder access permissions, but after restarting my computer and running the code again, I still got the same error.
However, this time around my antivirus gave me a pop-up message also, stating that it blocked permission for Node.exe to write or open files. So once I flagged Node.exe as safe for my anti-virus program (Avast).
It worked for me. Disabling my antivirus could've also temporarily fixed it, I guess.
If you use windows 10, you must turn off Ransomware protection. Ransomware protection will prevent all folder and file changes.You can turn off it in Windows Security Center. See screenshot below:

Could not start virtuoso on windows server 2003

I have installed opensource virtuoso on windows server 2003.
I followed all the instructions given on the link openlinksw even the service instance has been created i can see the service list but whenever I'm trying to start the service it's giving me following error:
could not start Open link virtuoso server "Virt" service on local
computer. Error 193:0xc1.
Any help is appreciated.
Thanks in advance.
What is the actual command you are running to start the Virtuoso Server and where is this being run from ?
Please checking the "virtuoso.log" file in the "database" directory of your installation to see why it might be failing to start.
The simplest way to try and start Virtuoso to verify base operabiity is to run the following command from the "database" directory of your installation from a command prompt:
..\virtuoso-t -f
which will start it in foreground debug mode and you can see the startup attempt in progress ...

Setup.exe is rolling back (Built for Asp.net Application In Install Shield12)

I build Setup.exe file in Install Shield 12 for Web Project of .Net Framework.
When i m going to run this setup.exe file , i got rolling back error while execute Virtual Directory and setup had not been completed.
How could i resolve this Rolling Back error due to Virtual Directory ?
With which application of install shield this issues is connected ?
You need to find out what the actual error is that is causing the rollback to occur.
To do this, you'll want the installer to create a log for you.
You can do this by running the exe like this:
setup /V"/L*v c:\everything.log"
Then, look through the log file and find out where it decides to rollback (searching for "rollback", then looking just above that should get you close.)

Exceptions using CruiseControl.NET

I recently updated to CC.NET 1.5 and I'm now getting some strange exceptions.
On one project I get: -
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: svn: Can't create a character converter from native encoding to 'UTF-8'
This happens when CC is checking a subversion repository for any mods. If I run the actual command line CC says is failing it works and returns an empty XML (there are no mods).
Some other projects also fail to check mods with another "Source control operation failed" exception but no further info. Again the command is an "svn log" which when run from command line works ok.
I'm using subversion 1.4.5 client side and my source repository exists on a separate box than my build server.
Anyone got any ideas?
Have u try to update Svn client ? I doubt it is so simple, but let's check !
Try a svn cleanup
What is your svn config in ccnet ?
What is the build revision of ccnet you are using ? You should try the latest 1.5.x nigthly build, which is very stable for me.
http://ccnetlive.thoughtworks.com/CCNet-builds/1.5.0/
did you try to change the startup parameters of CCService?
Namely, set the "Allow service to interact with desktop" check box on Log On tab.
Also, you may try to use other account than "Local System".
I am not sure, but seems it may fix the issue, since it may be "Local System" account specific issue effect.

Resources