Article ID: 2009, created on Jul 11, 2007, last review on May 9, 2014

  • Applies to:
  • Plesk 8.2 for Windows
  • Plesk 8.1 for Windows
  • Plesk 7.6 for Windows


Sitebuilder for Windows is shown as not activated in Plesk components.


Such problem occurs when Plesk cannot connect to Sitebuilder web site.


To find out the reason you need to try to connect to Sitebuilder web site directly, using any Internet browser.

Note: You have to check it directly from within server.

To get a URL of Sitebuilder web site, open registry and navigate to the following key

HKEY_LOCAL_MACHINE\SOFTWARE\SWsoft SiteBuilder for Windows

Check the following values:

CREATEDWEBSITEHH defines host header of Sitebuilder panel. By default empty.

CREATEDWEBSITEIP defines IP address of Sitebuilder panel. By default "*".

CREATEDWEBSITEPORT defines Sitebuilder panel port number. By default "2006".

If CREATEDWEBSITEHH is not configured (empty) then Plesk checks CREATEDWEBSITEIP.

If CREATEDWEBSITEHH is configured (some domain name is inserted) then Plesk skips CREATEDWEBSITEIP.




Created URL will look like

Sitebuilder panel should be displayed without errors. If you see any errors you need to fix them.

Then you need to check IP address restrictions for the web site. To do it open IIS management console

IIS, Web Site, Find Sitebuilder Web Site, ServiceFacade, Properties, Directory Security, “IP address and domain name restrictions” section, Edit

By default Denied access option should be selected. The list of allowed IP addresses should contain all the IP addresses of the server, including

Once all problems are fixed and you got Sitebuilder web site working, Plesk should be able to connect to Sitebuilder.

If Sitebuilder web site shows no errors you need to check the Plesk event logs.
Open Event Viewer, Plesk. Find nearest error message from defpackagemng.exe related to Sitebuilder. You will see exact error message why Plesk could not connect to Sitebuilder web site. Depend on error from utility you need to find out the corresponding solution.

c0c38d2367acfa8909699e0b34b01dea 7000fbc03a7e92b93bc676a7c04a4ce6 b23c51a6195823476e308cc12db2be0e 85a92ca67f2200d36506862eaa6ed6b8 a914db3fdc7a53ddcfd1b2db8f5a1b9c e115c1a9652baf38f4af4f18d5b7ac6e c45acecf540ecd42a4bbfb242ce02b1d 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF