[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 14405
  • Last Modified:

Outlook 2007 getting error 0x80190194 when connecting to a new Exchange 2007 install

I am in the process of updating my company and am setting up a new Exchange 2007 server in a new domain.  I have setup Exchange 2003 before, but this is my first time touching 2007 and it has changed a lot.  
I did a full install of all Exchange services on the server, then created an AD user as well as an Exchange mailbox for myself.

When I went to my laptop (already joined to the new domain) and tried to connect my Outlook 2007 to the Exchange server I receive "Task 'Microsoft Exchange' reported error (0x80190194) : 'The operation failed.'".  I need help figuring out what is causing this (since I am new to Exchange 2007) and how to fix it.

Thanks
0
jjwolven
Asked:
jjwolven
1 Solution
 
briancassinCommented:
see if this information helps

Error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB
You can receive the following error (0x80190194) in Outlook when trying to download a Web Distribution only enabled Offline Address Book. The error 0x80190194 is an HTTP 404 error:

C:\WINDOWS\system32>err 0x80190194
# for hex 0x80190194 / decimal -2145844844
BG_E_HTTP_ERROR_404 bitsmsg.h
# 1 matches found for "0x80190194"

The reason for this error message is that when an Outlook 2007 client downloads the OAB files they are not being found on the Client Access Server.

Here is the flow for downloading the OAB:

An Outlook client starts up.
The Outlook client talks to the autodiscover service and retrieves the autodiscover.xml file which contains the URLs for all of the Exchange Web Services.
The Outlook client parses this autodiscover.xml file and looks for the <EXCH> section which is for the internal corporate network, and <EXPR> for Outlook Anywhere (External).
You select Tools | Send/Receive | Download Address Book.
The Outlook client looks for the OABUrl which looks like this: <OABUrl>http://OABServer.domain.com/OAB/edb3e44f-c49b-4597-b996-cb1093405985/</OABUrl>.
Once the Outlook client locates the OABUrl the Outlook client makes a HTTPS connection to the OAB Web Virtual Directory specified in the <OABUrl>.
If the connection to the OAB Web Virtual Directory is successful the Outlook client  it will look in the directory for the OAB you are download and retrieve the OAB.xml file.
The Outlook client will examine the OAB.xml manifest file and find out what OAB files are needed for updating the Outlook client's local copy of the OAB.  
Now, the Default OAB Web Site on the Client Access Server will have a local directory associated with it that has the path of: <Drive Letter>:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB. This is the location for the OAB files when they are copied over from the Mailbox server by the FDS (File Distribution Service).

If you are in a single server site these OAB files should be copied over immediately to this directory after the OAB has been generated. If you have a multi-server site where your  Client Access Server that is separate from your Mailbox server that is generating the OAB, the OAB files will be copied over under a few situations (not all are listed here):

A new OAB is created
A change to the OAB has happened
The OAB Generation Server has changed
The Default Polling Interval is up (this is 8 hrs by default).
There are new OAB files (new binpatch.oab file has been created).
One way to tell if your OAB files have been replicated to the Default OAB Web Site is to look for the event id 1008 in the application log. This event will be logged by the FDS (File Distribution Service) on the Client Access Server.

Event Type: Information
Event Source: MSExchangeFDS
Event Category: FileReplication
Event ID: 1008
Date: 11/28/2006
Time: 1:55:46 PM
User: N/A
Computer: OABServer
Description:
Process MSExchangeFDS.exe (PID=2484). Offline Address Book data synchronization task has completed successfully. OAB name: "Default Offline Address Book", Guid: edb3e44f-c49b-4597-b996-cb1093405985

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If the OAB files are missing you will need to find out why the FDS service is not replicating them.

Workaround 1

Run 'net stop MSExchangeFDS' and then 'net start MSExchangeFDS' to restart the Microsoft Exchange File Distribution Service on your (All in one Exchange Server) or on your Client Access Server.
Check for the 1008 event id after the services are restarted.
Workaround 2 - This is just a workaround ONLY until you get the FDS replication fixed

You can go your mailbox server (OAB Generation Server) and go to one of the following locations:
Local directory - C:\Program Files\Microsoft\Exchange Server\ExchangeOAB
Unc path - \\ExchangeServerName\OAB\<GUID of OAB>
Copy the OAB directories that are needed for your clients over to the client access server location:
c:\Program Files\Microsoft\Exchange Server\Client Access\OAB\
Once the files have been replicated to this directory the Outlook client will be able to download them and you will not receive this error.



You may also want to look at this

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2253159&SiteID=17
0
 
jjwolvenAuthor Commented:
I checked the Event Viewer, and event 1008 shows up already.

I stopped and restarted MSExchangeFDS with no difference.

I went to try Workaround2 as noted, but the directory was already there.

After trying all of that the same error is still occurring.  Is there something I might have missed or need to check?
0
 
jjwolvenAuthor Commented:
Is there anything else I can try?  All that was done and I still receive the error.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
jjwolvenAuthor Commented:
I have everything fixed and running to send and receive email through the exchange server, but I am still getting this error.
0
 
briancassinCommented:
have you tried redoing the account on the laptop ?
0
 
jjwolvenAuthor Commented:
It is happening on multiple computers.
0
 
briancassinCommented:
try this too

If FDS states that it has replicated the files they should be there. If you want to run a test to see if anything else is going on you can do the following:

1. Delete all of the OAB folders in the distrubition point.

2. Open both directories for the OAB and \Client Access\OAB

3. Change the polling interval to 2 minutes (this will speed up the test). Run Get-OabVirtualDirectory| Set-OabVirtualDirectory -pollinterval 2. (You will want to change this back after).

4. Rebuild your OAB and then watch to see if the folder gets replicated over.

If your still getting this error it is equal to a 404 file not found
0
 
itgrooveCommented:
One followup note from a different perspective. I had the same errors/issues but in my case, it was because my OAB settings (set in the dialogs) weren't being set, because Exchange couldn't do any Remote Procedure Calls (RPC's) to itself.  It turned out the local Remote Registry Service was disabled on my Exchange Server (which was a Windows 2008 Server box).  I enabled that, went in and unchecked/checked the OAB boxes and voila, my problem was sorted.
0
 
malbotejuCommented:
excellent post briancassin
0
 
rafatifardCommented:
How did you enabled that ?
0
 
helpdesk2300Commented:
Good Afternoon All,

One of my clients is currently experiencing this issue. I've checked all the solutions stated above and it still gives an error when i go to a client computer and try to download the address book. None of their new users are showing up in the GAL, all the older users show up just fine, but any recent changes don't show up. The OAB folders are populated and users can search for other users, however, updating fails, any ideas?

Thank you!
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now