I have installed Elmah using Nuget and I am wondering how to hide server variables from error page shown below:
You can update the error logged in ELMAH before it is persisted like described here: http://blog.elmah.io/removing-sensitive-form-data-before-logging-to-elmah/
Related
I am trying to install Umbraco by using the Azure Marketplace. There they offer a template for it. I am always receiving the error below. I tried to install it a couple of times now but I always get the same error.
Does anybody know what this error message means? Is anybody able to install Umbraco by using the template in the Azure Marketplace?
]
You're asking 2 questions above.
Please see my answers and proposed troubleshooting guide/workaround below:
The error message means that the MSDeploy process failed due to some error which renders it unable to deploy the web deploy package for your Umbraco web app.
Yes I am able to provision a Umbraco web app from the Azure Market successfully (Location: Central US) and couldn't reproduce your issue
Troubleshooting Guide:
Append .scm in front of the azurewebsites.net of your Umbraco Web App as shown below and go to the Url.
Click on the Diagnostic Dump. You will be prompted to download a .zip file
Extract the zip file. You should see 2 folders at root level
Go into
LogFiles\SiteExtensions\MSDeploy
You should see the detail log files for MSDeploy
Detailed MSDeploy log messages are in the appManagerLog.xml file.
If it is related to client side issue which can be resolved by yourself, you can try to resolve it and try again.
If it is related to server side issue, you should create a support ticket for Microsoft to look into with the detailed MSDeploy log which pinpoints the root cause which will help them a lot.
Hope this is useful.
A Microsoft employee confirmed this is a bug in the application currently. I have to wait for a fix.
I have encountered numerous problems with the Azure installer of Umbraco, try setting it up in VS2015 then publishing it to Azure. I have found that this works well.
I had a site running asp.net 5 beta4, and decided to upgrade to beta5. The site runs locally fine. I pushed the changes to master and it was picked up from bitbucket and deployed successfully.
When I try to hit the site in azure, I get a 500 Internal Server Error. I've tried a number of things, but can't seem to track down the root cause of the failure. I'm looking for suggestions as I'm hitting a wall. From what I've tried below it seems like some fundamental initialization is failing.
Here's what I've tried:
Enabling customerrors="off". I added a web.config to the wwwroot folder with system.web/customErrors mode="Off". I've verified that the web.config is populated correctly in the deployed wwwroot and had the appsettings containing the dnxversion etc merged correctly.
Customizing the custom error page, adding runtimeinfo. I have the following set in my Startup.cs:
app.UseErrorHandler("/Home/Error");. I also have set the error page to display the exception. This doesn't seem to be hit.
Attached to the remote process to debug. Visual studio eventually freezes, so haven't gotten anywhere with this.
Enabled application insights. This registers events when I debug locally, but doesn't capture anything from the azure instance.
Enabled application logs and request failure tracing. The detailed errors show a 500.0, without much detailed information.
Imgur
Imgur
I've also verified through the console that the runtime is set correctly to beta5.
Update:
I set the ASPNET_ENV to Development and it loaded with appsettings loaded via the azure portal. Setting ASPNET_ENV to something else isn't working. I also removed any custom code from startup.cs pertaining to the non-development environments, with no help. I'm still looking for a means of capturing the original error.
Assuming you are targeting DNX451 and not dnxcore50, there is a good chance Azure it still trying to run it against the beta4 runtime instead of beta5. If that's the case, you won't get a decent error message.
Try adding an environment variable in Azure "SCM_DNX_VERSION" and set it to 1.0.0-beta5. It looks like kudu was recently upgraded to support beta5 https://github.com/projectkudu/kudu/commit/55175a017779bf493ff8e6ce87b96dd1451f7d7b, so you might want to try to redeploy from bitbucket in the case that the Kudu team has already deployed this change.
For a little more detail, you can check out my previous answer (although it is very dated and references the old "K" names) here:
Deploying ASP.NET vNext beta 2 on Azure with Kudu
Every time you update to a new beta, you will have to update your SCM_DNX_VERSION environment variable.
I'm totally new to web deployement. I did set up a deploy on one of my project, I did the same thing on another one. But when I try to publish my website, I have this error with no code.
I don't even know where to search for the log file on the IIS server. Can you tell me, Everything is running with default configuration. I just need to know where to find the information so I can publish my website.
I finally found this blog where the solution is explained : http://bartwullems.blogspot.fr/2013/01/webdeploy-error-systemunauthorizedacces.html
I didn't know where to look for the logs but once I found the right log, the error is : System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. at System.Security.AccessControl.Win32.SetSecurityInfo
I am getting an error message on my website:
The page cannot be displayed because an internal server error has occurred.
How do I troubleshoot this. I can't find the log file. Please help.
Some information on debugging youe node.js site on Azure websites can be found here:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-debug/
and here: http://www.hanselman.com/blog/StreamingDiagnosticsTraceLoggingFromTheAzureCommandLinePlusGlimpse.aspx
To enable application logging instead of updating the iisnode.yml file, you can also use the portal and from the Website/CONFIGURE tab you can enable application logging to file system.
Also look into: http://blog.azure.com/2014/03/28/windows-azure-websites-online-tools-you-should-know-about-2/ for an easy way to see the log files without installing any tools.
I am trying to set up an internal nuget feed for my company. I have built the site and deployed it to IIS server. I can install from the site itf I manually add packages to it but I cannot push to it from the command line. When I try to I get prompted for credential (none work) then get an error that says "Cannot access a closed Stream." I have been to NuGet and read everything they propose but none of it works. I am thinking this is a server setting but I have no idea which one. Has anyone encountered this that can share the solution?
Solved this issue by removing WebDAV and adding PUT to the web.config authorization
I just added a comment to the Github issue tracker for a similar (probably identical) problem raised there:
https://github.com/NuGet/NuGetGallery/issues/487
This is probably a result of WebDAV being installed in IIS - it seems to interfere with the settings required for NuGet Gallery. We certainly saw a similar issue with 405 errors, and uninstalling the WebDAV module fixed the problem.