Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have two websites ASP Classic - www.company.com and www.companytesting.com.

At this time of year, company.com is pointed to a folder called website2012 and companytesting.com is pointing to a folder called website2013. The contents of those two folders are almost identical, just minor changes for our season change (which I was supposed to do today - lol).

Up until a couple of weeks ago, I was running Windows Server 2003. To update the "live" website, I'd make a copy of the test site folder, and rename it website2013R1, and point the test site there, then point the live site at website2012.

We now have Windows Server 2008 R2 64. (I had someone migrate the websites to the new server for me.)

The companytesting.com site, when I pointed it to website2013R1, worked fine.

The company.com site, when I pointed it to website2013 (which worked just before, for the companytesting.com site) gives an empty page. (i.e. view source = nothing there.) There is nothing in the failed request log when this happens.

I can use the Explore button/link (upper right) in IIS7.5 and see all of the files there. If I use the browse button (either in general or on the index.asp page) I get the blank page again.

One weirdness about how these are set up is that companytesting.com uses a login (which I think is windows authentication - it's simply a single username and password for staff, and to keep the GoogleBots out of it). Obviously, company.com does not. But redirecting the to website2013r1 kept the login in place. (So I'm not absolutely clear whether that's attached to the folder or to the site. Hitting the company.com site after changing the path did not yield a password request.)

The permissions on the folders all seem to be the same, but obviously, I'm missing something.

Why isn't changing the physical path working?

As is probably obvious, I'm not knowledgeable about servers. I did OK in 2003, but since it's not my main task and I'm buried right now, I have barely looked at 2008. So I may have really stupid questions when you ask me to check something.

share|improve this question
    
I was thinking something wrong with the folder, but that's not right. I copied everything from my 2013 folder to my 2012 folder, and the problem reoccured. I'm thinking that instead of being a server issue, like I initially thought - though it still might be, partly - that it's at least partly a programming issue, in which case, it belongs on StackOverflow instead of ServerFault. I will post my eventual resolution here ('cause I hate finding threads with my problem and non answer) but I think I will re-ask the question there. –  Julie Aug 29 '12 at 23:53
add comment

1 Answer

up vote 1 down vote accepted

The issue lies in the different ways Win Server 2003 and Win Server 2008 handled the password protected testing site, or at least the way the consultant I hired set it up.

The problem was that the web.config file varied between the website2012 and website2013 folders. Access to the development site was restricted in the web.config file, and contained the line:

            <remove users="*" roles="" verbs="" />

Since the live website didn't have a username/password attached to it, it didn't bring up the username password box and simply gave me a blank page.

I dropped the web.config from the "old" website into the website2013 file, and the problem was solved.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.