5

So.. I'm migrating a physical server to a virtual (Hyper-V) one.

The physical server is running Windows Server 2008 R2 with IIS6 and Windows SQL Server 2012.

I've set up a VM with Windows Server 2016, IIS10 and Windows SQL Server 2017.

I'm testing with just moving 1 db at a time (we have about 20, 1 per client running this software and a few others) and I've already imported all of the IIS sites.

So the database import and IIS import went smoothly and was surprisingly without hassle but now I'm trying to run the website that I imported the database for and it is throwing 503 Errors at me.
I've been trying to find out the cause but for some reason IIS isn't making any logs.
It's not any 64/32bit system problems (they're both x64) and I can't seem to find anything wrong with the imported config.

Anyone got any ideas?

Comments
  • 1
    Asp or php
  • 0
  • 1
    is something about this in the eventviewer?
  • 0
    @stop it's pretty weird, I was getting some errors in event viewer (code 5002) but no real information of value and looking up the code wasn't of much help.
  • 0
    @dontbeevil probably not, I'll look through it and enable it. Thanks.
  • 0
    @dontbeevil I've added httpLogging into the web.config file and it already had debugging; I've also made sure that logging was set up in the GUI. But it still doesn't work. :/
  • 1
    @dontbeevil
  • 1
    Is the applicationpool running?
  • 0
    @stridsberg didn't think to check. It keeps turning off, it was set to .NET v4 so I've set it to V2 but it still keeps turning off.
  • 0
    @stridsberg checked the physical server, it had v4 for the pool so I've set it back.

    The server itself should be on v2 (it is on physical) but it was v4 on virtual (I changed it to v2 before(?)) so I've set that to v2 but still no luck.
  • 0
    @dontbeevil nope... I'll try that now.

    This job is my first time working with IIS (and MS Servers in general) sorry.
  • 0
    @dontbeevil still getting 503 and the pool is still stopping.
  • 1
    A 503 like that probably means IIS has gone into rapid failure detection mode and turned off the Application Pool.

    You'll have to keep deactivating the AppPool to keep troubleshooting.
  • 0
    @kwilliams @dontbeevil thanks, I'll give it a go.
Add Comment