The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 05 Dec 08 12:36 PM
|
Is there some magical trick to deploy a portal to a site with host headers? The only way I've been able to successfully deploy a port is to make sure there isn't a single host header assigned to that website in IIS. If I want to use host headers I have to first remove them completely, deploy the portal, then add them back.
Surely there's an easier way, though Sage support says there isn't...
Has anyone else seen this and/or have a different option?
|
|
|
| |
|
Re: Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 05 Dec 08 3:35 PM
|
The problem is with deployment itself. I get either "Access denied" or "Unable to find host" or "can't convert system.object[] to system.string" depending on which value I use for the portal server value. (FQDN, machine name, host header, IP).
As soon I remove the host headers from IIS for that website and deploy to the machine name - BAM - works like a champ.
|
|
|
|
Re: Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 05 Dec 08 3:41 PM
|
| Does it looks like it deploys everything OK but then just fails at the end when it attempts to configure IIS? I have seen that on occasion (not directly related to host headers though), but if that is the case it can be ignored as long as IIS has been configured at some point (either by AA or manually) and the site should still work fine. Have you tried accessing it after the error to see if it is working anyway? |
|
|
|
Re: Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 05 Dec 08 3:50 PM
|
With one host header on the IIS site (port 80 / assigned to slx.domain.com only) I get the follow errors when deploying to the IIS machine, (while on the IIS machine, incidentally)
(It repeats for all portals, I just selected processHost for this example)
[code]
INFO - Writing target Manifest for portal ProcessHost
INFO - Beginning site precompilation for ProcessHost
INFO - Building directory '/ProcessHost/App_GlobalResources/'.
INFO - Using inherited target port and app pool settings
INFO - Configuring IIS Directory for ProcessHost
ERROR - Could not configure IIS Server for Portal ProcessHost. The web server slx-web:80 could not be located
ERROR - Exception was thrown when setting up target. Message is Failed to configure IIS Server
ERROR - One or more of the targets failed for portal 'ProcessHost' to configure successfully. Please review deployment settings and try to deploy the portal again.
ERROR - Deployment has completed but Errors have occurred. Please review and if required change the configuration and re-deploy.
[/code]
|
|
|
| |
| |
|
Re: Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 06 Dec 08 7:57 AM
|
Its is using the IIS Metabase to locate the server as specified in the target settings. Since it cannot find it it is incapable of configuring the IIS settings. The actual deployment to the filesystem is still valid, and since you have altered the IIS configuration for your portal, you more then likely would not like the settings overwritten by the simpler configuration provided by the Deployment engine. So as Ryan states you should be more then fine.
I am also curious with the title to the forum post, is deployment blowing up or simply stating that it cannot perform a step 
Mark
|
|
|
|
Re: Deploying 7.5 portal to IIS website with host headers blows up...
Posted: 08 Dec 08 11:35 AM
|
[quote]I am also curious with the title to the forum post, is deployment blowing up or simply stating that it cannot perform a step[/quote]
Aren't these the same? 
I mean, who wants a half deployed portal?
(Perhaps I was exaggerating a tiny bit....)
Edit: Apparently I don't know the tags for this board.... |
|
|
|