|
|
Browse by Tags
All Tags » DevMsgTeam » http (RSS)
Showing page 1 of 2 (11 total posts)
-
One of my customer updated that whenever they try to make the remote Exchange Web Service (EWS) call from his C#.Net 2008 application (VS.Net 2008 - .Net Framework 3.x), he gets the following error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel I had a detailed look at their application code. // Create the Exchange Service Binding ExchangeServiceBinding esb = new ExchangeServiceBinding(); // Add its relevant Credentials like user
Posted to Le Café Central de DeVa (Weblog) by deva on May 23, 2009
Filed under: Exchange Web Services (EWS), Exchange Server 2007, Best Practices, certificate authorities, Secure Sockets Layer(SSL), TLS, Errors, Troubleshooting, DevMSGTeam, Programming, Security, SSL, HTTP, CredentialCache, credentials, proxy, EWS, ExchangeServiceBinding, x509, EWS Troubleshooting
-
Hmmm, there are very few samples on setting multiple extended properties on folders using a POST to EWS... so, I thought I would blog one. This sample can be used with: http://blogs.msdn.com/webdav_101/archive/2009/02/27/howto-post-xml-to-ews-using-exchangeservicebinding-credentials.aspx Note the following: The version is set. Each property being set is done under a separate SetFolderField node. <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
Posted to Dan's WebDAV 101 (Weblog) by danba on February 27, 2009
Filed under: Exchange 2007, EWS, sample, folder, xml, http, exchange web services, DevMsgTeam, post, extended property
-
'This example uses PS_INTERNET_HEADERS for setting a custom property const smbx="mymailbox" ' TODO: Change const ssrv="myserver" ' TODO: Change const mycdoInetPset = "8603020000000000C000000000000046" const myXheader = "X-SPAM" ' TODO: Change to your property set oses=createobject("mapi.session") oses.logon "", "", false, true, 0, true, ssrv & vblf & smbx set omsg=oses.inbox.messages.getfirst sfrom=omsg.fields.item(myXheader,myCdoInetPset).value wscript.echo sfrom omsg.fields.add myXheader,
Posted to Dan's WebDAV 101 (Weblog) by danba on January 14, 2009
Filed under: Exchange 2007, EWS, xml, http, exchange web services, DevMsgTeam, post, ExchangeServiceBinding
-
Code Snippet (C#): //Declaration part string strExchSvrName = "" ; string strMailbox = "" ; string strCalendarUri = "" ; string strDomain = "" ; string strUserName = "" ; string strPassword = "" ; System.Net.HttpWebRequest WebDavRequest = null ; System.Net.HttpWebResponse WebDavResponse = null ; System.Net.CredentialCache MyCredentialCache = null ; byte [] bytes = null ; System.IO.Stream WebDavRequestStream = null ; // Provide the Exchange server name; strExchSvrName = "mydomain.in" ; // Provide
Posted to Le Café Central de DeVa (Weblog) by deva on December 3, 2008
Filed under: Exchange Server 2003, Code Snippets, Calendar, WebDAV, XMLHTTP, appointment, DevMSGTeam, Programming, development, C#, HTTPS, HTTP
-
Please find the Code Snippet Access Exchange Server 2003 using WebDAV in your Web application per KB : 1: 'Declaration Section 2: Dim strServerName as String = "Server Name" 'TODO: Change to your environment 3: Dim strDomain as String = "Domain Name" 'TODO: Change to your environment 4: Dim strUserID as String = "Username" 'TODO: Change to your environment 5: Dim strPassword as String = "Password" 'TODO: Change to your environment 6: 7: ' Create our destination URL. 8: Dim strURL As String = "https:/"
Posted to Le Café Central de DeVa (Weblog) by deva on December 2, 2008
Filed under: Exchange Server 2003, Code Snippets, WebDAV, design, XMLHTTP, DevMSGTeam, Programming, development, HTTPS, SSL, HTTP, XML Parser, Forms Based Authentication
-
I started working from Visual Basic 6, where i had used XML Parser (MS XML) to fetch the data's using WebDAV. But the same logic won't apply for you when you do with .Net applications. So, where we need to use MSXML and .Net Framework classes's for XML? Microsoft XML Core Services (MSXML) : As i updated you earlier you can easily use MSXML in Visual Studio 6.0 applications as DOM and SAX Parser with support for XSLT and XPath. .NET Framework Classes for XML : But when you're planning to implement
Posted to Le Café Central de DeVa (Weblog) by deva on October 23, 2008
Filed under: Code Snippets, Architecture, WebDAV, KB, Troubleshooting, DevMSGTeam, Known Issues, Programming, .Net, development, COM, Interop, HTTP, Visual Basic, XML Parser, MS XML
-
Publishing Free/Busy data: Free/busy data is published information that contains a user's personal availability data based on the user's schedule. Microsoft Exchange Server uses the information extensively when users schedule meetings. Exchange Server 2003 stores free/busy information in a dedicated public folder that is named SCHEDULE+ FREE BUSY . This folder contains a separate subfolder for each administrative group in your Exchange organization. When a user publishes free/busy data, Exchange
Posted to Le Café Central de DeVa (Weblog) by deva on October 13, 2008
Filed under: Public Folder store, Exchange Server 2007, Exchange Server 2003, cmdlet, Powershell, Tutorials, Outlook 2007, MAPI, Outlook 2003, Calendar, entourage, Active Directory, Outlook Mobile Service, mailbox, Events, Errors, Troubleshooting, Customization, appointment, DevMSGTeam, Programming, MSDN, Outlook UI Issues, MAPI Error, Schedule, Free/Busy, Public Folder, Application Log, Outlook Web Access, Client Access Server (CAS), Outlook Errors, Offline Address Book (OAB), permissions, legacy, Test-OutlookWebServices, MSExchangeFBPublish, Unified Messaging, AvailabilityAddressSpace, Availability Service, Profile, MSExchangeSA, HTTPS, resource mailbox, SSL, HTTP, MadFB, Outblook Mobile Access, Outlook Anywhere, Autodiscover, Publish, GUID, cleanfreebusy, Exchange Connector, legacyExchangeDN, forest
-
Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol Specifications section of MSDN in preliminary form for developers to review and provide feedback. You can read more about the announcement in this press release. Here is the press release: Microsoft Publicly Posts Additional Protocol Documentation http://www.microsoft.com/presspass/press/2008/apr08/04-08ProtocolPR.mspx
Posted to Dan's WebDAV 101 (Weblog) by danba on May 1, 2008
Filed under: Outlook, meeting, WebDAV, Exchange, properties, security, VCalendar, mime, stream, appointment, distribution, attachments, .msg, mapi, authentication, category, messaging, c++, property, icalendar, availability, folders, descriptor, access, http, rtf, format, transport, meeting requests, guid, autodiscovery, permission, attachent, rfc2445, personal, sms, encode, book, s/mime, rpc, resources, protocol, users, uid, decoding, client, configuration, message body, redirects, X-, rfc2447, rss, ietf, specifications, groups, directory access, protocal, nspi, flagging, journal, mailbox, attachements, extends, personal distribution, flags, provisioned, streams, note, address, events, working, encoding, compressed, search folder, permissions, server, permissible, conversion, standard, schema, hours, directory, body, offline, rfc2446, behalf, structures, notifications, oab, converts, smtp, address book, remote operations, operations, contacts, structure, response messages, MS-OXO-, decode, compressed stream, warning, rights-management, retrieval, information, core, enriched text format, forum, specs, extensions, .msg file, structs, bulk, msg files, object, best body retrieval, voice mail, .msg files, reminder, msg file, bulk data transfer, rights management, enriched, support, mms, templates, pop3, data transfer, phishing, best, compression, document, documentation, DevMsgTeam, webdav101blog
-
Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol Specifications section of MSDN in preliminary form for developers to review and provide feedback. You can read more about the announcement in this press release. Here is the press release: Microsoft Publicly Posts Additional Protocol Documentation http://www.microsoft.com/presspass/press/2008/apr08/04-08ProtocolPR.mspx
Posted to Dan's WebDAV 101 (Weblog) by danba on May 1, 2008
Filed under: Outlook, meeting, WebDAV, Exchange, properties, security, VCalendar, mime, stream, appointment, distribution, attachments, .msg, mapi, authentication, category, messaging, c++, property, icalendar, availability, folders, descriptor, access, http, rtf, format, transport, meeting requests, guid, autodiscovery, permission, attachent, rfc2445, personal, sms, encode, book, s/mime, rpc, resources, protocol, users, uid, decoding, client, configuration, message body, redirects, X-, rfc2447, rss, ietf, specifications, groups, directory access, protocal, nspi, flagging, journal, mailbox, attachements, extends, personal distribution, flags, provisioned, streams, note, address, events, working, encoding, compressed, search folder, permissions, server, permissible, conversion, standard, schema, hours, directory, body, offline, rfc2446, behalf, structures, notifications, oab, converts, smtp, address book, remote operations, operations, contacts, structure, response messages, MS-OXO-, decode, compressed stream, warning, rights-management, retrieval, information, core, enriched text format, forum, specs, docment, extensions, .msg file, structs, bulk, msg files, object, best body retrieval, voice mail, .msg files, reminder, msg file, bulk data transfer, rights management, enriched, support, mms, templates, pop3, struct, data transfer, phishing, best, compression, document, documentation, DevMsgTeam
-
CDO 1.21, CDOEX, etc can get Free/Busy information, however WebDAV cannot directly. You may use a GET against OWA to get this information. A GET against an OWA URL is really not a WebDAV call… it’s really just plain HTTP GET call – you just need to be sure that the URL is correctly formatted. Most OWA URLS being called in this manor are not supported, however this is one of the few exceptions. Here are some things to be aware of: · Free/Busy information is stored in the public store under the NON_IPM_SUBTREE
Posted to Dan's WebDAV 101 (Weblog) by danba on April 16, 2008
Filed under: OWA, WebDAV, VBS, oof, C#, free, freebusy, free busy, get, sample, .net, url, http, out of office, out of facility, scheduling, free/busy, oof vb.net, DevMsgTeam, webdav101blog
1
|
|
|
