Forum Discussion

Domdomdeo's avatar
Domdomdeo
Copper Contributor
Oct 04, 2023

Issue IIS migration server

Hello,

As part of my job, I need to migrate an IIS server but I'm currently running into a problem.

I have a source server where there are two sites/apps and my destination server which is "blank" for the moment.
The two servers don't have the same hostname or IP address but are on the same domain.
On the source server there's an A security certificate and on the destination server a B security certificate.

I used the Microsoft Web Deploy utility, and the installed roles and dependencies are identical on both servers.
From my source server, I export a server package containing the IIS configuration. I move the exported
file to the destination server.

However, as soon as I want to import the file on the destination server, I get the error message :
[Error: A specified logon session does not exist. It may already have been terminated (Exception from HRESULT:0x80070520)[/b]

I've tried several times and still have the same problem. I've searched the net but nothing very conclusive.

So if anyone has any ideas, any leads, I'd love to hear from you.

Thank you in advance for your help.

 

Windows Server
  • LeonPavesic's avatar
    LeonPavesic
    Silver Contributor
    Oct 05, 2023

    Hi Domdomdeo,

    1. Make sure that the user account that you are using to import the server package has the correct permissions. The user account must be a member of the Administrators group on the destination server.
    2. Try restarting the destination server. This can sometimes resolve minor issues that are preventing the import operation from completing successfully.
    3. Try importing the server package from a different user account. If you have another user account that has administrator privileges on the destination server, try importing the server package from that account.
    4. Try importing the server package using a different method. For example, you can try importing the server package using the Import-WebDeploymentPackage cmdlet in Windows PowerShell.

    If you are still unable to import the server package after trying the above steps, you may need to contact Microsoft support for assistance.


    Here are some additional troubleshooting tips:

    • Make sure that the source and destination servers are running the same version of IIS.
    • Make sure that the source and destination servers have the same installed roles and features.
    • Make sure that the source and destination servers have the same security settings.
    • Make sure that the source and destination servers have the same network configuration.


    Please click Mark as Best Response & Like if my post helped you to solve your issue.
    This will help others to find the correct solution easily. It also closes the item.


    If the post was useful in other ways, please consider giving it Like.


    Kindest regards,


    Leon Pavesic
    (LinkedIn)

Resources