After reboting the Filemaker 14.4 server service is not starting anymore.
Nothing that I know about has changed.
Any ideas?
As it seams this preferency file got corupted, at least it was empty:
C:\Program Files\FileMaker\FileMaker Server\Data\Preferences\dbs_config.xml
So I replaced it with a backup and all is fine now.
Related
Once upon a time I had a Postgres database that worked with pgAdmin. I have a webservice running on a WildFly server that made connections to the DB and everything worked fine.
After a while(a few months) I have tried to open pgAdmin again and it stuck on the loading...
I remove postgres and pgAdmin using Revo Uninstall, then installed postgres 9.6 and opened pgAdmin and it stays in the loading screen forever.
Can anyone help me ? [Using postgres 9.6 with pgAdmin v1.3],
On Event Viewer I saw the following error in pgAdmin :
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x580f31f6
Faulting module name: MSVCP120.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000135
Fault offset: 0x00000000000ecdd0
Faulting process id: 0x1de4
Faulting application start time: 0x01d2a7d1566324ba
Faulting application path: C:\Program Files\PostgreSQL\9.6\pgAdmin 4\bin\pgAdmin4.exe
Faulting module path: MSVCP120.dll
Report Id: 984dd9d8-13c4-11e7-832d-5ce0c535006f
Faulting package full name:
Faulting package-relative application ID:
I had the same problem and I resolved it following the steps on link
https://www.pgadmin.org/faq/#12
When I launch pgAdmin 4 v4.28 or later on Windows, the loading page
never closes. Why? pgAdmin 4 v4.28 includes additional security
features, one of which is intended to prevent security issues caused
by Content Sniffing.
Unfortunately some Windows systems are mis-configured such that this
causes Javascripts used by pgAdmin to fail to load. Opening the
developer tools on your browser will show an error similar to this:
Refused to execute script from
'http://127.0.0.1:57313/static/vendor/require/require.min.js?ver=42800'
because its MIME type ('text/plain') is not executable, and strict
MIME type checking is enabled.
(index):39 Uncaught ReferenceError: require is not defined at
(index):39 This will occur when the value of the registry key at
HKEY_CLASSES_ROOT.js\Content Type is set to text/plain. To resolve
the issue, use the Registry Editor and reset the value of
HKEY_CLASSES_ROOT.js\Content Type to: text/javascript
Finally, restart the pgAdmin server.
I just had this problem on macOS so I went to Terminal and typed ps aux | grep -i pgadmin and made a note of the process id (second column from the left). Then I killed that process with kill -s TERM <process id>. You can also use the simpler form with killall pgAdmin4. Then I was able to start "pgAdmin 4" from the Applications directory.
I just had the same issue on a Windows 7, 64bit machine, DBA told me to "upgrade" to pgAdmin 3 (latest build) and it works.
as per Abrahim's suggestion, it worked fine for me in the environment. Windows 10, pgAdmin 4.28
"value of the registry key at HKEY_CLASSES_ROOT.js\Content Type is set to text/plain. To resolve the issue, use the Registry Editor and reset the value of HKEY_CLASSES_ROOT.js\Content Type to: text/javascript "
I had this issue on Mac. I resolved it by:
Closing the instance of PgAdmin 3 AND PgAdmin4 (I had both open)
System Preferences -> Security & Privacy -> Allow apps downloaded from: Anywhere
Reopen PgAdmin4
I faced the same issue (on window server)
My solution is just open task manager and finds out pg_ctl then just end that task and reopen pgadmin again. It will work!in case it still doesn't work just try to terminate mysql.exe too.
For me, the postgresql server was set to start manual and it was not running in services, i started the service and it worked
Download pgAdmin from its website and install it separately from postgres.(Its works for me on Windows 10 - 64 Bit)
Response from pgadmin-support mail group:
Please try one of the Mac/Windows test builds at https://developer.pgadmin.org/~dpage/.
I would strongly advise doing a complete uninstall before installing, to ensure no old, unused files are left behind.
I had a similar issue and was able to fix it by re-installing the latest Java JDK x64 8 at http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I found a solution here pgAdmin 4 v3.1 How can I use another browser? (Win 7)
My pgadmin4 stopped working in firefox but it works in chrome. Now i use this configuration to open pgadmin 4 using chrome. It is interesting that pgadmin4 now open in his own window.
I think this is the correct way to use pgadmin4.
Go to Services and restart PostgreSQL Server.
I was trying to follow the instructions from postgresqltutorial to load a sample database into postgresql using pgadmin. But after the database was restored(since I can query data from the database), the process watcher just won't go away, and it keeps saying that the command is "running"(as of this writing, it has been running for over 400 thousands seconds, but the size of the sample database is just a few megabytes). Reboot and reinstallation couldn't fix the problem.
Here are some screen shots:
And when I click "click here for details":
I am using postgresql 9.6 with pgadmin4 on windows 10. So what's going on here? Is it a bug? How can I get rid of the process watcher?
I had the same issue with posgresql 9.5 and pgAdmin4 on Windows 7. I solved it without loosing server list by opening %APPDATA%\pgAdmin\pgadmin4.db file with SQLite Manager (Firefox Add-on) and deleting all entries from the 'process' table.
This is a bug in pgAdmin4 & reported,
https://redmine.postgresql.org/issues/1679
close pgAdmin, restart the system, open %APPDATA% and erase the folder pgAdmin and the pgAdmin is Ready to start without errors.
Greetings
For stability reasons (OS X stability) I decided to use 10.6.8 with java 6 again. When I try to use studio I get the following
2015-11-17 10:16:34:828 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OConfigurationException: Database 'XXXXX' is not configured on server (home=XXXXX/orientdb-community-2.0.12/databases/) [ONetworkProtocolHttpDb]
2015-11-17 10:16:41:062 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OConfigurationException: Database 'XXXX' is not configured on server (home=XXXXXX/orientdb-community-2.0.12/databases/) [ONetworkProtocolHttpDb]
And studio asks for the login info endlessly without showing any data.
Any workarounds? This didn't happen with mavericks and java 7
Seems there is no database under that path. Please check the database folder if exists or it's empty.
Ok, after I eliminated the "." from the database dir name the severe error did not appear anymore.
But the endless credentials pop-up did not stop. Even when I managed to issue a "select from e", the query never returned.
BUT if I checked the "store pair in keychain" box everything started to work as always. It should not be mandatory.
Forget about this one
After setting up MongoDB service on Windows Server 2008 R2 this error was raised.
C:\mongodb\bin>net start MongoDB
The Mongo DB service is starting.
The Mongo DB service could not be started.
A system error has occurred.
System error 1067 has occurred.
The process terminated unexpectedly.
The error came from an unclean shutdown detected.
Please visit http://dochub.mongodb.org/core/repair for recovery instructions.
a few steps will fix it (as it's written in the link above):
1) remove the file /data/db/mongod.lock
2) run mongod.exe --repair
3) start the mongod service net start MongoDB
For anyone who faced this error on 2020, with version 4.4.1 of mongo, and the accepted answer not solve the issue, here is what I've done:
Remove all mongo services from pc (add/remove programs).
Go to program files and backup the MongoDB folder.
Remove the MongoDB folder.
Re-install mongo db.
And it should work.
UPDATE for January 2021, the following saved me without re-installing MongoDB and losing all my data:
C:\Program Files\MongoDB\Server\4.4\bin>mongod --dbpath "C:\Program Files\MongoDB\Server\4.4\data" --repair
I was facing the same issue and I closed the other command prompt which was opened with mongoDB.exe, and hence created a lock on that executable. Simply only closing that command prompt window worked fine. Thanks for the help.
Make sure you have at least 5 Gb available space on the drive of the database. For me, clearing that space enabled the ability to restart Mongodb.
If you are in the Windows. you should change the mongodb's config in the System disk.For example
1) I change C:\Windows\system32\mongodb.exe.
2) And I make the path in D:\mongodb\mongod.cfg .Before this,you should remove previous.
3) Finally , you can net the serve. net start mongodb.
I hope it can help you .English is not very good ,please forgive me.
enter image description here
I was having the problem of starting the the MongoDB. The logs are pretty descriptive and you can find suggestion from there.
There is a 'd' folder that needs to be created within data folder like
data\d which was missing.
This solved my problem.
Although, not an ideal solution, I ended up deleting all of the database files in \data\db and was then able to successfully run the MongoDB service. Note, this will delete all of the data in the database.
I am trying to install the Sphinx Search Server. I followed the steps given here http://itsonrail.wordpress.com/2010/05/23/installing-sphinx-on%C2%A0windows/
I added C:\Sphinx\bin to environment path and Sphinx Search is listed in the Services panel. When I try to start it, this error occurs:
Windows could not start SphinxSearch service on local computer
Error: 1067 The process terminated unexpectedly.
Please help me solving this problem. Thanks in advance.
I trid this http://sphinxsearch.com/forum/view.html?id=2684 but it didn't help.
I had the same error in my Windows 7 x64. The step below helped to solve my problem:
Create folders data and log in C:\Sphinx.
Then try to start sphinx with cmd:
C:\sphinx\bin>searchd
I have faced the same problem and eventually moved the sphnix.conf to C:\Sphinx\bin\sphnix.conf from root and the services starts. Please try this. (Please make sure there are data\, log\ directories in the root with write permission)
It is looking like your configuration is not setup properly. Have you tried to run search daemon from sphinx directory path via command prompt?
C:\sphinx\bin> searchd
C:\sphinx\bin>indexer --rotate –all
Also please ensure the log via search.log or windows event log.
If it is not running after this than try to reinstall it again
I hope it will work for you
Error 1067 doesn't say much about the problem, except that the process terminated unexpectedly. Try looking some more informations in searchd.log.
I've got same error code when I tried to update Sphinx with newer version.
In the log file, I've found
FATAL: no valid indexes to serve
My problem was that I tried running new version of Sphinx using index files created with an older version. It was solved by deleting all old index files and creating new indexes.
==>> close your cmd window and restart the sphinxsearch service...
I got this error suddenly, when Shpinx was working fine yesterday. Turns out the query log file was hitting 4Gb in size. I deleted it, and service started with no problems.
Make sure all the folders defined in the conf file actually exist. I was missing the LOG folder and that's why I was getting the error. Once I added the folder, the problem was solved.