The problem was as Lori has told us all along... I just like seeing those words again. Glad to hear it's fixed for you Ken! Mine (shaking the leftover sage smudge) has not had a single hiccup since I told my users to suck it up.
Now if I ever finish recovering files from my file server disaster (caused by Netshield 4.5) I will probably look into that publishing the calendars on the intranet thing that someone kindly sent me. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 11:24 AM To: Exchange Discussions Subject: RE: Auto Accept Script Well, I finally got it fixed. Thanks to the help and suggestions of all, it is now working. I tried the moving it all to a PST and then moving them back on by one. I could not get it to work since every time that I attempted to do it the system would lock up again. I received several different hotfix CDO.DLLs (q281935, q289606)from Microsoft. None seemed to work; however, one of them did succeed in giving me about 100 or more reminder messages suddenly. As Michael pointed out, it keeps this from happening again, does not fix the current problem. I was never able to get the Exchange client to work for some reason. I was able though to get it up in OWA and delete reoccurring appointments until it started working again. The problem was as Lori has told us all along that the calendar was set up with the Autoaccept script and the ability for users to direct book as well. That has now been changed. For me, it is right up there with PST=BAD. Thanks again to all. Ken Powell Systems Administrator Clark County Office of Budget and Information Services (OBIS) Vancouver, Washington [EMAIL PROTECTED] Voice: (360) 397-6121 x4658 Fax: (360) 759-6001 -----Original Message----- From: Semiglia, Michael [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 2:03 PM To: Exchange 5.5 List Subject: FW: Auto Accept Script The fix does not fix existing corrupted meeting notices, it just prevents future ones. Use the exchange client or OWA in conjunction with Outlook to nail down the corrupted meetings by moving a chuck of meetings at a time to a new folder and then trying to open Outlook. Michael Semiglia -----Original Message----- From: Hunter, Lori [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 3:33 PM To: Exchange Discussions Subject: RE: Auto Accept Script Sometimes you just have to export to PST and add the appts back in chunks to find the bad one. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 1:08 PM To: Exchange Discussions Subject: RE: Auto Accept Script I am currently going through the same thing. I got the updated CDO.DLL but it did not fix the problem. I will let you know what finally fixes it. Ken Powell Systems Administrator Clark County Office of Budget and Information Services (OBIS) Vancouver, Washington [EMAIL PROTECTED] Voice: (360) 397-6121 x4658 Fax: (360) 759-6001 -----Original Message----- From: Semiglia, Michael [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 10:41 AM To: Exchange 5.5 List Subject: FW: Auto Accept Script Sounds like you might have corrupted meeting notice. See technet for post sp4 fixes for CDO. CDO is what the auto-accept script uses. Michael Semiglia -----Original Message----- From: John Martinez [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 1:07 PM To: Exchange Discussions Subject: Auto Accept Script Exchange 5.5 SP4 Windows 2000 SP2 Outlook 2000 SP1 Hi all, I am running the Auto Accept Script from exchangecode.com. I have a secretary that did something that is forcing me to directly access the Calendar for the resource running the script but whenever I try to access it Outlook2000 just hangs. I tried running the /cleanfreebusy several times on Friday but it acts the same. Opens and hangs forever. Does anyone know how I can fix this so I can get to the Calendar? The script is still running fine. John _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
