Several months ago I updated a computer from Windows XP to Windows 7.  There was several issues with user access to files and directories for a number of applications including EDB which are usually relatively easy to resolve.

With EDB, if I reboot the PC, then I cannot access the remote sessions UNTIL I perform the following steps.

* Stop Elevate DB Server which is running as a service.
* Start EDB Server as an application.
* I can now access the remote sessions that have been set up in EDB Manager.
* Close the EDB Server application.
* Start Elevate DB Server as a service.
* Can now access remote sessions in EDB Manager.

After this, I can access remote sessions until the next time the PC is shut down.  Does this make any sense?

Richard Harding

Richard,

<< After this, I can access remote sessions until the next time the PC is shut down.  Does this make any sense? >>

Are you seeing any error messages at all during session connection ?

Tim Young
Elevate Software
www.elevatesoft.com

Good morning Tim.

The message is:

ElevateDB Error #1100 A connection to the server at 'wck' cannot be established ('Socket error: No connection could be made because the target machine actively refused it (10061), on API 'connect'')

The same message is received if there is no EDB Server running.

Richard

Richard,

<< The message is:

ElevateDB Error #1100 A connection to the server at 'wck' cannot be established ('Socket error: No connection could be made because the target machine actively refused it (10061), on API 'connect'') >>

It sounds like a dependency issue.  You should be able to see any server startup errors by doing the following:

1) Open the EDB Manager.

2) Select a session node that either a) connects to the EDB Server using a remote session or b) is a local session that points to the same configuration file path as the EDB Server.

3) In the tasks menu, select the View Logged Events option.

4) Filter the logged events on FunctionName='Start Server'

That should show you any errors with starting the server.  If there aren't any, then the problem is between the EDB Server and your application.  This could be AV/security software, a wrong IP address/port binding, etc.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim

<<It sounds like a dependency issue. >>

I put a delayed start for the EDB Service and the problem has gone away.

Great - thank you . . .

Richard

Richard,

<< I put a delayed start for the EDB Service and the problem has gone away. >>

Yep, the network layer is probably not initialized yet.   The interesting question is why....

The system services are supposed to start first, and should normally be ready to go by the time that the EDB Server service starts.

Tim Young
Elevate Software
www.elevatesoft.com