big problem!!!!!

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

Guest

hello,

we use this ODBC connectionstring:
"Driver=Sybase SQL Anywhere 5.0;Dbf=C:\SqlAny\Demo.db;Uid=me;Pwd=me"

in a windows application it works fine, but in an asp.net applicatie we get
the next 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).

any ideas?
 
IDEA: Dbf=C:\SqlAny\Demo.db

Not sure about Sybase (have not used it), but the location of the database
is most likely your issue. This gives you a couple of options:

1) Break down ASP.NET (and possibly IIS) security to allow access to this
file path location. Potential security hole?

2) Move the database to a directory your app has access to. Potential
security hole?

3) Set up an interface (non ASP.NET) to wrap the database access. If you
want to make it easy to move from machine to machine, consider a web service
(Remoting style, not ASMX) and have it serve from the database. DataSets are
highly conducive to web service serving of data (ie, SOAP).

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

***************************
Think Outside the Box!
***************************
 
Thanks Gregory for your fast response. You put me on the right way!
(The Internet Guest Account and ASP.NET Machine Account have now access to
the folder where the db is located (and the dbengine))


But now I found a real problem (for me)...


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. (Sybase SQL Anywhere Database
Engine Version 5.5.04)


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
that error.

What do I have to do solve/work around this problems??


Cowboy (Gregory A. Beamer) - MVP said:
IDEA: Dbf=C:\SqlAny\Demo.db

Not sure about Sybase (have not used it), but the location of the database
is most likely your issue. This gives you a couple of options:

1) Break down ASP.NET (and possibly IIS) security to allow access to this
file path location. Potential security hole?

2) Move the database to a directory your app has access to. Potential
security hole?

3) Set up an interface (non ASP.NET) to wrap the database access. If you
want to make it easy to move from machine to machine, consider a web service
(Remoting style, not ASMX) and have it serve from the database. DataSets are
highly conducive to web service serving of data (ie, SOAP).

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

***************************
Think Outside the Box!
***************************


Wilco said:
hello,

we use this ODBC connectionstring:
"Driver=Sybase SQL Anywhere 5.0;Dbf=C:\SqlAny\Demo.db;Uid=me;Pwd=me"

in a windows application it works fine, but in an asp.net applicatie we get
the next 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).

any ideas?
Click to expand...
Click to expand...
 
Back
Top