Hi

I have suddenly got this problem starting a server.
---------------------------
ElevateDB Server
---------------------------
ElevateDB Error #100 There is an error in the metadata for the
configuration EDBConfig (The object has been updated by a newer version
of the engine)
---------------------------
OK
---------------------------

I haven't applied any EDB updates for "months".

The server is v2.18 B4, last modified date is 23/03/2015.

The EDBConfig.EDBLog last modified date is 24/03/2015 (today)

The EDBConfig.EDBCfg last modified date is 21/03/2015 (3 days ago)

An app that runs all day every day stopped at 2015-11-24 14:17:15, being
unable to connect to the server.  (The app syncs the user details
between two servers every 15 minutes.)

2 questions

1.  How can I fix this now so that I can get the server up and running?

2.  What could have caused this problem so that I can stop it happening
again?

Cheers

Jeff

On 24/11/2015 2:46 p.m., Jeff Cook wrote:
> Hi
>
> I have suddenly got this problem starting a server.
> ---------------------------

Further to first posting ...

I rebooted the server machine and now get
---------------------------
ElevateDB Manager
---------------------------
ElevateDB Error #1100 A connection to the server at '127.0.0.1' cannot
be established ('Socket error: No connection could be made because the
target machine actively refused it.

 (10061), on API 'connect'')
---------------------------

.... trying to open a session on serve machine or on another PC on my
network.  Same message for both except for the server address.

Server is running in the Task Manager Processes - running as a service.

Bamboozled.

Jeff

Jeff

The 2 errors you have reported are pretty dramatically different.

The second one usually follows on a fire-wall or anti-virus process blocking connections to EDB.

Try temporarily switching off any anti-virus on the server, also check Windows Firewall and consider adding a Rule allowing connections to EDB SRVR.

It is even worth renaming the EDBSrvr EXE and running it. If a Windows warning "should this programme be allowed to make connections" pops up ... then click "Allow" and your problem ought to go away.

Adam

Jeff


As Adam says two different and probably unrelated errors.

---------------------------
ElevateDB Server
---------------------------
ElevateDB Error #100 There is an error in the metadata for the
configuration EDBConfig (The object has been updated by a newer version
of the engine)
---------------------------
OK
---------------------------

This doesn't mean that you've installed a newer engine, it could be a backup has been restored which isn't compatible.

The second one

---------------------------
ElevateDB Manager
---------------------------
ElevateDB Error #1100 A connection to the server at '127.0.0.1' cannot
be established ('Socket error: No connection could be made because the
target machine actively refused it.

 (10061), on API 'connect'')
---------------------------

Whilst ElevateDB Manager may be telling you it doesn't come from Elevate, its a Windows error. Its the second one of this nature reported (it was 10050 though)  and Tim's response was


<<Handled via phone - environmental issue with sockets, not resolved completely so let me know if you're still stuck.>> so I suggest contacting him to see if your's is similar

Roy Lambert

Thanks Roy and Adam

Still struggling with this problem.  After reading Tim's responses to
earlier posts with the same error message, I figure it must be an
environmental problem of some sort so "not Elevate's problem"  - which I
don't mean in a nasty way!

Re: Roy's comment, I can be almost certain that there was no restore of
older versions of anything on this particular PC.

This is my latest situation and I'd be interested if anyone could
suggest any other things to check out.
------------------------------------------------
Testing with EDB Manager.

I'm getting this error:-

ElevateDB Error #1100 A connection to the server at '127.0.0.1' cannot
be established ('Socket error: No connection could be made because the
target machine actively refused it.
-----------------------------

The problem is the same whether I try from the server PC using the
127.0.0.1 address or from another PC in the LAN except, of course, the
server address is different in  the error message.

The server PC (ASL3) is definitely alive on the LAN.  Proved this by
using Windows Explorer to view files on ASL3 from my own PC (ASL5).
Also can use Remote Desktop(RDP) to connect to ASL3 from ASL5.

Things I have tried:-

1.  Reboot ASL3.
2.  Stopped Windows Firewall on ASL3.
3.  In Network connections, disable/enable LAN connection.
4.  Stop EDBsrvr running as a service and restart as an ordinary program.
5.  Checked Router to make sure port 12010 TCP is forwarded to ASL's IP
and port 12010.
6.  Tests conducted with and without RDP running.

Running an app on ASL5 that connects to ASL3's EDBsrvr also fails with
the same error.

Dislodging bricks from a wall with my head

Hi

Getting closer ...

I found via Mr Google and
http://www.howtogeek.com/howto/28609/how-can-i-tell-what-is-listening-on-a-tcpip-port-in-windows/

 that *netstat -aon | more* gives you a list of processes listening to
ports, so:-

Active Connections

  Proto  Local Address       Foreign Address        State           PID

  TCP    192.168.1.11:1787   XXX.109.87.xx:12010    ESTABLISHED     2604

Where XXX.109.87.xx is my correct fixed IP
      PID=2604 is EDBMgr.exe  BUT shouldn't it be my EDBSrvr.exe!!!!
      192.168.1.11 is my correct LAN IP


      And I have no idea where 1787 comes from!!!!!

Cheers

Jeff

On 25/11/2015 4:34 p.m., Jeff Cook wrote:
>
>    Proto  Local Address       Foreign Address        State           PID
>
>    TCP    192.168.1.11:1787   XXX.109.87.xx:12010    ESTABLISHED     2604
>
> Where XXX.109.87.xx is my correct fixed IP
>        PID=2604 is EDBMgr.exe  BUT shouldn't it be my EDBSrvr.exe!!!!
>        192.168.1.11 is my correct LAN IP

So I stopped EDBMgr.exe and tried to start the server again and I'm back
to this error:-
--------------------
ElevateDB Error #100 There is an error in the metadata for the
configuration EDBConfig (The object has been updated by a newer version
of the engine)
--------------------
.... and as stated earlier, no new versions have been installed for
months and no backups restored.

Cheers

Jeff

Jeff,

>  no new versions have been installed for
> months and no backups restored.

Nevertheless: please stop the EDBServer and check in the options if the
character set is set correctly (ANSI, UNICODE).

Uli

Uli

>Nevertheless: please stop the EDBServer and check in the options if the
>character set is set correctly (ANSI, UNICODE).

Good catch - I'd forgotten that

Roy

Jeff Cook wrote:

> Hi
>
> I have suddenly got this problem starting a server.
> ---------------------------
> ElevateDB Server
> ---------------------------
> ElevateDB Error #100 There is an error in the metadata for the
> configuration EDBConfig (The object has been updated by a newer
> version of the engine) --------------------------- OK
> ---------------------------
>
>
> 1.  How can I fix this now so that I can get the server up and
> running?
>
> 2.  What could have caused this problem so that I can stop it
> happening again?


I know little of this, but my thoughts are that the message is what you
should focus on. I'd be looking at the config files, and how they might
be corrupt. I presume that the service is not starting because it has
bad data, and that would cause it to stop responding etc. Start off
with a backup (not overwriting your existing one), and then shut the
server down and use the desktop tools to access the database and see
what they say. Check server ini files to ensure it is pointing to the
right place etc.

Also look at anti-virus updates - that will have been updating, and may
well be denying access to a key file or whatever.

--

Matthew Jones