Re: Outlook 2k7 and Ex2k7 -> 0X80190197

Outlook 2007 clients will use the proxy settings that are in IE or used in the WinAPIs. Good luck!!

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Dgoldman
http://blogs.msdn.com/dgoldman


"John Fullbright [MVP]" <fjohn@donotspamnetappdotcom> wrote in message news:%23sPuSmRUHHA.3316@xxxxxxxxxxxxxxxxxxxxxxx
If the client hosts have been updated with 842309, then you can do a GPO to push the reg setting (UseLMCompat). It beats walking around to individual machines.

The adm template would look something like:

CLASS MACHINE

CATEGORY "SOFTWARE\Microsoft\Windows\CurrentVersion\BITS"
KEYNAME "SOFTWARE\Microsoft\Windows\CurrentVersion\BITS"

POLICY "UseLmCompat"
PART "UseLmCompat"
NUMERIC
DEFAULT 00000000
VALUENAME "UseLmCompat"
END PART
END POLICY

END CATEGORY


"Derek Martin" <argo_martin@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:3865A343-7C8C-46CA-A053-E50AA69BBA72@xxxxxxxxxxxxxxxx
That is fantastic! After searching around google last night, the only instances of that error showed to be from various apps that did use Bits! After digging a bit more, I noticed that our CEO didn't have this problem (he doesn't go through a proxy!!!!) - and my final confirmation was (we're a small company) - disabling the entire proxy for the enterprise to confirm it and sure enough - BINGO!!! Four days of searching...thank you all so much for your help and research. That rounds out my list of upgrade woes - we're now (at the moment!!! haha) error free on EX07!!!

Thank you again!

Derek

"Dave Goldman [MSFT]" <Dgoldman@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23Wm8J$PUHHA.3996@xxxxxxxxxxxxxxxxxxxxxxx
Yes your error is a bits error

C:\Windows\system32>err 0X80190197
# for hex 0x80190197 / decimal -2145844841
BG_E_HTTP_ERROR_407 bitsmsg.h
# 1 matches found for "0X80190197"


Things I have tried:
1. No security warnings on Outlook startup - You wont if you are internal (external you should have only been given one)
2. Test Email Autoconfiguration shows no problems - This is testing autodiscover and should work fine. You would see an issue here if you had a cert problem.
3. Visit the OAB URL from the user's workstation: https://<servername>/oab/<guid>/oab.xml with no problems and no errors or SSL warnings (this is also ok. This shows that your proxy settings are ok, cert is ok, ews is responding)
4. Even tried 'installing' the certificate but that shouldn't affect anything (this is incorrect, installing your cert will jack your setup up if not done correctly)

1. I would get a netmon trace from your client to see if you are lossing packets. Additionally I would turn on advanced logging from within outlook and restart your client because we now log things for bits, autodiscover, etc. The log that you want to look for is in %temp% and is oldisk.log.
2. In addition to this you can check to see which mailbox store you are on and then look at the configuration for that OAB in the Offline Address List container. See if this OAB is configured for PF distribution, Web Distribution or both.
3. I would get your IIS logs to see what is going on from the CAS Server.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Dgoldman
http://blogs.msdn.com/dgoldman


"John Fullbright [MVP]" <fjohn@donotspamnetappdotcom> wrote in message news:uhoBpBMUHHA.528@xxxxxxxxxxxxxxxxxxxxxxx
Isn't that an http error? 407 proxy authentication required?

I go to technet and I see:

Support for Offline Address Book (OAB) Version 4 enhances OAB download support, including HTTP download distribution points that do not require Public Folders, interrupted downloads restart where they were interrupted (instead of at the beginning), trickle download to help with low bandwidth scenarios.

That sounds an awful lot like BITS 2.0...

So, I check out the exchange team blog and:



Exchange Server 2007 introduces a new mechanism for distributing Offline Address Books (OAB) that doesn't require Public Folders. It instead uses HTTP(S) and the Background Intelligent Transfer Service (BITS). There are several potential advantages of the new distribution mechanism including supporting more concurrent clients, reduced bandwidth usage, and more control over the distribution points. It is important to note that the new distribution mechanism requires Outlook 2007, but you can always choose to use both Public Folder Distribution and Web Based Distribution of OABs. That way, older clients can still access their OABs using Public Folders while Outlook 2007 clients can take advantage of the enhanced functionality.



Sure is BITS, and I recall that specific error with BITS:



http://support.microsoft.com/kb/842309/en-us



I'd start there.






"Derek Martin" <argo_martin@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:39E3A837-7F01-48E5-ADCB-025A3B91B5C8@xxxxxxxxxxxxxxxx
Some users, when attempting to download the OAB in Outlook 2007 against our Exchange 2007 are getting error message: 0X80190197.

Things I have tried:
1. No security warnings on Outlook startup
2. Test Email Autoconfiguration shows no problems
3. Visit the OAB URL from the user's workstation: https://<servername>/oab/<guid>/oab.xml with no problems and no errors or SSL warnings
4. Even tried 'installing' the certificate but that shouldn't affect anything

Anyone ever seen, can describe or even know what this error is?

Thanks,
Derek








.

Relevant Pages

  • Re: Outlook 2k7 and Ex2k7 -> 0X80190197
    ... No security warnings on Outlook startup - You wont if you are internal ... Additionally I would turn on advanced logging from within outlook and restart your client because we now log things for bits, autodiscover, etc. ... In addition to this you can check to see which mailbox store you are on and then look at the configuration for that OAB in the Offline Address List container. ... See if this OAB is configured for PF distribution, ...
    (microsoft.public.exchange.admin)
  • Re: GAL and OAB problems with SBS2003
    ... I've also tried you suggestion with turnig on cached mode, ... when trying to download the OAB. ... > Outlook 2003 clients are set to be in Cached mode which does uses the ... > reboot or restart the Exchange SA you should see the clients get the info. ...
    (microsoft.public.windows.server.sbs)
  • Re: Offline Address Book download error
    ... services as an Outlook 2007 client does. ... the OAB from the public folder store and download the OAB that is associated ... with their mailbox store. ... I thought v2 was only for older clients? ...
    (microsoft.public.exchange.connectivity)
  • Re: Outlook 2k7 and Ex2k7 -> 0X80190197
    ... Additionally I would turn on advanced logging from within outlook and restart your client because we now log things for bits, autodiscover, etc. ... In addition to this you can check to see which mailbox store you are on and then look at the configuration for that OAB in the Offline Address List container. ... See if this OAB is configured for PF distribution, ... There are several potential advantages of the new distribution mechanism including supporting more concurrent clients, reduced bandwidth usage, and more control over the distribution points. ...
    (microsoft.public.exchange.admin)
  • Re: OAB distribution point and Test E-mail AutoConfiguration Outlook Tool
    ... when I change the distribution pointthere is a problem. ... public folder location then appears OK. ... why does it take so long for my Outlook client to pick up ... the changes i've made to the OAB in EMS. ...
    (microsoft.public.exchange.admin)
Loading