So, ran into several issues trying to get the Portal installed – keep in mind I'm exercising installation options that few use but ones I tend to prefer when deploying our solutions. Let's start with host headers.
Back in RC0 I posted a bug where the installer would fail if a host header was used in WSS. While it was closed "as fixed", it still seems to be an issue if you try and install the portal when the default site collection is running under a host header:
Taking a look at the installation log reveals what looks like hardcoded addresses still:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CheckSharepointWebApporSiteExisting, location: C:\Users\bturner\AppData\Local\Temp\2\MSI3F65.tmp, command: action=IsDefaultWebApplicationOrSiteExisted absoluteURL="http://localhost"
MSI (c) (C4:E8) [15:19:58:400]: Product: Forefront Identity Manager Service and Portal -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CheckSharepointWebApporSiteExisting, location: C:\Users\bturner\AppData\Local\Temp\2\MSI3F65.tmp, command: action=IsDefaultWebApplicationOrSiteExisted absoluteURL=http://localhost
I've done my best to override everything both in the GUI and using the MSI parameters so I know I'm not passing "localhost" anywhere. Backtracking further and removing all of the host headers I can get a bit further now but then run into this one next:
This appears to be linked to an inability to validate the FIM Service account during the installation, resetting the password seems to have resolved this issue for me. I was able to eventually complete the install, and like I said, I chalk much of this up to my incessant tinkering. There was one other error I'd like to see corrected where the installer detects that the WSP solution file has already been deployed and it instructs you to go remove it while it waits for you – not a great experience.
2 comments:
Brad,
I'm currently deploying a two node NLB setup (FIM portal&service), and I have configured a WSS 3.0 farm. Now when installing the FIM bits on the second node I get the error you referenced to:
There was one other error I'd like to see corrected where the installer detects that the WSP solution file has already been deployed and it instructs you to go remove it while it waits for you – not a great experience.
It makes sense as IIS/Sharepoint wise, sharpoint does it magic. But the FIM setup fail on it...
My question on technet (no answser yet...):http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/4871187f-d012-4cc6-800b-bde8d02a0431
Any thoughts on this subject?
Make sure that when you install FIM Portal & Service on the second node that you *only* select Service and not either of the Portal options. Once you install FIM Portal into the farm, it is replicated to all members so you don't have to install it again. What I would like to see happen is the installer detect this condition and skip the solution load.
You will need to check the Central Admin site and look at the Operations/Solution Management page. You should see:
ilmpasswordportal.wsp - Deployed
microsoftidentitymanagement.wsp - Deployed
microsoftilmportalcommondlls.wsp - Deployed
You may not have deployed the Password Portal, but if the others are not Deployed then you'll want to click the hyperlink for each solution and then click the "Retract Solution" hyperlink and try and reinstall.
Post a Comment