We (Kinetic Data) reported this problem a couple years back. We like to use the GUID as a web parameter -- URLs generally don't like special characters.
We do not use/have CMDB -- so this is a raw ARS issue. The docs say that a GUID is:* (from BMC Dev Network -- which is pretty nice BTW)* *Structure of GUID: * This 30-character identifier is composed of the following: - 2-character prefix, padded with underscore if necessary (default prefix is "ID" if no prefix is supplied) - 12-character server MAC address, or hostname truncated or padded with zeros on the left as necessary - 6-character datetime (seconds, hex, since start of 1 Jan 1970) - 6-character clock ticks (hex, since start of server, with rollover) - 4-character counter So - no mention of non-alpha chars in the definition. In fact - they specify HEX as the character clock ticks. (see my GUID below) We reported the issue -- to the previous ARS Product Manager - he agreed it was a bug. It was fixed in the sense that they changed the [ to a # -- which equally sucks - for our needs. In fact - just ran into a bad GUID today. 6.03.00 patch 20 Windows Here is my GUID -- KR00D0B7A9C485quzmRgU2#IlA#74B (YUP 2 # signs) KR -- 2-character prefix, padded with underscore if necessary 00D0B7A9C485 - 12-character server MAC address quzmRg - 6-character datetime U2#IlA - 6-character clock ticks #74B - 4-character counter So - a pesky bug -- in my opinion. And a hassle to deal with. Meaning - you probably have historic data with bad GUIDs -- so a patched server (with GUID fix) -- may not generate new bad GUIDs - but you still have the historical data to deal with. As an FYI -- one strategy we did was to replace # with X. -John On 9/10/07, Murtuza B < [EMAIL PROTECTED]> wrote: > > ** Known Issue. This was solved by CMDB 1.1 Patch 003 for me. > I had this problem only while generating CMDB instance IDs though. > > If you are having it with plain ARS, then try a higher patch for ARS. > > Regards, > Murtuza Bookwala > > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *remedy arlist > *Sent:* Monday, September 10, 2007 4:13 PM > *To:* [email protected] > *Subject:* Instance ID > > ** > > Hi Arlist, > > I have ARS 6.03 installed on SQL 2000. Some of the instance Id's produced > by Remedy inclueds characters like '[' (ex: SH00110A5FEA769fTbRgY[X4QgbTsG) > which are unable to be resolved by SQL 2000. Please let me know if i can > restrict the system to generate instance ID independent of '[' character, if > not is their a way in which SQL 2000 can read this data. > > Awaiting a speedy reply, > > Regards, > AV > __20060125_______________________This posting was submitted with HTML in > it___ > __20060125_______________________This posting was submitted with HTML in > it___ > -- John David Sundberg 235 East 6th Street, Suite 400B St. Paul, MN 55101 (651) 556-0930-work (651) 247-6766-cell (651) 695-8577-fax [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
