Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ......is ambiguous in the namespace ...is ambiguous in the namespace 'ASP'
Previous
 
Next
New Post
2/21/2007 12:10 AM
 
 

Earlier today I checked a subportal for the first time since I updated from DNN 437 to 441 and I got the same error for the particular skin on that site. Cannot figure out why. This is not a production site yet, so I was still in research mode.

Now here is the bigger issue for me. I was troubleshooting a memory issue on my server and I tried to assign a DNN install on my server to a Dedicated Application Pool using my DotNetPanel control panel. For some reason it did not appear to work, as when I look back at the setting in my control panel, it is no longer checked. But now 2 out the 3 portals on this DNN install are giving me the same error as you have. The third portal is coming up without issue. Here is the error.

DotNetNuke.Services.Exceptions.PageLoadException: Unhandled error loading page. ---> System.Web.HttpCompileException: C:\HostingSpaces\cmoamerica\cmoamerica.com\wwwroot\Portals\0\Skins\ElementBlue\LaptopHome.ascx(71): error BC30560: 'admin_skins_logo_ascx' is ambiguous in the namespace 'ASP'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.Framework.DefaultPage.LoadSkin(String SkinPath) --- End of inner exception stack trace ---

Can't figure out what changing the app pool setting could have to do with this. I have done IIS resets and then rebooted the server and still two of three sites are not working.

Anyone have any ideas? This is pretty urgent as these are production sites.


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
3/7/2007 2:09 PM
 

Has anyone figured this out? Last night everything was working fine. This morning I'm getting the "ambiguous" errors on DNN 4.4.0 when trying to view the Host Settings and Site Settings. Is the solution to upgrade to 4.4.1? Thanks...

Here's the Host Settings error:

DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> DotNetNuke.Services.Exceptions.ModuleLoadException: Error: Host Settings is currently unavailable. ---> System.Web.HttpCompileException: D:\xxx\wwwroot\admin\Host\hostsettings.ascx(97): error BC30560: 'controls_skincontrol_ascx' is ambiguous in the namespace 'ASP'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

And the Site Settings error:

DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> DotNetNuke.Services.Exceptions.ModuleLoadException: Error: Site Settings is currently unavailable. ---> System.Web.HttpCompileException: D:\xxx\wwwroot\Admin\Portal\sitesettings.ascx(59): error BC30560: 'controls_urlcontrol_ascx' is ambiguous in the namespace 'ASP'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

 
New Post
3/7/2007 4:05 PM
 
I had another issue on my server and my server guy forced a recompile of all .NET applications somehow and it resolved my problem. When I went to the other site that had this particular issue it was gone. So I would recommend forcing a recompile on your .NET stuff and see if that works. Sorry I cannot be more specific on exactly what to do....but maybe it will help if you can figure it out...and maybe a guru can jump in and say what the issue is and why a recompile resolved it.

Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
3/7/2007 5:12 PM
 

Thanks for the reply. My DNN 4.x site has been having various problems ever since I installed a listserv application that uses the Chilkat Email .NET components. Removing the ChilkatDotNet.dll file from the bin folder eliminates the DNN errors, but doing so breaks the email application.

The problems have gotten too bad to ignore. So I'm building a DNN 3.3.7 portal dedicated to sending email. (The Chilkat problems don't seem to affect DNN 3.x.)

Obviously, I can't say whether this fix will do anyone else any good, but maybe it will help someone ... Cheers!

 
New Post
9/26/2008 2:34 PM
 

I was having the same problem just now. I fixed it by replacing the file with a new one from the installation zip.

 


--------------------------- Carlos ---------------------------
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ......is ambiguous in the namespace ...is ambiguous in the namespace 'ASP'


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out