System might be interpreting the field with colon
inside the [$$ $$] mulitline bracket
remove all the colons : and replace it with a dash -
Chuck G.
On Tuesday, May 8, 2012 3:10:37 AM UTC-5, Aluru, Radhika wrote:
> **
>
> Hi All,
>
>
>
>
>
> I am creating Incidents based on the Incoming Emails in the Remedy
> understandable format. In one email, I had the Detailed description
> mentioned as below. If the Detailed Description contains anything like
> “Name: “, it is failing to create Incidents. If I replace “Name:” with
> “Nam:”, then system is creating tickets.
>
>
>
> I have verified AR System Email error logs and I am getting ARERR 103 with
> the description as “Name parameter (or name field in a parameter) is longer
> than the maximum allowed length null”.
>
>
>
> Any ideas to solve this issue?
>
>
>
>
>
> Detailed Description ! 1000000151!: [$$Alert: FIM Server User Logon
>
>
>
> Source: USHOUFIM01VD.corpdev.dev
>
>
>
> Path:
>
>
>
> Last modified by: System
>
>
>
> Last modified time: 5/3/2012 11:34:30 AM
>
>
>
> Alert description: Event Description: An account was successfully logged
> on.
>
>
>
> Subject:
>
> Security ID: NT AUTHORITY\SYSTEM
>
> Account Name: USHOUFIM01VD$
>
> Account Domain: CORPDEV
>
> Logon ID: 0x3e7
>
>
>
> Logon Type: 10
>
>
>
> New Logon:
>
> Security ID: CORPDEV\d-jacobje
>
> Account Name: d-jacobje
>
> Account Domain: CORPDEV
>
> Logon ID: 0xe1b3e27
>
> Logon GUID:
> {475D8E05-7AD7-6513-548E-ECF2E10F69AC}
>
>
>
> Process Information:
>
> Process ID: 0x17b4
>
> Process Name:
> C:\Windows\System32\winlogon.exe
>
>
>
> Network Information:
>
> Workstation Name: USHOUFIM01VD
>
> Source Network Address: 10.193.224.41
>
> Source Port: 61955
>
>
>
> Detailed Authentication Information:
>
> Logon Process: User32
>
> Authentication Package: Negotiate
>
> Transited Services: -
>
> Package Name (NTLM only): -
>
> Key Length: 0
>
>
>
> This event is generated when a logon session is created. It is generated
> on the computer that was accessed.
>
>
>
> The subject fields indicate the account on the local system which
> requested the logon. This is most commonly a service such as the Server
> service, or a local process such as Winlogon.exe or Services.exe.
>
>
>
> The logon type field indicates the kind of logon that occurred. The most
> common types are 2 (interactive) and 3 (network).
>
>
>
> The New Logon fields indicate the account for whom the new logon was
> created, i.e. the account that was logged on.
>
>
>
> The network fields indicate where a remote logon request originated.
> Workstation name is not always available and may be left blank in some
> cases.
>
>
>
> The authentication information fields provide detailed information about
> this specific logon request.
>
> - Logon GUID is a unique identifier that can be used to
> correlate this event with a KDC event.
>
> - Transited services indicate which intermediate services
> have participated in this logon request.
>
> - Package name indicates which sub-protocol was used among
> the NTLM protocols.
>
> - Key length indicates the length of the generated session
> key. This will be 0 if no session key was requested.
>
>
>
>
>
> Alert view link: "
> http://USHOUSCOM01T:51908/default.aspx?DisplayMode=Pivot&AlertID=%7bcc054f8a-1964-43be-9ce1-6f218bf05049%7d
> "
>
> Notification subscription ID generating this message:
> {34F52EC3-0572-DB7D-CE1E-781CD682B800}$$]
>
>
>
>
>
>
>
>
>
> ****************************************************************
> Confidentiality Note: The information contained in this
> message, and any attachments, may contain confidential
> and/or privileged material. It is intended solely for the
> person(s) or entity to which it is addressed. Any review,
> retransmission, dissemination, or taking of any action in
> reliance upon this information by persons or entities other
> than the intended recipient(s) is prohibited. If you received
> this in error, please contact the sender and delete the
> material from any computer.
> ****************************************************************
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
