1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

SiteBuilder WebAppPool error

Discussion in 'Sitebuilder 4.2 for Windows' started by KBarefoot, Mar 25, 2008.

  1. KBarefoot

    KBarefoot Guest

    0
     
    My installation is incomplete...I hit a road block.

    The error says to check the install.log.

    The install.log says: <h1>Service unavailable</h1>

    I was asked to check the WebAppPool.

    The pool starts, but fails to stay up.

    Message states that it is "unable to load rpcproxy.dll".

    I have uninstalled and reinstalled the RPC for HTTP component several times with no impact on the issue.

    The file is located where it specifies: C:\Windows\System32\RPCProxy

    The installation is on a desktop with the following specs:
    CPU: AMD X2 4800+ x64
    RAM: 2 x 1GB PC2-5300
    OS: Win Server 2003 R2 x64
    DB: SQL Server 2005 Developers Edition

    Any suggestions?
     
  2. Bender

    Bender Guest

    0
     
    Hi,

    Looks like you have custom global isapi filter configured, try disable its loading.

    Open iis management console: start > run > inetmgr

    Open "Web sites" properties > isapi filter, remove filter referring to rpcproxy.dll.
     
  3. KBarefoot

    KBarefoot Guest

    0
     
    I found no ISAPI filters...

    First off, thanks for the reply...no one else seems able to even venture a guess.

    I looked in the Global Websites entry and in each individual Website and found no ISAPI filters defined.

    I'm not sure if it is worthy of note or not, but I had already installed SQL Server 2005 Developers Edition on that server prior to loading SiteBuilder. SiteBuilder is pointed to that installation and therefore did not install the default SQL Server Express.
     
Loading...