I'm getting a 8000401A (the server process could not be started because 
the configured identity is incorrect.  check the username and pasword) 
when my ASP page tries to create my component with

	Set oFlow = Server.CreateObject("XFSStart.clsFlow")   

This class is set up as a component in a COM+ Server Application that is 
set to run as the Interactive User.  The COM+ Application uses default 
settings throughout; I haven't made any changes other than adding the 
component.  What is strange is that if I log in to the W2K server, the 
error does not occur; the object gets created and works fine.  It's almost 
like the COM+ application is not recognizing the security context in which 
the IIS 5 application is running and uses the interactive user's context 
instead.

Any ideas?

Thanks in advance for your help.
Pete Anfinsen

The reason is you configured idenity is 'interactive user'
'Interactive user'  means the all components under the package 
use 'Currently login user account'
So if nobody log in to your win 2k box, there is no currently login user 
then your all components under the package does not have any user 
credentials.
That's why it works fine when you log in.

So the best solution is change the identity setting to any specific user 
account then it will works fine even if nobody log in to your win 2k box.

Shin Kyoun(Stanley) CHOI

> The reason is you configured idenity is 'interactive user'
'> Interactive user'  means the all components under the package 
u> se 'Currently login user account'
S> o if nobody log in to your win 2k box, there is no currently login user 
t> hen your all components under the package does not have any user 
c> redentials.
T> hat's why it works fine when you log in.

> So the best solution is change the identity setting to any specific user 
a> ccount then it will works fine even if nobody log in to your win 2k box.

> Shin Kyoun(Stanley) CHOI

Thanks for your reply, Stanley.

So let me see if I've got this straight.  I have an IIS 5 server, to which 
users must authenticate in order to use my application.  However, I can't 
run components using the NTLM credentials they supply; I must explicitly 
specify an account, or depend upon the account that's currently in use on 
the console?  In other words, IIS is unable to permit my component to 
impersonate the authenticated user?

BTW, your solution works fine - it's just that I'd like to rely on the 
rights that have been granted to the current IIS user.

Hi,
The components built under NT version works perfectly under 2K environment also. U
do not need any switch  or bridge where  as viseversa doesn't.
Just see the error properly its saying "the configured identity is incorrect"
The user u logged in as doesnt have persmissions to create object. This happens
only when u configured the properties of the component  to particular. So u better
change the permissions to "interactive user" option. then it doesn't give any
problem.

Swathi

Pete Anfinsen wrote:

> I'm getting a 8000401A (the server process could not be started because
> the configured identity is incorrect.  check the username and pasword)
> when my ASP page tries to create my component with
>
>         Set oFlow = Server.CreateObject("XFSStart.clsFlow")
>
> This class is set up as a component in a COM+ Server Application that is
> set to run as the Interactive User.  The COM+ Application uses default
> settings throughout; I haven't made any changes other than adding the
> component.  What is strange is that if I log in to the W2K server, the
> error does not occur; the object gets created and works fine.  It's almost
> like the COM+ application is not recognizing the security context in which
> the IIS 5 application is running and uses the interactive user's context
> instead.
>
> Any ideas?
>
> Thanks in advance for your help.
> Pete Anfinsen
>
> To unsubscribe send a blank email to %%email.unsub%%
>