There's always the time-proven: "Inky dinky winky pow! I order you to work now!"
If that fails, then use: "I SUMMON THE VAST POWER OF CERTIFICATION!!!" If THAT fails, then use: "Finite Incantatem" -Paul -----Original Message----- From: Michael B. Smith [mailto:mich...@theessentialexchange.com] Sent: Wednesday, February 25, 2009 3:04 PM To: MS-Exchange Admin Issues Subject: RE: OAB 0X8004010F Error Truth be told (and I spend a ridiculous amount of time doing these things, far above what I can possibly bill my clients) you can debug this kinda stuff. It's just a pain-in-the-rear and it is far faster to make the ministrations than to debug and then fix. -----Original Message----- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Wednesday, February 25, 2009 3:59 PM To: MS-Exchange Admin Issues Subject: Re: OAB 0X8004010F Error Well, at least you think it did, and that's what's important, right? Heh. I love systems so complex (Exchange/AD) that cargo cult ministrations and incantations are sometimes all that's available. Kurt On Wed, Feb 25, 2009 at 08:11, Roger Wright <rwri...@evatone.com> wrote: > > Yep, appeared randomly for me as well. Going through the steps corrected it, though. > > Roger Wright > > Network Administrator > > Evatone, Inc. > > 727.572.7076 x388 > > _____ > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Wednesday, February 25, 2009 10:55 AM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > And the errors just started again today all on it's own... go figure. > > > > ________________________________ > > From: Roger Wright [mailto:rwri...@evatone.com] > Sent: Monday, February 23, 2009 5:08 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > Exactly what happened to me mid-last year. Struggled for a couple weeks, then *Poof!* - all was well again. > > > > About a month ago had the issue again, this time it was resolved within 24 hours. > > > > > > > > Roger Wright > > Network Administrator > > Evatone, Inc. > > 727.572.7076 x388 > > _____ > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Monday, February 23, 2009 5:53 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > I don't need to try it again - it just started working on it's own! (You must have missed that from my original post...) > > > > The problem just magically went away after a month of me taking all the necessary steps to resolve the issue. > > > > Weird. > > > > ________________________________ > > From: Roger Wright [mailto:rwri...@evatone.com] > Sent: Monday, February 23, 2009 4:44 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > Try it again, in the order I listed. Wait until morning to see if it's resolved. Worked for my, YMMV. > > > > > > > > Roger Wright > > Network Administrator > > Evatone, Inc. > > 727.572.7076 x388 > > _____ > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Monday, February 23, 2009 5:37 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > Um... yes, Jan 28th. A few hours ago ;) > > ________________________________ > > From: Roger Wright [mailto:rwri...@evatone.com] > Sent: Monday, February 23, 2009 4:19 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > You may need to allow several hours to see the results... > > > > > > > > Roger Wright > > Network Administrator > > Evatone, Inc. > > 727.572.7076 x388 > > _____ > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Monday, February 23, 2009 5:15 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > Those are just some of the things I tried on Jan 28th :) > > > > ________________________________ > > From: Roger Wright [mailto:rwri...@evatone.com] > Sent: Monday, February 23, 2009 4:11 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > I was plagued with this issue recently. > > End up deleting the OAB(s), recreating it, rebuilding it, then reassigning it on each Exchange DB. > > > > > > > > Roger Wright > > Network Administrator > > Evatone, Inc. > > 727.572.7076 x388 > > _____ > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Monday, February 23, 2009 4:54 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > Oddly enough, I noticed these errors just stopped as of yesterday. I have not changed anything since Jan 28th. I finally have a current OAB. > > > > Weird a$$ Exchange. > > > > ________________________________ > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Wednesday, January 28, 2009 2:00 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > Nope > > > > ________________________________ > > From: KevinM [mailto:kev...@wlkmmas.org] > Sent: Wednesday, January 28, 2009 1:45 PM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > Do you have Exchange clustered? > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Wednesday, January 28, 2009 9:11 AM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > > > Total oops! > > > > Everything is 2003 (Client, server, network, outlook), SP2 on exch, single/no replicas. > > > > Public folder structure: > > > > 'New' is a test OAB I created last night to make sure changes were being updated to the system folders. Not sure what the EX:/ folder is all about. Dates on the contents are very very old. > > > > ________________________________ > > From: Michael B. Smith [mailto:mich...@theessentialexchange.com] > Sent: Wednesday, January 28, 2009 11:05 AM > To: MS-Exchange Admin Issues > Subject: RE: OAB 0X8004010F Error > > Exchange version and backend topology? (And yes, it may be relevant) > > > > Regards, > > > > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP > > My blog: http://TheEssentialExchange.com/blogs/michael > > I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php > > > > From: Sam Cayze [mailto:sam.ca...@rollouts.com] > Sent: Wednesday, January 28, 2009 11:37 AM > To: MS-Exchange Admin Issues > Subject: OAB 0X8004010F Error > > > > Yes, the famous 0X8004010F error. Tons of info on the web, I know, but here is a twist that I can't find any information about online: > > > > I only get the download OAB error if I can connected via TCP/IP. If I am connected via HTTPS, the OAB download works great... > > > > I have done all the basis OAB error checking, rebuilt it, checked the public/system folders, made sure an oab is selected for the storage group.. > > > > > > Anyone know of a good place to start looking? > > > > Tia! > > > > Sam > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
