An Error occured while creating EventSource, The Source and Log properties must be matched, or you may set Log to the empty string

-
If you get
"
The source 'xxx SourceName' is not registered in log 'xxx LogName'. (It is registered in log 'Application'.) " The Source and Log properties must be matched, or you may set Log to the empty string, and it will automatically be matched to the Source property.
"

while calling System.Diagnostics.EventLog.CreateEventSource with sourceName and LogName params,Just check registry whether SourceName is not registered in any other LogName(s).
Verify LogName and SourceName in the Operationg Sytem is unique via REGEDIT;
HKLM\System\CurrentControlSet\services\eventlog\|...
if it is defined previously, you can not create . You must delete or change SourceName.


regards,
P.S:Please do not hesitate to share your comments.

Comments

Post a Comment

Popular posts from this blog

Complex Query in QueryExpression in Microsoft CRM 2011

-
Hi, Here is tables and relation,QueryExpression statement afterwards. contact 1--->N new_ticket N --> N new_tour QueryExpression query = new QueryExpression()                     {                         EntityName = "contact",                         ColumnSet = new ColumnSet(new string[] {                                                             "contactid",                                                             "firstname",                                                             "lastname",                                                             "birthdate",                                                             "fullname"                                                             }                                                   )                     }; Query Expression will execute the query against contact. For performance issue; do not retrieve any columns that we do
Read more

Exception caught instantiating TERADATA report server extension SQL Reporting Services

-
Hi, If you face an error in Reporting Services Log File (C:\Program Files\Microsoft SQL Server\MSRSxx_xx.MSSQLSERVER\Reporting Services\LogFiles) such as : extensionfactory!ReportServer_0-1!ea4!03/26/2013-08:20:15:: e ERROR: Exception caught instantiating TERADATA report server extension:  System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.  ---> System.IO.FileNotFoundException: Could not load file or assembly 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c' or one of its dependencies. The system cannot find the file specified. File name: 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c'    at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)    at System.Refl
Read more

Microsoft Power Apps Portal integration with Dynamics 365 CE On-Premise - Step By Step Guide

-
Image
 Hello, It has been quite long since I did not post any guides with you. Today, I am going to share a PoC of mine result with detailed screenshots as much as possible.  You will see how we can easily position Power Apps Portal in front of Dynamics 365 CRM ( CE ) Engine 9.x on-premise edition. You are going to see following subjects in the study; Solution generation for the scenario in Dynamics 365 CRM on-premise  Create Solution Create Custom Entity Add Existing entity to a custom solution 1:N relation Form creation for Portal visibilities for portal specific fields Microsoft Common Data Service (Microsoft Dataverse) - an environment -creation Solution generation for the scenario in Dynamics 365 CRM on-premise  Microsoft Power Apps Portal creation (Starter Portal) in the environment Microsoft Dynamics 365 On-Premise customization for PoC Scenario implementation Reflecting Dynamics 365 On-Premise solution to CDS (Microsoft Dataverse) - to the environment- Aligning Microsoft Power Apps P
Read more