Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade Issue from 5.1.2 to 5.4.4 - LinkClick.aspxUpgrade Issue from 5.1.2 to 5.4.4 - LinkClick.aspx
Previous
 
Next
New Post
7/15/2010 7:12 PM
 
Bruce Chapman


www.dnnsoftware.com
Joined: 12/7/2005
Posts: 792
Sebastian : the standard configuration of the Url Master module is setup to handle linkclick Urls, so this should only ever be a problem if a change has been made to the settings.

In this case, it's likely that moving the files from the server to a virtual directory might be the issue here.   The linkclick handler reads and streams file contents back to the requesting visitor, so if those files move, then there is going to be an issue with the handler finding and reading, then streaming the files.

If you shift the file back to the portals folder, and it starts working, that's most likely to be the point where the issue is.
 
New Post
7/16/2010 2:39 PM
 
throttlenet programmers

Joined: 7/8/2008
Posts: 8

The issue is able to reproduced consistently in our test environment and we have isolated the issue down to the virtual directory.

To reproduce the issues seen in production we performed the following tests

1.       Test One – Verify system updates properly without virtual directory for Portals

a.       Installed Novus site to current production configuration

b.      Upgraded versions with no virtual directory

c.       All upgrades were successful and linkclick.aspx was operating properly

d.      This was successful across multiple incremental upgrades all the way to 5.4.4

2.       Test Two – Verify upgrade fails when using virtual directory for Portals

a.       Installed Novus site to current production configuration

b.      Immediately established Portals folder as virtual directory

c.       Verified site operated at version 5.1.2 with virtual directory

d.      Conducted upgrade to version 5.2.3

e.      Verified linkclick.aspx failed after upgrade with 404 error

3.       Test Three – Update install with no virtual directory and then move updates site Portals folder to virtual directory

a.       Installed Novus site to current production configuration

b.      Upgraded to version 5.2.3 with no virtual directory

c.       All upgrades were successful and linkclick.aspx was operating properly

d.      After upgrade was complete we configured the Portals directory as a virtual directory

e.      At this point the linkclick.aspx stops working and returns 404 error

f.        Removed the virtual directory and restored Portals folder to DNN install folder

g.       The linkclick.aspx immediately began functioning again

We will be working to test and see if the upgrade will work properly with the entire install as virtual directory. Our results will also be posted to the DotNetNuke user forums to continue support there and hopefully prompt a fix from core team. All other options for upgrade will be reviewed as I know you are looking to upgrade to Pro shortly. Our final results and recommendations should be ready tomorrow and will follow up further at that time.

We have our hosting environment set up in a unique way i guess. The DNN core and module files are located on two separate servers. The Portals directory is located on a file share. This spreads the applications files accross two nodes for better performance, reduced I/O, load balancing, and scalability.

From the DNN Documentation I have seen it show the Web Farm as 2 servers running IIS and all files(core, module, application, portals, etc) on a central file share. The two server access the same filesets but this places all files on a single server which could have I/O issues under high load. Does anyone have any thoughts on Web Farm configuration?
 
New Post
8/5/2010 12:18 PM
 
throttlenet programmers

Joined: 7/8/2008
Posts: 8
All, we have successfully resolved this issue by modifying our hosting setup and conforming to the recommended environment for DNN on web farm. All files were moved to a central, redundant file share.

The two IIS servers had all application files removed and the IIS heads were setup to access all application files from the central file share. Voila' all problems are now resolved.

My thoughts are this is likely due to a change in how DNN creates the portals directory path. This code must no longer read the virtual path and simply assumes Portals will never be in virtual directory. We have run into this issue before with custom applications we have created and is just symantecs on how you build the file path. If you don't use the map path method the application is never aware of the full physical path to the file directory.

Also, in order to complete the hosting configuration with 2 IIS heads we had to resolve a permissions issue with CASPOL. Here is link to resolution of this issue if anyone else runs across http://forums.iis.net/t/1148003.aspx
 
New Post
8/5/2010 12:23 PM
 
throttlenet programmers

Joined: 7/8/2008
Posts: 8
One question on this for Ken Grierson. Would you still like me to report this as a bug in Gemini?

Technically it was due to a difference in our hosting setup that deviated from the recommended implementation. From that perspective I'm not sure if you consider this a bug or not.
 
New Post
8/5/2010 2:55 PM
 
Ken Grierson


Joined: 7/18/2009
Posts: 613
throttlenet programmers wrote:
One question on this for Ken Grierson. Would you still like me to report this as a bug in Gemini?

Technically it was due to a difference in our hosting setup that deviated from the recommended implementation. From that perspective I'm not sure if you consider this a bug or not.

 Matt;

Please log this as an issue in Gemini. We're looking at every customer report from the forums, Support and Gemini for roadmapping I'd like us to review your scenario when we consider feature changes within and around Portal creation.

Ken Grierson
DotNetNuke Corporation
Test Lead
 
 Page 3 of 3
Previous123 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade Issue from 5.1.2 to 5.4.4 - LinkClick.aspxUpgrade Issue from 5.1.2 to 5.4.4 - LinkClick.aspx


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