Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outlook 2003 - 0x8004010F error - URGENT

Status
Not open for further replies.

maya14

Technical User
May 8, 2007
274
ZA
Joined new company and every new installation of Outlook gives me this error. Task 'MS Exchange Server' reported error (0x8004010F): 'The operation failed. 'An object could not be found'
I have Google this several times but cant seem to fix this.Most say its a OAB problem.No one else gets the error in the organisation except our site. We have DC's and Exchange on different domains. Both online and cache mode gives me errors.
 
Guys i realy need your help on this one.

Every new Outlook installation gives me this problem. I have tried different MSO SP's. Also check the OAB settings on Exchange but users in other sites dont have this problem.
 
And you're not setting the profile to deliver to a (non-existant) local PST file?
 
Delivery is set to Exchange mailbox.
 
Yes i have tried the rebuild. I know it seems like an OAB issue but why is our site/domain the only one having this issue. We all use the same Exchange server.
 
Yes i have seen article. What worries me the most is that users on the Exchange domain dont have these issues. Our users AD account is not on the same domain as Exchange. They have another account on AD for Exchange. We opening Outlook we get prompted for the Exchange domain login.
 
Your AD account is not on the same domain as Exchange? What? Sounds like a cross domain auth issue. What's in the event logs?
 
Don't you just hate it when a poster does all silent on the thread like this?
 
Our Exchange crashed so i have not been unable to test again.
We have AD account on domain A for files shares, login etc. and AD account on domain B for Exchange.DC on our site is for domain A.
 
Do you have a trust in place? Can you not collapse things into one domain?
 
Yes we have trust in place.
I mentioned we had Exchange crash and after restore no more errors for now. Don't what solved it but i'm not complaining about the result.
 
Resolved in good, solved is better. Either is a result...thanks for closure.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top