I am using ElevateDB 2.17.01 64 bits over WIndows 2012 R2 server with latest updates.

I was using it on Windows Server 2008 as a service without problems.

Now we have moved everything to a new windows 2012 server. Made a copy of the folder, same paths etc, same EXE, same config files.

When using it as a service I have a lot of connection problems: #300 mostly.

When I stop the service and run it as an application it works correctly. But I cannot keep like this since when the desktop closes it close together.

Please, I wonder what could be creating this problem.

Thanks

Eduardo

<<
I am using ElevateDB 2.17.01 64 bits over WIndows 2012 R2 server with latest updates.
>>
I think you should install the server with the following command line:

dbsrvr /install /nointeract

and then start it

net start dbsrvr

I use DBISAM with Windows 2008 R2, Windows 2012 R2 with 32 and 64 bits and it works perfectly

I'll have to double-check my deployment, but you definitely have to make sure there is no interaction/GUI.  I'm running latest code and run the server as a service and have customers running 2003-2012 Server.

Lance

Eduardo wrote:

I am using ElevateDB 2.17.01 64 bits over WIndows 2012 R2 server with latest updates.

I was using it on Windows Server 2008 as a service without problems.

Now we have moved everything to a new windows 2012 server. Made a copy of the folder, same paths etc, same EXE, same config files.

When using it as a service I have a lot of connection problems: #300 mostly.

When I stop the service and run it as an application it works correctly. But I cannot keep like this since when the desktop closes it close together.

Please, I wonder what could be creating this problem.

Thanks