"The Operation Failed. An object could not be found."

  • Thread starter Thread starter Michael Sainz
  • Start date Start date
M

Michael Sainz

Hey all,
Heh...yes...I have read KB312354. This didn't work. Here is the
situation. Out of 12 client computers (SBS2k3, WinXPPro) 1 is getting this
error. I have created another profile and used it to try and connect up to
the Exchange server, but under the new profile I get the same error. From
what I have read, it has to do something with the offline address book, so I
went to the system manager, right clicked, and selected rebuild. No love
there either. This is a rather important client of ours and this problem
seems so simple, but i'm just not seeing it. Any help is MUCH appreciated!

Michael
 
In
Michael Sainz said:
Heh...yes...I have read KB312354. This didn't work. Here is the
situation. Out of 12 client computers (SBS2k3, WinXPPro) 1 is getting
this error. I have created another profile and used it to try and
connect up to the Exchange server, but under the new profile I get
the same error. From what I have read, it has to do something with
the offline address book, so I went to the system manager, right
clicked, and selected rebuild. No love there either. This is a rather
important client of ours and this problem seems so simple, but i'm
just not seeing it. Any help is MUCH appreciated!
Click to expand...

Hi Michael,

If you start Outlook with /safe from the command line does this error appear
again?
 
We are also experiencing this exact problem. We're having this issue on
more than one client, however - it's happening on quite a few folks.

Here's what I've tried:

- Rebuilding the OAL (works fine, no errors, but clients still receive
errors when syncing)

- Creating a new OAL with a different name and waiting for store
maintenance/replication - same results

- Changing the OAL server that generates list... no dice

- Rebuilding the profile on the client machine... still doesn't work.

- Reset system folders... still the same results.

There's a bad, bad bug here that isn't covered in the MSKB, I'm betting...

So far the only way to get clients to stop complaining about it is to
disable cached exchange mode or disable downloading of the address book in
send/receive options.

--JM

--
Vermyndax@[[[NOSPAM]]]galaxycow.com
http://blogs.galaxycow.com/vermyndax

Because this E mail address is transmission exclusive use, message it does
not reply, fish prayer it is to call it does.
 
Much the same problem here with 140 clients and i have tried all of the
suggestions below. Almost tempted to put the clients back to a local pst file
just to stop the phone going.

I originally thought it had something to do with Outlook 2003 and cached
mode as my 2000 and 2002 clients dont seem to be having this problem.

I recently put in a new 2003 server with SP1. The older one it replaced
didn't have SP1 on it and i didn't have these issues.

Will be interesting to see what you come up with

Scott
 
Back
Top