• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SiteBuilder WebAppPool error

K

KBarefoot

Guest
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?
 
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.
 
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.
 
You must log in or register to reply here.
Back
Top