Lucky! LOL
Candace DeCou DOI Remedy Systems Analyst Verizon Business Office: (408) 371-1112 Email: [EMAIL PROTECTED] Verizon Business - global capability, personal accountability. This e-mail is strictly confidential and intended only for use by the addressee unless otherwise indicated ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Tuesday, June 10, 2008 7:58 AM To: [email protected] Subject: Re: Caught Exception Error - RESOLVED Okay, so even though it shouldn't....clearing the cache fixed it. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Decou, Candace M Sent: Tuesday, June 10, 2008 9:35 AM To: [email protected] Subject: Re: Caught Exception Error ** William - we had a very similar situation with a caught exception error being thrown only in Dev but not in production (which were supposedly identical). BMC support wasn't able to help even after tons of workflow and mid-tier logs, BUT when we refreshed our Dev environment from the production environment again the problem ceased to exist. If you have the bandwidth you might try a DB restore from your dev environment to your QA environment and see if that resolves it. What I found when going through this problem is that there was a particular field that the system thought was missing on an active link firing for set fields (different form, different app though). I could find the field, unhide it, see it being set but in the mid-tier it still presented us with errors and in the thick client it presented errors also. Absolutely no amount of troubleshooting helped at all. Even an import of the form in place from the good environment to the dev environment didn't help. It was only after another restore of the 'good' DB to the dev system that the problem cleared up. And I can't tell you why. We are on ITSM 7.03 Patch 6. Candace DeCou DOI Remedy Systems Analyst Verizon Business Office: (408) 371-1112 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Verizon Business - global capability, personal accountability. This e-mail is strictly confidential and intended only for use by the addressee unless otherwise indicated ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Tuesday, June 10, 2008 7:22 AM To: [email protected] Subject: Caught Exception Error In IM 7.03 using the web and going to... Application Admin > Custom Config > Foundation > People > People I do a search by user ID and get the following error: Caught exception :'t.LoadResultsList' is null or not an object This is our QA system. It is IDENTICAL to our DEV system and the DEV system does not throw this error. All of the AR Server and Mid-tier config settings are the same. I checked previous ARS list posts about "Caught Exception" errors and none of them applied to this (checked duplicate fields, results list, etc etc). In fact, Migrator says our two copies of CTM:People on the servers are the same as well. Vital stats of the system AR Server 7.1 patch 001 on Solaris IM 7.03 AR Mid-tier 7.1 patch 001 on Solaris (separate box) with IBM HTTP Server + Websphere. William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
