Solved

Problem after upgrade with ASP.NET subsites seeing root web.config and not their own

Posted on 2009-05-06
8
989 Views
Last Modified: 2012-05-06
Original configuration:

ASP application for the root web site
Subsite applications were various ASP.NET (1.1 and 2.0) sites with their own web.config
Subsite applications were access using www.domain.com/app1

After upgrade:

Root web site became a ASP.NET site with it's own web.config
Subsite applications break because they only see the root web.config

What is the best way to remedy this and have subsite application still access using www.domain.com/app1?

Using Windows Server 2003 Standard and IIS6.

Thanks!
0
Comment
Question by:OCSDTech
  • 4
  • 4
8 Comments
 
LVL 37

Expert Comment

by:samtran0331
ID: 24317901
So the root web site after the upgrade is still Classic ASP right?
I'm not sure you can "remove" ASP.Net from it...but since it isn't an ASP.Net site, you could try removing the root's web.config (just rename it to something else)...and see what happens...
0
 

Author Comment

by:OCSDTech
ID: 24317953
The root web site after the upgrade is now ASP.NET and it needs to be ASP.NET as certain features are based on .NET.
0
 
LVL 37

Accepted Solution

by:
samtran0331 earned 500 total points
ID: 24318220
Coincidentally, this question was right before yours...see the link I posted in the solution...
http://www.experts-exchange.com/Programming/Languages/.NET/ASP.NET/Q_24385966.html?cid=236#a24317800
0
 

Author Comment

by:OCSDTech
ID: 24320067
samtran0331,

The root site has three subsites: 2 running 2.0.50727 and 1 running 1.1.4322.

The 2.0.50727 subsites and the root site work fine but the 1.1.4322 subsite complained about the xmlns of the <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> statement.

When I took that part out, the 2.0.50727 subsites and the root site still worked but the 1.1.4322 subsite now complained about the inheritInChildApplications attribute in the location element.
Parser Error Message: Unrecognized attribute 'inheritInChildApplications'.

The 1.1.4322 subsite doesn't like the new 2.0.50727 attributes.
0
Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

 
LVL 37

Expert Comment

by:samtran0331
ID: 24324587
Is the 1.1x app still actively being developed?
If not, in IIS switch the ASP.Net version for that app from 1.1x to 2.x
I've had situations where a 1.1x project will work fine under the 2.x framework...and I've had other situations where it just completely blows up.  You might have to make some minor web.config changes... But if you can get it to run under 2.0, the inheritInChildApplications attribute will work.

If the 1.1x project is still actively developed/changed...I would recommend you upgrade the project to 2.0...it will take a little effort but I've never had a failed upgrade.

Alternately, you might just have to run the 1.1x app in a separate web site...you could redirect any users that use the old address to the new address...but I don't know if there is any other way around this "child app" problem...
0
 

Author Comment

by:OCSDTech
ID: 24325981
samtran0331,

I should have mentioned it in our last post but I did try having the 1.1x subsite run under 2.x and the subsite ran okay except that the Crystal reporting stopped working under 2.x.  

As you suggested, we're now looking into upgrading the project to 2.x.  Hopefully that will be relatively painless.
0
 
LVL 37

Expert Comment

by:samtran0331
ID: 24326205
The upgrade would be the best route any way you look at it.

But you said:
subsite ran okay except that the Crystal reporting stopped working under 2.x.  

One thing you might want to try is:
1. create a new 2005 asp.net 2.0 project.
2. Add a crystal report to it and look at the web.config entries for crystal.
3. see if putting/replacing those entries in the old app's web.config makes the old app run under 2.x

Good luck!

0
 

Author Comment

by:OCSDTech
ID: 24435866
Thanks for all your help.  It looks like we'll be looking to update the 1.1x site to 2.x.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Just a quick little trick I learned recently.  Now that I'm using jQuery with abandon in my asp.net applications, I have grown tired of the following syntax:      (CODE) I suppose it just offends my sense of decency to put inline VBScript on a…
If you don't have the right permissions set for your WordPress location in IIS, you won't be able to perform automatic updates. Here's how to fix the problem.
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
This video explains how to create simple products associated to Magento configurable product and offers fast way of their generation with Store Manager for Magento tool.

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now