big problem 2!!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We use Sybase SQL Anywhere Database (Version 5.5.04).

When running only a asp.net webpage (or webservice) everything is working
fine.
The dbeng50.exe is running under the ASPNET account but you can't see the
dbengine is running.

When running a windows application, this service is running under my
account, and I can see the dbengine is running.

Now the problem: these have to run together!!

When I run a windows application (or other) which works with this engine,
and I try to make a webservice call (when the application is running!), I get
this error:

ERROR [08001] [Sybase][ODBC Driver]Unable to connect to database server:
unable to start database engine ERROR [01000] [Microsoft][ODBC Driver
Manager] The driver doesn't support the version of ODBC behavior that the
application requested (see SQLSetEnvAttr).

(The Internet Guest Account and ASP.NET Machine Account have access to
the folder where the db is located (and the dbengine))

It looks like my account lockes the dbengine, so the ASPNET account can't
start this engine because it's already running, (the same problem occurs the
other way round)

What do I have to do solve/work around this problems??
 
Set up a COM+ application that uses the same account as the windows
application. Create a .NET class library that wraps all of the functions of
the driver and acts as a passthrough. Have you web service call this
application. That should solve the two worlds problem.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
Back
Top