AutoDiscover not working after Exchange 2010 SP2 - SP3 update.

Hi Everyone,
I'm sorry if this is a really simple thing, but i've played around for hours and exhausted google.
I run a 2010 exchange server for everyone at the office, and today I updated from 2010 SP2 to SP3.
The problem I have is auto discover no longer accepts anyones username or password. If you set the account up on the client machine by manually entering the details everything works great.
All the DNS records are correct and have been working for 2+ years. I have recreated the Autodiscovery virtual directory in EMC.
If i manually browse to mydomain/Autodiscover/Autodiscover.xml, when asked for a username and password it says it incorrect. I can then log in to OWA with the same credentials and it works.
Thanks,
Garrett
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mydomaincom.au:443/Autodiscover/Autodiscover.xml for user mydomain.com.au.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
HTTP Response Headers:
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/html
Date: Wed, 22 Apr 2015 00:44:51 GMT
Set-Cookie: __cfduid=dc0261b4643b5dbe27f750bbc28bfef7c1429663490; expires=Thu, 21-Apr-16 00:44:50 GMT; path=/; domain=.macarthurcs.com.au; HttpOnly
Server: cloudflare-nginx
WWW-Authenticate: Negotiate,NTLM,Basic realm="mydomain.com.au"
X-Powered-By: ASP.NET
CF-RAY: 1dad4d701ae911c5-SJC
Elapsed Time: 3357 ms.
Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com.au:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.

Hi,
Based on my knowledge, the above issue is caused by the loopback check being enabled. Please follow the steps below to disable loopback on the CAS servers:
1. Run regedit, in Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
2. Right-click Lsa, point to New, and then click DWORD Value.
3. Type DisableLoopbackCheck, and then press ENTER.
4. Right-click DisableLoopbackCheck, and then click Modify.
5. In the Value data box, type 1, and then click OK.
6. Quit Registry Editor, and then restart your computer.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Similar Messages

OOF not working after Exchange 2010 install

I have a Exchange 2007 server environment where I recently installed a new Exchange 2010 server. After installing the 2010 server, my clients are receiving the following error when trying to configure OOF. "Your automatic reply settings
cannot be displayed because the server is currently unavailable. Try again later." I've not moved any mailboxes to the new server, just installed it.
I've done all the tests I can find online and all pass without issue. I'ma able to get to the OOF URL without issue as well.
The 2007 server is on SP 3 rollup 12.

Hi,
The above problem generally occurs because the CAS server uses the credentials that you used to log on to Windows instead of the credentials that you used to log on to the mailbox in Outlook. I recommend you install the hotfix in the following KB to solve
this issue.
"Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later" error when you try to open the Out of Office Assistant in Outlook 2010
http://support.microsoft.com/kb/2596516
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support
Not sure that would be the issue with every machine on the network, plus the user I'm logging in with is the mailbox I need to access so the credentials should be the same.

Chat not working after nokia C3-01 software update...

Chat not working after nokia C3-01 software update from 5.65 to nokia 6.00

when is there's gonna this be fixed it has been more than a month
satisfaction level is decreasing with the product

Exchange AutoDiscover not working correctly in 2010/2013 environment

