Support Code 0x80072F17
|
Prev: GFI Faxmaker 12 setup on SBS2003
Next: dcom error 10021
From: ABC on 29 Jan 2006 09:30 I have now worked through this problem with Microsoft support in India and have resolved the problem. In order to assist anyone else with similar issues I have posted below the steps we took: Problem Description-: ================ The Dell Mobile device cannot synchronize with the Server, getting the error message: 0x80072f17 Steps performed in this case-: ====================== Here are the steps that we followed -: ð You were using SSL for accessing OWA. ð Form Based Authentication was activated. ð Checked the Exchange VDs in the IIS Manager............the authentication type was selected incorrectly on most of them..........changed the same ð A certificate issued to : publishing.instant-search.local was being used. ð The domain name was "internalsearch.loca", the external url being used was "mailserver.instant-search.com" ð Removed the certificate and installed a new one locally. ð We got an error code : 0x80072f17 - when trying to synchronize with the PDA from the Cradle from inside the network. ð The ICW wizard was already executed on the SBS 2003 and then the method 2 mentioned in the 817379 was followed. ð The new Virtual Directory called Exchange-OMA did not have the settings as expected. ð We deleted this directory and created a new one. ð Edited the Web.config to create the required log file. ð the log file indicated this : An Unknown error occured during the processing of the current request MESSAGE:User Anthony(a)InstantSearch.local has Microsoft(R) Exchange server BRUCE, which is not running Exchange Server 2003. That server is not accessible by Outlook(R) Mobile Access. SOURCE:Microsoft.Exchange.OMA.ExchangeDataProvider STACK: at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders() at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user) MESSAGE:Exception has been thrown by the target of an invocation. ð Removed the checkbox that said that "use SSL" ð Now OMA was working locally. ð The "hostmaster(a)dsvr.co.uk" is the ISPs server and it directs the queries for port 80 and 443 to their router. ð Tried accessing OMA using this ip address and could access OMA if i used https and could not access when using http. ð So it was letting us in through port 443 but not through port 80. ð The port 80 was freed up now and OMA was working but that was leaving the default web site open to the Internet. ð We restricted access to the internal website from the outside world by removing the "anonymous access" check box on the Defautl website. ð Both the OMA and just a query on port 80 were working fine now, both asking for authentication. ð Tried the following options : http://mailserver.instant-search.com/oma ---> 404 : requested url could not be found https://mailserver.instant-search.com/oma---> Asks for username and password and lets me in. http://mailserver.instant-search.com/exchange ---> 404 : requested url could not be found https://mailserver.instant-search.com/exchange---> worked properly. ð Removed the require SSL and FBA from the Exchange VD ð Tried the same again...............exactly the same result for both OMA and Exchange which was a clear indication that the router was blocking the requests on port 80. ð In the IIS logs there is no change when we try to use the external url on port 80 so the request was not reaching the Exchange Server. ð A few settings on the Exchange Server were changed again and the OWA had stopped working. ð We were getting the 440 Login timeout error messages even when browsing from the local Exchange Server. ð Checked from the local Exchange Server by browsing in the IIS Virtual Directory and that was working. ð Https://localhost/exchange brings up FBA and did not let us log in. ð Removed FBA and restarted IIS. ð Https://localhost/exchange was working now. ð Put back the FBA and restarted the IIS. ð We tryed to access OWA using the RWW for SBS. ð It was working fine now. ð Since you wanted this default website to be secured and ask for authentication all the time. ð Forced SSL on it and also set the Authentication type to "Integrated" If you have any questions after closing this incident feel free to contact me. Additional Information and Recommendations-: ================================== The Exchange Server Best Practices Analyzer can be downloaded from the link: http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx This is a very handy tool to check the overall health of your Exchange Server. Articles related to configuring and using Certificates: 1. http://support.microsoft.com/?id=823024 2. http://support.microsoft.com/?id=830827 3. http://support.microsoft.com/kb/218445/ -- Anthony Capstick www.instant-search.com UK ""Nathan Liu [MSFT]"" wrote: > Hi James, > > Thank you for posting in the SBS newsgroup. > > First of all, please note that Charles is taking leave, and I am his backup. > > Considering the current condition, I suggest you create a new thread on the > SBS newsgroup. The reason why I recommend this is that you will get the > most qualified pool of respondents, and other partners who the newsgroups > regularly can share their knowledge. Thanks for understanding. > > Additionally, I am glad to provide the following general information for > your reference: > > SYMPTOMS > ======= > When you try to synchronize a Microsoft Windows Mobile-based device with a > computer, Microsoft ActiveSync4.0 may report an error similar to the > following: > > Activesync encoutered an error with the desktop. > Support code: 85010014 > > CAUSE > ==== > This problem occurs when one of the following conditions is true. > > o Microsoft Outlook is in offline mode. > o The application data folder is redirected. > o ActiveSync 4.0 is incorrectly registered to Outlook. > o Outlook script is blocked by Antivirus software. > > RESOLUTION > ========= > To resolve this problem, download and install Microsoft ActiveSync 4.1. > http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx > > I appreciate your time and cooperation. > > Have a nice day! > > Best regards, > > Nathan Liu (MSFT) > > Microsoft CSS Online Newsgroup Support > Get Secure! - www.microsoft.com/security > > ====================================================== > This newsgroup only focuses on SBS technical issues. If you have issues > regarding other Microsoft products, you'd better post in the corresponding > newsgroups so that they can be resolved in an efficient and timely manner. > You can locate the newsgroup here: > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > When opening a new thread via the web interface, we recommend you check the > "Notify me of replies" box to receive e-mail notifications when there are > any updates in your thread. When responding to posts via your newsreader, > please "Reply to Group" so that others may learn and benefit from your > issue. > > Microsoft engineers can only focus on one issue per thread. Although we > provide other information for your reference, we recommend you post > different incidents in different threads to keep the thread clean. In doing > so, it will ensure your issues are resolved in a timely manner. > > For urgent issues, you may want to contact Microsoft CSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > > Any input or comments in this thread are highly appreciated. > ====================================================== > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > -------------------- > >Thread-Topic: Support Code 0x80072F17 > >thread-index: AcYdwAdp4wa196lYTMOdtYUX35oOEg== > >X-WBNR-Posting-Host: 212.32.43.17 > >From: "=?Utf-8?B?SmFtZXMgRHVubg==?=" <James Dunn(a)discussions.microsoft.com> > >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> > <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> > <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> > <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> > >Subject: RE: Support Code 0x80072F17 > >Date: Fri, 20 Jan 2006 04:50:02 -0800 > >Lines: 268 > >Message-ID: <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> > >MIME-Version: 1.0 > >Content-Type: text/plain; > > charset="Utf-8" > >Content-Transfer-Encoding: 7bit > >X-Newsreader: Microsoft CDO for Windows 2000 > >Content-Class: urn:content-classes:message > >Importance: normal > >Priority: normal > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 > >Newsgroups: microsoft.public.windows.server.sbs > >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 > >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl > >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238171 > >X-Tomcat-NG: microsoft.public.windows.server.sbs > > > >Hi Guys > > > >I have been have the exact same problem with our SBS server. > > > >I have followed the step Charles has suggest but still get Support code > >85010014 when trying Sync a PDA windows mobile 5 with of SBS server > (either > >via active sysn or directly over a wireless connection) > > > >If there is anything I can do to help please le tme know > > > >Best regtard > > > >James Dunn > >jamesd(a)netinst.co.uk > > > >""Charles Yang [MSFT]"" wrote: > > > >> > >> HI, > >> > >> There is some additional steps: > >> > >> > >> 1. New account: > >> > >> For further test, please create a new test account and let me know the > >> following information. > >> > >> - Credential of this test account > >> - The public URL of your Exchange Server > >> - Domain name > >> > >> 2. Clean the sync state file in this problematic mailbox which Windows > >> Mobile 5.0 PPC tries to sync. > >> > >> 1). Open Internet Explorer. > >> 2). Click File-> Open. > >> 3). Please select the "Open as Web Folder" check box. > >> 4). Type > >> > http://servername/exchange/username/NON_IPM_SUBTREE/Microsoft-Server-Actives > >> ync and then click OK. > >> 5). Open the PocketPC folder. > >> 6). Delete the 'DeviceID' folder. > >> 7). Try to run Server ActiveSync in Windows Mobile 5.0 PPC again. > >> > >> 3. IIS Log > >> > >> Please collect the IIS log on Exchange Server so that I can perform > further > >> research: > >> > >> 1). On Exchange Serves, open IIS MMC, right click Default Web Site and > then > >> click Properties. > >> 2). Click Website tab and then check Enable logging. > >> 3). Stop the Default Website and RENAME the existing IIS log files under > >> C:\WINDOWS\system32\LogFiles\W3SVC1. > >> 4). Restart the Default Website and reproduce the problem, which will > >> generate new IIS log file with the exact error. > >> 5). Go to the following folder on Exchange Server: > >> C:\WINDOWS\system32\LogFiles\W3SVC1. > >> 6). Send me the log files to my working email address > >> v-chayan(a)microsoft.com. And please let me know the alias of the user who > >> encountered the issue. > >> > >> Please emails all information to my mailbox. Thanks again for your > effort. > >> > >> > >> Best regards, > >> > >> Charles Yang (MSFT) > >> > >> Microsoft CSS Online Newsgroup Support > >> > >> Get Secure! - www.microsoft.com/security > >> > >> ====================================================== > >> This newsgroup only focuses on SBS technical issues. If you have issues > >> regarding other Microsoft products, you'd better post in the > corresponding > >> newsgroups so that they can be resolved in an efficient and timely > manner. > >> You can locate the newsgroup here: > >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > >> > >> When opening a new thread via the web interface, we recommend you check > the > >> "Notify me of replies" box to receive e-mail notifications when there > are > >> any updates in your thread. When responding to posts via your > newsreader, > >> please "Reply to Group" so that others may learn and benefit from your > >> issue. > >> > >> Microsoft engineers can only focus on one issue per thread. Although we > >> provide other information for your reference, we recommend you post > >> different incidents in different threads to keep the thread clean. In > doing > >> so, it will ensure your issues are resolved in a timely manner. > >> > >> For urgent issues, you may want to contact Microsoft CSS directly. > Please > >> check http://support.microsoft.com for regional support phone numbers. > >> > >> Any input or comments in this thread are highly appreciated. > >> ====================================================== > >> This posting is provided "AS IS" with no warranties, and confers no > rights. > >> > >> > >> ===================================================== > >> When responding to posts, please "Reply to Group" via your newsreader so > >> that others may learn and benefit from your issue. > >> ===================================================== > >> > >> This posting is provided "AS IS" with no warranties, and confers no > rights. > >> > >> -------------------- > >> | X-Tomcat-ID: 129062622 > >> | References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> > >> <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> > >> | MIME-Version: 1.0 > >> | Content-Type: text/plain > >> | Content-Transfer-Encoding: 7bit > >> | From: v-chayan(a)online.microsoft.com ("Charles Yang [MSFT]") > >> | Organization: Microsoft > >> | Date: Wed, 11 Jan 2006 07:01:38 GMT > >> | Subject: RE: Support Code 0x80072F17 > >> | X-Tomcat-NG: microsoft.public.windows.server.sbs > >> | Message-ID: <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> > >> | Newsgroups: microsoft.public.windows.server.sbs > >> | Lines: 117 > >> | Path: TK2MSFTNGXA02.phx.gbl > >> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235707 > >> | NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122 > >> | > >> | HI, > >> | > >> | Thanks for updates. > >> | > >> | After doing some research, we suggest you refer to my steps for > further > >> | troubleshooting: > >> | > >> | It looks like there is a conflict between Activesync 4.0 and Outlook. > I > >> see > >> | that in some of the previous instances, uninstalling Office and > Outlook > >> | completely in the following manner did help to resolve the issue: > >> | > >> | Uninstall Outlook 2003 > >> | Delete Microsoft Office folder Program Files > >> | Delete Outlook folder from C:\Documents and Settings\ > >> | (Username)\Application Data\Microsoft > >> | Delete the following keys from registry: > >> | HKEY_CURRENT_USER\Software\Microsoft\Office\11.0 > >> | HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0 > >> | > >> | Clear Temp folder (Start> Run>%temp% >OK) > >> | > >> | > >> | > >> | 2. As soon as OL is connected to the Exchange server, it would not > sync > >> and > >> | would give the same support number: 85010014. > >> | > >> | Hence I was thinking of creating a new profile in your OL, and > configure > >> a > >> | POP test account in the same and try to sync. In that way, your office > >> | account will remain untouched and we would get to know if the exchange > >> | server connection is creating the problem. > >> | > >> | I appreciate your effort on this issue, please feel free to post back. > >> | > >> | > >> | > >> | Best regards, > >> | > >> | Charles Yang (MSFT) > >> | > >> | Microsoft CSS Online Newsgroup Support > >> | > >> | Get Secure! - www.microsoft.com/security > >> | > >> | ====================================================== > >> | This newsgroup only focuses on SBS technical issues. If you have > issues > >> | regarding other Microsoft products, you'd better post in the > >> corresponding
From: "Nathan Liu [MSFT]" on 30 Jan 2006 20:39 Hi Anthony, I am sorry for the delay in responding due to weekend, thanks for the understanding. Thank you for your reply and the detailed additional feedback on how you were successful in resolving this issue. Your solution will benefit many other users, and we really value having you as a Microsoft customer. Please do not hesitate to post in this great newsgroup if you need any assistance in the future. I look forward to working with you again. Have a nice day! Best regards, Nathan Liu (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ====================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- >Thread-Topic: Support Code 0x80072F17 >thread-index: AcYk4IxFwkSlnznJQvK5u632IdZcTw== >X-WBNR-Posting-Host: 82.69.96.190 >From: =?Utf-8?B?QUJD?= <ABC(a)discussions.microsoft.com> >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> <VVew3RMIGHA.3696(a)TK2MSFTNGXA02.phx.gbl> >Subject: RE: Support Code 0x80072F17 >Date: Sun, 29 Jan 2006 06:30:27 -0800 >Lines: 421 >Message-ID: <F465A3F7-8227-4E69-A144-F4E2CF391ABC(a)microsoft.com> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="Utf-8" >Content-Transfer-Encoding: 8bit >X-Newsreader: Microsoft CDO for Windows 2000 >Content-Class: urn:content-classes:message >Importance: normal >Priority: normal >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >Newsgroups: microsoft.public.windows.server.sbs >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:240082 >X-Tomcat-NG: microsoft.public.windows.server.sbs > >I have now worked through this problem with Microsoft support in India and >have resolved the problem. In order to assist anyone else with similar issues >I have posted below the steps we took: > >Problem Description-: >================ >The Dell Mobile device cannot synchronize with the Server, getting the error >message: 0x80072f17 >Steps performed in this case-: >====================== >Here are the steps that we followed -: >ð You were using SSL for accessing OWA. >ð Form Based Authentication was activated. >ð Checked the Exchange VDs in the IIS Manager............the >authentication type was selected incorrectly on most of them..........changed >the same >ð A certificate issued to : publishing.instant-search.local was being >used. >ð The domain name was "internalsearch.loca", the external url being used >was "mailserver.instant-search.com" >ð Removed the certificate and installed a new one locally. >ð We got an error code : 0x80072f17 - when trying to synchronize with >the PDA from the Cradle from inside the network. >ð The ICW wizard was already executed on the SBS 2003 and then the >method 2 mentioned in the 817379 was followed. >ð The new Virtual Directory called Exchange-OMA did not have the >settings as expected. >ð We deleted this directory and created a new one. >ð Edited the Web.config to create the required log file. >ð the log file indicated this : >An Unknown error occured during the processing of the current request >MESSAGE:User Anthony(a)InstantSearch.local has Microsoft(R) Exchange server >BRUCE, which is not running Exchange Server 2003. That server is not >accessible by Outlook(R) Mobile Access. >SOURCE:Microsoft.Exchange.OMA.ExchangeDataProvider >STACK: >at >Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFold ers() >at >Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo >user) > > >MESSAGE:Exception has been thrown by the target of an invocation. > > >ð Removed the checkbox that said that "use SSL" >ð Now OMA was working locally. >ð The "hostmaster(a)dsvr.co.uk" is the ISPs server and it directs the >queries for port 80 and 443 to their router. >ð Tried accessing OMA using this ip address and could access OMA if i >used https and could not access when using http. >ð So it was letting us in through port 443 but not through port 80. >ð The port 80 was freed up now and OMA was working but that was leaving >the default web site open to the Internet. >ð We restricted access to the internal website from the outside world by >removing the "anonymous access" check box on the Defautl website. >ð Both the OMA and just a query on port 80 were working fine now, both >asking for authentication. >ð Tried the following options : > >http://mailserver.instant-search.com/oma ---> 404 : requested url could >not be found > >https://mailserver.instant-search.com/oma---> Asks for username and >password and lets me in. > >http://mailserver.instant-search.com/exchange ---> 404 : requested >url could not be found > >https://mailserver.instant-search.com/exchange---> worked properly. > >ð Removed the require SSL and FBA from the Exchange VD >ð Tried the same again...............exactly the same result for both >OMA and Exchange which was a clear indication that the router was blocking >the requests on port 80. >ð In the IIS logs there is no change when we try to use the external url >on port 80 so the request was not reaching the Exchange Server. >ð A few settings on the Exchange Server were changed again and the OWA >had stopped working. >ð We were getting the 440 Login timeout error messages even when >browsing from the local Exchange Server. >ð Checked from the local Exchange Server by browsing in the IIS Virtual >Directory and that was working. >ð Https://localhost/exchange brings up FBA and did not let us log in. >ð Removed FBA and restarted IIS. >ð Https://localhost/exchange was working now. >ð Put back the FBA and restarted the IIS. >ð We tryed to access OWA using the RWW for SBS. >ð It was working fine now. >ð Since you wanted this default website to be secured and ask for >authentication all the time. >ð Forced SSL on it and also set the Authentication type to "Integrated" > >If you have any questions after closing this incident feel free to contact me. > >Additional Information and Recommendations-: > >================================== > >The Exchange Server Best Practices Analyzer can be downloaded from the link: > >http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyz ers/default.mspx > >This is a very handy tool to check the overall health of your Exchange Server. >Articles related to configuring and using Certificates: > >1. http://support.microsoft.com/?id=823024 > >2. http://support.microsoft.com/?id=830827 > >3. http://support.microsoft.com/kb/218445/ > >-- >Anthony Capstick >www.instant-search.com >UK > > >""Nathan Liu [MSFT]"" wrote: > >> Hi James, >> >> Thank you for posting in the SBS newsgroup. >> >> First of all, please note that Charles is taking leave, and I am his backup. >> >> Considering the current condition, I suggest you create a new thread on the >> SBS newsgroup. The reason why I recommend this is that you will get the >> most qualified pool of respondents, and other partners who the newsgroups >> regularly can share their knowledge. Thanks for understanding. >> >> Additionally, I am glad to provide the following general information for >> your reference: >> >> SYMPTOMS >> ======= >> When you try to synchronize a Microsoft Windows Mobile-based device with a >> computer, Microsoft ActiveSync4.0 may report an error similar to the >> following: >> >> Activesync encoutered an error with the desktop. >> Support code: 85010014 >> >> CAUSE >> ==== >> This problem occurs when one of the following conditions is true. >> >> o Microsoft Outlook is in offline mode. >> o The application data folder is redirected. >> o ActiveSync 4.0 is incorrectly registered to Outlook. >> o Outlook script is blocked by Antivirus software. >> >> RESOLUTION >> ========= >> To resolve this problem, download and install Microsoft ActiveSync 4.1. >> http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx >> >> I appreciate your time and cooperation. >> >> Have a nice day! >> >> Best regards, >> >> Nathan Liu (MSFT) >> >> Microsoft CSS Online Newsgroup Support >> Get Secure! - www.microsoft.com/security >> >> ====================================================== >> This newsgroup only focuses on SBS technical issues. If you have issues >> regarding other Microsoft products, you'd better post in the corresponding >> newsgroups so that they can be resolved in an efficient and timely manner. >> You can locate the newsgroup here: >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx >> >> When opening a new thread via the web interface, we recommend you check the >> "Notify me of replies" box to receive e-mail notifications when there are >> any updates in your thread. When responding to posts via your newsreader, >> please "Reply to Group" so that others may learn and benefit from your >> issue. >> >> Microsoft engineers can only focus on one issue per thread. Although we >> provide other information for your reference, we recommend you post >> different incidents in different threads to keep the thread clean. In doing >> so, it will ensure your issues are resolved in a timely manner. >> >> For urgent issues, you may want to contact Microsoft CSS directly. Please >> check http://support.microsoft.com for regional support phone numbers. >> >> Any input or comments in this thread are highly appreciated. >> ====================================================== >> >> This posting is provided "AS IS" with no warranties, and confers no rights. >> >> >> >> -------------------- >> >Thread-Topic: Support Code 0x80072F17 >> >thread-index: AcYdwAdp4wa196lYTMOdtYUX35oOEg== >> >X-WBNR-Posting-Host: 212.32.43.17 >> >From: "=?Utf-8?B?SmFtZXMgRHVubg==?=" <James Dunn(a)discussions.microsoft.com> >> >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> >> <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> >> <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> >> <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> >> >Subject: RE: Support Code 0x80072F17 >> >Date: Fri, 20 Jan 2006 04:50:02 -0800 >> >Lines: 268 >> >Message-ID: <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> >> >MIME-Version: 1.0 >> >Content-Type: text/plain; >> > charset="Utf-8" >> >Content-Transfer-Encoding: 7bit >> >X-Newsreader: Microsoft CDO for Windows 2000 >> >Content-Class: urn:content-classes:message >> >Importance: normal >> >Priority: normal >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >> >Newsgroups: microsoft.public.windows.server.sbs >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl >> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238171 >> >X-Tomcat-NG: microsoft.public.windows.server.sbs >> > >> >Hi Guys >> > >> >I have been have the exact same problem with our SBS server. >> > >> >I have followed the step Charles has suggest but still get Support code >> >85010014 when trying Sync a PDA windows mobile 5 with of SBS server >> (either >> >via active sysn or directly over a wireless connection) >> > >> >If there is anything I can do to help please le tme know >> > >> >Best regtard >> > >> >James Dunn >> >jamesd(a)netinst.co.uk >> > >> >""Charles Yang [MSFT]"" wrote: >> > >> >> >> >> HI, >> >> >> >> There is some additional steps: >> >> >> >> >> >> 1. New account: >> >> >> >> For further test, please create a new test account and let me know the >> >> following information. >> >> >> >> - Credential of this test account >> >> - The public URL of your Exchange Server >> >> - Domain name >> >> >> >> 2. Clean the sync state file in this problematic mailbox which Windows >> >> Mobile 5.0 PPC tries to sync. >> >> >> >> 1). Open Internet Explorer. >> >> 2). Click File-> Open. >> >> 3). Please select the "Open as Web Folder" check box. >> >> 4). Type >> >> >> http://servername/exchange/username/NON_IPM_SUBTREE/Microsoft-Server-Actives >> >> ync and then click OK. >> >> 5). Open the PocketPC folder. >> >> 6). Delete the 'DeviceID' folder. >> >> 7). Try to run Server ActiveSync in Windows Mobile 5.0 PPC again. >> >> >> >> 3. IIS Log >> >> >> >> Please collect the IIS log on Exchange Server so that I can perform >> further >> >> research: >> >> >> >> 1). On Exchange Serves, open IIS MMC, right click Default Web Site and >> then >> >> click Properties. >> >> 2). Click Website tab and then check Enable logging. >> >> 3). Stop the Default Website and RENAME the existing IIS log files under >> >> C:\WINDOWS\system32\LogFiles\W3SVC1. >> >> 4). Restart the Default Website and reproduce the problem, which will >> >> generate new IIS log file with the exact error. >> >> 5). Go to the following folder on Exchange Server: >> >> C:\WINDOWS\system32\LogFiles\W3SVC1. >> >> 6). Send me the log files to my working email address >> >> v-chayan(a)microsoft.com. And please let me know the alias of the user who >> >> encountered the issue. >> >> >> >> Please emails all information to my mailbox. Thanks again for your >> effort. >> >> >> >> >> >> Best regards, >> >> >> >> Charles Yang (MSFT) >> >> >> >> Microsoft CSS Online Newsgroup Support >> >> >> >> Get Secure! - www.microsoft.com/security >> >> >> >> ====================================================== >> >> This newsgroup only focuses on SBS technical issues. If you have issues >> >> regarding other Microsoft products, you'd better post in the >> corresponding >> >> newsgroups so that they can be resolved in an efficient and timely >> manner. >> >> You can locate the newsgroup here: >> >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx >> >> >> >> When opening a new thread via the web interface, we recommend you check >> the >> >> "Notify me of replies" box to receive e-mail notifications when there >> are >> >> any updates in your thread. When responding to posts via your >> newsreader, >> >> please "Reply to Group" so that others may learn and benefit from your >> >> issue. >> >> >> >> Microsoft engineers can only focus on one issue per thread. Although we >> >> provide other information for your reference, we recommend you post >> >> different incidents in different threads to keep the thread clean. In >> doing >> >> so, it will ensure your issues are resolved in a timely manner. >> >> >> >> For urgent issues, you may want to contact Microsoft CSS directly. >> Please >> >> check http://support.microsoft.com for regional support phone numbers. >> >> >> >> Any input or comments in this thread are highly appreciated. >> >> ====================================================== >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> >> >> >> ===================================================== >> >> When responding to posts, please "Reply to Group" via your newsreader so >> >> that others may learn and benefit from your issue. >> >> ===================================================== >> >> >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> >> -------------------- >> >> | X-Tomcat-ID: 129062622 >> >> | References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> >> >> <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> >> >> | MIME-Version: 1.0 >> >> | Content-Type: text/plain >> >> | Content-Transfer-Encoding: 7bit >> >> | From: v-chayan(a)online.microsoft.com ("Charles Yang [MSFT]") >> >> | Organization: Microsoft >> >> | Date: Wed, 11 Jan 2006 07:01:38 GMT >> >> | Subject: RE: Support Code 0x80072F17 >> >> | X-Tomcat-NG: microsoft.public.windows.server.sbs >> >> | Message-ID: <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> >> >> | Newsgroups: microsoft.public.windows.server.sbs >> >> | Lines: 117 >> >> | Path: TK2MSFTNGXA02.phx.gbl >> >> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235707 >> >> | NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122 >> >> | >> >> | HI, >> >> | >> >> | Thanks for updates. >> >> | >> >> | After doing some research, we suggest you refer to my steps for >> further >> >> | troubleshooting: >> >> | >> >> | It looks like there is a conflict between Activesync 4.0 and Outlook. >> I >> >> see >> >> | that in some of the previous instances, uninstalling Office and >> Outlook >> >> | completely in the following manner did help to resolve the issue: >> >> | >> >> | Uninstall Outlook 2003 >> >> | Delete Microsoft Office folder Program Files >> >> | Delete Outlook folder from C:\Documents and Settings\ >> >> | (Username)\Application Data\Microsoft >> >> | Delete the following keys from registry: >> >> | HKEY_CURRENT_USER\Software\Microsoft\Office\11.0 >> >> | HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0 >> >> | >> >> | Clear Temp folder (Start> Run>%temp% >OK) >> >> | >> >> | >> >> | >> >> | 2. As soon as OL is connected to the Exchange server, it would not >> sync >> >> and >> >> | would give the same support number: 85010014. >> >> | >> >> | Hence I was thinking of creating a new profile in your OL, and >> configure >> >> a >> >> | POP test account in the same and try to sync. In that way, your office >> >> | account will remain untouched and we would get to know if the exchange >> >> | server connection is creating the problem. >> >> | >> >> | I appreciate your effort on this issue, please feel free to post back. >> >> | >> >> | >> >> | >> >> | Best regards, >> >> | >> >> | Charles Yang (MSFT) >> >> | >> >> | Microsoft CSS Online Newsgroup Support >> >> | >> >> | Get Secure! - www.microsoft.com/security >> >> | >> >> | ====================================================== >> >> | This newsgroup only focuses on SBS technical issues. If you have >> issues >> >> | regarding other Microsoft products, you'd better post in the >> >> corresponding >
From: Tony G on 24 Feb 2006 02:01 Any rate you could expand a little more on what exactly you guys did to rememdy this situation. Been spending days and hours trying to get this going and I'm having no luck whatsoever. I'd appreciate it, Thank you. "ABC" wrote: > I have now worked through this problem with Microsoft support in India and > have resolved the problem. In order to assist anyone else with similar issues > I have posted below the steps we took: > > Problem Description-: > ================ > The Dell Mobile device cannot synchronize with the Server, getting the error > message: 0x80072f17 > Steps performed in this case-: > ====================== > Here are the steps that we followed -: > ð You were using SSL for accessing OWA. > ð Form Based Authentication was activated. > ð Checked the Exchange VDs in the IIS Manager............the > authentication type was selected incorrectly on most of them..........changed > the same > ð A certificate issued to : publishing.instant-search.local was being > used. > ð The domain name was "internalsearch.loca", the external url being used > was "mailserver.instant-search.com" > ð Removed the certificate and installed a new one locally. > ð We got an error code : 0x80072f17 - when trying to synchronize with > the PDA from the Cradle from inside the network. > ð The ICW wizard was already executed on the SBS 2003 and then the > method 2 mentioned in the 817379 was followed. > ð The new Virtual Directory called Exchange-OMA did not have the > settings as expected. > ð We deleted this directory and created a new one. > ð Edited the Web.config to create the required log file. > ð the log file indicated this : > An Unknown error occured during the processing of the current request > MESSAGE:User Anthony(a)InstantSearch.local has Microsoft(R) Exchange server > BRUCE, which is not running Exchange Server 2003. That server is not > accessible by Outlook(R) Mobile Access. > SOURCE:Microsoft.Exchange.OMA.ExchangeDataProvider > STACK: > at > Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders() > at > Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo > user) > > > MESSAGE:Exception has been thrown by the target of an invocation. > > > ð Removed the checkbox that said that "use SSL" > ð Now OMA was working locally. > ð The "hostmaster(a)dsvr.co.uk" is the ISPs server and it directs the > queries for port 80 and 443 to their router. > ð Tried accessing OMA using this ip address and could access OMA if i > used https and could not access when using http. > ð So it was letting us in through port 443 but not through port 80. > ð The port 80 was freed up now and OMA was working but that was leaving > the default web site open to the Internet. > ð We restricted access to the internal website from the outside world by > removing the "anonymous access" check box on the Defautl website. > ð Both the OMA and just a query on port 80 were working fine now, both > asking for authentication. > ð Tried the following options : > > http://mailserver.instant-search.com/oma ---> 404 : requested url could > not be found > > https://mailserver.instant-search.com/oma---> Asks for username and > password and lets me in. > > http://mailserver.instant-search.com/exchange ---> 404 : requested > url could not be found > > https://mailserver.instant-search.com/exchange---> worked properly. > > ð Removed the require SSL and FBA from the Exchange VD > ð Tried the same again...............exactly the same result for both > OMA and Exchange which was a clear indication that the router was blocking > the requests on port 80. > ð In the IIS logs there is no change when we try to use the external url > on port 80 so the request was not reaching the Exchange Server. > ð A few settings on the Exchange Server were changed again and the OWA > had stopped working. > ð We were getting the 440 Login timeout error messages even when > browsing from the local Exchange Server. > ð Checked from the local Exchange Server by browsing in the IIS Virtual > Directory and that was working. > ð Https://localhost/exchange brings up FBA and did not let us log in. > ð Removed FBA and restarted IIS. > ð Https://localhost/exchange was working now. > ð Put back the FBA and restarted the IIS. > ð We tryed to access OWA using the RWW for SBS. > ð It was working fine now. > ð Since you wanted this default website to be secured and ask for > authentication all the time. > ð Forced SSL on it and also set the Authentication type to "Integrated" > > If you have any questions after closing this incident feel free to contact me. > > Additional Information and Recommendations-: > > ================================== > > The Exchange Server Best Practices Analyzer can be downloaded from the link: > > http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx > > This is a very handy tool to check the overall health of your Exchange Server. > Articles related to configuring and using Certificates: > > 1. http://support.microsoft.com/?id=823024 > > 2. http://support.microsoft.com/?id=830827 > > 3. http://support.microsoft.com/kb/218445/ > > -- > Anthony Capstick > www.instant-search.com > UK > > > ""Nathan Liu [MSFT]"" wrote: > > > Hi James, > > > > Thank you for posting in the SBS newsgroup. > > > > First of all, please note that Charles is taking leave, and I am his backup. > > > > Considering the current condition, I suggest you create a new thread on the > > SBS newsgroup. The reason why I recommend this is that you will get the > > most qualified pool of respondents, and other partners who the newsgroups > > regularly can share their knowledge. Thanks for understanding. > > > > Additionally, I am glad to provide the following general information for > > your reference: > > > > SYMPTOMS > > ======= > > When you try to synchronize a Microsoft Windows Mobile-based device with a > > computer, Microsoft ActiveSync4.0 may report an error similar to the > > following: > > > > Activesync encoutered an error with the desktop. > > Support code: 85010014 > > > > CAUSE > > ==== > > This problem occurs when one of the following conditions is true. > > > > o Microsoft Outlook is in offline mode. > > o The application data folder is redirected. > > o ActiveSync 4.0 is incorrectly registered to Outlook. > > o Outlook script is blocked by Antivirus software. > > > > RESOLUTION > > ========= > > To resolve this problem, download and install Microsoft ActiveSync 4.1. > > http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx > > > > I appreciate your time and cooperation. > > > > Have a nice day! > > > > Best regards, > > > > Nathan Liu (MSFT) > > > > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > > > > ====================================================== > > This newsgroup only focuses on SBS technical issues. If you have issues > > regarding other Microsoft products, you'd better post in the corresponding > > newsgroups so that they can be resolved in an efficient and timely manner. > > You can locate the newsgroup here: > > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > > > When opening a new thread via the web interface, we recommend you check the > > "Notify me of replies" box to receive e-mail notifications when there are > > any updates in your thread. When responding to posts via your newsreader, > > please "Reply to Group" so that others may learn and benefit from your > > issue. > > > > Microsoft engineers can only focus on one issue per thread. Although we > > provide other information for your reference, we recommend you post > > different incidents in different threads to keep the thread clean. In doing > > so, it will ensure your issues are resolved in a timely manner. > > > > For urgent issues, you may want to contact Microsoft CSS directly. Please > > check http://support.microsoft.com for regional support phone numbers. > > > > Any input or comments in this thread are highly appreciated. > > ====================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > > > > > -------------------- > > >Thread-Topic: Support Code 0x80072F17 > > >thread-index: AcYdwAdp4wa196lYTMOdtYUX35oOEg== > > >X-WBNR-Posting-Host: 212.32.43.17 > > >From: "=?Utf-8?B?SmFtZXMgRHVubg==?=" <James Dunn(a)discussions.microsoft.com> > > >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> > > <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> > > <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> > > <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> > > >Subject: RE: Support Code 0x80072F17 > > >Date: Fri, 20 Jan 2006 04:50:02 -0800 > > >Lines: 268 > > >Message-ID: <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> > > >MIME-Version: 1.0 > > >Content-Type: text/plain; > > > charset="Utf-8" > > >Content-Transfer-Encoding: 7bit > > >X-Newsreader: Microsoft CDO for Windows 2000 > > >Content-Class: urn:content-classes:message > > >Importance: normal > > >Priority: normal > > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 > > >Newsgroups: microsoft.public.windows.server.sbs > > >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 > > >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl > > >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238171 > > >X-Tomcat-NG: microsoft.public.windows.server.sbs > > > > > >Hi Guys > > > > > >I have been have the exact same problem with our SBS server. > > > > > >I have followed the step Charles has suggest but still get Support code > > >85010014 when trying Sync a PDA windows mobile 5 with of SBS server > > (either > > >via active sysn or directly over a wireless connection) > > > > > >If there is anything I can do to help please le tme know > > > > > >Best regtard > > > > > >James Dunn > > >jamesd(a)netinst.co.uk > > > > > >""Charles Yang [MSFT]"" wrote: > > > > > >> > > >> HI, > > >> > > >> There is some additional steps: > > >> > > >> > > >> 1. New account: > > >> > > >> For further test, please create a new test account and let me know the > > >> following information. > > >> > > >> - Credential of this test account > > >> - The public URL of your Exchange Server > > >> - Domain name > > >> > > >> 2. Clean the sync state file in this problematic mailbox which Windows > > >> Mobile 5.0 PPC tries to sync. > > >> > > >> 1). Open Internet Explorer. > > >> 2). Click File-> Open. > > >> 3). Please select the "Open as Web Folder" check box. > > >> 4). Type > > >> > > http://servername/exchange/username/NON_IPM_SUBTREE/Microsoft-Server-Actives > > >> ync and then click OK. > > >> 5). Open the PocketPC folder. > > >> 6). Delete the 'DeviceID' folder. > > >> 7). Try to run Server ActiveSync in Windows Mobile 5.0 PPC again. > > >> > > >> 3. IIS Log > > >> > > >> Please collect the IIS log on Exchange Server so that I can perform > > further > > >> research: > > >> > > >> 1). On Exchange Serves, open IIS MMC, right click Default Web Site and > > then > > >> click Properties. > > >> 2). Click Website tab and then check Enable logging. > > >> 3). Stop the Default Website and RENAME the existing IIS log files under > > >> C:\WINDOWS\system32\LogFiles\W3SVC1. > > >> 4). Restart the Default Website and reproduce the problem, which will > > >> generate new IIS log file with the exact error. > > >> 5). Go to the following folder on Exchange Server: > > >> C:\WINDOWS\system32\LogFiles\W3SVC1. > > >> 6). Send me the log files to my working email address > > >> v-chayan(a)microsoft.com. And please let me know the alias of the user who > > >> encountered the issue. > > >> > > >> Please emails all information to my mailbox. Thanks again for your > > effort. > > >> > > >> > > >> Best regards, > > >> > > >> Charles Yang (MSFT) > > >>
From: "Nathan Liu [MSFT]" on 24 Feb 2006 04:47 Hi Tony, Thank you for posting in the SBS newsgroup. Considering the current condition, I suggest you create a new thread on the SBS newsgroup. The reason why I recommend this is that you will get the most qualified pool of respondents, and other partners who the newsgroups regularly can share their knowledge. Thanks for understanding. Additionally, I am glad to provide the following general information for your reference: 0x80072f17 is explained as ERROR_INTERNET_SEC_CERT_ERRORS, which means certificate that was issued to your web site cannot be used for ActiveSync. To simplify the troubleshooting process, please disable Requiring SSL on ActiveSync Virtual Directory of IIS and let's focus on the issue during ActiveSync accessing without SSL. Since it is a Time Out error during ActiveSync accessing without SSL, in order to verify whether the issue is related to wireless network or Firewall Settings, please locate a Workstation in the LAN, and connect Pocket PC through cradle with this PC; then synchronize mailbox by ActiveSync on Exchange Server directly without passing Firewall. Please verify the issue and let me know the result. If the issue disappears here, obviously the Exchange Server is configured very well for ActiveSync access and issue must be caused by non-Exchange factors, such as Wireless Network or Firewall Settings. In this case, please contact the manufacturer directly for more information. Have a nice weekend! Best regards, Nathan Liu (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ====================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- >Thread-Topic: Support Code 0x80072F17 >thread-index: AcY5ECKcSguuzyd7SziZySGRrFmNHw== >X-WBNR-Posting-Host: 68.229.1.16 >From: =?Utf-8?B?VG9ueSBH?= <TonyG(a)discussions.microsoft.com> >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> <VVew3RMIGHA.3696(a)TK2MSFTNGXA02.phx.gbl> <F465A3F7-8227-4E69-A144-F4E2CF391ABC(a)microsoft.com> >Subject: RE: Support Code 0x80072F17 >Date: Thu, 23 Feb 2006 23:01:28 -0800 >Lines: 308 >Message-ID: <F64A2B00-B4FC-4800-8EC8-A658CD5BC78F(a)microsoft.com> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="Utf-8" >Content-Transfer-Encoding: 8bit >X-Newsreader: Microsoft CDO for Windows 2000 >Content-Class: urn:content-classes:message >Importance: normal >Priority: normal >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >Newsgroups: microsoft.public.windows.server.sbs >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:247143 >X-Tomcat-NG: microsoft.public.windows.server.sbs > >Any rate you could expand a little more on what exactly you guys did to >rememdy this situation. Been spending days and hours trying to get this going >and I'm having no luck whatsoever. > >I'd appreciate it, Thank you. > >"ABC" wrote: > >> I have now worked through this problem with Microsoft support in India and >> have resolved the problem. In order to assist anyone else with similar issues >> I have posted below the steps we took: >> >> Problem Description-: >> ================ >> The Dell Mobile device cannot synchronize with the Server, getting the error >> message: 0x80072f17 >> Steps performed in this case-: >> ====================== >> Here are the steps that we followed -: >> ð You were using SSL for accessing OWA. >> ð Form Based Authentication was activated. >> ð Checked the Exchange VDs in the IIS Manager............the >> authentication type was selected incorrectly on most of them..........changed >> the same >> ð A certificate issued to : publishing.instant-search.local was being >> used. >> ð The domain name was "internalsearch.loca", the external url being used >> was "mailserver.instant-search.com" >> ð Removed the certificate and installed a new one locally. >> ð We got an error code : 0x80072f17 - when trying to synchronize with >> the PDA from the Cradle from inside the network. >> ð The ICW wizard was already executed on the SBS 2003 and then the >> method 2 mentioned in the 817379 was followed. >> ð The new Virtual Directory called Exchange-OMA did not have the >> settings as expected. >> ð We deleted this directory and created a new one. >> ð Edited the Web.config to create the required log file. >> ð the log file indicated this : >> An Unknown error occured during the processing of the current request >> MESSAGE:User Anthony(a)InstantSearch.local has Microsoft(R) Exchange server >> BRUCE, which is not running Exchange Server 2003. That server is not >> accessible by Outlook(R) Mobile Access. >> SOURCE:Microsoft.Exchange.OMA.ExchangeDataProvider >> STACK: >> at >> Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolde rs() >> at >> Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo >> user) >> >> >> MESSAGE:Exception has been thrown by the target of an invocation. >> >> >> ð Removed the checkbox that said that "use SSL" >> ð Now OMA was working locally. >> ð The "hostmaster(a)dsvr.co.uk" is the ISPs server and it directs the >> queries for port 80 and 443 to their router. >> ð Tried accessing OMA using this ip address and could access OMA if i >> used https and could not access when using http. >> ð So it was letting us in through port 443 but not through port 80. >> ð The port 80 was freed up now and OMA was working but that was leaving >> the default web site open to the Internet. >> ð We restricted access to the internal website from the outside world by >> removing the "anonymous access" check box on the Defautl website. >> ð Both the OMA and just a query on port 80 were working fine now, both >> asking for authentication. >> ð Tried the following options : >> >> http://mailserver.instant-search.com/oma ---> 404 : requested url could >> not be found >> >> https://mailserver.instant-search.com/oma---> Asks for username and >> password and lets me in. >> >> http://mailserver.instant-search.com/exchange ---> 404 : requested >> url could not be found >> >> https://mailserver.instant-search.com/exchange---> worked properly. >> >> ð Removed the require SSL and FBA from the Exchange VD >> ð Tried the same again...............exactly the same result for both >> OMA and Exchange which was a clear indication that the router was blocking >> the requests on port 80. >> ð In the IIS logs there is no change when we try to use the external url >> on port 80 so the request was not reaching the Exchange Server. >> ð A few settings on the Exchange Server were changed again and the OWA >> had stopped working. >> ð We were getting the 440 Login timeout error messages even when >> browsing from the local Exchange Server. >> ð Checked from the local Exchange Server by browsing in the IIS Virtual >> Directory and that was working. >> ð Https://localhost/exchange brings up FBA and did not let us log in. >> ð Removed FBA and restarted IIS. >> ð Https://localhost/exchange was working now. >> ð Put back the FBA and restarted the IIS. >> ð We tryed to access OWA using the RWW for SBS. >> ð It was working fine now. >> ð Since you wanted this default website to be secured and ask for >> authentication all the time. >> ð Forced SSL on it and also set the Authentication type to "Integrated" >> >> If you have any questions after closing this incident feel free to contact me. >> >> Additional Information and Recommendations-: >> >> ================================== >> >> The Exchange Server Best Practices Analyzer can be downloaded from the link: >> >> http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyze rs/default.mspx >> >> This is a very handy tool to check the overall health of your Exchange Server. >> Articles related to configuring and using Certificates: >> >> 1. http://support.microsoft.com/?id=823024 >> >> 2. http://support.microsoft.com/?id=830827 >> >> 3. http://support.microsoft.com/kb/218445/ >> >> -- >> Anthony Capstick >> www.instant-search.com >> UK >> >> >> ""Nathan Liu [MSFT]"" wrote: >> >> > Hi James, >> > >> > Thank you for posting in the SBS newsgroup. >> > >> > First of all, please note that Charles is taking leave, and I am his backup. >> > >> > Considering the current condition, I suggest you create a new thread on the >> > SBS newsgroup. The reason why I recommend this is that you will get the >> > most qualified pool of respondents, and other partners who the newsgroups >> > regularly can share their knowledge. Thanks for understanding. >> > >> > Additionally, I am glad to provide the following general information for >> > your reference: >> > >> > SYMPTOMS >> > ======= >> > When you try to synchronize a Microsoft Windows Mobile-based device with a >> > computer, Microsoft ActiveSync4.0 may report an error similar to the >> > following: >> > >> > Activesync encoutered an error with the desktop. >> > Support code: 85010014 >> > >> > CAUSE >> > ==== >> > This problem occurs when one of the following conditions is true. >> > >> > o Microsoft Outlook is in offline mode. >> > o The application data folder is redirected. >> > o ActiveSync 4.0 is incorrectly registered to Outlook. >> > o Outlook script is blocked by Antivirus software. >> > >> > RESOLUTION >> > ========= >> > To resolve this problem, download and install Microsoft ActiveSync 4.1. >> > http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx >> > >> > I appreciate your time and cooperation. >> > >> > Have a nice day! >> > >> > Best regards, >> > >> > Nathan Liu (MSFT) >> > >> > Microsoft CSS Online Newsgroup Support >> > Get Secure! - www.microsoft.com/security >> > >> > ====================================================== >> > This newsgroup only focuses on SBS technical issues. If you have issues >> > regarding other Microsoft products, you'd better post in the corresponding >> > newsgroups so that they can be resolved in an efficient and timely manner. >> > You can locate the newsgroup here: >> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx >> > >> > When opening a new thread via the web interface, we recommend you check the >> > "Notify me of replies" box to receive e-mail notifications when there are >> > any updates in your thread. When responding to posts via your newsreader, >> > please "Reply to Group" so that others may learn and benefit from your >> > issue. >> > >> > Microsoft engineers can only focus on one issue per thread. Although we >> > provide other information for your reference, we recommend you post >> > different incidents in different threads to keep the thread clean. In doing >> > so, it will ensure your issues are resolved in a timely manner. >> > >> > For urgent issues, you may want to contact Microsoft CSS directly. Please >> > check http://support.microsoft.com for regional support phone numbers. >> > >> > Any input or comments in this thread are highly appreciated. >> > ====================================================== >> > >> > This posting is provided "AS IS" with no warranties, and confers no rights. >> > >> > >> > >> > -------------------- >> > >Thread-Topic: Support Code 0x80072F17 >> > >thread-index: AcYdwAdp4wa196lYTMOdtYUX35oOEg== >> > >X-WBNR-Posting-Host: 212.32.43.17 >> > >From: "=?Utf-8?B?SmFtZXMgRHVubg==?=" <James Dunn(a)discussions.microsoft.com> >> > >References: <B09A0558-677B-42AA-AD19-171E384E963C(a)microsoft.com> >> > <0BDA48D3-E33B-456D-82A5-8B71796EF591(a)microsoft.com> >> > <at9diznFGHA.3680(a)TK2MSFTNGXA02.phx.gbl> >> > <UQ#BLLoFGHA.1240(a)TK2MSFTNGXA02.phx.gbl> >> > >Subject: RE: Support Code 0x80072F17 >> > >Date: Fri, 20 Jan 2006 04:50:02 -0800 >> > >Lines: 268 >> > >Message-ID: <4D1E9F05-0A8E-4B65-8DAD-B8D2655A8460(a)microsoft.com> >> > >MIME-Version: 1.0 >> > >Content-Type: text/plain; >> > > charset="Utf-8" >> > >Content-Transfer-Encoding: 7bit >> > >X-Newsreader: Microsoft CDO for Windows 2000 >> > >Content-Class: urn:content-classes:message >> > >Importance: normal >> > >Priority: normal >> > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >> > >Newsgroups: microsoft.public.windows.server.sbs >> > >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >> > >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl >> > >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238171 >> > >X-Tomcat-NG: microsoft.public.windows.server.sbs >> > > >> > >Hi Guys >> > > >> > >I have been have the exact same problem with our SBS server. >> > > >> > >I have followed the step Charles has suggest but still get Support code >> > >85010014 when trying Sync a PDA windows mobile 5 with of SBS server >> > (either >> > >via active sysn or directly over a wireless connection) >> > > >> > >If there is anything I can do to help please le tme know >> > > >> > >Best regtard >> > > >> > >James Dunn >> > >jamesd(a)netinst.co.uk >> > > >> > >""Charles Yang [MSFT]"" wrote: >> > > >> > >> >> > >> HI, >> > >> >> > >> There is some additional steps: >> > >> >> > >> >> > >> 1. New account: >> > >> >> > >> For further test, please create a new test account and let me know the >> > >> following information. >> > >> >> > >> - Credential of this test account >> > >> - The public URL of your Exchange Server >> > >> - Domain name >> > >> >> > >> 2. Clean the sync state file in this problematic mailbox which Windows >> > >> Mobile 5.0 PPC tries to sync. >> > >> >> > >> 1). Open Internet Explorer. >> > >> 2). Click File-> Open. >> > >> 3). Please select the "Open as Web Folder" check box. >> > >> 4). Type >> > >> >> > http://servername/exchange/username/NON_IPM_SUBTREE/Microsoft-Server-Actives >> > >> ync and then click OK. >> > >> 5). Open the PocketPC folder. >> > >> 6). Delete the 'DeviceID' folder. >> > >> 7). Try to run Server ActiveSync in Windows Mobile 5.0 PPC again. >> > >> >> > >> 3. IIS Log >> > >> >> > >> Please collect the IIS log on Exchange Server so that I can perform >> > further >> > >> research: >> > >> >> > >> 1). On Exchange Serves, open IIS MMC, right click Default Web Site and >> > then >> > >> click Properties. >> > >> 2). Click Website tab and then check Enable logging. >> > >> 3). Stop the Default Website and RENAME the existing IIS log files under >> > >> C:\WINDOWS\system32\LogFiles\W3SVC1. >> > >> 4). Restart the Default Website and reproduce the problem, which will >> > >> generate new IIS log file with the exact error. >> > >> 5). Go to the following folder on Exchange Server: >> > >> C:\WINDOWS\system32\LogFiles\W3SVC1. >> > >> 6). Send me the log files to my working email address >> > >> v-chayan(a)microsoft.com. And please let me know the alias of the user who >> > >> encountered the issue. >> > >> >> > >> Please emails all information to my mailbox. Thanks again for your >> > effort. >> > >> >> > >> >> > >> Best regards, >> > >> >> > >> Charles Yang (MSFT) >> > >> >
From: Tony G on 26 Feb 2006 21:31 I have EAS working internally behind the firewall without a problem, SSL is disbaled on that VDir, here is what happens though, my issue as of now is when I goto Sync over the Cell network (GPRS) it says my account does not have permission to do so, although it works fine within our network, whether the device is connected to my PC going through the LAN, or disconnected going over our WLAN. For the ActiveSync settings on the phone SSL requirement is not checked, which i believe to be correct..here is some more info, when Im within our local network, I have Integrated Auth enabled on the /exchange-oma VDir, not on the OMA VDir or Exchange-Active-Sync VDir. I've tried removing Intergrated Auth just for the hell of it, but then it doesnt sync anymore within our network. so that is the scenario for the most part
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: GFI Faxmaker 12 setup on SBS2003 Next: dcom error 10021 |