We have a user who unusually (and by that I mean he is the only one in a domain of about 100 people), sees a grey hatched line if he tries to schedule meeting requests in Outlook 2007 when viewing other's mailboxes. I have checked the calendar properties for odd recurrent tasks, correct free/busy settings and that the 'automaticlaly generate Microsoft Exchange views' is checked but to no avail. Has anyone seen this and know of a resolution? At the moment I can't see many other optiins than either recreating the user profile or exporting the data and trashing and recreating the mailbox. Any thoughts?

Have you checked Autodiscovery is working or not in his account in OUtlook.Thanks

You could try running Outlook.exe /cleanfreebusyMark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

I ran into similiar problems when setting up Outlook Anywhere. The problem for me was that "autodiscover.yourdomain.com" wasn't resolving to the correct address. I put a host file entry on the computer I was having issues with for autodiscover and put my CAS server IP in. It could also be a permissions issue. Does the user see the same thing when they schedule meetings in OWA? Do you get any errors when running "test-outlookwebservices" on your exchange server?

1. Modify the follow Registry information on each client machine(Take registry backup before performing it on client machine)A. Hkey_current_user –> Software –> Microsoft –> Office –> 12.0 –> Outlook -> autodisover ** you will find a number of built in xml file installed with Outlook** You can also add the following registry key to force Outlook to prefer the xml fileHKCU\Software\Microsoft\Office\12.0\Outlook\AutodiscoverDWORD: PreferLocalXML = 1 B. create a String Value called yournamespace i.e madeup.com(yourdomainname.com) C. Set the path to Drive\autodiscover\autodiscover.xml ( or whatever path you choose)Note:- you can get autodiscover.xml data after accessing, https://exchange.domainname.com/autodiscover/autodiscover.xml) copy all content from here and make folder in c driver with name autodiscover and make a autodiscover.txt inside that and paste all content on txt file and then rename it autodiscover.xml. D. Deploy the XML file to the clients machineLet me know if you face still same problem.Thanks

Yes I have and yes it is. Have already tried deleting and recreating his profile and autodiscovery is working fine.

Yes, already tried this and to no avail. Have also tried editing the registry to remove the Internet Free/Busy key and adding in a Legacy FB Dword value.

Can other users see his free busy information?When you set up his profile again did autodiscover work ok?What happens why he uses OWA can he see the free busy info then?

Hi,As others requested, what's the result in the OWA? Did you try?And please enable Outlook Logging on the problematic Outlook client, then reproduce this issue and collect the log. Then post the log type is FB (free/busy) under %temp%olkas folder on the forum or send it to me at v-allson@microsoft.com.ThanksAllen

Yes, autodiscovery is working just fine.

Yes, tried that but it doesnt change anything

Quite a lot of, although not always all of his busy information is seen as grey hatched lines if others try to scehdule meetings with him, which suggests to me it is his mailbox/profile and not a wider problem. No-one else has a problem. When we re setup his profile, auto-discover worked just fine with no errors but it didnt cure the problem. Havent checked on OWA but there is no suggestion that it will be any different - will verify this.

Hi,As others requested, what's the result in the OWA? Did you try?And please enable Outlook Logging on the problematic Outlook client, then reproduce this issue and collect the log. Then post the log type is FB (free/busy) under %temp%olkas folder on the forum or send it to me at v-allson@microsoft.com.ThanksAllen Going through this at present and will send the log files as and when i have them.. Rob

Hi,As others requested, what's the result in the OWA? Did you try?And please enable Outlook Logging on the problematic Outlook client, then reproduce this issue and collect the log. Then post the log type is FB (free/busy) under %temp%olkas folder on the forum or send it to me at v-allson@microsoft.com.ThanksAllen Allen I've uploaded the logs to your email address in zipped format in such state as were there. Rob

Hi Rob, The log is not correct. You need to send the log type is FB, such as 20100317-115817455-fb.log. And the log path is:%temp%\olkas Thanks Allen

