THIS DOCUMENT IS NO LONGER RELEVANT IN RELEASE 1.2.1
How To Run Hosted Solution Services with WebsitePanel v1.2.0
The WebsitePanel v1.2.0 codebase has been migrated to .NET 4.0. The problem some users may face is that certain Enterprise-level modules (eq. Hosted SharePoint, Exchange 2010 and etc.) do not support .NET 4.0 runtime
and thus they might be unable to use these services in the environment if it has been upgraded to v1.2.0. To avoid this problem we propose a workaround that gives you ability to continue to use Enterprise-level modules with v1.2.0.
Here is some background information for your convenience on how the workaround delivers the desired solution in a WebsitePanel environment to give you an idea how it actually works.
So there is a software WSE SOAP Router that decides which incoming SOAP messages (based on the target ASMX service name) route to *:9004 instance for processing or continue with *:9003 instance as by default. Routing schema is defined in referralCache.config
file that gives WSE SOAP Router mapping clues to apply to all incoming messages.
This workaround enabling process is almost automated via a PowerShell (PS) script but one of its parts (static route map configuration) should be done manually if your environment settings are different than in the scenario described.
(!!) First of all, please make a backup of WebsitePanel Server component’s folder on the target server to ensure you can revert the changes back if necessary.
Then download all packages attached. Here are links and brief description of these packages:
- Hosted Solution v3.5.zip (binaries compatible with .NET 2.0/3.5 runtime and referralCache.config)
- Setup WSP Ent Services.ps1 (PowerShell script performing all the job)
- Setup WSP Ent Services Cleanup.ps1 (PowerShell script performing cleanup and should be run in case if you would like to revert everything done
by “Setup WSP Ent Services.ps1” script to its original state)
Once downloaded, extract all the content from the archives and ensure you unblocked these .ps1 files downloaded. Otherwise you will not be able to run these scripts at all as operating system will block execute attempts to prevent any harm that files without
a digital signature could potentially do for your computer.
Open “Setup WSP Ent Services.ps1” in Notepad to validate whether default script settings correspond to your environment’s configuration (highlighted lines), eq. path to folders, site names, port number and etc. If you find some settings
do not correlate with your settings, please feel free to change it as appropriate.
Then launch PS console on the server and navigate to the folder where Hosted Solution v3.5.zip’s content has been extracted via PS.
Once you are there, execute the following cmdlet to allow run unsigned scripts in the current PS session:
Set-ExecutionPolicy RemoteSigned –Force
Then type Setup and press TAB key so PS could infer the script name for you instead of typing it. Ensure the script name is correct and then press ENTER to run the script.
You will be prompted by the script to provide a location of the extracted content of
Hosted Solution v3.5.zip archive you downloaded previously.
Below is the sample output in the console after running the script on a demo environment:
Once the script has finished its work, open Internet Information Services Manager console, navigate to “WebsitePanel Server (Hosted Solution)” site. Bindings for that site are copied from the original site (eq. “WebsitePanel Server”)
with the only difference in port number (9004 instead of 9003).
Then click “Browse” button to validate that the site is up and running.
Last and the final step you should validate that
referralCache.config file routing map corresponds to your environment’s configuration. Below is a sample screenshot of routing map settings by default.
So, for example you need to change that default routing map described in referralCache.config should be changed to correspond to your environment’s settings. Eq. components are running on 10.1.2.34 instead of 127.0.0.1.
To do this, you can simply run “Replace” command on the file to replace 127.0.0.1 with 10.1.2.34, like on the picture below.
Once you have done with adjusting the routing map, save your changes and then go to WebsitePanel and validate whether this workaround did the trick by following the scenario that previously failed to complete.
In case of any issues, you should want to run “Setup WSP Ent Services Cleanup.ps1” script to cleanup all the changes made by “Setup WSP Ent Services.ps1” script.
Or you may also to contact us at any time for your convenience and we will do our best to help you solve the issue.