G
Gianluca Torta
Cross posting since I had no reply yet from
microsoft.public.dotnet.framework.component_services
Hi all,
I have an ASP.NET app and a Serviced Component that runs within a COM+
app
the Serviced Component is intended to access a remote database with an
identity that is NOT <MACHINE>\ASPNET but an account MYDOMAIN\MYUSER
that actually can access the remote database
the COM+ app has been configured to RUN AS SERVER and I have specified
in the identity tab that the app should run as MYDOMAIN\MYUSER
however, when I open my ASP.NET app and click on the button which
makes the call to the Serviced Component, I can see from SQL Server
Profiler that the user which tried to access the remote DB is
<MACHINE>\ASPNET
for some reason, the COM+ app is not running as the account that I
specify in the Identity tab but as the caller (which in this case is
<MACHINE>\ASPNET)
I guess I have some configuration problem, but I really couldn't
figure out what it is:
- I correctly wrote my Serviced Component
- I strongly named the assembly .DLL produced by compiling the
component
- I registered the component with regsvcs.exe
- my ASP.NET application references the DLL that has been strongly
named
Any suggestions would be welcome!
Thanks in advance,
-Gianluca Torta
microsoft.public.dotnet.framework.component_services
Hi all,
I have an ASP.NET app and a Serviced Component that runs within a COM+
app
the Serviced Component is intended to access a remote database with an
identity that is NOT <MACHINE>\ASPNET but an account MYDOMAIN\MYUSER
that actually can access the remote database
the COM+ app has been configured to RUN AS SERVER and I have specified
in the identity tab that the app should run as MYDOMAIN\MYUSER
however, when I open my ASP.NET app and click on the button which
makes the call to the Serviced Component, I can see from SQL Server
Profiler that the user which tried to access the remote DB is
<MACHINE>\ASPNET
for some reason, the COM+ app is not running as the account that I
specify in the Identity tab but as the caller (which in this case is
<MACHINE>\ASPNET)
I guess I have some configuration problem, but I really couldn't
figure out what it is:
- I correctly wrote my Serviced Component
- I strongly named the assembly .DLL produced by compiling the
component
- I registered the component with regsvcs.exe
- my ASP.NET application references the DLL that has been strongly
named
Any suggestions would be welcome!
Thanks in advance,
-Gianluca Torta