We had discovered this very same issue, however, this started occurring prior to installing Patch 20. So I don't think this is Patch 20 specific. This is occurring on our development servers that has Patch 18. If anyone has an answer to how it is happening and how it can be corrected we would love to hear it.
Christopher Pruitt Consultant Specialist EDS - Bank of America mailto:[EMAIL PROTECTED] Confidentiality Notice: This message and any files transmitted with it are intended for the sole use of the entity or individual to whom it is addressed, and may contain information that is confidential, privileged, and exempt from disclosure under applicable law. If you are not the intended addressee for this e-mail, you are hereby notified that any copying, distribution, or dissemination of this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately destroy, erase, or discard this message. Please notify the sender immediately by return e-mail if you have received this e-mail by mistake. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A. Sent: Tuesday, February 27, 2007 9:51 AM To: [email protected] Subject: Re: Problem With ARS 6.3 Patch 20 and Querying Join Forms We experienced the same issue but we did not install patch 20 on our User tool. I confirmed that the issue does not occur on our production environment which is on patch 16 but it happens on our development environment which is on patch 20. It seems this is not an issue with Patch 20 for the client but Patch 20 for AR Server. We are on Windows 2003 for our application servers. Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Derek Berube Sent: Tuesday, February 27, 2007 10:34 AM To: [email protected] Subject: Problem With ARS 6.3 Patch 20 and Querying Join Forms Good morning listers. I was just curious to know if anyone else has encountered this little peculiar aspect of AR System behavior. We upgraded to ARS 6.3 Patch 20 (running on a Solaris 8 server) and now, if you go to a Join form in the ARS User tool and try to search using the Query By Example method and placing a value in the 'Join Request ID' field, then you get the following error message when trying to initiate the search. ARERR [101] Entry ID parameter value is longer than the maximum allowed length However, if you go to the advanced search bar and issue the following query, the search executes. 'Join Request ID' = "NOM000000000037|NODE00000000001|000000000101931" This happens whether the user is running with the ARS 6.3 Patch 20 or 7.0.1 patch 1 User tools. Derek ______________________________________________________________________ Derek Berube <[EMAIL PROTECTED]> Wildstar Technologies, LLC. 1453 Riverview Run Lane Suwanee, Georgia 30024 (678) 229-1475 - Office (678) 229-1476 - FAX (404) 444-5283 - Mobile http://www.wildstartech.com/ AIM Handle: BerubeDB Jabber: [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] Yahoo! Messenger: derekberube ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
