« Previous Next »

Thread: deploy asp.net web application error message

Last post 07-10-2009 9:50 AM by mikekay. 4 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (5 items)

Sort Posts:

  • 07-10-2009, 9:29 AM

    • mikekay
    • Top 200 Contributor
    • Joined on 01-20-2009, 2:43 PM
    • Posts 29

    deploy asp.net web application error message

    Greetings. Last night I got the code for our web based application, published it in visual studio and plopped the app into our test server - a Server 2008 Standard box running IIS7 with the basic defaults setup. When I try to start the web site I get the following error: The process cannot access the file because it is already being used by another process. (Exception from HRESULT:0x80070020) Our programmer feels this may be a dll issue - but I have no idea what dll or how to troubleshoot this error. Any help most appreciated.
  • 07-10-2009, 9:36 AM In reply to

    Re: deploy asp.net web application error message

    Obvious question:  Is the file open in VS?

    Jeff

    Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com
  • 07-10-2009, 9:38 AM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,247

    Re: deploy asp.net web application error message

    Most probably, the ip:port the site is trying to bind to is already taken by another process - use "netstat -ano" to figure out who it is.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 07-10-2009, 9:43 AM In reply to

    • mikekay
    • Top 200 Contributor
    • Joined on 01-20-2009, 2:43 PM
    • Posts 29

    Re: deploy asp.net web application error message

    Nope. VS is closed.
  • 07-10-2009, 9:50 AM In reply to

    • mikekay
    • Top 200 Contributor
    • Joined on 01-20-2009, 2:43 PM
    • Posts 29

    Re: deploy asp.net web application error message

    Fixed! Thank you very much. As soon as I saw the ip:port post, I knew how to fix it. The conflict was on port 80.
Page 1 of 1 (5 items)