[Modus] Domain Admin can't logon to webadmin

[Robb Bryn]

Nope… the ones we are seeing the problem on are Registry only (I don’t have any datatbase based admins).  I’m trying real hard to find a predictable pattern but haven’t found it yet.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TDE Internet Sent: Friday, November 14, 2003 10:45 AM To: [EMAIL PROTECTED] Subject: [Modus] Domain Admin can't logon to webadmin   At 03:11 PM 11/14/2003 +0000, you wrote: Can you check and see what the entries are for the FullName, you should be able to find this from the Modus Mail console. I think you might find the DomainAdmins who cant login have blank entries.   The error below is happening here as well.  I beleive this is related to a known software bug in M3.  The bug has to do with being authenticated with an ODBC database.  The problem/bug is that the WebAdmim pages are extremely slow (30+ seconds to load a page) if authenticated via ODBC.  We don't see the error below for Registry mailboxes.  We have tried like heck to make it happen with Registry mailboxes, but can only make it happen with ODBC mailboxes. Jim TDE Internet   Regards,       SuneelJhangiani Inter-ComputerTechnologyLtd.     Modus3 Bug Hunt Winner A rock --> me <-- A hard place     From: Robb Bryn [mailto:[EMAIL PROTECTED]] Sent: 14 November 2003 14:55 To: [EMAIL PROTECTED] Subject: [Modus] Domain Admin can't logon to webadmin   Some of our Domain Admins are getting .NET errors when attempting to logon to the WebAdmin.  At this time I have been unable to determine the pattern.  The error is below.   Thanks Robb Bryn Webmaster CFWebmasters.com   Server Error in '/WebAdmin' Application.     Unhandled Execution Error 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: 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(0x80040057)]     VircomMailLib.MailboxClass.get_FullName()+0     Vircom.modusWebAdmin.UserControls.Login.CustomValidatorLogin_ServerValidate(Objectsource, ServerValidateEventArgs args)+926     System.Web.UI.WebControls.CustomValidator.OnServerValidate(String value)+136     System.Web.UI.WebControls.CustomValidator.EvaluateIsValid()+88     System.Web.UI.WebControls.BaseValidator.Validate()+138     Vircom.modusWebAdmin.UserControls.Login.ButtonSubmit_Click(Object sender,EventArgs e)+207     System.Web.UI.WebControls.Button.OnClick(EventArgs e)+108     System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(StringeventArgument)+57     System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandlersourceControl, String eventArgument)+18     System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)+33     System.Web.UI.Page.ProcessRequestMain()+1277     Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

<<image001.gif>>