I am running a web server recently upgraded from Windows Server 2003 to Windows Server 2008. All my virtual server's (websites) are now working, but only using the Classic pipeline. I can't serve web pages using the Integrated pipeline. In order to take advantage of IIS 7.0's Integrated pipeline I was told that I should uninstall IIS 7 and Windows Process Activation Service, reinstall IIS 7.0 and deploy my sites using MSDeploy. After doing so, I'm supposed to be able to choose between Integrated and Classic.
Based on instructions found in the 'Migrating from IIS 6.0 to 7.00 using MS Deploy' article, I wanted to use AppCmd to "make a backup of the destination server."
I hadn't used AppCmd before so I ran AppCmd /? and saw instructions for use and the list of objects/command/parameters. Having done this I knew appcmd existed at the path I ran and that it was working.
I was instructed to use the 'add' command and the 'backup' object and name the backup "PreMSDeploy". I ran the following:
c:\Windows\System32\inetsrv\appcmd add backup "PreMSDeploy"
I got an error message which stated:
ERROR < hresult:80070003, message:Command execution failed. The system cannot find the path specified.>
I tried to run:
c:\Windows\System32\Inetsrv\appcmd list apppool
and got the following error message:
ERROR < hresult:8007007e, message:Command execution failed. The specified module could not be found.>
At this point I'm wondering if I should even attempt to take the above steps to get the Integrated Pipeline working. I should probably get AppCmd working first.
What do you think?