« Previous Next »

Thread: migrating path

Last post 11-23-2008 8:07 AM by VorlonShadow. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 11-21-2008, 3:33 PM

    migrating path

    OK. This is driving me nuts.  I'm getting the following error when I go to my application now:

    HTTP Error 500.23 - Internal Server Error

    An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

    I don't know why this suddenly changed, but the details are telling me that I need to migrate the application. OK.  The syntax for this is supposed to be as follows:

    \%SystemRoot%\system32\inetsrv\appcmd migrate config "<default site>/"

    Problem is that "Default Site" is disabled.  I'm running several web sites on this server.  Plus, the application is not a "Virtual Directory", it's an Actual Directory.  OK. So, searching around, from what I can tell, I can use the web site name/Folder name, but when I try:

    \%SystemRoot%\system32\inetsrv\appcmd migrate config "thinkregistration/TSA0808/" I get the error, "The filename, directory name, or volume label syntax is incorrect.".  So, how do I find the path to the application, so I can migrate it?

    Jesse

  • 11-22-2008, 5:47 PM In reply to

    Re: migrating path

    Try changing the application pool to Classic Mode.  I'm not certain where it says your site needs "migrated".

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 11-23-2008, 8:07 AM In reply to

    Re: migrating path

     Sorry, I should have come back and replied to this message.  I found the problem.  I had an old way of bringing in a handler in my web.config file.  Actually, I had both the old way and the new way.  I removed the old way, and it worked fine after that.  The odd thing is that it worked just fine that way for quite a while, then suddenly, it stopped working.  Oh well.  Anyway, it's resolved.

     Thanks,
    Jesse

Page 1 of 1 (3 items)
Microsoft Communities