Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...continuous redirect loop after upgradingcontinuous redirect loop after upgrading
Previous
 
Next
New Post
8/8/2006 2:46 PM
 

Hi

I just upgraded from 4.0.3 to 4.3.4 (the latest as of today)

after the upgrade procedure, I went to my site, the update appeared to work correctly, and I got the "Click Here to access your Portal" link at the bottom.  I clicked the link, and the site was hung forever in IE, never loaded, never errored.  After retrying and looking for answer, I installed a utility called Fiddler, and it shows that Im hitting myDir/Default.aspx?alias=mydomain.com/myDir.  It seems to be stuck in a continuous redirect.  I looked in datatable and all my portal aliases are there just as they were before.

Any ideas?

 
New Post
8/13/2006 11:04 AM
 

Did you ever sort this? I have exaclty the same problem but with a fresh install of 4.3.4.

I have XP Pro 64bit, IIS 6.0, and SQL Server 2000.

All installed with no errors reporting. I Clicked on the link: "Click here to access your portal" and after a few second of rapid hard drive activity nothing happens other than the internet explorer flag waves at me forever, and the progress indicator in the status bar flickers madly. The screen doesn't even go blank, it just keeps showing the original installation screen.

 

 

 

 
New Post
8/13/2006 7:09 PM
 

hi

I never really found an answer for this other then doing a fresh install.  this error occured after trying to upgrade a vs.net 2005 installation.  I was having the same problems as found in this thread, and there is no answer yet that I know of other then vs.net 2005 installs are bugged.

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/51508/scope/posts/Default.aspx#60543

Good luck on finding answer let me know what you find :)  thanks.

-Jay

 
New Post
8/15/2006 11:58 AM
 

Hi,

I was using windows authentication which I can't get to work (see below). I'm now using Forms Authentication which works fine. However I really want windows authentication to work so that I can use our Active Directory server.

Windows Authentication:
I've tried this on my home machine:Window XP Pro (IIS6), and the works Windows Server 2000 machine and they both have the same problem.

  • In IIS: Integrated Windows Authentication checked, and Anonymous Access unchecked. 
  • On the Dotnetnuke folder and subfolders and the Database: ASPNET and NETWORK SERVICES have full dbowner access
  • In web config: connectionString="Server=(local);Database=DotNetNuke;Integrated Security=True;"
    Also tried integrated security = SSPI
  • In the web config, Forms authentication not used, windows authentication used instead:
    <authentication mode="Windows" />
    <identity impersonate="true" />
  • In the database all the tables and stored procedures have been created (including dbo.GetPortals)
  • I'm not using a qualifier: objectQualifier="" databaseOwner="dbo"
  • My database is not case sensitive.

Despite the install page saying everything has installed correctly the Windows Application Event Viewer reveals something else:
It seems to be saying that ASPNET is not Authenticated nor is it Impersonating. I've hilighted the 2 lines in bold (and xxx'd out my IP address, account name, and server name):

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 15/08/2006 16:23:10

Event time (UTC): 15/08/2006 15:23:10

Event ID: ed91e6a2c28a4e8bbfebe88db8181163

Event sequence: 2

Event occurrence: 1

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/Root/DotNetNuke-1-128001289855175000

Trust level: Full

Application Virtual Path: /DotNetNuke

Application Path: C:\Inetpub\wwwroot\DotNetNuke4\Website\

Machine name: xxx

Process information:

Process ID: 5508

Process name: aspnet_wp.exe

Account name: xxx\ASPNET

Exception information:

Exception type: SqlException

Exception message: Could not find stored procedure 'dbo.GetPortals'.

Request information:

Request URL: http://xxx/dotnetnuke/Default.aspx

Request path: /dotnetnuke/Default.aspx

User host address: xxx.xx.xxx.xxx

User:

Is authenticated: False

Authentication Type:

Thread account name: xxx\ASPNET

Thread information:

Thread ID: 1

Thread account name: xxx\ASPNET

Is impersonating: False

Stack trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()

at System.Data.SqlClient.SqlDataReader.get_MetaData()

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)

at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership)

at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)

at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText)

at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)

at DotNetNuke.Data.SqlDataProvider.GetPortals()

at DotNetNuke.Entities.Portals.PortalController.GetPortals()

at DotNetNuke.Common.Global.CacheMappedDirectory() in C:\Inetpub\wwwroot\DotNetNuke4\Website\App_Code\Global.asax.vb:line 145

at DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in C:\Inetpub\wwwroot\DotNetNuke4\Website\App_Code\Global.asax.vb:line 255

Custom event details:

Hope anyone reading can see where I'm going wrong?

Regards,

Simon Norman

 

 
New Post
8/18/2006 4:06 PM
 
ski06 wrote

Good luck on finding answer let me know what you find :)  thanks.

-Jay

Ok I think I've narrowed it down a bit further. With a lot of trial and error I've got a half way house.

Using Forms authentication (but with IIS set to Windows Authentication and Anonymous user unchecked), I uncommented the authentication module and impersonation=true, and then pointed my browser at the winsdowssignin.aspx page. Hey presto it auto logged me in as an ordinary user. Viewing the Database through Enterprise Manager I could see that my user login details had been added to the users table and aspnet_users table in the form of DOMAIN\USER, but no firstname, lastname, displayname, and no AD roles. - which led me to believe active directory wasn't being accessed correctly. (I changed my role to 0 - Admin for good measure whilst I was here).

Now I could leave things like this, everyone can log on automatically, and I can fill in their missing names and assign them to dnn roles manually.

However, I really would like to get the AD synching working, so, feeling that I was getting somewhere, I commented out forms authentication and uncommented windows authentication and tried to auto log in again. Amazing, it auto logged me in with admin priveldges (no looping this time, probable because I now exist in the user tables). However, still no firstname, lastname, or displayname though. So, off to Admin Menu -> authentication: I believe that I can leave the domain, user and password boxes blank and just check the two check boxes. This is because it should be using my impersonated details to access AD. And I certainly have no problems accessin AD in my own applications without providing these details. Si I hit the update button hoping it will tell me what's wrong:

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
Could not access LDAP to obtain domain info

I can't figure out what is wrong with this last bit and the signin page still hangs for everyone else even though it is now working for me.

So unless anyone else has an answer it looks like I'll have to use impersonation with forms authentication and manually amend my users details as and when they very first auto log on.

Cheers,

Si

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...continuous redirect loop after upgradingcontinuous redirect loop after upgrading


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out