Hi Rob, The log is not correct. You need to send the log type is FB, such as 20100317-115817455-fb.log. And the log path is:%temp%\olkas Thanks Allen Hi Allen There is no logfile with an fb in it, not even in my personal fully-effective client(which I turned logging on to work out where the logs got stored). Similiarly there isnt an OLKAS directory anywhere. This is Exchange 2007. I also assume this log is the one on the client and not on the server? Rob

Hi, To turn on logging via the check box found at Tools-Options-Other tab-Advanced Options-Enable logging. After restarting Outlook, add one or more attendees to a meeting request. As soon as you add the first attendee, and you are on the Scheduling Assistant tab, a log file will be generated. This is on the client side. Thanks Allen

Hi, To turn on logging via the check box found at Tools-Options-Other tab-Advanced Options-Enable logging. After restarting Outlook, add one or more attendees to a meeting request. As soon as you add the first attendee, and you are on the Scheduling Assistant tab, a log file will be generated. This is on the client side. Thanks Allen Hi Allen Yes I know, but the only log files created are the ones sent. There wasn't any olkas directory. I have asked the user to re-enable logging to see if it will work on re-logging. Rob

Hi, To turn on logging via the check box found at Tools-Options-Other tab-Advanced Options-Enable logging. After restarting Outlook, add one or more attendees to a meeting request. As soon as you add the first attendee, and you are on the Scheduling Assistant tab, a log file will be generated. This is on the client side. Thanks Allen As a follow-up, I have asked the user to re-enable logging but the olkas folder does not get created and consequently there isn't any fb logs to upload. I have aksed him to reinstall Outlook to see if that will fix the problem.

As a follow-up, I have asked the user to re-enable logging but the olkas folder does not get created and consequently there isn't any fb logs to upload. I have aksed him to reinstall Outlook to see if that will fix the problem.

Hi Allen I have sent you the latest logs I have found. They weren't from the original pc - that wouldnt giv logs under any circumstances but user has a similiar machine where the issue still occurs but the logs get created.Rob

Have you checked his calendar from OWA, is it working fine or not? Thanks Amit Rawat

Have you checked his calendar from OWA, is it working fine or not? Thanks Amit Rawat Yes I have and yes, it worked fine, but of course that isnt a lot of use if you default to the client in normal Windows.

Hi Rob, After reviewing the log that you sent, I found the error code 8004010F was received when getting the AS URL. Apparently, it's failed to get the AS URL which causes the user cannot use the URL to access others user's free/busy. Whether only one user has this issue? If it is, did you test this issue in another computer for this user? And please run test-outlookwebservices -identity useraccount@domain.com command for this user to do the testing, then post here. Thanks Allen

@rdevereux, Hey, Remove this Legacy FB Dword key then check your calendar must be working fine. this is my promise. Thanks Amit Rawat

Yes, already tried this and to no avail. Have also tried editing the registry to remove the Internet Free/Busy key and adding in a Legacy FB Dword value. @rdevereux, Hey, Remove this Legacy FB Dword key from registry then check your calendar must be working fine. this is my promise. Let me know if this doesn't work. Thanks Amit Rawat

Hi Rob, After reviewing the log that you sent, I found the error code 8004010F was received when getting the AS URL. Apparently, it's failed to get the AS URL which causes the user cannot use the URL to access others user's free/busy. Whether only one user has this issue? If it is, did you test this issue in another computer for this user? And please run test-outlookwebservices -identity useraccount@domain.com command for this user to do the testing, then post here. Thanks Allen Hi Allen Yes, it is just this one user and yes the issue occurs on other pcs he uses too. Rob

Yes, already tried this and to no avail. Have also tried editing the registry to remove the Internet Free/Busy key and adding in a Legacy FB Dword value. @rdevereux, Hey, Remove this Legacy FB Dword key from registry then check your calendar must be working fine. this is my promise. Let me know if this doesn't work. Thanks Amit Rawat Amit I added the key to see if this made any difference; it wasn't there before. I removed it when I found that it made no difference. Rob