Here's my setup:
Mixed environment transitioning:
Exchange 2010 running on Server 2008 in a VM
Exchange 2013 running on Server 2012 in a VM
I have split dns so that autodiscover.domain.com points to my 2013 server internally and my 2010 server externally. When setting up new profiles in outlook internally, autodiscover seems to work fine. However, when I try moving the public autodiscover.domain.com
DNS record over to the 2013, things stop working (like auto profile setup).
I know that the 2013 server is reachable from the outside because mail.domain.com will to go owa and ecp without a problem. I can log in to both without an issue.
If I point public DNS back to my 2010 server, then all is well again with outlook anywhere and mobile connectivity.
I'm not really sure what needs to be tweaked for the 2013 server to be ready to take over the day to day communications so that I can decommission my 2010 server.
Here are the results of the connectivity analyzer:
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for me.
Testing Autodiscover failed.
Additional Details
Elapsed Time: 1774 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 1773 ms.
Test Steps
Attempting to test potential Autodiscover URL https://domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 489 ms.
Test Steps
Attempting to resolve the host name domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 98.129.228.152
Elapsed Time: 165 ms.
Testing TCP port 443 on host domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 97 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 225 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US, Issuer: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US.
Elapsed Time: 170 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name domain.com doesn't match any name found on the server certificate CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US.
Elapsed Time: 1 ms.
Attempting to test potential Autodiscover URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 1009 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 70 ms.
Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 189 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 300 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
Elapsed Time: 220 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover.domain.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 5/19/2014 12:00:00 AM, NotAfter = 5/18/2016 11:59:59 PM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 276 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 172 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 171 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 207 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 15 ms.
Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 76 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: HTTP Response Headers:
X-FEServer: SMSE2013
Content-Length: 0
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 115 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Elapsed Time: 39 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.domain.com in DNS.
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Additional Details
Elapsed Time: 39 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'domain.com' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it
Additional Details
There is no Autodiscover CNAME record for your domain 'domain.com'.
Elapsed Time: 28 ms.
I just double checked my SSL cert and it has the three typical entries:
DNS Name=mail.domain.com
DNS Name=AutoDiscover.domian.com
DNS Name=domain.com
I have assembled the output for the following commands
HERE
Get-OutlookProvider | fl
Get-OutlookAnywhere | fl
Get-ActiveSyncVirtualDirectory | fl
Get-AutodiscoverVirtualDirectory | fl
Get-EcpVirtualDirectory | fl
Get-OabVirtualDirectory | fl
Get-OwaVirtualDirectory | fl
Get-PowerShellVirtualDirectory | fl
Get-WebServicesVirtualDirectory | fl
Text
I have gone through the Exchange Server Deployment Assistant. Almost everything was as it should have been. I made some changes in the "Enable and configure Outlook Anywhere" and "Configure
service connection point."
I have switched external DNS over to my 2013 server, and the connectivity test is still failing. It is also not proxying the 2010 mailboxes through 2013 as it should (according to the Deployment Assistant).
I have a 2010 test account and a 2013 test account. Both work fine in their respective WebMail's, but the 2010 mailbox will not pull up through the 2013 WebMail.
Just for the heck of it, I have checked my SonicWall and it is configured the same for the 2010 host and the 2013 host. I knew that ports 80 and 443 were passing on both hosts anyway because the port 80 redirect works and https webmail works
on both hosts.
If I try to access the xml file directly on both hosts:
https://mail.domain.com/Autodiscover/Autodiscover.xml (2013)
https://webmail.domain.com/Autodiscover/Autodiscover.xml
(2010)
I do get an xml response from both of them after authenticating like this:
<Autodiscover>
<Response>
<Error Time="18:17:41.0173284" Id="2526055628">
ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Sooo...I'm stuck.

Update since my last post.
I have all mailboxes migrated off of 2010 and onto 2013. I'm ready to turn 2010 off as soon as I can figure out this autodiscover problem and get mail flow going in and out of the 2013 server instead of the 2010 one.
Brian, I had a http redirect enabled in 2013. I disabled that redirect and checked for any others. There is currently no redirect in place anywhere under the default web site (the root site now goes to an IIS 8 page). AutoDiscover is still
failing according to the Exchange Connectivity site.
When I switch autodiscover.domain.com over to the 2013 server I still get failures:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 146 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Mon, 11 Aug 2014 16:50:27 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 145 ms.
If I try to hit the xml manually, I get the expected 600 error after providing a username and password. Should IIS be prompting for credentials when hitting the path for AutoDiscover.xml directly?
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="10:53:38.3228589" Id="36607859">
<ErrorCode>600</ErrorCode>
<Message>Invalid
Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
If I switch autodiscover.domain.com back over to my 2010 server the test passes:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 444 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
<Culture>en:us</Culture>
<User>
<DisplayName>Exchange 2013. Test</DisplayName>
<EMailAddress>[email protected]</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Name>https://mail.domain.com/Microsoft-Server-ActiveSync</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>HTTP Response Headers:
Persistent-Auth: true
Content-Length: 736
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 11 Aug 2014 17:08:12 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Elapsed Time: 444 ms.
One interesting thing to note, is that <Url>https://mail.domain.com/Microsoft-Server-ActiveSync</Url>
is my 2013 server, not my 2010 server

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Free/Busy availability and Out of Office not working after Exchange 2003 to Exchange 2010

We just migrated from Exchange 2003 to Exchange 2010 as an intermediate step before we get to Exchange 2013. I want to make sure everything is working OK before we start the migration to Exchange 2013.
The users have Outlook 2010, and there are 2 issues. They can't view free/busy times for other people using the scheduling assistant, and they can't set their Out of Office messages. If they go in through Outlook Web Access, then these features
work!
I've searched the forums, and I see a few similar issues, but I don't think this is related to the .Net issue on the CAS server.
Any suggestions?
Thanks!
--Kent

