When I upload any module in System->Extensions in DotNetNuke 5.6.3, running on a Windows 2008 R2 server, IIS 7.5, after the correct module information is displayed and I hit next, I receive the error message
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object.. ---> System.NullReferenceException: Object reference not set to an instance of an object.at DotNetNuke.UI.WebControls.FieldEditorControl.CreateEditor()at DotNetNuke.UI.WebControls.FieldEditorControl.DataBind()at
DotNetNuke.UI.WebControls.PropertyEditorControl.AddFields(Table tbl)at
DotNetNuke.UI.WebControls.PropertyEditorControl.CreateEditor()
[...]
and the module is not installed. The file system of the web has not been touched, so I thought it was a permission problem, but even allowing user Everyone to do everything doesn't help (after making sure the ApplicationPoolIdentity user has been allowed full access as well).
Any hint is appreciated.
The manifest of the module is valid (it's Dynamic Registration 4.1).
Update: Installation steps (note: I am using a German installation of Windows 2008, so some translations might not be accurate)
Log in as Hosts Super User (Admin)
Either navigate to System->Extensions or System->Module Definitions (System might be identical to Hosts) - I tried both
In System->Extensions, click Installation assistant for extensions
Select file to upload
Click next
Description of uploading package appears correctly - click next
Error message Object reference not set to an instance of an object. appears on top of the page. Log View shows stack trace as partly displayed above.
What can cause an error in DotNetNuke.UI.WebControls.FieldEditorControl.CreateEditor()?
What kind of permissions could be missing?
Update 2: By step-by-step debugging, I found out that the view state is broken, for some reason. The method BindPackage() in DesktopModules\Admin\Extensions\Install.aspx.vb doesn't find the current Installer Package. I have not yet found out why the viewstate breaks. It is enabled and huge in the rendered page source.
As described in Update 2, the page's viewstate is lost in DesktopModules\Admin\Extensions\Install.aspx.vb. Simply replacing ViewState by Session works (but this workaround may be lost after the next DNN update).
Update (in case someone has a similar issue):
The DNN container that was used had its viewstate turned off! This results in all kinds of weird behaviour, but it took time to track that error. Now it's obvious.
Related
I was a Railo user who just started setting up a new server. As part of this migration I thought I would update to the newest version of Lucee as well.
The Lucee install went much smoother than I remember my last Railo install going and all sites worked immediately after setup. However, when I set my IP address to show debugging information to I get the following error at the end of all pages on my sites:
Message template [[**My Webroot**]\Nightscape\WEB-INF\lucee\context\Component.cfc] must contain a component or an interface.
Stacktrace The Error Occurred in
C:\lucee\tomcat\lucee-server\context\context\admin\debug\Debug.cfc: line 1
1: <cfcomponent>
2:
3: <cfset fields=array()>
called from C:\lucee\tomcat\lucee-server\context\context\admin\debug\Modern.cfc: line 1
This occurs whether I set the debug template to classic or modern. I haven't done anything on this server yet other than install Lucee, tweak some of the settings in the server admin, and setup my sites in IIS. I did try to navigate to [My Webroot]\Nightscape\WEB-INF\lucee\context\Component.cfc and found that it is just a blank file; is it supposed to have content?
I found that some other sites were working once they were setup. Upon comparison, the other sites had the following content in \WEB-INF\lucee\context\Component.cfc
<cfcomponent displayname="Component" hint="This is the Base Component"></cfcomponent>
A similar problem happened with other sites leading to a variety of errors, but they all traced back to zero length files created by Lucee that I just had to copy from other sites.
I am in the process of upgrading from Orchard 1.7 to 1.8. Everything seems fine locally, but when I deploy my site, 1 of my custom modules is disabled. When I click the "Enable" link in the modules section of the dashboard, the page refreshes, but the module is still disabled. My local instance is connected to the same database and shows the module enabled so not really sure what is happening. I don't see any details in the standard error logs.
Is there any way to see any errors that could be causing a module to fail being enabled?
Thanks
This turned out to be due to a case mismatch in my feature name vs my module folder name. My module was originally named in Pascal case ie. 'MyModule'. Somewhere along the way my folder had gotten renamed to 'Mymodule' while the Module.txt file still listed the primary feature as 'MyModule'.
I finally hunted this down by copying the Orchard.Modules.pdb file into the bin folder of my precompiled web application and attached the VS debugger to it to see what was going on. The issue presented itself inside of Orchard.Modules.Controllers.AdminController.Features() where a comparison of FeatureDescriptor.Id == ShellFeature.Name failed to match on account of the case mismatch. The result was that my feature was being shown as disabled even though it is enabled in the database.
Not a direct answer to your question but did you do a complete rebuild before publishing your orchard site (assuming that is how you deployed it)? I have found that sometimes you have to do a rebuild all before publishing.
I am facing a strange error in xpages. Whenever i preview any xpage in internet explorer I get error 500. I've tried this with new nsf, I created only one blank xpage with no elements and tried to preview, I got the same error.
I've also checked the "Display Xpages runtime error page" in xpages tab in Application Properties section but got the same 500 error.
(I am working on my local machine)
Url of my xpage:
http://localhost/test/testdb.nsf/testxpage.xsp
For every preview attempt log.nsf has below entry
04/17/2012 03:24:10 PM HTTP Web Server: Command Not Handled Exception [/test/testdb.nsf/testxpage.xsp] Anonymous
Below is the error on ie.
Error 500
HTTP Web Server: Command Not Handled Exception
Step 1: Go to the application properties and tick "Show standard error page"
Step 2: Make sure that your application is build (default autobuild in project is ON, but you never know)
Step 3: Try project clean
Step 4: Check the errorlog in data/domino/workspace/log
Step 5: Post your code here to have a look
Based on your description most probable reason is security: you have no right to run XPages on the server. Either sign with proper ID or manage to be in "Sign agents or XPages to run on behalf of the invoker:" field of server document (in Security tab).
Anyway, you should always look for the log mentioned by #Simon McLoughlin.
Try looking at the stack trace in C:/domino-Data-Directory/IBM_TECHNICAL_SUPPORT and the most recent xpages_...log file, generally a lot more helpful than the one line errors you get in other places
If you are working on Windows Vista/7 then for starting your Lotus Notes, right click on Lotus Notes icon and click on "Run as administrator". It works this way on my local machine. I guess this is due to UAC (User Account Control).
I guess that it is your Notes client. Then you need to check with your admin.
Some of the time, We do not have a sufficient privilege for data folder. I am also faced this issue.
Check your server port, probably it may 80. So some your application takes port 80 like face book, skype... So quit that process and try :)
Are you using Extension library in the application ?
Then you need to do a double installation, both the designer and the Client installation to be able to preview.
I'm experiencing the same issue with my server, I only did what #stwissel suggested and then restarted my server and it all worked, but in your case your running it locally try restarting you PC and hope it works.
Are you running Quicker? I found this article and thought it might help, http://www.zarazaga.net/web/z.nsf/dx/getting-error-500-on-opening-an-xpage
I'm trying to deploy a winform application with IIS and ClickOnce. I can access the publish.htm page and the install even starts when I click on the provided link.
However I get this error during the installation process:
Downloading http://MyWebSiteUrl/.../Interop.SHDocVw.dll did not succceed.
The remote server returned an error: (500) Internal Server Error.
Can anybody help me out on this ?
Thanks,
Bruno
I found out that I needed to check "use .deploy file extension" (under properties>Publish>Options>Deployment
[Answering this old question because it comes up as the best match in my case and the accepted answer was of no use to me].
Background, in an IIS hosted ClickOnce scenario, the downloadable components are itemized in a manifest file at the root of the deployment (that's how you can specify a single download link and deploy all the supporting components).
I was converting a tested application from a WiX installation to a lightweight version with ClickOnce and received the HTTP 500 error without anything else in the logs. Naturally, I failed to think it through and instead found myself getting dragged down the rabbit hole on the internets, with instructions for detailed logging, magic spells, etc.
Upon more sober reflection, the problem was simple and I should have been able to tell immediately from the IIS log: a 500 followed by a 0 is shorthand for 'you're an idiot, the content isn't where you said it was' and it had almost nothing to do with ClickOnce.
I had copy/paste/edited an existing download link template in MVC that was in use for simple apps and it happened to cater to only two levels of subfolders in the manifest. When I ported a more complex project structure, I ended up leaving items in a Resources sub-sub-subfolder that looked fine in the manifest but the path was being truncated in MVC so that the related item could not be found.
Moral of the story - if you get a 500 error always check first to make sure your non-functioning appliance is plugged into a working outlet...
After deploying an upgrade to a particular feature which contains ghostable page template, the page starts returning a 404 response.
In the SharePoint log, I get the following
Cannot get ghost document: Features\FeatureName\SubFolder\PageName.aspx
Unknown SPRequest error occurred. More information: 0x80070002
I am able to get the page working by going through SharePoint Designer and deleting the file, then deactivating/activating the feature on that site.
I've attempted resetting the web to its definition with no change.
I would like to have a programmatic solution, whether it be fixing something in the feature's configuration or an update program.
I was able to work-around the problem by
Adding a snip of code to the feature deactivating event to delete the file in question from SitePages.
SPFolder sitePagesFolder = web.GetFolder("SitePages");
foreach (SPFile file in sitePagesFolder.Files)
if (file.Name == "pagename.aspx")
file.Delete();
And using a utility, go through all the affected webs, re-activating the feature in question, which causes the 'orphaned or whatever' file to be removed, replacing it with the current version's
I don't understand the inner workings of the issue completely, but it seems that when the feature is deleted/reinstalled, sometimes the associated, ghosted file is orphaned, leading to this issue.
Is it possible that the upgrade deleted the file from the file system? cause this is the likely reason. go to the feature folder and see if the file is still there. the feature folder would be under template\features under 12/14 (depending on SP version)