« Previous Next »

• 09-17-2009, 6:14 AM

  darianva Joined on 10-09-2008, 9:48 AM Posts 31

  IIS Shared Config. There was an error while saving settings joing server to the config Reply Contact Hi All, I thought that I had all my issues with my shared config resolved earlier in the week, when in fact I was back to square 1! The initial issues I had was a result of copying my applicationhost.config from server to shared config, which resulted in the encryption getting broken. The symptoms I had was that I was not able to edit the credentials of app pools, or IIS VDirs or IIS applications directories.  Other symptoms were that session state was not working. However I updated the key values and all servers were working independantly out of the shared config. (doc http://blogs.iis.net/webtopics/archive/2009/03/15/caution-while-xcopying-iis-7-0-config-files.aspx descibes the error I was getting when editing app pools etc and I followed the steps to resolve the encryption) So I thought I was all good creating my new shared config....NO! I could export the data from the server (01), but could not join the shared cluster. I decided to export the config from another server (02) which worked fine. I was then able to join the shared config for this server and the remaining servers in the cluster, except server 01......Tried unistalling and reinstalling the IIS role did not help. Then I found this doc https://forums.iis.net/t/1154548.aspx which decribes that WAS needs to be removed as a feature, and I did that and uninstalled IIS and deleted the IIS and WAS keys from C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys these keys are the same for IIS servers....they begin with 76944fb33636aeddb9590521c2e8815a for WAS and 6de9cb26d2b98c01ec4e9e8b34824aa2 for IIS. So after deleting them, I reinstalled IIS role and WAS and it joined the shared config! That is when I thought I was out of the woods and all good, but in fact I was back to square 1 as I was no longer to update app pools etc with the bad data error :( I proceeded to pull all servers back out the shared config, and update their local apphost.configs with the correct sessionkeys for AES and IIS. Again as 4 individual IIS servers I was able to edit the app pools, and everything was working as expected. Now here is the very very funny thing, Server 01 and 02 (both originally used as the first server in the shared config, and the server where the config was previous exported from) could not join the shared config.....if you recall from above it was server 01, now server 01 and 02. The error is from these servers is There was an error while saving settings. I proceeded to export the config from server 03 and join server 03 to the shared config. verified all was working. proceeded to the next server, verified that all was working and everything was. I then tried to join server 01 or 02 to the shared config to get the error There was an error while saving settings, however after a few attempts server 01 did join...weird! Server 02 however has not joined again. Sorry for such a long post, but I had to include all the details. Anyone have experience of the above, and there are no server events logs to help! Thanks Darian

• 09-17-2009, 6:24 AM

  In reply to

  darianva Joined on 10-09-2008, 9:48 AM Posts 31

  Re: IIS Shared Config. There was an error while saving settings joing server to the config Reply Contact Sorry just to add this appendix to my post (also for Steve Schofield) is that another symptom of my original issue was that I was not able to edit an IIS dir/VDIR to render content over a UNC connection. When trying to save the VDIR with the UNC path and the domain\user details with the password I was presented with the Bad Data error. It was this Bad Data error that helped me find the doc http://blogs.iis.net/webtopics/archive/2009/03/15/caution-while-xcopying-iis-7-0-config-files.aspx Steve (and All) I hope this helps as I feel there are probably many more issues that will be a result of the corrupted key in the applicationhost.config file!