If it looks like you have done all of this, try turning on the client
debugging (on the advanced page of your ASA ODBC DSN) and see what
information you get.
Jason Hinsperger
Product Quality
Adaptive Server Anywhere
"Jason Hinsperger" <nos...@ever.ever> wrote in message
news:39A17EBF...@ever.ever...
What happens when you try to connect/run the server/client?
Is your ODBC datasource a SYSTEM datasource or a USER datasource?
Finally, you are using 5.5.04, but what build (you can get this by
looking at the properties of the dbsrv50.exe, or by looking in the
server message window when you start it)?
"Jason Hinsperger" <nos...@ever.ever> wrote in message
news:39A1A3CC...@ever.ever...
Sybase Developers Network
http://sdn.sybase.com/sdn/mec/mec_home.stm
I found that this problem is with security restriction.
Internet user IUSR_MACHINE_NAME does not have persmission to load ASA odbc
DLL .
When you assign IUSR_MACHINE_NAME to administrators group or
when you delete password for IUSR_MACHINE_NAME in WinNT user manager,
the problem is resolved but you have big security problem now.
Jim Egan <dba...@eganomics.com> wrote in message
news:MPG.140ba114a...@199.93.177.77...
"Jason Hinsperger" <nos...@ever.ever> wrote in message
news:39A282A2...@ever.ever...
"Eduard Nesiba" <igna...@iname.com> wrote in message
news:a3UrxXB...@forums.sybase.com...
> I have the same problem with ASA 6 and IIS 4.0
>
> I found that this problem is with security restriction.
> Internet user IUSR_MACHINE_NAME does not have persmission to load ASA odbc
> DLL .
> When you assign IUSR_MACHINE_NAME to administrators group or
> when you delete password for IUSR_MACHINE_NAME in WinNT user manager,
> the problem is resolved but you have big security problem now.
>
>
>
>
>
Try this:
Change the database server service to start with the '-Z' and '-o
eng.out' switch to log debug information. Also add the -hs switch to
turn off shared memory connections to the server. This will force all
connections to use the dbclient.
Start the database server service. Allow it to interact with the
desktop so you can see the server messages.
Start dbclient (use the -Z switch to get debug info.) - make sure it
finds the server.
Try your IIS connection. What happens? Any messages in the database
server window? The client window?