We logged an issue a few months ago. We noted that we had a work around and Support resolved the ticket. Since this never addressed if it was a bug or working as designed we had it reopened. It seems that some times you just need to keep pressing. Dave ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thad Esser Sent: Monday, February 26, 2007 1:50 PM To: [email protected] Subject: Re: Caught exception :Object Expected (Resolved-sort of) ** I was poking around this issue a little more and you also get the error if you don't have any preference server configured. As far as I understand it, having a preference server is NOT a requirement of using Mid-Tier, is it? I would think this is a Mid-Tier bug. The response from BMC Support, "we are aware of the workaround. <snip> Please let me know how you would like me to handle this ticket further for you." Um... how about you fix it? I know.. that's just crazy talk. Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "Thad Esser" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 02/26/2007 09:43 AM Please respond to [email protected] To [email protected] cc Subject Re: Caught exception :Object Expected (Resolved-sort of) ** Mary Ann, Setting the Time Zone on the Locale tab of the User Preference record has worked for two of us here now. Thank you for pointing in the right direction. This was tested on Patch 21, so it sounds like the same fix works for 20 and 21. Although I won't attest to the fitness of patch 21 yet. Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "Mary Ann" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 02/23/2007 11:16 AM Please respond to [email protected] To [email protected] cc Subject Re: Caught exception :Object Expected We are having the same problem on our Mid-Tier - 'Caught Exception: Object Expected' when displaying any time fields after installing Patch 20 on Mid- Tier 6.3. The problem only seems to be happening from Windows XP machines. When I access the Mid-Tier from a Windows 2000 server, it does not happen. To solve the problem temporarily, I added a User Preference record for each user and set the Locale Timezone value in the record to America/Chicago (since all our users are on Central Standard Timezone). Based on what Lynn did, I'm going to try to re-install Patch 20 by manually replacing the files instead of re-running the installers. BMC suggested Patch 21 also (limited release) but I'm not ready to try that yet based on Thad still having the same problem. Thanks for all the valuable information. Mary Ann On Fri, 23 Feb 2007 13:31:44 -0500, Axton <[EMAIL PROTECTED]> wrote: >We are observing a series of caught exception errors with MT 7.0.01 >p001. They come and go. For a 5-10 minute window, anyone that logs >into the mid-tier will get the following error: > >Caught Exception :'this.mColFields[...].mObj' is null or not an object. > >After the window, the error can not be reproduced, until it occurrs >the next time. It's very frustrating because I can find nothing to >link the error to any specific event. I've had a ticket open for a >little over a week, and I'm supposed to have a webex today; we'll see. > >Axton Grams > >On 2/23/07, Lucero, Michelle - IST contractor ><[EMAIL PROTECTED]> wrote: >> ** >> Hi, Thad: >> >> Mid-Tier 7.0.01 (Windows 2003/IIS/Java 1.6/Apache Tomcat 5.5) >> ARS 6.3 P18 and P20 >> Windows 2003/SQL Server 2000 >> >> We too we're receiving Caught Exceptions, except they were the "permission >> denied" type. They started happening after we started using Mid-Tier >> 7.0.01 Patch 1 in both dev and production. >> >> I was able to duplicate that error repeatedly by following a few steps. I >> came in yesterday morning and was about to send a bunch of logs to tech >> support regarding this. But, something very interesting happened on >> Thursday morning. The Windows Automatic Live Update loaded updates. I >> assume some were IE related and no one, not even the person that originally >> reported the error can duplicate the caught exception errors, anymore. >> >> The errors have magically disappeared in both Dev and Production >> environments at the same time. So, I wonder if (at least in our case) that >> it was IE or possibly Windows related? >> >> We're still investigating the mystery to this fix. >> >> Thanks, >> Michelle >> ________________________________ >> From: Action Request System discussion list(ARSList) >> [mailto:[EMAIL PROTECTED] On Behalf Of Thad Esser >> Sent: Thursday, February 22, 2007 7:19 PM >> To: [email protected] >> Subject: Caught exception :Object Expected >> >> ** >> Hello, >> >> We are getting this error, "Caught exception :Object Expected", on our >> mid-tier patch 21 (21 is a restricted release, but this was happening on >> patch 20 as well) whenever we click on the calendar button for a date/time >> field or try to view a record after a search. We are doing the "send us >> your logs" dance with BMC, but since its been going on for a few weeks, I >> thought I'd ask here. >> >> I read through the other "Caught exception" posts even though they were for >> a different exception. There are no pop-up blockers involved, the MT cache >> has been flushed as well as the local IE cache on two different PCs. This >> wasn't happening when MT was at patch 14. >> >> Has anyone else seen this particular error or can offer any advice? >> >> Thanks in advance, >> Thad Esser >> Remedy Developer >> "Argue for your limitations, and sure enough, they're yours."-- Richard Bach >> >> ***IMPORTANT NOTICE: This communication, including any attachment, contains >> information that may be confidential or privileged, and is intended solely >> for the entity or individual to whom it is addressed. If you are not the >> intended recipient, you should delete this message and are hereby notified >> that any disclosure, copying, or distribution of this message is strictly >> prohibited. Nothing in this email, including any attachment, is intended to >> be a legally binding signature.*** >> __20060125_______________________This posting was submitted >> with HTML in it___ >> __20060125_______________________This posting was submitted >> with HTML in it___ > >_______________________________________________________________________ ___ _____ >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" ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** __20060125_______________________This posting was submitted with HTML in it___ ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
