Task 'mail ID' reported error (0x80190194) : 'The Operation failed.'

Hi, Have a look into this blog : http://blogs.msdn.com/b/dgoldman/archive/2006/11/27/error-0x80190194-when-using-an-outlook-2007-client-to-download-a-web-distribution-enabled-oab.aspx It say that first follow these steps : 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. Further steps are explained in link above. Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hi, What's the version of your exchange server?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hi, i got the sol for this issue as mention below: Scenario - CCR cluster Servers In this cluster type nodes do not share the same physical storage; instead, the passive node continuously replicates database updates, but not the OAB files. Therefore, as the OAB Generation process needs access to the results of previous generation, only one CCR cluster node is able to generate the OAB data files, making such cluster basically asymmetric with regard to OABGen. To control this behavior the Exchange setup process creates the registry value 'SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OABGen-Server\EnableOabGenOnThisNode' which contains name of the node installed first, and from now on assumed as ‘primary’ cluster node. Whenever cluster has failed over to the ‘secondary’ node, the scheduled or forced OAB Generation task will log the event id 9395 and finishes. Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9395 Date: 2007-01-26 Time: 1:55:10 User: N/A Computer: OABGen-Server Description: OALGen is running on CCR cluster node which does not have registry value 'SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OABGen-Server\EnableOabGenOnThisNode' or it is not set to this node name. OAB generation will not be performed. With this being said OAB's are still available from both Public Folders and CAS servers, but the data becomes stale and is not updated until the ‘primary’ node becomes active again. If mentioned above registry value is completely missing, or contains name of machine that no longer exists or is no longer part of this cluster, one should change it to the name of the existing node. If Public Folder distribution is not enabled on one or more OABs generated by such CMS, switching to the new node will cause full download by clients, as OAB sequence number will be reset. How To Fix This is an expected error if the ‘primary’ CCR node is temporarily unavailable, so just make sure it is back online ASAP. Otherwise, the following registry key needs to be in place and contain valid cluster node name: HKLM\System\CurrentControlSet\Services\MSExchangeSA\Parameters\Server-Name\EnableOabGenOnThisNode ="ThisNodeName". NOTE: Make sure that you updated the registry value on the CCR node to be the name of the CCR node. Thanks to Mihir for reviewing this blog(Dgoldman's WebLog)!!! SYED Syed