This morning I’m putting together a distributed UDDI 3.0 environment on a active-passive SQL cluster for a client. The steps are pretty simple and outlined in the documentation found here. Basically,
- Install the UDDI 3.0 “Database Component” only on the passive SQL cluster node
- Install the UDDI 3.0 “Database Component” only on the active SQL cluster node
- Install the UDDI 3.0 “Web Component” and “Administrative Tools” on each Web Server
The only hiccup I had was with WAS not being fully configured. This resulted in the UDDI configuration wizard on the web server throwing an error as below,
Could not load file or assembly ‘Microsoft.Web.Administration, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified
To remedy this follow the below instructions which were taken from here,
This is due to an incomplete installation of the Windows Activation Service (WAS). Ensure that all components of WAS are installed prior to running ServiceModelReg.exe. To do so, complete the following steps:
- Open the “Turn Windows Features On or Off” dialog by clicking Start -> Control Panel -> Programs and clicking the “Turn Windows Features On or Off link.”
- In the tree view, select the “Windows Activation Service” checkbox.
- Expand the “Windows Activation Service” checkbox and ensure the following sub-components are also selected:
– .NET Environment
– Configuration APIs
– Process Model
- Click “OK” and wait for the components to finish installing.
- Re-run ServiceModelReg.exe to register the WCF activation components with WAS.
These steps will install the minimal set of components required to support WCF service activation over non-HTTP protocols.
Now run the UDDI configuration wizard again. i.e. You MUST shut the wizard down and start again. Just ticking the Launch Configuration checkbox on the finish screen of the configuration wizard and clicking through will fail.