In WFF 2.0, 32 bit msi's were not getting installed because they were getting downloaded in C:\Windows\Sytem32 and because of syswow redirection WebPI was not able to find the file. Starting WFF 2.1, we started loading the user profile on start which is
causing issues for you. Please let me know the results.
Thanks,
I finally got some time to revisit this. I've disabled UAC and I'm still seing the same issue. I also tried making the setup simpler by setting up TestWebApp1 as the controller AND primary machine. Adding the Primary server to the farm fails because of
this "required privilege is not held by the client" error, even though the primary is the same box as the controller.
I have setup the web farm to use an AD service account that belongs to the administrator group on all machines. I have not touched the Web Farm Framework services at all (haven't changed the "Run as" accounts or anything).
What permissions are needed by what accounts on what machines? I've reviewed everything in the setup posts (here and
here), and I'm not seeing anything that we haven't gotten configured. Perhaps those posts need updating for 2.1, but as they stand now, I'm not seeing anything we haven't done.
We tested this on a clean Windows Server 2008 R2 installation on a separate machine. Totally clean slate. Nothing installed but the prerequisites for WFF. Used the Web Platform Installer to drop in the recommended IIS configuration, etc.
Added WFF 2.1 to the new machine. Set the same machine as the primary on a brand new web farm, and it failed with the same message.
Web Farm Framework 2.1 is broken. End of story. I don't think I've ever used a Microsoft product that was this poorly documented, tested before release, and supported after release. That includes a number of beta products. This is disappointing to say the
least.
This is a fantastic concept with poor execution. I'll be back when the IIS team has demonstrated that this is a serious product with real documentation and support.
I really have to agree, even with v2.2 I'm installing it in a test environment. (2) cleanly installed servers, followed the installation instructions to the letter, even opened up completely clear access between the two machines on the firewall and still had
nothing but continuous failures. 502 web errors, unable to run "autorepair", unable to install additional products on the second server. I actually never saw my test web (just a single simple default.htm file), just 404 and 502 errors. I, too, am having a
really hard time finding documentation on the product and ARR. I've had nothing but good luck with Microsoft products, but WFF has been exceedingly frustrating.
Yeah, there are a number of problems. We have removed servers from farms, and though they werent listed in the applicationhost.config file anymore,nor were they shown in the interface, they were still deployed to. Best practice is to restart the webfarm
service whenever your remove a server from a farm.
Things like that. But the sync engine itself works well, if you can live with having to be so careful with it, and dont use any of the other "features".
Update: I completed the installation, and the servers seem to be running OK at this point. I did have a few issues with the installation as well as the hostablecore service running afoul on one of the secondary servers, but it looks like it's up and running
for now.
jcgillespie
23 Posts
Re: Multiple WFF 2.1 installation problems
Sep 01, 2011 03:23 PM|LINK
I finally got some time to revisit this. I've disabled UAC and I'm still seing the same issue. I also tried making the setup simpler by setting up TestWebApp1 as the controller AND primary machine. Adding the Primary server to the farm fails because of this "required privilege is not held by the client" error, even though the primary is the same box as the controller.
I have setup the web farm to use an AD service account that belongs to the administrator group on all machines. I have not touched the Web Farm Framework services at all (haven't changed the "Run as" accounts or anything).
What permissions are needed by what accounts on what machines? I've reviewed everything in the setup posts (here and here), and I'm not seeing anything that we haven't gotten configured. Perhaps those posts need updating for 2.1, but as they stand now, I'm not seeing anything we haven't done.
Thanks,
Josh
jcgillespie
23 Posts
Re: Multiple WFF 2.1 installation problems
Sep 06, 2011 02:37 PM|LINK
We tested this on a clean Windows Server 2008 R2 installation on a separate machine. Totally clean slate. Nothing installed but the prerequisites for WFF. Used the Web Platform Installer to drop in the recommended IIS configuration, etc.
Added WFF 2.1 to the new machine. Set the same machine as the primary on a brand new web farm, and it failed with the same message.
Web Farm Framework 2.1 is broken. End of story. I don't think I've ever used a Microsoft product that was this poorly documented, tested before release, and supported after release. That includes a number of beta products. This is disappointing to say the least.
This is a fantastic concept with poor execution. I'll be back when the IIS team has demonstrated that this is a serious product with real documentation and support.
talldaniel
93 Posts
Re: Multiple WFF 2.1 installation problems
Mar 09, 2012 01:12 AM|LINK
jajanes
2 Posts
Re: Multiple WFF 2.1 installation problems
Aug 10, 2012 05:00 PM|LINK
talldaniel
93 Posts
Re: Multiple WFF 2.1 installation problems
Aug 10, 2012 10:23 PM|LINK
Yeah, there are a number of problems. We have removed servers from farms, and though they werent listed in the applicationhost.config file anymore,nor were they shown in the interface, they were still deployed to. Best practice is to restart the webfarm service whenever your remove a server from a farm.
Things like that. But the sync engine itself works well, if you can live with having to be so careful with it, and dont use any of the other "features".
jajanes
2 Posts
Re: Multiple WFF 2.1 installation problems
Aug 13, 2012 07:52 PM|LINK