Article ID: 2114, created on Aug 23, 2007, last review on Mar 17, 2016

  • Applies to:
  • Plesk for Windows
  • Plesk Sitebuilder for Windows


Sitebuilder isn’t integrated with Plesk. Component management page shows :

SiteBuilder for Windows 4.0.253 not activated

Event Viewer shows the following error:

Sitebuilder account validation is failed in Sitebuilder: System.Net.WebException: The request failed with HTTP status 400: Bad Request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at WSAccount.AccountWebService.GetAccountByName(String username)
   at SBNETProxy.Provider.validateAdminAccount(String& status, String& accounttype, String& accountId)
Execute file name: C:\Program Files\SWsoft\Plesk\admin\bin\defpackagemng.exe

However Sitebuilder itself works properly and can be accessed


Most likely the reason of the problem is that Sitebuilder website runs on the different IP than it has configured in registry.


Please open regedit and go to the following key :

HKEY_LOCAL_MACHINE\SOFTWARE\SWsoft SiteBuilder for Windows

Ensure that value CREATEDWEBSITEIP points to the same IP address as Sitebuilder website has in IIS.

fad6dc0c8e983c17ae70a51ac7952cd0 85a92ca67f2200d36506862eaa6ed6b8 a914db3fdc7a53ddcfd1b2db8f5a1b9c 2a62cbceb986d1b8f45bcd3ff4cb29a5 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF