Please Help!-Trying to brows my asp.net application but I get a logon prompt-

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

J-T - 21 Jul 2005 19:29 GMT

Hi All,

We have an asp.net application on a windows 2003 server which is part of a
domain controller which my worksatis is too. We have impersonated in our
applciation with a fixed identity account which is also a domain account and
is part of the admininstrator group of the webserver.The application is set
to use NTLM and its application pool's IDENTITY is also set to use that
imperssonated account,when I try to browse the application from my
workstation(same network) I get a logon prompt (which *should not* be poped
up as
I'm using NTLM) and even when I insert my username and password ,it rejects
it and says that I'm not authorized to see the page.I have added the
administator group to the local security policioes like "Logon locally" "log
on as a service" ","log on as abatch job" "Access this computer from the
network".Why I cannot see my application ??

Reply to this Message

J-T - 21 Jul 2005 19:44 GMT

I followed up this link :
http://www.kbalertz.com/kb_871179.aspx

and I solved the logon problem ,but now I get this error

Logon failure: unknown user name or bad password
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Logon
failure: unknown user name or bad password
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[COMException (0x8007052e): Logon failure: unknown user name or bad
password]
System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) +707
System.DirectoryServices.DirectoryEntry.Bind() +10
System.DirectoryServices.DirectoryEntry.get_IsContainer() +10
System.DirectoryServices.ChildEnumerator..ctor(DirectoryEntry container)
+24
System.DirectoryServices.DirectoryEntries.GetEnumerator() +26
CgaCanada.Org.Common.ADUtils.getMMSList() in
c:\vss\SMIA\Common\ADUtils.cs:111

[SystemException: Failed to retrieve examiner list.Logon failure: unknown
user name or bad password]
CgaCanada.Org.Common.ADUtils.getMMSList() in
c:\vss\SMIA\Common\ADUtils.cs:118
SMIA.Business.ApplicationCache.GetExaminers() in
c:\vss\SMIA\Business\ClassFiles\ApplicationCache.cs:962
SMIA.Business.ApplicationCache.init() in
c:\vss\SMIA\Business\ClassFiles\ApplicationCache.cs:1163

[SystemException: ApplicationCache initialization failed. ]
SMIA.Business.ApplicationCache.init() in
c:\vss\SMIA\Business\ClassFiles\ApplicationCache.cs:1204
SMIA.Business.ApplicationCache..cctor() in
c:\vss\SMIA\Business\ClassFiles\ApplicationCache.cs:31

[TypeInitializationException: The type initializer for
"SMIA.Business.ApplicationCache" threw an exception.]
SMIA.Business.ApplicationCache.get_Reference() +0
SMIA.Business.BusinessLayer.Init(String baseName, String assemblyName) in
c:\vss\SMIA\Business\ClassFiles\BusinessLayer.cs:28
SMIA.Web.Global.Application_Start(Object sender, EventArgs e) in
c:\vss\SMIA\SMIAWeb\Global.asax.cs:50

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032

Reply to this Message

J-T - 22 Jul 2005 21:25 GMT

I actually solved the problem there were some issues involved:

1) It has nothing to do with Authentication type of the application and the
user we used to connecto to active direcoty caused all those problem.It ws
not setup properly.

2) some body deployed PDB files( Debug mode) to the production and some
unnecessay PDB files there were making the situation even worse.Our
Authorization amanger store file(XML) file could not be found because we
were using App.Domain.CurrentDirecoty() which is different in Debug and
Release mode...Stupid mistake

3) Authorziation manager File (XML) was out of date too:-)

It has been solved now,and agian it has nothing to do with impersonation and
authentication type and it was all about our own mistakes talking to Active
direcoty using ADSI.

Thanks again

>I followed up this link :
> http://www.kbalertz.com/kb_871179.aspx
[quoted text clipped - 49 lines]
> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
> ASP.NET Version:1.1.4322.2032

Reply to this Message

Please Help!-Trying to brows my asp.net application but I get a logon prompt-

Free Magazines