| Scott 
  New Member
 Posts:39
 
  
 
  | 
    
     | 02/02/2008 10:26 PM |  |  
     | Hi Peter, I just installed DMX 4.2 on my DNN 4.8 portal.  Following the installation process, everything seemed to proceed normally without any errors.  Since I am installing over a DMX3 installation I also ran the specified update script.  While I was logged in, everything seemed to function normally.  However, after logging off and attempting to log back into my site, I received a Windows Authentication challenge.  I tried using my server username/password and I also tried using both my DNN host and admin username/passwords.  Nothing worked.  The site is running but I can't login. Note that I didn't make any changes in IIS other than what was specified in the installation manual.  That is, I didn't change the authentication or access control.  The DesktopModules\Bring2mind\DMX directory appears to have the correct worker process and rights (Menu and Core exist) and the database checks out as well.  I made no other changes to the site.  Fortunately, I have everything backed up, but I'm hoping you'll have an answer before I have to backout the changes. Thanks Scott |  
     |  |  
     |  |  
    |  |  | 
    
    
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 02/03/2008 9:28 PM |  |  
        | Hi Scott,Have you restarted IIS yet? Secondly can you tell me which httpModules are listed in your web.config? I've not seen this before and I'm very curious about what might cause this.
 Peter
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 02/04/2008 4:37 PM |  |  
        | Hi Peter, Yes, I did restart IIS and it didn't help.  I'll have to get back to you about the various httpModules.  In the meantime, I do have some additional information.  I restored my site using my backups and then reinstalled DMX4.  As I performed each step, I checked to see if I was having the same problem.  Everything worked until I went to activate the module.  Upon successful activation, I logged out, attempted to log back in, and received the Windows challenge.  I looked in my web.config and noticed that the key, order, and name referenced the old DMX 3 values.  Since I had printed out my new information, I tried using those values, but they didn't work either.  Anyway, I'll open the web.config file and get back to you.  Thanks. Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 02/04/2008 8:43 PM |  |  
        | Hi Peter, Here ya' go:       <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
 
 
 
 
 
 
 
 ThanksScott
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 02/04/2008 8:50 PM |  |  
        | Trying again: add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" add name="RequestFilter"type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxx" |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 02/05/2008 6:10 PM |  |  
        | Hi Scott,It appears the DMX handlers are not installed in the web.config. I guess you followed instructions to set IIS settings (i.e. Application Configuration) correctly. It's imperative that the httpModules and httpHandlers are also present (see installation manual). What you can do is to run the 'reinstall config' script. Then check your web.config again. If nothing has changed then asp.net has no read/write access to your web.config.
 Peter
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 02/05/2008 8:18 PM |  |  
        | Hi Peter, My mistake.  I was unclear about the handlers.  My web.config file WAS updated with the requisite handlers identified in the installation instructions.  I checked off each step as it was completed.  The list I provided shows what I have AFTER restoring my system to its original state.   I'll try a third time to install DMX4 and provide you with the relevant contents of my web.config file.  Sorry for the confusion. Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/09/2008 8:47 PM |  |  
        | Peter, Sorry for the long delay.  I restored my system and only recently had a chance to try again.  Unfortunately, I have the same problem. 1.  I'm using IIS 6.02.  I'm using SQL 2005
 3.  I'm running DNN 4.8.0
 4.  I've installed DMX 4.2.0
 5.  I made a backup of both the site and database (saved me last time!)
 6.  Installation was successful (no red comments or errors; I have copy of results as well)
 7.  This is copied from the IIS dialog box:
 GET,HEAD,PUT,OPTIONS,PROPFIND,PROPPATCH,COPY,MOVE,DELETE,MKCOL,LOCK,UNLOCK,DEBUG
 From "Executable":
 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
 unchecked "Verify that file exists"
 8. Prohibited WebDAV as instructed.
 9. Verified that DesktopModules\Bring2mind\DMX directory exists
 10. Verified that Menu and Core sub folders exist; I am upgrading from DMX3
 11. Verified that tables exist in database; Both DMX_Permissions and DMX_Entries are present
 12.  I did NOT check for the stored procedures
 13. Verified entries in DesktopModules table; Verified entries in ModuleDefinitions table
 ModuleDefId is 129; found 9 entries in ModuleControls table
 14. Verified all 5 additions to web.config (I will show contents below)
 15. Updated host settings as specified; (Whitespace not checked; added the
 exclude path for desktopmodules\bring2mind\dmx\download.aspx; used
 'Deflate Compression" as you did in the example.
 16. Ran DMX 3 to DMX 4 upgrade script (no errors; I have copy of results as well)
 17. Ran Reindex installation script (no errors; I have copy of results as well)
 18. I did NOT activate yet.
 After all of the above, I logged out and attempted to login again.  At that time I received the Windows Authentication Challenge and I cannot log in to my site.  Thanks. See web.config below:     <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
 
 
 
 
 
 
 
 
 
 
 
     <!-- This is for CAPTCHA support -->
 
 <!-- This is for Serving files, secure, insecure, from database -->
 
 <!-- This adds syndication support -->
 
 <!-- This adds legacy support for the Logoff page -->
 
 <!-- ASP.NET AJAX support -->
 
 
 
 
 
 
 
 
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/09/2008 8:54 PM |  |  
        | Arrgghhh...  I tried to copy the xml in the previous message and it doesn't work.  I removed the chevrons so the content can be seen.  I hope this works.    httpModulesadd name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication"
 add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules"
 add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules"
 add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules
 add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules
 add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules"
 add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules"
 add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules"
 add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
 add name="RadUploadModule" type="Bring2mind.Telerik.WebControls.RadUploadHttpModule, Bring2mind.Telerik.RadUpload.Net2"
 add name="WebDAVAuthenticationModule" type="Bring2mind.DNN.Modules.DMX.WebDAV.AuthenticationModule, Bring2mind.DNN.Modules.DMX.WebDAV"
 httpModules
 httpHandlers
 -- This is for CAPTCHA support --
 add verb="*" path="*.captcha.aspx" type="DotNetNuke.UI.WebControls.CaptchaHandler, DotNetNuke"
 -- This is for Serving files, secure, insecure, from database --
 add verb="*" path="LinkClick.aspx" type="DotNetNuke.Services.FileSystem.FileServerHandler, DotNetNuke"
 -- This adds syndication support --
 add verb="*" path="RSS.aspx" type="DotNetNuke.Services.Syndication.RssHandler, DotNetNuke"
 -- This adds legacy support for the Logoff page --
 add verb="*" path="Logoff.aspx" type="DotNetNuke.Services.Authentication.LogOffHandler, DotNetNuke"
 -- ASP.NET AJAX support --
 remove verb="*" path="*.asmx"
 add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
 add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
 add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"
 add path="Bring2mind.Telerik.RadUploadProgressHandler.aspx" verb="*" type="Bring2mind.Telerik.WebControls.RadUploadProgressHandler, Bring2mind.Telerik.RadUpload.Net2"
 add path="/" verb="OPTIONS,PROPFIND" type="Bring2mind.DNN.Modules.DMX.WebDAV.DavHandler, Bring2mind.DNN.Modules.DMX.WebDAV" validate="false"
 add path="dmxdav.axd" verb="GET,HEAD,PUT,OPTIONS,PROPFIND,PROPPATCH,COPY,MOVE,DELETE,MKCOL,LOCK,UNLOCK,DEBUG" type="Bring2mind.DNN.Modules.DMX.WebDAV.DavHandler, Bring2mind.DNN.Modules.DMX.WebDAV" validate="false"
 /httpHandlers
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/09/2008 10:09 PM |  |  
        | Peter,
 This time, rather than quickly restoring my site, I decided to restore only the web.config file.  Although I'm sure this will affect the DMX module, I can now login to the site.  Knowing this I diff'd the before and after versions to see what changed.
 
 1.  The 5 expected changes were present.  2 within httpModules and 3 within httpHandlers.
 2.  My htmlEditor are wrong.  I had installed a trial version of the RAD editor (by Telerik).  The settings are incorrect.  I'll remove and let you know if this is fixed.
 
 Scott
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/09/2008 10:43 PM |  |  
        | Peter,
 I've narrowed it down to this line:
 add name="WebDAVAuthenticationModule" type="Bring2mind.DNN.Modules.DMX.WebDAV.AuthenticationModule, Bring2mind.DNN.Modules.DMX.WebDAV"
 
 If it is in my web.config, I am confronted with a Windows Authentication Challenge.  If I leave it out, I get my normal login page and I can access my site.  Thoughts?
 
 Scott
 
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 03/10/2008 10:00 AM |  |  
        | Hi Scott,
 Great research! Could you do the following for me: run a Fiddler session and send me the saved/zipped sessions? This will show me what the server responds. It might give me a clue as I can compare it to a regular session. Send to peter@bring2mind.net.
 
 Peter
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/12/2008 6:58 PM |  |  
        | Hi Peter, Okay, I sent it.  I'm not a fiddler expert, so I hope the file helps.  Please let me know if you find anything. Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 03/12/2008 9:04 PM |  |  
        | I did find something. This is one of the headers:
 MicrosoftOfficeWebServer: 5.0_Pub
 
 Can you tell me why it's there? It shouldn't be. It is my primary suspect because any server running parallel to the regular IIS/DNN is liable to start throwing authentication errors.
 
 Peter
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/15/2008 7:36 PM |  |  
        | Peter, I'm not sure why MicrosoftOfficeWebServer would be there.  I did find an Office 2003 package on my server and removed it.  It still didn't take care of the problem.  I'm not real familiar with Fiddler; how do I find out if this header is still there? Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/15/2008 9:40 PM |  |  
        | Peter, I figured out the Fiddler question.  The header is still there.  Do you know if it is okay to run Frontpage Server Extensions?  This is the only thing I can see that might cause a problem.  My server is 'fairly' vanilla.  For the most part, I don't have office tools or other software running on the box.  I've googled the header and searched the Microsoft site, but other than removing the Office 2003 components (which I'm not sure how this was installed), I'm temporarily stuck. Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 03/17/2008 6:42 PM |  |  
        | Hi Scott,I have been working on this part a bit more. I found out that sometimes the browser can mangle a cookie (don't ask me why). It happened on an IE7/Vista installation here. In any case: it did lead to this error. I have made this part a bit more robust and will be integrated in 04.02.01 coming out any day soon.
 Peter
 |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Scott 
  New Member
 Posts:39
 
  
 
  | 
       
        | 03/21/2008 2:55 AM |  |  
        | Hi Peter, I'm sorry to say that I get the same results using 4.2.1.  I've tried using XP/IE1, Windows Server 2003/IE7 and Vista/IE7.  The one commonality is IE7.   Scott |  
        |  |  
        |  |  
        |  |  | 
  
    
     | Peter Donker 
  Veteran Member
 Posts:4536
 
  
 
  | 
       
        | 03/27/2008 12:31 PM |  |  
        | Hi Scott,Then I'm fairly stuck again. The code in the authentication module is pretty solid now. Can you run a Fiddler session again and send it to me?
 Peter
 |  
        |  |  
        |  |  
        |  |  |