When running EDB 2.11 64bit Unicode server as a service on Win7 64bit, I will sometimes see:

"ElevateDb Error #100 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")

The Service is running in the Services window.

BTW, I am using
 Server Name=MYSRVR
 Server Description=My Server
and this is what shows up in the Services window.

To fix the problem I run a batch file that stops the service, (uninstall it, reinstall it -may be unnecessary) and starts it again. Then EDBMgr and my application can then access the server.

This problem only occurs occasionally after the computer is booted. But like I said earlier, when the problem occurs the service is running in the Services window with Status=Started and Startup Type=Automatic.

1) What is causing this? This also occurred last Friday as well as today.

2) Is there a way I can monitor the EDB service to see if it is running properly without trying to connect to a database? If I wasn't running the server as a service, I could run the Server GUI and get some indication the server is running. But how do I monitor the EDB server when it is running as a service?

TIA
Barry

Barry,

<< 1) What is causing this? This also occurred last Friday as well as today.
>>

My first guess would be personal firewall/Internet security suite software.
When you start seeing Winsock errors like that, the usual cause is something
environmental.

<< 2) Is there a way I can monitor the EDB service to see if it is running
properly without trying to connect to a database? If I wasn't running the
server as a service, I could run the Server GUI and get some indication the
server is running. But how do I monitor the EDB server when it is running as
a service? >>

You can just try to connect a session (TEDBSession.SessionType=stRemote).

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<< 1) What is causing this? This also occurred last Friday as well as today.
>>

<My first guess would be personal firewall/Internet security suite software.
When you start seeing Winsock errors like that, the usual cause is something
environmental.>

Then it would have to be done at startup by ZoneAlarm (or something else).

Because even if I unload Zonealarm after I can't connect to the EDB server (on same machine as application/EDBMgr), I still can't connect to the EDB server. The program WhatsRunning shows no entry for edbsrvr.exe or port 12010 being used. The services window shows edbsrvr running. If I stop and restart the edbsrvr service, then Whatsrunning now shows an entry for edbsrvr listening on port 12010 and my program can connect to the service just fine. So something prevented edbsrvr from using port 12010 at startup.

When the problem occurs, if I don't unload Zonealarm and just stop and restart the edbsrvr service, everything starts working. So if ZoneAlarm is the problem, then why did it not prevent the service from using port 12010 when it was restarted, if that's what prevented it at boot up?

I will play around with it some more.
I changed the EDBSrvr service so it restarts automatically if it is not running. For some reason this was turned off under properties for the service. I think it was because I have a batch file to uninstall the service and re-install it. I'll look for a parameter to auto restart the service when it is installed.

If this doesn't solve the problem, I'll uninstall ZoneAlarm and see if it makes a difference.
If not, I'll go back to using the default service name (remember I had changed it to "MyServer" in the config file).
If that doesn't solve the problem, I'll switch back to 32 bit EDBSrvr.

<< 2) Is there a way I can monitor the EDB service to see if it is running
properly without trying to connect to a database? If I wasn't running the
server as a service, I could run the Server GUI and get some indication the
server is running. But how do I monitor the EDB server when it is running as
a service? >>

<You can just try to connect a session (TEDBSession.SessionType=stRemote).>
So I don't need to authenticate to a database? Great, then I'll write a utility program to check it at boot up.

Thanks
Barry

Barry,

<< Because even if I unload Zonealarm after I can't connect to the EDB
server (on same machine as application/EDBMgr), I still can't connect to the
EDB server. The program WhatsRunning shows no entry for edbsrvr.exe or port
12010 being used. The services window shows edbsrvr running. If I stop and
restart the edbsrvr service, then Whatsrunning now shows an entry for
edbsrvr listening on port 12010 and my program can connect to the service
just fine. So something prevented edbsrvr from using port 12010 at startup.
>>

Did you have ZoneAlarm running when you first tried to start the EDB Server
service ?

<< When the problem occurs, if I don't unload Zonealarm and just stop and
restart the edbsrvr service, everything starts working. So if ZoneAlarm is
the problem, then why did it not prevent the service from using port 12010
when it was restarted, if that's what prevented it at boot up? >>

You can find out if there's an error during startup by connecting to the EDB
Server using a remote session in the EDB Manager, and then clicking on the
View Logged Events option for the session node.  That will show you any
startup errors logged by the server.

<< So I don't need to authenticate to a database? Great, then I'll write a
utility program to check it at boot up.  >>

Nope, you just need to authenticate against the configuration for the EDB
Server, which is database-independent.

Tim Young
Elevate Software
www.elevatesoft.com