Hi, Can you post the result of test-outlookwebservices -identity problematicuser@domain.com Thanks Allen

Yes, already tried this and to no avail. Have also tried editing the registry to remove the Internet Free/Busy key and adding in a Legacy FB Dword value. @rdevereux, Hey, Remove this Legacy FB Dword key from registry then check your calendar must be working fine. this is my promise. Let me know if this doesn't work. Thanks Amit Rawat Amit I added the key to see if this made any difference; it wasn't there before. I removed it when I found that it made no difference. Rob It seems very weird, please share your output of auto discovery service test. Thanks Amit Rawat

Sure. I ran the first query against the standard email address and the second against the user@dlocaldomain. Results below. 2>test-outlookwebservices -identity oswann@naturalmotion.com Id Type Message -- ---- ------- 1010 Error Unable to identify user 'oswann@naturalmot... [PS] C:\Windows\system32>test-outlookwebservices -identity oswann@nm.local Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail... 1006 Information The Autodiscover service was contacted at ... 1016 Success [EXCH]-Successfully contacted the AS servi... 1015 Success [EXCH]-Successfully contacted the OAB serv... 1014 Success [EXCH]-Successfully contacted the UM servi... 1016 Information [EXPR]-The AS is not configured for this u... 1015 Success [EXPR]-Successfully contacted the OAB serv... 1014 Information [EXPR]-The UM is not configured for this u... 1013 Error When contacting https://mail1.naturalmotio... 1013 Error When contacting https://mail1.naturalmotio... 1017 Error [EXPR]-Error when contacting the RPC/HTTP ... 1006 Success The Autodiscover service was tested succes... 1021 Information The following web services generated error...

Sorry, realised that the first one bombed out because I got the address wrong. it should be : [PS] C:\Windows\system32>test-outlookwebservices -identity oliver.swann@naturalmotion.com Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail... 1006 Information The Autodiscover service was contacted at ... 1016 Success [EXCH]-Successfully contacted the AS servi... 1015 Success [EXCH]-Successfully contacted the OAB serv... 1014 Success [EXCH]-Successfully contacted the UM servi... 1016 Information [EXPR]-The AS is not configured for this u... 1015 Success [EXPR]-Successfully contacted the OAB serv... 1014 Information [EXPR]-The UM is not configured for this u... Sorry about the trunctaing but powershell wont expand any further than this

Sorry, realised that the first one bombed out because I got the address wrong. it should be : [PS] C:\Windows\system32>test-outlookwebservices -identity oliver.swann@naturalmotion.com Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail... 1006 Information The Autodiscover service was contacted at ... 1016 Success [EXCH]-Successfully contacted the AS servi... 1015 Success [EXCH]-Successfully contacted the OAB serv... 1014 Success [EXCH]-Successfully contacted the UM servi... 1016 Information [EXPR]-The AS is not configured for this u... 1015 Success [EXPR]-Successfully contacted the OAB serv... 1014 Information [EXPR]-The UM is not configured for this u... Sorry about the trunctaing but powershell wont expand any further than this Hi, Now there are some few question:- # is this machine in domain or member of domain? # R you login with domain credential? Please let me know i am very curious to help you out from this weird situation. Thanks Amit Rawat

Amit The machine that has the issues with free busy is on the domain and the server running the exchange service is also on the same domain. I am logged-into the Exchange Server with domain admin credentials. This is irrelevant to the client-side. Rob

Hi, Try below steps to catch the problem:- 1) configure this user's outlook on another machine which is in domain. and see problem is same with it. 2) Please provide the output of autodiscovery service status from problematic outlook, to do so check this... >press ctrl key and hold it and right click on outlook icon at right bottom. > Click on " Test Email-Autoconfiguration" > checked only "Use Autodiscover" option rest of all should be unchecked and click on "Run" and let us know the output. Thanks Amit Rawat

