471,618 Members | 1,285 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,618 software developers and data experts.

EventID and EventSource Problems

Hi guys,

I have an application that handle errors and log it at windows event log.
When we are logging events, we are changing the application source to use
our custom source (ex: MyApp) or maintaing "Application" source.

And to do it, we have to write a project installer that registers
necessaries keys at windows registry. Until now, everything is all right.

But we've customized our event IDs too. So thats the problem. When we look
events w/ event viewer, we've gotten messages like this:

The description for Event ID ( 31999 ) in Source ( Application ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: Log
Type: 'ExcLog';

So, how can I create a Event ID for Event Source ?
Thanks in advanced.

best,
wellington.

Feb 23 '06 #1
2 2104
Hi Wellington.
So, how can I create a Event ID for Event Source ?


Have you created and registered the corresponding Message file for your
custom event source?

If not, you may need to provide it--Message files are text files that
contain information about the various messages and categories that
applications want to support. These text files are then compiled as
resource DLLs. You can define your own Event ID and its description in the
message definition file, then use MC.exe to build it into a Message file,
and register it as well as your event source. Please refer to the following
article for the details:

Getting the most out of Event Viewer
http://www.codeproject.com/dotnet/ev...sp#xx1338258xx

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Feb 24 '06 #2
Hi Gary,

Thank you for your reply. Its must be very usefull.

Best,
Wellington.

""Gary Chang[MSFT]"" wrote:
Hi Wellington.
So, how can I create a Event ID for Event Source ?


Have you created and registered the corresponding Message file for your
custom event source?

If not, you may need to provide it--Message files are text files that
contain information about the various messages and categories that
applications want to support. These text files are then compiled as
resource DLLs. You can define your own Event ID and its description in the
message definition file, then use MC.exe to build it into a Message file,
and register it as well as your event source. Please refer to the following
article for the details:

Getting the most out of Event Viewer
http://www.codeproject.com/dotnet/ev...sp#xx1338258xx

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Mar 2 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

14 posts views Thread by Jim Hubbard | last post: by
5 posts views Thread by Corky | last post: by
1 post views Thread by Crea-Ue. Kirdar | last post: by
1 post views Thread by ipramod | last post: by
1 post views Thread by Jeff | last post: by
1 post views Thread by baburk | last post: by
1 post views Thread by XIAOLAOHU | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.