Geek Answers Handbook

Could not find schema information for elmah

I read all the answers already posted here, but no one seems to solve it. Elmah works flawlessly even if I received these warnings. I also got these errors when I run debug (f5) in visual studio 2012. Everything is fine on the assembly.

The section configuration in web.config is simple, so I really don't know how to solve it:

<configuration> <configSections> <sectionGroup name="elmah"> <section name="security" requirePermission="false" type="Elmah.SecuritySectionHandler, Elmah" /> <section name="errorLog" requirePermission="false" type="Elmah.ErrorLogSectionHandler, Elmah" /> <section name="errorMail" requirePermission="false" type="Elmah.ErrorMailSectionHandler, Elmah" /> <section name="errorFilter" requirePermission="false" type="Elmah.ErrorFilterSectionHandler, Elmah" /> </sectionGroup> </configSections> <elmah> <security allowRemoteAccess="1" /> <errorLog type="Elmah.SqlErrorLog, Elmah" connectionStringName="EvaConnection" /> <!--<errorLog type="Elmah.XmlFileErrorLog, Elmah" logPath="~/App_Data/ErrorLogs" />--> <!-- ELMAH class ErrorMailModule.cs has been modified to read config from AppSettings --> <errorMail from="dummy@dummy.com" to="dummy@dummy.com" subject="dummy" priority="High" async="true" smtpPort="25" smtpServer="dummy" useSsl="false" userName="dummy@dummy.com" password="dummy" noYsod="false" /> </elmah>
+8
web-config elmah configsection
source share
2 answers

I think this error is due to the fact that you chose SqlErrorLog as the type of errorLog. Have you run Elmah SQL Server DB Script in a database for which the EvaConnection connectionString parameter is EvaConnection ? If this is not the case, you will need to do this so that the correct tables and stored procedures are created to use Elamh when writing errors to the database.

If you are using a later version of SQL Server than 2005, see the note in the Implementation of ErrorLog - Relational Enterprise Database wiki page for a note about the ntext field ntext .

Update:

Paying more attention to the issue. A relevant post was found in ELMAH Google Group - Could not find schema information This is a problem that Visual Studio reports about an ELMAH configuration item because it does not have a .xsd file. There is a file that can be used to suppress this error / warning message in Visual Studio. Just by following the instructions Problem 239: Intellisense for web.config and external configuration files

+9
source share

I had everything that was, and then I sat, and I also had this error.

Before you begin to solve more complex solutions to this problem:

  • Restart Visual Studio
  • Clear solution
  • Create the solution again.

This solved the problem for me. Something seems to be cached (or broken) in Visual Studio.

0
source share

More articles:


All Articles