Http Error - 18599
Contents |
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
Sign in Pricing Blog Support Search GitHub This repository Watch 14 Star 14 Fork 2 bombadil/mod_proxy_msrpc Code Issues 14 Pull requests 0 Projects 0 Wiki Pulse Graphs New issue Error -19710 and -18599 #21 Closed Fredde87 https://groups.google.com/d/topic/microsoft.public.mac.office.entourage/EVrsIiiwzT8 opened this Issue May 31, 2014 · 3 comments Projects None yet Labels invalid Milestone No milestone Assignees No one assigned 2 participants Fredde87 commented May 31, 2014 Hi there, First of all, https://github.com/bombadil/mod_proxy_msrpc/issues/21 thanks for a awesome module! Just what I badly needed! I have it setup with Apache 2.4 and its working great for most clients (iPhones etc). However, I am having problems with Outlook 2011 for Mac. The clients seem to start to synchronise successfully but will then fail with error -19710 and -18599. Any ideas what could cause it? Fredde87 commented May 31, 2014 Sorry, couldnt find a way to attach a log file, below is copy and paste of a failed attempt, Logging started on 05/31/2014 @ 09:03:52.677584 [ 6885us, d -3496952us] Outlook Exchange Web Services: EWS: Request data on thread=2127696532, XML data= soap:Headeren-US/t:MailboxCulture/t:TimeZoneContext/soap:Headersoap:BodyIdOnly/t:BaseShapemyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1@mydomain.com/t:EmailAddress/t:Mailbox/t:DistinguishedFolderIdmyuser1
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Unable to connect to Exchange after upgrading from Office 2011 to 2016 for Mac Previous Versions of Exchange > Exchange 2010 for Hosters Question 0 https://social.technet.microsoft.com/Forums/office/en-US/84d5afcd-7859-423d-8e3b-123b03e90d34/unable-to-connect-to-exchange-after-upgrading-from-office-2011-to-2016-for-mac?forum=exchange2010hosters Sign in to vote After upgrading my Macbook Pro which runs OSX 10.10.5 (Yosemite) from Office 2011 to Office 2016, I am no longer able to connect to my Exchange 2010 corporate mailbox. Here is what http://www.ibm.com/support/docview.wss?uid=swg1PK18599 I've tried and what I'm seeing: I start Outlook 2016 which doesn't have an Exchange account.I go into Outlook==>Preferences==>Accounts.I click on the +v button at the bottom and select Exchange...I enter my Exchange email address, leave the http error Method as "User name and Password" and enter my User name (domain\username) and password.I uncheck the "Configure automatically" checkbox.I enter the email server name (same one I used in Outlook 2011 which worked) and click Add Account.I then get this message: A secure connection cannot be established with the server xyz.com because its intermediate or root certificate cannot be found. Do you want to continue? I click Continue.At this point, I start seeing emails access to the populate my inbox and the little dot next to the account I just created turns from yellow to green and it looks like everything is working properly.After a minute or so, I then notice that the little dot turns back to yellow. I close out of the Accounts screen.In the lower right corner of the main Outlook window it says "Connecting to: xyz". I do see all of my emails but it is no longer connected.Now if I compose a new email and attempt to send it, I the "Sending..." status with a blue progress bar in the bottom middle of the screen and the email never gets sent.Now if I close Outlook and restart it, I get the exact same message in 7 above.After a while, I'll see a '!' in the lower right and when I click on that, I'll see a -18599 error message. So it appears that something has changed in the way Outlook for Mac connects to Exchange between 2011 and 2016. Any suggestions or ideas would be greatly appreciate. Thank you. Friday, August 14, 2015 9:17 PM Reply | Quote Answers 0 Sign in to vote Hi, Please confirm whether you canuse your Exchangeaccount with "Configure Automatically" option. In your manually account setup, please confirm the Authentication settings and set it to authentic
IS USED IN A WSDL OR XSD FILE BEFORE IT IS DEFINED Subscribe You can track all active APARs for this component. APAR status Closed as duplicate of another APAR. Error description wsdl2java or the WebSphere development tools, such as Rational Application Developer or WebSphere Studio Application Developer, will log a WSWS3029W and then a subsequent WSWS3204E if the xsd or wsdl file uses a type before the type is actually defined. The WSWS3029W is logged when wsdl2java encounters the type and makes a mapping of that type to SOAPElement, since it has not other definition for this type. . The WSWS3204E is logged when the actual type definition is processed. Since wsdl2java already created a definition for this type, it logs the WSWS3204E when it encounters the actual definition. . These are the error messages that are logged WSWS3029W: Warning: The xml construct named {http://www.ibm.com/AC/commonbaseeve nt1_1}locationTypeType cannot be mapped to a java type. The construct will be m apped to javax.xml.soap.SOAPElement. WSWS3204E: Error: {http://www.ibm.com/AC/commonbaseevent1_1}>locationTypeType al ready exists. . The WSWS3204E message should be changed to indicate that a likely cause of the problem is the order of the xsd type definition and the use of the xsd type. The message text does not indicate that this is a likley cause of the problem. I propose rewording the error message as follows in the User Response of WSWS3204E User Response: Verify that the indicated type is defined before it is used in a type definition. If the type is not defined before it is used, then an accompanying WSWS3029W message is logged. If this situation is not the cause of this logged error, then see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ Local fix Restructure the xsd or wsdl file so that the definitions of types occur before the actual use of the type in another type definition or in a method definition. . This first,