« Previous Next »

• 02-24-2009, 8:56 AM

  Rene Olesen Joined on 02-24-2009, 1:24 PM Posts 4

  Problems after migrating with msdeploy beta 2 Reply Contact After migrating our IIS 6.0 to IIS 7.0 using msdeploy, we experience some problems. I used msdeploy to generate configurationsfiles without contentfiles. These files I coppied to the new 2008 server, and used msdeploy to import to IIS 7. At first it didn't work, because I had to rename usernames in the config file. Especially IUSR had to be renamed to be computer independent. I also renamed IWAM and NetworkService user to not include old computername. Afterwards everything seems to be running fine, but eventlog is full of warnings and errors. Warnings: "The directory specified for caching compressed content C:\Windows\IIS Temporary Compressed Files\XXX is invalid.  Static compression is being disabled." 1.1 Is this related to wrong usersettings since IIS can't created these folders? 1.2 Is it ok to change this path in applicationHost.config without using appcmd, and which user should have access to the new folder for this to work? We like to move these folder to another harddisk. Errors: "Error: The Template Persistent Cache initialization failed for Application Pool 'XXX' because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes.." (I can't find additional error codes!) 2.1 What is this error about? 2.2 Is these cache directories required and can they be moved away from c:\? We do not have dynamic compression enabled if this has something to do with that... Applicationpool editing results in an error: Trying to change default settings for application pools results in a message "The specified user name does not exist." I can avoid this error by clicking the Identity section and select NetworkService user before clicking to OK button. Before selecting the Identity it already says NetworkService, so to the eye there is no differens. 3. How can I change this for good, so all pools uses the correct NetworkService user? 4. Is all of these errors related to msdeploy importing to many settings from the old server? My experiense was that I had to delete some settings in the config file in order for msdeploy not to import the whole IIS. I only needed it to import the sites, not all the basic settings which aren't all IIS 7 compatible. Hope some wise person can put some light on these issues for me ':)

• 04-10-2009, 5:17 PM

  In reply to

  faith_a Joined on 06-02-2004, 8:40 PM Posts 109

  Re: Problems after migrating with msdeploy beta 2 Reply Contact Hi Rene, #1 we will investigate and see what is going on. #2 I also need to investigate as I'm not sure about the error. #3 is a known issue with migrating passwords, it's adding a password in config for the Network Service account and the IIS Manager UI is complaining that there's a password for a built-in account. You can remove these in config directly, I'm checking to see if there's any other option. #4 certainly seems like some of these are MS Deploy syncing stuff from IIS6. To import only the sites, you can create a custom manifest.xml containing all of them... I can give you steps if you want. It would be really interesting if you tried this again with RC1 that recently shipped...  thanks, -faith This posting is provided "AS IS" with no warranties, and confers no rights.

• 04-14-2009, 3:53 AM

  In reply to

  Rene Olesen Joined on 02-24-2009, 1:24 PM Posts 4

  Re: Problems after migrating with msdeploy beta 2 Reply Contact Hi faith_a Thank you very much for your reply, I already forgot I did make this post... ':) #1 and #2 I managed to solve by editing applicationHost.config manually. I changed the folder to another partition and gave these folders modify-access for IIS_IUSRS. #3 This issue is also gone. I just edited all apppools manually and selecting the right network user again before saving. I needed to do this once per apppool. In the beginning I just got confused because I was sertain that I already had done this for some of the folders with the error. But now every pool is ok, so it must have been me being to confused... I'm sorry but trying RC1 will not be an option for us, because the servers are now running fine. So starting from scratch again would be rather foolish ':) Regards René Olesen

• 07-13-2009, 11:42 AM

  In reply to

  davidbranka@yahoo.com Joined on 07-13-2009, 2:35 PM Posts 2

  Re: Problems after migrating with msdeploy beta 2 Reply Contact I am trying this same migration but without the same success. I get the following error when I try to modify the bindings and logfile locations of teh sites that were migrated.  \\?\C:\Windows\system32\inetserv\config\applicationHost.config Error: Command I used for msdeploy  msdeploy -verb:migrate -source:metakey=lm/w3svc,computername=Knet.test.local -dest:metakey=lm/w3svc > msdeploysync.log  I can see the annonymous user is the old server IUSR account but not sure what to change that too.

• 07-14-2009, 2:42 AM

  In reply to

  Rene Olesen Joined on 02-24-2009, 1:24 PM Posts 4

  Re: Problems after migrating with msdeploy beta 2 Reply Contact Hi David I'm not sure what your error is about. But as I wrote in my first post, I did manually rename computername_IUSR to IUSR in the xml-files that msdeploy generated. I did this before importing them to the new server. Now after several months of operation, I can add that the server never came up running like a charm! For some reason the servers had a connection limit of 200 concurrent connections. We never found out why or where to remove this limit. Even a support case with Microsoft porfessional support could not help us. So we are right now trashing these servers and starting from all over with new installations. I'm not blaming msdeploy, but just saying that if msdeploy is still in beta - I would take their advice and NOT use it for productions servers. Regards René Olesen

• 07-14-2009, 12:16 PM

  In reply to

  moshaikh Joined on 11-14-2008, 12:21 AM Posts 154

  Re: Problems after migrating with msdeploy beta 2 Reply Contact MSDeploy has an RC version out already here and we will be releasing RTW version soon. Can you let us know what is the issue that you are facing as regards to 200 concurrent connections? If the computername_IUSR is the default value then migrate should smartly move it to the new server when you carry a migration. If it is not or there is something else that you wish to do, let us know. Thanks

• 07-15-2009, 4:36 AM

  In reply to

  Rene Olesen Joined on 02-24-2009, 1:24 PM Posts 4

  Re: Problems after migrating with msdeploy beta 2 Reply Contact Hi Moshaikh I'm sorry if my earlier reply sounded as if I blaime msdeploy. Actually we dont know what went wrong, or where the "error"/limit is. But our first try to get support for the issue was denied because we have used beta software. We started a new case with the focus on the 200 limit, and then the case was accepted, but never solved. My best guess is that is was an issue with httpsys or below that (deeper in the system). When the server did get to the 200 connections, everything sloved down or stopped working. Even Surv-U ftp server, smtp service and remote desktop. We've searched the internet and did found a lot of places to try tweeking, but none worked. We tried moving the server to a virtual environment, making it independed of it's drivers - but it didn't help either. So we've now stoped searching for any sollution, and just started migrating the iis to new servers. In this process we can actually use IIS7's build in export functionallity, and it works like a charm ';) Regards René Olesen

• 07-15-2009, 12:02 PM

  In reply to

  davidbranka@yahoo.com Joined on 07-13-2009, 2:35 PM Posts 2	Re: Problems after migrating with msdeploy beta 2 Reply Contact I used the RC version of MSDeploy for my migration.  I may end up making the sites manually on the new server.  I can't afford to spend days making msdeploy do what I want it to do.

• 07-15-2009, 4:00 PM

  In reply to

  faith_a Joined on 06-02-2004, 8:40 PM Posts 109

  Re: Problems after migrating with msdeploy beta 2 Reply Contact Hi David, I'm very sorry to hear about the error and that your experience has been so poor. We would really like to help if we can. Was there any additional information in the error message or does it just return that line about the applicationHost.config? Is there anything in the event viewer after you see this error? Thanks, -faith This posting is provided "AS IS" with no warranties, and confers no rights.