Activesync not working for 27 days

[snotty54]

Hi All:

Still trying to fix my activesync, on the 16th it'll have been down for 30 days. Right now, running the MS Exchange Remote Connectivity Analyser, I'm getting this error: "Testing HTTP Authentication Methods for URL

https://mail.externaldomain.com/Microsoft-Server-Activesync/.

The HTTP authentication test failed"
"The Initial Anonymous HTTPS request didn't fail, but Anonymous isn't a supported authentication method for this scenario".
There is a solutions link but that didn't help, googled it and I've tried a couple of things, but no luck. Can anyone shed some light on my problem?

Thanks,

Scott

 

[58sniper]

What do the logs say? Can you be more specific about what you've tried?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.exchangeblogs.com/

 

[snotty54]

Hi Pat:

Which logs should I look at? There are a lot of them, and none seem to refer to Direct Push or Activesync.

I have changed very little, as I'm afraid to break Exchange or the Server. Since the autodiscover name error began in OA, I have deleted the original simple cert and installed a UCC cert from GoDaddy with 4 sans, and the autodiscover naming error coming up everytime I opened OA went away. The only other thing I did was based on a recommendation of BPA, in an error discovered by BPA, I deleted the port 443 binding to Default Web Site. This made OA and OWA go down and I finally figured out how to resurrect the Default Web Site without port 443 bound to it, through EMS I think, but I didn't record what I did.

I really don't know where to look now, and I've read and considered so many things to try and fix it that I'm in a general state of confusion. I've looked at Event view more than once but the error files, many of which I've tried to research online, have not lead me to anything definitive enough to try to fix the direct push.

Scott

 

[snotty54]

Hi Pat:

I spent some time thinking on the way home and I did correct the binding of port 443 to the Default Web Site by deleting the reference to it in the applicationhost.config file in %windir%\System32\inetsrv\config. That got OA and OWA working again, still no joy with mobile push. Near to the beginning of this saga, following a recommendation from another thread that the virtual directory might be corrupted, I deleted the Microsoft-Active-Sync virtual directory under Default Web Sites and tried to re-install it. I used the command to get the proper identity and location of the virtual folder before I deleted but had problems and finally searched for a generic command and finally made it work. These experiences make me reluctant to try anything unless it is specific to the prob. Perhaps the Microsoft-Active-Sync virtual folder is installed incorrectly? I don't get an error for that in the testactivesync program. I've checked the authentication and ssl settings for all the virtual folders and they appear to be correctly set according to what I can find online

Does any of that suggest anything? Can you tell me which log file folder might contain the errors that would pertain to activesync push?

Scott

 

[snotty54]

Started going through all the log files in event viewer, and the folder that seems to have errors rather than announcements is the admin events. Here are several of them:

Event ID = 3 - Config of Admin Connection/tcp in sql instance MSSMLBIZ is not valid

Event ID = 13042 - Self-update is not working

Event ID = 10010 - Server (XYZ) did not register with DCOM within the required timeout

Event ID = 2003 - Config info of performance library "c:\windows\system32\sqlctr90.dll" for instance MSSQL$MSSMLBIZ service does not match the trusted performance library info stored in registry. Functions in this library will not be treated as trusted.

Event ID = 3760 - sql database "ShareWebDb" on sql server instance n:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Login to ShareWebDb failed. Login failed for user "NT Authority\Network Service.

Event ID = 2424 - Update cannot be started because the content sources cannot be accessed. Fix errors and try update again.

Update on the server has not been working properly since I installed SBS2008/Exc2007 and I had to change registry settings on the client computers for them to update by themselves. Since this has not been working since the beginning and activesync push had worked for a couple of months prior to quitting last month, I presume they are unrelated. I'm not sure if any of these errors pertain to activeysync push or just update.

There are other errors sprinkled through other log event files but they don't seem to be linked to activesync.

Any ideas on where to go, what to look for, what to do to get ActivesyncPush working again?

Thanks

Scott

 

[58sniper]

Look at your IIS logs.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.exchangeblogs.com/

 

[snotty54]

Guess this is kinda dumb, and you're probably going to lose your patience with me, but I really can't seem to find any log files for IIS. I went into Events on the admin menu and looked through there but no reference to IIS. Selected my server in the IIS console and went to the C:\inetpub\logs\logfiles and went into every directory and examined the latest file but no reference to any error. It was mostly numbers with a few words but no theme or any kind of error. It wasn't obvious what the files were for.

Going to help on the IIS console comes up with a way to "enable" log files but thats all I could find.

Can you specifically tell me where I can find the IIS log files?

Thanks,

Scott

 

[58sniper]

http://www.lmgtfy.com/?q=where+are+IIS+logs

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.exchangeblogs.com/

 

[snotty54]

