What are the steps neccessary to enable custom errors for azure websites.
I have set the 'custom errors' xml tag to 'off', yet that still does not work and i am still getting nonsense generic 500 page.
<customErrors mode="Off">
</customErrors>
theres the 'remote debugging option' that allows me to select a visual studio version.Could that be it?
enter image description here
That's the correct way to turn off custom errors. However, that will only be effective if the requests actually reach your site. In some situation, the requests don't make it that far, at which point you lose control over custom errors. For example, if your site is stopped, or you have a free/shared site that ran out of quota, you won't be able to turn off custom errors.
Two suggestions:
clarify your question to specify exactly what error you are getting and in what situation
Practice turning off custom errors on a test site that's in a clean state, to isolate from the specific issue your site may be having.
Related
I am trying to work out how to host multiple sites on one instance of Umbraco, which is hosted on Azure. I've added the second domain as a custom domain on the Azure Web App. I've created two Home pages at the root of my Umbraco and set each to the appropriate hostname in 'Culture and Hostnames'. I can still navigate to the original site, but when I try to go to the second site I get the following error:
The call is ambiguous between the following methods or properties: 'Umbraco.Web.UmbracoHelper.Media(params int[])' and 'Umbraco.Web.UmbracoHelper.Media(params string[])'
No offending source code is identified.
I don't really know what I'm doing with this and try as I might I can't find any answers by googling the issue.
Got it. I had a Partial View that allows you to add some logos to the bottom of the homepage and as I was only doing a test run I hadn't added the logos in. So Umbraco was looking for images that weren't there and threw the error. Thanks for your pointer Mark.
Posted this on codeplex, but thought I'd try here as well.
I've created an Orchard application, which I've deployed to Azure, however when debugging it, it occasionally resets everything so that I have to enter the site details (i.e. site name, admin user, database, etc.) again. Because I'm using an existing database, it ends up duplicating various things, so I end up with multiple admin users, multiple navigation menus, etc. Why is this happening, and is there a way I can prevent it?
I think I've found the cause, as detailed here:
http://orchard.codeplex.com/discussions/428980
It's to do with the unit tests that are run in ClickToBuildAzurePackage. If I comment them out from AzurePackage.proj, it works.
I've been getting an error in SharePoint that reads:
System.Web.UI.ScriptManager is not allwoed on this page. The type is not registered as safe.
I googled around, and the results pointed to missing AJAX server extension installations while using the asp:scriptManager tag. However upon closer inspection of my project, there was no findings of such tag. Whats even more strange, was that after I reinstall/reset the masterpage, the error went away and I was able to read my site again.
I was wondering whether the above error would appear if certain SharePoint files gets overriden? Or are there other less obvious/non-trivial reasons for it?
Thanks.
When it comes to the error, it is very likely related to your custom masterpage is not including the tag itself but it has a control or code that requires and/or inserts the tag.
Example: it is a common practice to code a custom webpart or usercontrol in order to insert the ScriptManager under the forms tag programatically in case one isn't present, and once this custom code hooks the page render with the ScriptManager, it will check for whether it is allowed in web.config -- thus you get the error.
SharePoint's web.config does not comes with Ajax enabled. Telerik has a good tutorial on that.
When adding or editing a page in a SharePoint Pages library we get the following exception:
[COMException (0x81020016): Item does not exist
The page you selected contains an item that does not exist. It may have
been deleted by another user. Click "Home" at the top of the page to return
to your Web site.]
at Microsoft.SharePoint.Library.SPrequestInternalClass.RenderColumn.
The weird thing is, when we first do "Check in" and then click the Publish button it works perfectly. But clicking "Publish" directly generates theis error, BUT NOT ALWAYS!
The Pages library has publishing and item planning on, NO workflow (seeing as the person who adds / edit pages is also the approver) and Major/ Minor versions.
We use a content type derived from publishing page and a custom PageLayout.
I'm sure you would have already checked this but is there any more information in the ULS logs?
Also have you tried setting the debugger to break on all exceptions and does this give you more information? Go to Debug, Exceptions and tick Common Language Runtime Exceptions. Then go to Tools, Options, Debugging and untick Enable Just My Code. Finally attach to w3wp.exe.
If you are running Windows Server 2008 you could also try taking a dump file at the point the debugger breaks above. ADPlus might help if you are running Server 2003 but I don't have experience with it. You should then be able to open the dump file with DumpChk or WinDbg.
Edit: As discussed in the comments, this is code deployed to production that can't have its service interrupted. The only way you could create a dump file is programmatically. Have a look at this question I asked that will hopefully help you if you need to go down this route.
Other things to try if you don't want to get down and dirty with debugging is to try deploying your custom bits to a clean server. See if you can still reproduce the problem or if it changes.
I am assuming that you are using load balancing with 2 web servers.
The fact that it does not happen always points to there being a difference between the servers.
There are then a few things that you could check:
Are all the versions and service packs are the same on both machines
Have any of the servers had beta software installed
Is your code the same on both servers
One thing you could do to test without taking the system down: Is to remove the first web server from the cluster see if the error occurs, then add it back and do the same thing with the second web server.
While setting up a test environment I was attempting to set up many different types of sites for testing various things when I ran into a strange bug in SharePoint.
I was creating a subsite under a blank site template and saw the option for "News Site" so I selected it and got an error saying that the Publishing Feature was not enabled at the site collection level.
Fine. So, I went and activated it and then attempted to create the site again and I got the error:
The Web site address "/mpsite/news" is already in use
Ok, so the site must have been created anyway so I try to visit the URL and get:
The webpage cannot be found
Fine. So, obviously it errored in the middle of the site creation so I'll just delete it via STSADM. Wrong:
There is no top-level Web site named "http://server/mpsite/news/".
So, the site is listed in the sites and workspaces list, but doesn't really exist and can't actually be deleted.
How do I get rid of it from the Sites and Workspaces listing?
You've run into one of the lovely undocumented "features" of SharePoint - site templates get applied after the site gets created in a seperate, descrete step. This means that potentially, a site can "exist" (as far as the content database is concerned) without template, which leaves you with a site you can't browse to, but still sorta "exists" in SharePoint purgatory (I've actually written a couple of hacks that involve relying on this "feature").
It looks to me like you may have run into one such situation - when you went to go create your site, I'm guessing that you got the error before the template was applied to your news site.
The way I've fixed similar problems in the past has been to use SharePoint Designer to delete the sites - since it looks straight into the content database for what does and doesn't exist, it might do the trick for deleting your rouge news site.
Hope this helps!
Have you tried http://server/mpsite/news/_layouts/deleteweb.aspx ?
Or maybe the "Content and structure" (http://server/mpsite/_layouts/sitemanager.aspx) link from site actions?
I know this is old, but it may help somebody. In SP2013 running the Remove-SPWeb Powershell command with the url of the corrupted web worked perfectly for me.