• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Error SiteBuilder.Modules.WebControls.DLL

A

aabrahao

Guest
Hi,
The error appears after the user publish the site.
I change the web.config and the error above appears:
Server Error in '/' Application.
________________________________________
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The type 'SWsoft.SiteBuilder.Site.Helpers.WebControls.ErrorPage' is ambiguous: it could come from assembly 'c:\ddddd\Uuuuu\hhhhh\ddadadal\xxx.xxx.xx\www\bin\SiteBuilder.Modules.WebControls.DLL' or from assembly ' c:\ddddd\Uuuuu\hhhhh\ddadadal\xxx.xxx.xx\www\bin\Site.Helpers.DLL'. Please specify the assembly explicitly in the type name.

Source Error:

Line 1: <%@ Page Language="C#" AutoEventWireup="true" Inherits="SWsoft.SiteBuilder.Site.Helpers.WebControls.ErrorPage" %>
Line 2:
Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Source File: /Error.aspx Line: 1
________________________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
 
If this is still actual, you could try following solution:

It looks like there is file Site.Helpers.DLL exists in directory %SiteBuilder%\Repository\Common\bin\. But there should not be such file.
Solution:
1. Remove this file from %SiteBuilder%\Repository\Common\bin\
2. Check all sites directories %Sitebuilder%\Sites\*\bin and remove Site.Helpers.DLL file from there.

This file could came from previous 3.x version. It looks like Sitebuilder 3.x removal or upgrade was performed not quite correctly. Anyway, try to check solution and let me know about the results.
 
Back
Top