Follow up answer to this problem: It turns out to be a "bug" in the Outlook client. If you give additional rights beyond "Editor" to any DL or Default then the Outlook client will produce the below listed errors. So, you should only grant Editor and Author rights when using the direct booking methods.
david -----Original Message----- From: Tony Hlabse [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 19 June, 2002 2:19 AM To: Exchange Discussions Subject: Re: From nirvana to hell in one upgrade - the tail of direct booking in Outlook 2k+ Are all the clients running the same version of Outlook? SP1a I think fixed some Free/Busy issues. Try www.slipstick.com for more info. ----- Original Message ----- From: "Moore, David K" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Wednesday, June 19, 2002 3:06 PM Subject: From nirvana to hell in one upgrade - the tail of direct booking in Outlook 2k+ Here's the story - Running Exchange 5.5 and users booking appointments using the AutoAccept script from ExchangeCode.com - and my life is great (except for those darn reoccurring meetings from time to time). Now we make the big move to E2K and since the autoaccecpt script "doesn't" (some reports say it does, some it doesn't - my testing says it doesn't) work on E2K... so I need to come up with a new method. The two methods are using the really old method of leaving an Outlook97 machine logged in with all the resource accounts setup to delegate their appointments to the one dedicated Outlook97 account -or- use the new fangled Outlook 2000/2002 direct booking feature (Direct Booking of Resource Without a Delegate Acct. [Q196534]) where in the client directly books their own meetings using Outlook. Ok, I test it (the new direct book method) and all seems ok. But... when I roll it out into production I have random users (dozens out of 4,000 users) that can not book onto a room because Outlook first declines the meeting because it says it is "busy" and then follows that up with an error of "Unable to save Free/Busy". So, in trouble shooting I have narrowed it down to the client by: * Happens even if the user logs into another machine with their account (without roaming profiles) * Deleting the free/busy file of the calendar (using the GW-Client) and then re-setting it up fixes it from time to time * Granting Owner rights also "sometimes" fixes the problem but not always Is there anyone out there that is using the new OL2000+ direct booking method and has it working correctly? Is there some way to get the exchangecode.com script working on E2K? david moore Chevron Phillips Chemical Messaging Group _________________________________________________________________ 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]
