brian_appliedcpu
asked on
IIS7 New Website and Application and AJAX Controls
A website was created using Visual Studio 2010 and published to a test Windows 7 machine. After verifying that the website is functional, the files and folders that makeup the website were copied (not published) to a Win 2008 R2 server (Std. Ed.) running IIS 7.5.7600.
On the Win 2008 server, I first created the subfolder C:\inetpub\wwwroot\nihi. The files and folders that makeup the website were copied from the Win 7 machine to the Win 2008 nihi subfolder. Then in IIS7 Manager (Win 2008), I right-clicked on DefaultWebSite, and clicked "Add Virtural Directory", creating a virtual that points to C:\inetpub\wwwroot\nihi. The name I gave the virtual was nihiweb. Next in IIS Mgr, I right-clicked on the nihiweb virtual, and clicked "Convert to Application". While in IIS Mgr, I switched to "Content View", selected nihiweb in the left-hand pane, then right-clicked on Default.aspx, and clicked Browse. This launched IE and allowed me to successfully view and navigate thru the website.
But it is not desirable for me to have nihiweb under DefaultWebSite. So in Windows Explorer (of the same Win 2008 server), I created C:\Website\nihi. I copied all the files and folders from the Win 7 machine over to C:\Website\nihi. Then in IIS Mgr, I right-clicked Sites, and created a new website called NihiWebSite. Then I repeated all the steps above where I created a new virtual under NihiWebSite, and converted the virtual to an application. But in IIS Mgr, when I select nihiweb under the NihiWebSite, right-click on Default.aspx, and click Browse, all of my AJAX-type controls do not respond to user interaction. It's like they are frozen.
I am having trouble finding the cause of this problem. I have compared all the property settings between DefaultWebSite and NihiWebSite. I have compared the application properties for nihiweb under DefaultWebsite vs. nihiweb under NihiWebSite. I've made sure that the app pools are compatible. I've used Win Explorer to compare user and permissions between C:\inetpub\wwwroot\nihi and C:\Website\nihi.
Does anybody have a checklist that I can follow to try to determine what is wrong with my new website and web app settings? Please, any suggestions?
Thank you
On the Win 2008 server, I first created the subfolder C:\inetpub\wwwroot\nihi. The files and folders that makeup the website were copied from the Win 7 machine to the Win 2008 nihi subfolder. Then in IIS7 Manager (Win 2008), I right-clicked on DefaultWebSite, and clicked "Add Virtural Directory", creating a virtual that points to C:\inetpub\wwwroot\nihi. The name I gave the virtual was nihiweb. Next in IIS Mgr, I right-clicked on the nihiweb virtual, and clicked "Convert to Application". While in IIS Mgr, I switched to "Content View", selected nihiweb in the left-hand pane, then right-clicked on Default.aspx, and clicked Browse. This launched IE and allowed me to successfully view and navigate thru the website.
But it is not desirable for me to have nihiweb under DefaultWebSite. So in Windows Explorer (of the same Win 2008 server), I created C:\Website\nihi. I copied all the files and folders from the Win 7 machine over to C:\Website\nihi. Then in IIS Mgr, I right-clicked Sites, and created a new website called NihiWebSite. Then I repeated all the steps above where I created a new virtual under NihiWebSite, and converted the virtual to an application. But in IIS Mgr, when I select nihiweb under the NihiWebSite, right-click on Default.aspx, and click Browse, all of my AJAX-type controls do not respond to user interaction. It's like they are frozen.
I am having trouble finding the cause of this problem. I have compared all the property settings between DefaultWebSite and NihiWebSite. I have compared the application properties for nihiweb under DefaultWebsite vs. nihiweb under NihiWebSite. I've made sure that the app pools are compatible. I've used Win Explorer to compare user and permissions between C:\inetpub\wwwroot\nihi and C:\Website\nihi.
Does anybody have a checklist that I can follow to try to determine what is wrong with my new website and web app settings? Please, any suggestions?
Thank you
Kyle Abrahams, PMP
You shouldn't need to create a virtual directory under the Nihi website. You should just be able to browse. also make sure you have all of your isapi filters enabled.
Hi,
You have also not mentioned anything about "host header values", what name are you trying to run this under?
GH
You have also not mentioned anything about "host header values", what name are you trying to run this under?
GH
ASKER
OK, so I did away with nihiweb located under the nihiwebsite and I now have the nihiwebsite pointing directly at my web app (I have assigned a host header). But my result is the same; all ajaxified controls are non-responsive.
I have standard ASP.NET controls on the web pages, such as dropdownlist, and command buttons, and they all function fine. But any ajax controls do not respond to user input / interaction.
So what about these isapi filters? Isn't an "installed" filter the same as an "enabled" filter? In IIS mgr at least, I don't see where to go about enabling / disabling an isapi filter.
I have standard ASP.NET controls on the web pages, such as dropdownlist, and command buttons, and they all function fine. But any ajax controls do not respond to user input / interaction.
So what about these isapi filters? Isn't an "installed" filter the same as an "enabled" filter? In IIS mgr at least, I don't see where to go about enabling / disabling an isapi filter.
Can you check the logfiles for the new site, and see if the Server part of the ajax is actually being called (and returns 200)..
GH
GH
ASKER
this problem seems to only occur when browsing the site from the same server that is hosting IIS. The problem does not occur when accessing the site from the internet (and I think this is true from other machines within the intranet, but haven't fully tested that).
are you browsing using localhost?
What if you hit the website from the server using the full website name?
What if you hit the website from the server using the full website name?
ASKER
same problem when using localhost or the Internet URL.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
h