Your independent source for application and desktop virtualization.
Sign in
|
Join
Topics
Blogs
Forums
Videos
Podcast
Books
BriForum
See Us Live!
About Us
Discussion Forums
»
Tech Support Forums
»
Citrix Web Interface
»
WI 4.5 with IIS6 and multiple sites
WI 4.5 with IIS6 and multiple sites, in the Citrix Web Interface forum on BrianMadden.com
rated by 0 users
This post has 12 Replies | 0 Followers
Points 500
Reply
Kimber Conners
Posted: Wed, May 9 2007 10:33 AM
rated by 0 users
Though this documentation is older, I followed it for creating another WI site:
http://www.brianmadden.com/content/article/How-to-Run-Multiple-Unique-Web-Interface-Sites-Using-WI-30
My server was upgraded from WI 4.0 to 4.5 (w2k3 server) and I'm testing the creation of another site on my test server and I'm now getting this error when trying to browse to the new site created. I'm not very proficient with IIS.. can anyone help?
Server Error in '/Citrix/MetaFrame' Application.
--------------------------------------------------------------------------------
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized configuration section 'httpCookies'
Source Error:
Line 18:
Line 19:
Line 20:
Line 21:
Line 22: buffer="true"
Source File: M:\Inetpub\wwwroot\WI2\Citrix\MetaFrame\web.config Line: 20
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2379; ASP.NET Version:1.1.4322.2379
Thanks in advance!
KC-Tek
| Post Points: 20
Points 88,190
Reply
Jeff Pitsch
replied on
Wed, May 9 2007 11:33 AM
rated by 0 users
Ok first off read teh documentation that comes with the WI admin guide. You have followed the wrong directions. WI4 and WI4.5 have built-in mechanism's for creating multiple sites. There is a reason that article says for WI3.0.
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Wed, May 9 2007 12:34 PM
rated by 0 users
The first place I looked was in the WI Admin guide for 4.5.. I didn't see anything for multiple site configuration, just stated it was capable through the ASC. I check in 4.0 and there weren't any 'how to's' either.
I have gone in and clicked through the wizard to create the second site, but I'm giving it a completely different dns name and when I tried configuring it, I'd would not see the changes on my new page. In addition, both sites defaulted to the same http://serverip/Citrix/AccessPlatform id when viewing through the ASC.
What am I missing?
KC-Tek
| Post Points: 20
Points 88,190
Reply
Jeff Pitsch
replied on
Wed, May 9 2007 1:35 PM
rated by 0 users
I would start completely over. Uninstall both WI and IIS. You've got remnants that are interferring with WI from doing its job.
What do you mean you gave it a different DNS name? Have you configured IIS to handle multiple DNS names and multiple websites?
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Wed, May 9 2007 2:00 PM
rated by 0 users
I'll try that. What I mean by different DNS names is the first site is a normal, http://servername/citrix/metaframe address and the second site I need to setup as: http://citrixtest.domain.com. Make sense?
KC-Tek
| Post Points: 20
Points 88,190
Reply
Jeff Pitsch
replied on
Thu, May 10 2007 11:30 AM
rated by 0 users
Now I'm no expert on IIS but simply telling WI that you want to use a different dNS name is not how to get it done. That's an IIS function. I'm positive on that. well as positive as a nonexpert can be :)
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Fri, May 11 2007 10:28 AM
rated by 0 users
That's why I thought the article above would be a closer description to what I need to do. I know this is possible but can anyone point me to a 'how to' article or blog?
KC-Tek
| Post Points: 20
Points 2,139
Reply
Kevin Stewart
replied on
Fri, May 11 2007 10:51 AM
rated by 0 users
If you're going to setup multiple websites on a single IIS box, with different DNS names, you can enter "Host Header Name" information for each site. IIS will only send traffic to that site if the dns name your requesting data from matches that set in the Host Header Name field (ie. using an IP address in the browser would not get you to the site.)
To enter Host Header Name information, goto the properties of the website in IIS. On the Web Site tab, next to IP Address, click the Advanced button. Select the IP address, click Edit, and enter a Host Header Name.
Kevin
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Fri, May 11 2007 1:40 PM
rated by 0 users
Thanks Kevin! How will the WI site associate this separate address with the new site? Is this part impossible?
KC-Tek
| Post Points: 20
Points 88,190
Reply
Jeff Pitsch
replied on
Fri, May 11 2007 1:54 PM
rated by 0 users
WI doesn't, IIS does. What you'd do is create a new site into the new IIS website you created following Kevin's instructions.
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Thu, May 17 2007 9:49 AM
rated by 0 users
OK, Uninstalled IIS and WI 4.5. Re-installed both and created first site as normal. For 2nd site, I went into IIS, created a new website and entered the Host Header value with the new 2nd site name (citrixtest.ppdi.com). When I went back into the Access Suite console, I was able to select the new site from the drop down that normally says "Default". The path was correct and it's even showing up under WI configs with the correct name and directory path. But I'm still getting the same error listed in my first post.
It's referencing the web.config file Line 20
I do see the 'click here if you are not redirected' before I get this configuration error page.
Any other suggestions on where to look or how to correct this?
Thanks!
KC-Tek
| Post Points: 20
Points 2,139
Reply
Kevin Stewart
replied on
Thu, May 17 2007 3:39 PM
rated by 0 users
That web.config should be there, so not sure why its flagging as an error. Can you make sure that ASP.NET is set to version 2.0 under the AccessPlatform node in the IIS configuration of each web site. This may be a 2.0 specific web.config entry and 1.1 is choking on it. Also can you verify that you are in fact going to the different sites?
Kevin
| Post Points: 20
Points 500
Reply
Kimber Conners
replied on
Fri, May 18 2007 7:34 AM
rated by 0 users
Kevin, you are AWESOME!! That was it, I assumed that because ASP.NET 2.0 was installed that it would default to the lastest version. I had to select to use it within the properties of the site. It's working now! Thanks a bunch!!
KC-Tek
| Post Points: 5
Previous
|
Next
Page 1 of 1 (13 items) |
RSS
Copyright © 1997-2012 TechTarget |
Disclosures
|
Privacy Policy
|
Contact Info
BrianMadden.com
|
SearchVirtualDesktop.com
|
SearchEnterpriseDesktop.com
|
SearchServerVirtualization.com
|
SearchVMware.com