Creating a Network Server service in Windows 7 vs. Windows XP

[Former Member]

Hi, I having trouble getting dbsvc12.exe to run on Wnidows 7 32-bit and 64-bit systems.

I created a service on Windows XP with the following command and my program connects to my SQL Anywhere database just fine: I can manually start/stop the service from the services panel without a problem.

:sc create MyService start= auto binPath= "C:Program FilesSQL Anywhere 12Bin32dbsrv12.exe " DisplayName= "My Service Database Service"

but when I create the service with the EXACT same statement on Windows 7, I get the following error:

"Windows could not start the My Service Database Service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

I tried using the SQL Anywhere DbSvc utility, but then I get an error in my applcation "SQL Anywhere .NET Data Provider : Request to start/stop database denied (-75)"

Any help would greatly be appreciated!

[former_SQLA_member1694870]

Did you try creating the service with the Services Wizard from Sybase Central?

[Former Member]

Yes, with same results.

[former_SQLA_member1694870]

How have you defined the fields in the Configuration tab from the wizard?

[Former Member]

Well that's just it: for Windows XP I didn't have to setup the server via Sybase Central, but when I did setup via Sybase Central on windows 7 then I got the error -75 command the parameters were:

-x tcpip -c 8m c:\\programdata\\myapp\\Database\\mydatabase.db

[graeme_perrow]

Sounds like the dbsvc tool successfully created a service, since your application was able to connect to the server. I'd go back to that option and then we can diagnose the connection problem. Can you post your connection string?

[Former Member]

While I don't like the way the dbsvc names the service (it prepends SQLAnys_ ) to the name you provide. If this is the only way to get it to work with Windows 7, so be it.

A little background on my application. I actually have 2 databases that it connects to: mydatabase.db and history.db. Both have the exact same schema and tables, etc. In obtaining the connection string, I discovered that the connection to mydatabase.db is succesful. The failure is upon attempting the connection on the history.db. Here is the connection string for each:

mydatabase.db:

currentDB = new SAConnection(DatabaseFile=C:ProgramDataMyAppDatabasemydatabase.db;EngineName=MyDatabase;Start=C:Program FilesSQL Anywhere 12bin32dbsrv12.exe -x none -gd all -c 14M -ch 256M;UID=dba;pwd=sql;)

history.db:

historyDB = new SAConnection(DatabaseFile=C:ProgramDataMyAppDatabaseHistory.db;EngineName=MyDatabase;Start=C:Program FilesSQL Anywhere 12bin32dbsrv12.exe -x none -gd all -c 14M -ch 256M;UID=dba;pwd=sql;)

When I validate the connection,

currentDB.Open(); is successful hsitoryDB.Open(); fails ServerVersion = 'historyDB.ServerVersion' threw an exception of type 'System.InvalidOperationException'

[Former Member]

forgot to add last line to previous comment: Then it throws an SAException: 'Request to start/stop database denied', errorcode: -75.

[reimer_pods]

I'm a little puzzled by the connection strings: if you've already created a service for the network server, why do you use a start command for the server engine? Or haven't you been able to create the services successfully?

Wrt the error message: to start a database on a network server engine requires DBA authority (for existing connections using START DATABASE) or the engine parameter "-gd all" (cf. -gd server option ). You might also want to add "-n <engname>" to your service command.

[graeme_perrow]

Create the service so that it runs both databases:

dbsvc ... C:\\Program Files\\SQL Anywhere 12\\bin32\\dbsrv12.exe -n MyDatabase -x none
    -gd all -c 14M -ch 256M C:\\ProgramData\\MyApp\\Database\\mydatabase.db
    C:\\ProgramData\\MyApp\\Database\\History.db

Then change your connection strings to reference the database name rather than the file:

mydatabase.db:

currentDB = new SAConnection(DBN=mydatabase;EngineName=MyDatabase;UID=dba;pwd=sql)

history.db:

historyDB = new SAConnection(DBN=History;EngineName=MyDatabase;UID=dba;pwd=sql)

[Former Member]

Thanks for you answer. I didn't realize you could specify 2 databases with dbsvc. That would work for services created with dbsvc. But, I also figured out how to make it work with a service create with Microsoft's sc command. When looking at the service created by dbsvc, I noticed that it created a "Parameters" key that listed the parameters for the service. So, I added the following parameters (-n mydatabase -c 14M -ch 256M -x none -gd all -gp 4096)to my service and the access to both databases works as it does in XP.