Jeff,
Where is the SQL server located for your web service? Also, what are
the connection strings that you are using for each? You will need to
provide a little more information.
The fact that it runs in a Windows Forms application indicates that it
is a authorization issue of some sort (because the ASPNET application and
Windows Forms applications, if running the same code, differ in the security
context they are using).
Do not add the ASPNET account to the Local Administrators group. You
are just asking for trouble if an anonymous user hacks into the application,
because that user is now elevated to an administrator of the local machine,
and can cause some damage.
I would create a user on the network with limited rights (enough rights
to access the servers you need across the network) and then have the ASP.NET
application impersonate that user.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Jeff" <je**@nowhere.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
By default, ASP.NET runs under a local system account named ASPNET,
which has no access to the network. You are probably failing because of
this. What you have to do is configure the web app so that it runs with the user credentials of someone who can connect over the network to the
database.
Thanks for the info. but I'm afraid that didn't resolve my issue.
The odd thing is that my web service also makes calls to a MS SQL Server
without any problems. The logon information is embedded in the connection
string for both the Oracle connection as well as the MS SQL Server
connection. The only difference is that the MS SQL Server connection
works and the Oracle connection doesn't.
As a test I also added the "ASPNET" user to the "Local Administrators"
group but that had no effect.
Anyone have any other suggestions?
--- Thanks, Jeff