MTS Component Problems - HELP!

  • Thread starter Thread starter DavidM
  • Start date Start date
D

DavidM

Hello -- I have a web application that runs under II5 and COM+ as a public
facing web application using ASP. We have been using this application for
about 2 years now without problems. However, the issue that I've been
working on is that the application requires the renamed local Administrator
account to be logged on locally. I've narrowed the problem down to a COM+
component set up for "Interactive User - Logged on Locally".

I have since created an application user and gone to local policy settings
and set the "Log on as Batch", "Run as a service", "act as part of OS" and
made the account administrator.

Every time I click on a link to do a statement lookup, the applicatoin
simply hangs and will eventually tell me what it could not pull the
statements.

The particular component is a crypto component that we wrote inhouse.

I have loaded FileMon and from a terminal service session and tried to
access the web page locally. FileMon is showing me access to
C:\WINNT\Debug\UserMode\userenv.log

The log file simly says:

"USERENV(988.aa8) hh:mm:ss:sss GetProfileType: Profile is not loaded.

This repeats over and over until the ASP application returns the user errror
message that it cannot pull the statement.

If I log into the console locally as Admin and set the COM object to use
Interactive user... everything works fine.

How do I figure out how to fix this?

The COM apps right to a C:\MYAPP directory... and I have set the IUSR, IWAM,
Admin, and local application to FULL access to try and see if it is an NTFS
permission issue.

This is really frustrating because my web application has to stay logged on
locally as a admin user. I have an issue with this.

Any help or somments would be appreciated.
 
I don't work with MTS, but under COM+ it is important to note that the user
profile in not loaded automatically for the COM+
identity account. This means if you have code with depends on profile
settings, you will run into problems. I can see how this can occur with a
crypto component, since typically you need to get at digital certificates
found in the personal store belonging to the identity account.

You should be able to solve this by explicitly loading the profile settings
using LoadUserProfile().

Brian
 
Thanks for the feedback, Brian.

I kind of understand what you're saying about the personal store. We do
import a certificate to the Personal Store to be used by IIS for SSL
connections. I think the crypto component that I'm talking about is
primarily used for server-to-server encryption of the data. I do not
believe it uses the certificate for this.

As far as running the LoadUserProfile(). I'm not sure how I can do this,
considering I have no control or access to the code. I'm simply trying to
get something to work that nobody else has ever bothered to get working.

I think it is pretty sad that our web servers have to stay logged in as the
user that installed the application for the statement lookup to work. I'm
not sure what else I can check... I've tried changing the user on COM+ to a
valid NT user with appropriate policy settings. Nothing seems to work --
 
DavidM said:
Thanks for the feedback, Brian.

I kind of understand what you're saying about the personal store. We do
import a certificate to the Personal Store to be used by IIS for SSL
connections. I think the crypto component that I'm talking about is
primarily used for server-to-server encryption of the data. I do not
believe it uses the certificate for this.
Click to expand...

Obviously, I can't help you with this. You need to find out how this crypto
component works. From your description, it is doing something that requires
access to the profile settings. I just described one such example: accessing
a digital certificate stored in a Personal Store. But there could be other
activities. Is the author not available?
As far as running the LoadUserProfile(). I'm not sure how I can do this,
considering I have no control or access to the code. I'm simply trying to
get something to work that nobody else has ever bothered to get working.
Click to expand...

You don't need to do this directly. You could write an intermediary COM+
object that is called from the ASP page, and then calls LoadUserProfile,
then calls the "real" COM+ object. Just make sure both COM+ objects run in
the same COM+ application (I'm using COM+ language, but MTS does the same
thing).
I think it is pretty sad that our web servers have to stay logged in as the
user that installed the application for the statement lookup to work. I'm
not sure what else I can check... I've tried changing the user on COM+ to a
valid NT user with appropriate policy settings. Nothing seems to work --
Click to expand...

For the reasons I described.

HTH,

Brian
 
Back
Top