Hi Kent,
Try checking the free busy info Outlook 2010 with running /cleanfreebusy switch
Check the Free/Busy System Public Folder and pointed out to the correct server on each mailbox DB in Exchange 2010
Find the public folder replica database
get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse | fl name,Replicas
In E2k10 check if the exchange 2003 is added in the replica list. If not try adding them and check.
force Public folder content replication.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.
That will encourage me - and others - to take time out to help you.
Regards,
Sathish

EWS 1.2, Exchange 2010 SP2/SP3 - Appointment message body gets wrecked on update

We're seeing a very irritating issue with EWS and Exchange when updating the message body on an Appointment. To head it off, it does not appear to be the bug detailed here:
http://blogs.msdn.com/b/dhruvkh/archive/2012/05/18/sending-appointments-from-ews-apps-where-did-my-html-go.aspx
It happens on both 2010 SP2 and SP3. We're creating Appointments with some HTML formatting the message body. Nothing fancy, just a few tables and a little bit of inline styling (since a css style header disappears into a black hole when you try to use it
as part of the Appointment message body). We're able to make a nice-looking message body that goes out in the meeting requests. Well, with the exception of downlevel text at the top, but there doesn't seem to be much we can do about that short of a double-tap
save.
The problem comes into play if we need to update the message body on the Appointment. All of this is automated, so the user cannot directly edit it. If we make any changes to the message body, it completely wrecks the HTML. It's still an HTML-formatted message,
but much of the styling is lost and it looks awful. This happens without fail when we alter the message body of an Appointment with any considerable level of HTML formatting. BodyType is HTML, of course. I've done some digging on the best body algorithm and
some of the MAPI properties related to it. Some interesting bits of note:
When the Appointment is first saved, PidTagRtfInSync is true. PidTagNativeBody is 2, which indicates an RTF message. PidTagBody is present. PidTagRtfCompressed is present. However, PidTagBodyHtml is not present. After updating the Appointment with a message
body edit, PidTagBodyHtml is present, but now PidTagRtfInSync is false and PidTagNativeBody is 3.
If PidTagBodyHtml is set directly as an extended property instead of setting the message body via the EWS Appointment object, then the formatting is wrecked right out of the gate. At least it's consistent that way...
Attempting to set PidTagNativeBody manually had no effect.
When viewing the PR_BODY_HTML contents between a good and bad message, the good one will contain the transformed HTML. It doesn't look much like what we had initially handed to it, but gets changed in the conversion process. The bad one is much closer to
what we wrote in actual HTML, but has still had much of the styling removed. It's as if creating the Appointment does the RTF conversion, but any subsequent changes use a completely different code path serverside and there does not appear to be any way around
it short of even more guess and check with EWS and Exchange chewing up HTML. This is complicated by being unable to find any documentation that details how and what gets changed, discarded, etc in the process.
This will always affect requests, but only seems to affect Appointments in the calendar of attendees if the body includes the downlevel text. Appointments without the downlevel text appear to survive updates with their formatting intact. Appointments with
downlevel text get their formatting wrecked with updates.
Has anyone run into this before? It was painful enough when we found that our previously-used email HTML formatter wouldn't work with EWS and everything had to be inlined, but now it seems that there are even more inexplicable problems to get around. Is
there a way to update the message body without this happening?

