I am looking for information on how to get a DotNetNuke RSS Feed Module to work.
I have tried both DotNetNuke Modules 4.0.1 and 4.2.1 and I get errors. I have tried different settings in the module but nothing works. When I take the link and post it in a browser (I've tried IE and Firefox) it works, so it shouldn't be a RSS problem.
I have tried several RSS feed URLs and get the same error. Thanks in advance for any help! I have looked at several websites regarding this issue but so far I have not found an answer.
Error Message
System.Web.HttpException: Could not load type 'DotNetNuke.Modules.XML.XmlController'.
at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)
Looking at the error message it looks like there is something missing from the install of the module. You will want to confirm that DotNetNuke.Modules.XML.dll exists within the /bin folder of your site.
Related
Everything worked yesterday without any errors.
Today though, I created a new page and tried to load it, which returned an error. so I went and rebuilt the solution, and now I have this error on every page on my site.
error description:
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: Could not load type 'xxxx.Global'.
Source Error:
Line 1: <%# Application Codebehind="Global.asax.cs" Inherits="xxxx.Global" Language="C#" %>
Source File: /global.asax Line: 1
I tried to look up the error, but the solutions I managed to find didn't solve the problem, I would love some help as I am truly lost about what had caused this.
EDIT: so I tried deleting the Global.asax file and running the site, which caused the first line in all my pages to return an error messege. still trying to find a solution.
Managed to solve it, Here's what finally worked for me -
first, in the first line of your aspx pages, Masterpage.Master and Global.asax you'll need to replace CodeBehind with CodeFile.
(in order to access your Global.asax code open it through the directory with a text editor).
after that, in your Global.asax.cs code, change public class Global : System.Web.HttpApplication to public partial class Global : System.Web.HttpApplication.
worth noting - this is a mishmash of a number of solutions that I found while googling, trying these separately first could also solve the bug.
You can try to set the CPU to x64 in visual studio to slove this issue:
On the menu bar, choose Build, Configuration Manager.
In the Active solution platform list, choose a 64-bit platform for the solution to target, and then choose the Close button.
If the platform that you want doesn’t appear in the Active solution platform list, choose New. The New Solution Platform dialog box appears.
In the Type or select the new platform list, choose x64.
If you want to copy the settings from a current platform configuration, choose it, and then choose the OK button.
If this does not solve your problem, you can also refer to the solution in this link:
Could not load type 'XXX.Global'.
I'm trying to create a copy of our live DNN (version 8.4.2) on my local as part of an upgrade project. I cannot get to the bottom of the following error. Can anyone throw some light on this?
2018-06-20 07:57:31,511 [IT-Dev01][Thread:7][FATAL] DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication - System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.HttpModules.OutputCaching.OutputCacheModule.OnResolveRequestCache(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
For what it's worth, I made changes to four of the DNN DB tables and I'm not 100% sure which particular change fixed this. The production URL was being used in these tables and I had to change it to dnndev.me:
HostSettings
PortalSettings
PortalAlias
WebServers
Hopefully this will be of help to anyone experiencing this error. I would also suggest use of the Event Viewer to assist because not all errors show up accurately in the DNN logs.
Where are the default Descriptions stored for the various ASP.NET HTTP errors hosted on IIS? Can they be accessed via code?
EG. The default error page for a 404 will include the following text:
Description: HTTP 404. The resource you are looking for (or one of
its dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make
sure that it is spelled correctly.
Can we read this string via code?
I can catch an HttpException (I know a HttpException != HttpError) and do things like .GetHttpCode(), but I haven't seen anywhere detailing where the IIS error messages are stored and whether I can access via code.
It would be nice if I was able to reuse the default text in a custom error page when I don't want to come up with it myself.
UPDATE 1
Following one of the comments, I investigated IIS to see where it's Error Pages are configured. Sure enough, there is an Error Pages directory, defaulting to, for example "%SystemDrive%\inetpub\custerr\\404.htm", however these error messages are different from the ones that are shown by the web application (which I assume are generated by .NET).
EG
The resource you are looking for might have been removed, had its name
changed, or is temporarily unavailable.
These error pages are physical pages hosted on the web server, so accessing them via code is not the option I am seeking.
As suggested in the comments, these strings are resources within the System.Web assembly, and there's no systematic means of retrieving just the ones related to HTTP error codes1 (versus all of the other string resources within System.Web)
For example, this Console application, with a reference to System.Web:
using System;
using System.Resources;
namespace PlayAreaCSCon
{
class Program
{
static void Main(string[] args)
{
var rm = new ResourceManager("System.Web",
typeof(System.Web.HttpApplication).Assembly); //Arbitrary type
Console.WriteLine(rm.GetString("NotFound_Http_404"));
Console.ReadKey();
}
}
}
Generates this output2:
HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Note also that the fact that these strings are stored as resources is an implementation detail and not documented anywhere, so you'd have to accept that any code based on accessing these resources could be broken by any future updates to the .NET Framework (although it's unlikely to change in practice).
1By which I mean I had to use a decompiler to find the magic string "NotFound_Http_404" used in this sample. There's no logical way to go from that to the needed string for any other status code.
2On a machine where no effort has been made to select anything other than the en-US locale. YMMV.
I am trying to publish Umbraco 4.7.0 site.
when i am trying to publish Node get this error.
Cannot insert the value NULL into column 'id', table 'hedronDB.dbo.cmsPropertyData'; column does not allow nulls. INSERT fails.
And when i see in browser i get "Looks like there's still work to do" this error.
Any help is much appreciated!
I assume you are seeing the error in the database's [umbracoLog] error table?
Have you just migrated your site to a new server? If so, your umbraco.config file may be missing. This is usually why you see the "Looks like ..." message, because nothing has previously been published.
Also, check the permissions on the site to ensure that modify permissions have been given to the correct folders.
If none of these help, one of your doc types or pages may be corrupt, meaning that when a page or pages of a particular doc type are being saved, Umbraco thinks there should be a particular property on the doc type when there isn't.
Check the Umbraco logs in the database [umbracoLogs] table, and see if there is a reference to a particular doc type or page being saved. The solution here would be to recreate the offending doc type, and also recreate the pages from the doc type.
Aside from this, it is always worth checking or raising your issue at our.umbraco.org
Finally, if possible I would very much advise upgrading to the latest version of Umbraco (currently v6.1.2) or at the very least v4.7.2 which is a patched version of the version you are using.
My Web Application builds and publishes successfully, the problem arises after copying the files to the web server, where I get a compilation error when I try to browse to several pages, other pages however continue to function correctly.
My first thought that was some of the files may not have been successfully copied so I republished and tested the page and all seemed well until I checked a different page that had been working with the previous publish that was now exhibiting the same problem subsequent publishing have seen similar effect with the pages affected altering each time.
The pages that are failing on the web server have previously been functional on the web server have not been altered for this publish and continue to work fine in Visual Studio 2010 Debug.
I have recycled the application pool restarted the website and rebooted the server.
The error from our error logs is:
GAE:: System.Web.HttpException (0x80004005): The file /XXXX.aspx has not been pre-compiled, and cannot be requested.
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
EDIT: I have copied the source aspx and cs files for one of the failing pages (renaming the class) and re published it the solution. The new page works side by side with its failing counterpart.
This error can be a red herring and usually masks the real error.
1st check permissions on the IIS app, physcial directory and the affected file are correct.
If it's not permissions, set custom errors to RemoteOnly on the webserver only and re-publish. In the .net 4, publish the app with the following options ticked, "allow pre compiled site to be updateable" and "use fixed naming conventions and single page assemblies"
When deployed to the webserver you should find the correct issue reported now, which will be a missing custom or 3rd party assembly, this may be recently added and removed, or a blast from the past which has reared its head again for no apparent reason (this was our issue, assembly not used in any forms, but was defined in the config file and hence took several forms down)
Hope this helps you to solve your issue - good luck!
I ran into the same problem with VS2017 and an application that was already running for a long time.
The application used to be deployed thru XCOPY deployment without publishing. After switching to the publishing method the error showed up.
After some reasearch we found that in the production there was still an entry for profiles in the web.config while it had already been removed in developement since there was no need vor it anymore.
After uncommenting the node profiles in web.config the application was up and running.
While deploying we had also remove all files except APP_DATA and web.config.
Propably file or IO related. Did you copy all the files, not just binaries? You could try deleting all the old files (backup first) so it´s not some write protection or security issue.
I had the same issue.
Some of the pages throw error when trying to open after publishing them.
One solution which worked for me was .. When I checked the aspx files of those showing errors, had CodeFile and not CodeBehind...
I changed from CodeFile to CodeBehind and it worked fine. (Dont know if its a reason that CodeBehind alone available in the bin directory.. Am a newbie and may be this reason is not right. Please correct me if I was wrong)
But problem is, on localhost certain files throw error when they are left as CodeBehind.
I think this thread may be related:
How to fix ASP.NET error "The file 'nnn.aspx' has not been pre-compiled, and cannot be requested."?
As indicated there, our solution was to delete all the files under:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root
I know this issue is old but if anyone comes into this problem, before playing with versions, files, etc, could I suggest to Clean the project first? After a very stressful day, this is what sorted my problem.