Thanks Pat. Should've figured that out myself. Looking through the folder contents there are 5 sub-directories that I think pertain to other things, and the log files for IIS are the "IN1011" | "IN1012" and so on. There are 6 of these files and the first one is about a month or so after I got the Server and Exchange first working and they are spaced roughly a month apart, with the last one on 14th April. Looking at the log file for February when the Push sync was working, here is a typical line: ""ROESERVER","RAS",02/10/2011,00:24:41,4,,,,,,,,"192.168.0.2",,,"192.168.0.2",,,,,,,,,,0,,,,,,7,,,,"1",,,,,,,,,,,,,,,,,,,,,,,,,,2,,,,"

Another one from the same log file that may pertain to push sync is: ""ROESERVER","RAS",02/25/2011,17:21:15,4,,,,,,,,,,,,,,,5,,,,,,0,,,,,,2,,,,,,,,,,"{7720246E-F30B-4A40-BDA3-A9E499125E0B}",,,,,,,,,,,,,,,,,,,"TS GATEWAY AUTHORIZATION POLICY",,,,,"

Bringing up the latest log file of the 14th April, the first entry is: ""ROESERVER","RAS",04/02/2011,00:15:00,4,,,,,,,,"192.168.0.2",,,"192.168.0.2",,,,,,,,,,0,,,,,,7,,,,"1",,,,,,,,,,,,,,,,,,,,,,,,,,2,,,," which looks the same as when push sync was working, maybe this is the wrong log file?

Last entry is: ""ROESERVER","RAS",04/14/2011,15:58:42,4,,,,,,,,,,,,,,,5,,,,,,0,,,,,,2,,,,,,,,,,"{4BE31BC7-81FF-4DB8-B56D-5A39F6F440CE}",,,,,,,,,,,,,,,,,,,"TS GATEWAY AUTHORIZATION POLICY",,,,,"

I downloaded SmarterTools program to read and decipher the errors but couldn't make it work, it wants IIS(7.0) not IIS(6.0) which is what is on my Server.

Do those error codes make any sense?

Also, in reading about IIS error codes off technet (i.e. 301/403.2 etc.) I followed the instructions for enabling logging and discovered that the Default Web Site was stopped under Sites in IIS(6.0) so restarted it and forced a push sync on my e63 but came back with the usual error "Error in communication, please try again later".

Scott

 

[snotty54]

Still searching for an answer and going back through the log file directories in "httperr4" sub-directory which I now realize is probably the correct log file for activesync, here is an entry from when the push sync was working: "2011-03-10 20:56:12 192.168.0.23 49871 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-03-10 21:04:38 208.82.217.122 56299 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-03-10 21:14:39 208.82.217.122 56307 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-03-10 21:17:44 192.168.0.23 49883 192.168.0.2 80 - - - - - Timer_ConnectionIdle -"

Here is the latest entry from the latest log: "2011-04-18 20:58:09 192.168.0.12 51386 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-04-18 21:06:05 208.82.217.122 51654 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 21:08:10 192.168.0.12 51461 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-04-18 21:16:11 208.82.217.122 51665 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 21:26:17 208.82.217.122 51667 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 21:36:23 208.82.217.122 51765 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 21:46:34 208.82.217.122 51988 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 21:56:35 208.82.217.122 52005 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-18 22:06:41 208.82.217.122 52039 192.168.0.2 443 - - - - - Timer_ConnectionIdle -
2011-04-19 00:49:26 192.168.0.12 49798 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-04-19 00:59:26 192.168.0.12 49999 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-04-19 01:09:32 192.168.0.12 50066 192.168.0.2 80 - - - - - Timer_ConnectionIdle -"

These log files don't seem to point to any issue. Earlier in the most recent log file there is this entry: "2011-04-01 06:15:15 192.168.0.20 63936 192.168.0.2 80 HTTP/1.1 POST /SimpleAuthWebService/SimpleAuth.asmx 404 - NotFound -
2011-04-01 06:15:15 192.168.0.20 63937 192.168.0.2 80 HTTP/1.1 POST /SimpleAuthWebService/SimpleAuth.asmx 404 - NotFound -
2011-04-01 06:21:33 fe80::64f0:4457:317c:70b0%10 27767 fe80::64f0:4457:317c:70b0%10 80 HTTP/1.1 GET /selfupdate/iuident.cab 404 - NotFound -
2011-04-01 06:24:43 192.168.0.12 61664 192.168.0.2 80 - - - - - Timer_ConnectionIdle -
2011-04-01 06:25:28 192.168.0.23 49400 192.168.0.2 80 HTTP/1.1 POST /SimpleAuthWebService/SimpleAuth.asmx 404 - NotFound -
2011-04-01 06:26:13 192.168.0.20 63947 192.168.0.2 80 HTTP/1.1 POST /SimpleAuthWebService/SimpleAuth.asmx 404 - NotFound -"

One of the entries seems to be with self update, another issue for another time, but do these entries point to the problem?

Thanks, Scott