Ugh... hopefully I can ask you gentleman how to solve my issue.
I recently implemented code to allow our users to turn-on HTML-encoding for when our Sync'ing app goes to add/update items for them into Exchange.
If thev'ye turned-on HTML formatting, when I create a CalendarItemType's (in C# based off the EWSProxies.EWS.Itemtype) the Body.Value is being set with a string which contains very minimal HTML tags... just <br>'s instead of "\r\n" and for
URL link values we are embedding into the text, I'm encapsulating those within an <a href>
Example: <a href="http://TheWebSite.com/EventDisplay.aspx?uri=1234">Event Display Link</a>
My problem is... when I retrieve an item from Exchange... there is a huge amount of extra HTML encoding it wraps around everything!
By inspecting in the debugger... I've discerned that :
For Appts... the main bunch of text that I inserted in an item when originally creating it is contained just within the <div> tag.
For Tasks... the main bunch of text that I inserted in an item when originally creating it is contained just within the <body> tag (and on these there is no <div> tag created).
I was able to use the HTML Agility Pack and load this Body.Value string into the enhanced HtmlDocument object. I first attempt to parse first for the <div> nodes contents. If the <div> is not-null that's an Appt. If the <div>
is null, I instead parse out the <body> nodes contents, and those are Tasks.
I noticed for Appts :
For every <br> tag I had in my original text.. it appends two consecutive "\r\n" 's after it! No problem I can just do a Replace("\r\n", "") and zap those. But then the <a href> I have in there... it
encapsulates it with a <font> node where it sets a color for the link and also an underline <u> node. I can handle the <u> nodes easy enough with a Replace("<u>","") and a Replace("</u>", "");
But what about the damn <font> node? It's in the format of <font color=\"blue\"></font> and I'm sure the \"blue"\ part could be different for every user.
I noticed for Tasks :
It prepends a "\r\n" just inside the begininng<body> tag. Each of the original <br> tags gets an "\r\n" appended behind it. and for the TaskType for the <a href> node IT DOES NOT encapsulate it with the <font>
and <u> nodes as it does for the Appt.
How can I stop it from changing the Body content when retrieving it? Will it not change anything if I go the extra mile and make sure to wrap everything with an <html> and <body> node when initially creating the items?
Any and all help on this issue is sorely appreciated.
Thank You,
-G

Setting Out Of Office from Outlook not working with exchange 2010

Hi
We have an exchange 2010 server with 2 load balanced CAS server and Mailbox servers in a DAG. We have a few domain
names accepted (will call it firstdomain.com and seconddomain.com) but only one is in certificate (firstdomain.com).
The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later” where
setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
we have both internal and external urls for all virtual directories set to external
host address (https://mail.firstdomain.com
  etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
( https://mail.firstdomain.com/ews/exchange.asmx)
wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
I enabled logging in outlook and thats what I am getting in there:
We have an exchange 2010 server with 2 load balanced CAS server and Mailbox servers in a DAG. We have a few domain
name accepted (will call it firstdomain.com and seconddomain.com) but only one is in certificate (firstdomain.com).
The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later” where
setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
we have both internal and external urls for all virtual directories set to external
host address (https://mail.firstdomain.com
  etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
( https://mail.firstdomain.com/ews/exchange.asmx)
wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
I enabled logging in outlook and thats what I am getting in there:
1600       0x49763D20        02/02/15 16:50:44
+++++++++++++++++++++++++++++++
1600       0x49763D20        02/02/15 16:50:44
OWINHTTP SEND HTTP REQUEST BEGIN
1600       0x49763D20        02/02/15 16:50:44
Profile=Outlook
1600       0x49763D20        02/02/15 16:50:44
  [email protected]
1600       0x49763D20        02/02/15 16:50:44
URL=https://mail.firstdomain.com/ews/exchange.asmx
1600       0x49763D5F        02/02/15 16:50:45
GetLastError=0; httpStatus=401.
1600       0x49763D5F        02/02/15 16:50:45
OWinHtpp disabled auth schemes:
1600       0x49763D5F        02/02/15 16:50:45
<NONE>
1600       0x49763D5F        02/02/15 16:50:45
OWinHtpp supported auth schemes:
1600       0x49763D5F        02/02/15 16:50:45
Negotiate
1600       0x49763D5F        02/02/15 16:50:45
NTLM
1600       0x49763D5F        02/02/15 16:50:45
Basic
1600       0x49763D5F        02/02/15 16:50:45
OWinHttp attempting Auto-Negotiate with Desktop Credentials.
1600       0x49763D5F        02/02/15 16:50:45
OWinHttp USING pcreds->dwAuthScheme:
1600       0x49763D5F        02/02/15 16:50:45
Negotiate
1600       0x49763D9D       02/02/15 16:50:45
GetLastError=0; httpStatus=500.
1600       0x49763DAD       02/02/15 16:50:45
OWINHTTP SEND HTTP REQUEST END
1600       0x49763DAD       02/02/15 16:50:45
Last thing - we are using proxy server and with proxy off it works fine although all
possible exchange server hosts/domains/ip addresses excluded from proxy.
Aside from obvious question - what can be wrong and what to test next, another question
is - how can I check/monitor setting OOF on server side (log files etc)?
Last thing - we are using proxy server and with proxy off it works fine although all
possible exchange server hosts/domains/ip addresses excluded from proxy.
Aside from obvious question - what can be wrong and what to test next, another question
is - how can I check/monitor setting OOF on server side (log files etc)?
Thanks

Hi,
According to your description, I understand that Outlook client with second domain name cannot use OOF setting and get an error “Your Out of Office settings cannot be displayed, because the server is currently unavailable.” However OWA works fine.
If I misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account or some special user experience this question.
Would you please try to reconfigure Outlook profile in other Computer, Outlook version and return the results?
If this issue only appeared on Outlook 2010, please refer to below link to troubleshooting:
https://support.microsoft.com/kb/2596516?wa=wsignin1.0
Please try to run ExBPA to test OOF to get more details about this question. Additional, I find a similar thread about your question, for your reference:
https://social.technet.microsoft.com/Forums/exchange/en-US/81ebc1de-c899-4097-b224-a0e4b33e4162/users-cant-open-out-of-office-assistant
Best Regards,
Allen Wang

Scan to Email from VPN sites not working on Exchange 2010

Hi,
       I have Exchange 2010 SP1 with HCAS array installed in the organization. We have site offices connected through site to site VPN. All our outlook clients are working fine in the sites. We have MFP printers in both Head
office and site offices. HO scanners are working fine for Scan to email (Internal recepients), but site offices scanners are able to send the email without any attachment. We have tried creating new receive connectors for the scanner with anonymous authentication,
but still attachments were not receiving. Log found in the printer as shown below.
1 page(s)
Document Size:A4
Subject:Scanned File from SS AUH Printer
E-mail Destination(s)
to: [email protected] (Success)
E-mail processed by the Device
File format: pdf (color)
File Size:0
I have configured Valid mailbox as the SMTP authentication and from Address for the scanner and the User received the following delivery failure report
******* HP Digital Sending: Delivery Error *****
The following job has not been delivered. Please retry sending the job. If the problem continues contact your network administrator.
----- Transcript/error-code of session follows -----
0/33 (0X21)
Kindly advice.
Regards,
Emthias
With Regards, Emthias Abdulsalam

Hi
   >>HO scanners are working fine for Scan to email (Internal recepients), but site offices scanners are able to send the email without any attachment. We have tried creating new receive connectors for the scanner with
anonymous authentication, but still attachments were not receiving.
    I have question about these sentences. If I misunderstand your saying, please correct me.
    1. Have scanners function to send email to exchange system?
        Did you test it before?
Do you try to send email to another account like (windows live,yahoo)?
    2. According to your error log, it seems to be network configuration problem.
        Do you modify network configuration of scanner?
    3. Can you check transport rule of your server?
You can read this
article. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Help please! Keyboard not working after installing windows XP sp3 on T61

I just changed to windows XP sp3 in last weekend on my T61. From then on, when I turn on the T61 every morning, the key board is not working, sometimes I could not type password. I need reboot several times to make it work. I installed the keyboard customizer utility from some online information, however, it's not helping. I searched the lenovo support website, but there are lots of drivers there,I don't know which to pick. Does anyone had met the similar issue or know how to solve it? Thanks a million!

I have exactly the same problem. It is not related to docking for me - just regular standby/resume. A reboot solves the problem. Not exactly what you'd expect from a high-end business model. This is the first time in my over 22 years history of using computers that the keyboard fails randomly. Fix this IMIDIATELY Lenovo!
Message Edited by Chigu on 06-13-2009 12:39 PM

Active sync on bionic will not work with exchange 2010

We recently upgraded our corporate email system to exchange 2010. Prior to this, while on exchange 2007 I had no issues with active sync. On the day we upgraded active sync no longer worked for me I have others at work running older Droid OS. 2.2.2 and 2.2.3. They have no issues with the new exchange. I am on 2.3.4. I am able to do the setup and the setup will detect the new server and act as if the account is setup correctly. When it tries to sync I get a "connection error" message.

Hi,
From your description, I recommend you use the following URL to check if you can access EAC. I see it works for several people about this issue.
https://<Exchange 2013 CAS FQDN>/ecp?ExchClientVer=15
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

HDMI output not working after 1.0.8.6067 update on sharp LCD TV's

Have three TV's two of which are Sharps Aquos and the other is a Samsung. After updating to 1.0.8.6067 the Playbook cannot detect the two Sharps(each different model #'s) . I have three different cables that worked fine before the update and all three cables still work perfectly with the Samsung TV. This issue has been giving me trouble from when i got the device. I even sent the unit back to RIM and of course it was no fault found. About a month ago it suddenly started to work on the Sharps. i've been using the playbook daily on these TV's without incident until the latest software update. It now only works on the Samsung. Obviously something is going on with the playbook HDMI software driver. RIM support was unable to get it working reliable during my 3 month support window. Of course it started to work on the last day of my support but the recent update has put me back to square one. Any suggestions?
Tony

I have not had any issue with any brand TV yet
I dont remember if I tried a sharp on not. I do know that teh several Samasung ones worked fine.
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Facetime, iMessage, and Mail not working after iOS 6.1.3 update

I've had my iPod touch 4th generation since Oct 2010 and never updated the iOS until very recently. Before the update, Facetime worked consistently and easily. After I finally got around to updating my iOS a week ago, my iPod has come into severe issues.
99% of the time, I cannot send or receive Facetime calls. If I try to make a call, it doesn't make the dial tone and eventually it just says "Connection Lost". Nothing happens if someone is trying to send me a call. I only Facetime with my boyfriend and his iPod hasn't changed since Facetime was last working. HIs other iPod is also updated with iOS 6.1.3.
I never used iMessage before the iOS update, but because it says on Apple support that it uses push notifications like Facetime does, so I tried it. Most of the time, I cannot send or receive messages. I rarely used Mail before the update, but I never had a problem with it. Now, when I enter my gmail password, it keeps saying my username and password are not correct, even though I haven't changed my credentials.
I only use my iPod for Facetime, iTunes, and Pandora. I don't need iMessage or Mail, but I am testing with those to see if this can help find the root cause of the problem. Pandora works smoothly so I know it's not a wifi connection issue. I have searched for remedies on end and tried:
1. Reset, turn off/restart, turn Facetime on and off, etc.
2. Changing the DNS server address to 8.8.8.8, which made Facetime work normally for one time and never again
3. Updating my Apple ID password online, then signing out and signing back in
4. Creating another Apple ID with my other gmail account. Maybe 1 out of 10 Facetime call attempts, I can generate the dial tone, but when my boyfriend clicks to receive the call, it says that I am unavailable. iMessage has about the same success rate. It seems when I miraculously can send or receive texts through iMessage, I can manage to get the dial tone when I try Facetime, though the call cannot go through.
This is of course extremely frustrating and I highly regret the update now. I was hoping for an improved iPod after the update, and now I have a near-dud! I did make sure to check my location and date and time, and both are correct (US, Central time). Any help would be greatly appreciated. Thank you.

I spoke too soon. I tried Facetime again last night and had the same problems. Another factory reset did not work. I think it may be time to just call Apple support.

Port Forwarding not working after 7.7.1 Firmware update

I bought the new 6th generation Airport Extreme today, and after I set it up, everything worked great. I have a VoIP phone that needs to have traffic on port 5060 forwarded to it, and that worked just fine as well.
However, I then updated to the 7.7.1 firmware, and the port forwarding stopped working. I tried a hard reset of the Airport and re-entered all the settings, but it still didn't work. I spent about 30 minutes on the phone with 2 Apple support people who tried hard, but couldn't help. They also couldn't find a way to download the 7.7 firmware, so there was no way to downgrade. They suggested I go back to the store and exchange it for another one, which I did, and now it all works again.
Has anyone else had issues with port forwarding on 7.7.1? I'm just wondering how I'll ever be able to update the firmware, since failure means having to get a new Airport.

Huh,
turns out the problem went away with another restart of the Mac Mini. I'm still uneasy about it though, as I do not understand how it went from working to not-working over night in the first place. But, at least for now, the problem seems gone.
Thanks for commenting.
Cheers
Niels Olof

Earbuds with Mic and Skip Functions not working after IOS 6.0.1 update?

I have earbuds with a mic and skip buttons functions and noticed that mic and the skip music functions stop working after updating to IOS 6.0.1. Now when I talk on the phone the mic on iPhone itself is working and not the mic on my earbuds. Also when playing music he skip functions has stop working. Has anyone noticed these problems?

Phone restart > if that doesn't work then do a reset of the settings. Full restore would be the last option.

AutoDiscover not working after Exchange 2010 SP2 - SP3 update.

Similar Messages

Maybe you are looking for