Microsoft Knowledge Base Email Alertz

KBAlertz.com: Event Viewer incorrectly displays IPv6 addresses in event descriptions

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 2.0 Web Hosting with SQL 2005: Click Here!
Discount ASP.NET Hosting


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




In Windows, Event Viewer incorrectly displays IPv6 addresses in event descriptions

Article ID:934640
Last Review:April 17, 2007
Revision:1.2

SYMPTOMS

In Windows, when you use Event Viewer to view an event log that contains Microsoft Internet Protocol version 6 (IPv6) addresses, the IPv6 addresses do not display correctly in the descriptions of events. For example, an element of the event log payload replaces the scope ID part of the IPv6 address. In some cases, the multiple replacements are repeated several times in the IPv6 address.

Back to the top

CAUSE

This problem occurs when the IPv6 address contains a scope ID. A scope ID is represented by a percent sign (%) that is followed by a number.

In the following example, the IPv6 address contains a scope ID of 1:
1234:5678:90123:4567:8901:2345%1
Such an address will not display correctly in Event Viewer.

The event descriptions are formed by using a template and by using replacement values from the event payload. You do this by replacing any percent sign that is followed by a number with the appropriate event parameter.

In the 1234:5678:90123:4567:8901:2345%1 example, %1 will be replaced with the first parameter from the event payload. This replacement may be repeated multiple times. The number of times this replacement is repeated depends on the version of the operating system. Multiple replacements will occur if the parameter number that contains the IPv6 address matches the scope ID.

Note You cannot use an escape character to replace the percent sign in the IPv6 address.

Back to the top

WORKAROUND

To work around this issue when you publish a series of events into an event log, use one of the following methods:
•Preprocess the IPv6 parameters to make sure that the scope ID is removed. For example, use the following IPv6 address format:
1234:5678:90123:4567:8901:2345
•Preprocess the IPv6 parameters to make sure that a character, such as space, is inserted between the percent sign and the numeric scope ID. For example, use the following IPv6 address format:
1234:5678:90123:4567:8901:2345% 1
Other workarounds including the following methods:
• Remove the parameter that contains IPv6 address from the event description.
•Add the parameter to the binary data that is associated with the event.

Back to the top


APPLIES TO
•Windows Vista Ultimate
•Windows Vista Home Premium
•Windows Vista Business
•Windows Vista Enterprise
•Windows Vista Home Basic
•Microsoft Windows XP Professional
•Microsoft Windows XP Home Edition
•Microsoft Windows XP Media Center Edition
•Microsoft Windows XP Tablet PC Edition
•Microsoft Windows Millennium Edition

Back to the top

Keywords: 
kbtshoot kbeventlog kbexpertiseinter kbprb KB934640

Back to the top

       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please