Output from the Test Email-Autoconfiguration check: <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> - <User> <DisplayName>Oliver Swann</DisplayName> <LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=oswann</LegacyDN> <DeploymentId>fa85f4ba-08e3-4d58-b780-91c5e96af317</DeploymentId> </User> - <Account> <AccountType>email</AccountType> <Action>settings</Action> - <Protocol> <Type>EXCH</Type> <Server>WOODCHUCK.NM.local</Server> <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=WOODCHUCK</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=WOODCHUCK/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>WOODCHUCK.NM.local</PublicFolderServer> <AD>Capybara.NM.local</AD> <ASUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://woodchuck.nm.local/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://exchange.nm.local/OAB/0c3776a2-449f-4957-ba2f-b81fa728f6fd/</OABUrl> </Protocol> - <Protocol> <Type>EXPR</Type> <Server>mail1.naturalmotion.com</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <OABUrl>https://mail1.naturalmotion.com/OAB/0c3776a2-449f-4957-ba2f-b81fa728f6fd/</OABUrl> </Protocol> - <Protocol> <Type>WEB</Type> - <External> <OWAUrl AuthenticationMethod="Fba">https://mail1.naturalmotion.com/owa</OWAUrl> </External> - <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://exchange/owa</OWAUrl> - <Protocol> <Type>EXCH</Type> <ASUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Hi, How does Outlook of the problematic user connect with Exchange server? TCP/IP or RPC Over HTTPS? Please check it. From the testing result, we know that the ASUrl is retrieved correctly via Autodiscover and contacted without issue for EXCH (TCP/IP), but not available for EXPR (Outlook Anywhere). Please press Ctrl+right click Outlook icon in System Tray, select Connection Status, you can see it. Thanks Allen

Output from the Test Email-Autoconfiguration check: <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> - <User> <DisplayName>Oliver Swann</DisplayName> <LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=oswann</LegacyDN> <DeploymentId>fa85f4ba-08e3-4d58-b780-91c5e96af317</DeploymentId> </User> - <Account> <AccountType>email</AccountType> <Action>settings</Action> - <Protocol> <Type>EXCH</Type> <Server>WOODCHUCK.NM.local</Server> <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=WOODCHUCK</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=WOODCHUCK/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>WOODCHUCK.NM.local</PublicFolderServer> <AD>Capybara.NM.local</AD> <ASUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://woodchuck.nm.local/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://exchange.nm.local/OAB/0c3776a2-449f-4957-ba2f-b81fa728f6fd/</OABUrl> </Protocol> - <Protocol> <Type>EXPR</Type> <Server>mail1.naturalmotion.com</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <OABUrl>https://mail1.naturalmotion.com/OAB/0c3776a2-449f-4957-ba2f-b81fa728f6fd/</OABUrl> </Protocol> - <Protocol> <Type>WEB</Type> - <External> <OWAUrl AuthenticationMethod="Fba">https://mail1.naturalmotion.com/owa</OWAUrl> </External> - <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://exchange/owa</OWAUrl> - <Protocol> <Type>EXCH</Type> <ASUrl>https://woodchuck.nm.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover> It Seems perfect and How about my second question that is Have you configured same user profile in another domain added machine? Thanks Amit Rawat

Amit If you followed the thread back you would see that we have tried other machine's before and what the answer was. Rob

Allen It is using TCP/IP. Incidentally since running the autodiscover test we are now getting issue son that client with the GAL not updating properly and giving error "Task 'oswann@naturalmotion.com' reported error (0x8004010F) : 'The operation failed. An object cannot be found.'" Rob

OK. Use the programatic user Outlook, create a Outlook profile for other users, say, your own mailbox or a test mailbox, will the issue be duplicated? Here is some other things you can try 1. backup user's calendar, use mdbvu32 to delete the user's calendar folder, run Outlook /resetfolders, import rhe calendar and try it again. 2. export user's mailbox to a pst, create new mailbox, and import the pst, try it again. Sometimes, we will have to create a brand new mailbox for problematic users since their mailbox data is corrupt. reconnect mailbox sometime doesn't help either if user data is corrupt. good luck.