Previous Next

Thread: migration from IIs6 to IIs 7 problems

Last post 06-24-2008 3:54 PM by monkeyhouse. 0 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (1 items)

Sort Posts:

  • 06-24-2008, 3:54 PM

    migration from IIs6 to IIs 7 problems

    I am trying to pull one site from IIs 6(server 2003) to a new machine, server 2008(IIs 7). I have installed the migration utility, but get some errors that I don't quite understand. I created an archive of the site from the old source(old) server and copied it to the destination(new) server. Here is what I am trying to run and what I am receiving.

     

    C:\Program Files\Microsoft Web Deploy>msdeploy -verb:migrate -source:archivedir=
    c:\archive -dest:metakey=lm/w3svc/2
    Error: The InUseDependency dependency check detected FrontPageServerExtensions i
    n use in the source data but the msdeploy tool does not support configuring it o
    n the destination machine.
    Error: The InUseDependency or IsapiCgiExistence dependency check detected AspNet
    1.1 in the source data but not installed on the destination server.
    Fatal: The dependency check 'InUseDependency' found issues up to 'Error' level t
    hat must be resolved before the current operation can be processed.  See previou
    s messages.
    Error: The InUseDependency or IsapiCgiExistence dependency check detected C:\Per
    l\bin\PerlEx30.dll in the source data but not installed on the destination serve
    r.
    Error: The InUseDependency or IsapiCgiExistence dependency check detected C:\Per
    l\bin\perlis.dll in the source data but not installed on the destination server.

    Error: The InUseDependency or IsapiCgiExistence dependency check detected C:\WIN
    DOWS\system32\inetsrv\httpodbc.dll in the source data but not installed on the d
    estination server.
    Error: The InUseDependency or IsapiCgiExistence dependency check detected C:\Per
    l\bin\perl.exe "%s" %s in the source data but not installed on the destination s
    erver.
    Fatal: The dependency check 'IsapiCgiExistence' found issues up to 'Error' level
     that must be resolved before the current operation can be processed.  See previ
    ous messages.
    Change count: 0
    Fatal count: 2
    Error count: 6

     

    for the front page server extensions, I haven't configured them because I have no sites installed, but was hoping this error wouldn't cause the migration to fail.

    For the asp.net, server 2008 has asp.net already installed, so I'm not sure how to get around that one.

    Perl is installed on the new server. So, I am baffled by that error. Possibly a path error?

    I really have no clue on the odbc error though.

     

    Any help would be appreciated.

    Thanks,

    Rodge

Page 1 of 1 (1 items)
Page view counter