Quote:
quote:Originally posted by englere
.. or else just avoid using the custom events (remove from web.config).
|
First I tried to remove the line:
<add name="TBH Events" type="MB.TheBeerHouse.WebCustomEvent, MB.TheBeerHouse.CustomEvents" />
after that I removed the tag eventMappings, after that the complete tag healthMonitoring (details about the part in web.config see below).
The result was allways, that the errors remained.
But the method of Catalyst (opening as Website on the TBH_Web folder) worked.
Christian
<healthMonitoring heartbeatInterval="10800" >
<providers>
<remove name="SqlWebEventProvider" />
<add name="SqlWebEventProvider" connectionStringName="LocalSqlServer"
buffer="false" bufferMode="Notification" maxEventDetailsLength="1073741823"
type="System.Web.Management.SqlWebEventProvi der,System.Web,Version=2.0.0.0,Culture=neutral,Pub licKeyToken=b03f5f7f11d50a3a" />
</providers>
<eventMappings>
<add name="TBH Events" type="MB.TheBeerHouse.WebCustomEvent, MB.TheBeerHouse.CustomEvents" />
</eventMappings>
<rules>
<clear />
<add name="TBH Events" eventName="TBH Events" provider="SqlWebEventProvider" profile="Critical" />
<add name="All Errors" eventName="All Errors" provider="SqlWebEventProvider" profile="Critical" />
<add name="Failure Audits" eventName="Failure Audits" provider="SqlWebEventProvider" profile="Critical" />
<add name="Heartbeats" eventName="Heartbeats" provider="SqlWebEventProvider" profile="Critical" />
</rules>
</healthMonitoring>