Hi all,

I am the developer of an application, which uses a Sybase (SQLAnywhere
10) database and which supports multi-user on the same machine this
way:

- When a user with a windows login (say: user1) has invoked the
application, it can read and write to the database over an ODBC
connection..
- At the same time, from the same machine, if user2 is logged on and
he/she invokes the application, he can access the database but cannot
write to it (over the same ODBC connection).

I supported this functionality already in the previous versions of the
application without any problems. However, my app was running on a
Windows 2003 Server machine and was developed on a Windows XP machine.

Now, I installed the new version of my application to a Windows 2008
Server machine and get the following error when the second user tries
to invoke the application: "Specified database file already in use". I
tested in on a Windows 7 machine and get the same error. When I try it
on a Windows XP machine, it works as normally.

What is the problem with Windows 2008 Server and 7? I also tried with
SQLAnywhere 12 but the problem stays.

Some of my ODBC information follows:

Database tab:
Start Line: dbeng10.exe -c 8m [had a -x tcpip but I deleted it, I
don't need tcp/ip for this application. All connections are local. It
wasn't working with -x tcpip either.]
[x] Start database automatically
[x] Stop database automatically

Network tab:
[ ] TCP/IP
[ ] SPX
[x] Shared Memory (it didn't work when I unchecked this, either)

Advanced tab:
[x] Allow multiple record fetching

I would highly appreciate if you could help me. I don't understand why
it works on Windows Server 2003 & XP and why it doesn't on Windows
Server 2008 & 7.

On May 16, 11:36*pm, Onur <onu... (AT) gmail (DOT) com> wrote:
I also have same issue but I'm installing SQL Anywhere 9 on my Vista
laptop.
Similar to your situation SQL Anywhere 9 runs without this error on my
XP machine.
But refuses run > 1 connection on Vista - Spent a day trying
everything I could think of to resolve it then ran out of patience.
I suspect same situation on Windows 7 too.
Looking forward to getting this resolved so will be following this
thread.

Steve

I couldn't find any solution. I solved the problem using dbsrv instead
of dbeng.