|
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
Don Macary
Joined: 13 Aug 2003 Posts: 51
|
|
Another Instance of Derby has already booted the database |
|
Hi
Getting this error when trying to start the GUI (as admin).
[b]
Error occurred during 24x7 intialization. Another instance of Derby may have already booted the database.
If I stop the 24x7 service I can then start the GUI.
[/b]
Out of 3 servers where this is installed , this is the only one that behaves this way.
the other 2 all me to open the GUI and change the jobs database while the service is running.
This is version 6.1 btw running on windows server 2016.
Can you please help me?
thanks
|
|
Mon Mar 25, 2024 10:23 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7904
|
|
|
|
Is it already running as a Windows service in the background. Could you please check?
|
|
Mon Mar 25, 2024 12:32 pm |
|
|
Eric.Charbonneau
Joined: 03 Nov 2016 Posts: 20 Country: United States |
|
|
|
I am having this same issue upgrading to v7
2024-07-03 08:49:55,511 [main] FATAL com.softtreetech.jscheduler.db.rdbms.DerbyJobDb - Unable to start job database server: Could not listen on port 4850. Address already in use.
|
|
Wed Jul 03, 2024 8:52 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7904
|
|
|
|
The error is very telling "Could not listen on port 4850. Address already in use."
The scheduler is unable to start because there is something else already running and using port 4850, which causes a collision. Two applications cannot use the same port. Perhaps there is another instance of the scheduler already started. Are you trying to start the desktop version while already running 24x7 Windows service? Can you check your Windows services applet and see if 24x7 is already started?
|
|
Wed Jul 03, 2024 9:11 am |
|
|
Eric.Charbonneau
Joined: 03 Nov 2016 Posts: 20 Country: United States |
|
|
|
|
|
The error is very telling "Could not listen on port 4850. Address already in use."
The scheduler is unable to start because there is something else already running and using port 4850, which causes a collision. Two applications cannot use the same port. Perhaps there is another instance of the scheduler already started. Are you trying to start the desktop version while already running 24x7 Windows service? Can you check your Windows services applet and see if 24x7 is already started? |
Yes I've always been able to have the scheduler service running while using the desktop app up until version 7. what has changed with v7?
|
|
Wed Jul 03, 2024 9:58 am |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|