Cannot locate web subscription
-
6. března 2012 21:01
I have been banging my head on this one, I have an error in the CAS event log (ID 5,6,7) where there is a send notification for a subscription failing, and I am trying to determine which user it is coming from so that I may correct it. Has anyone else ran up against this and have been able to locate which user had the subscription? What kind of subscription is this and where is it coming from? I can only assume a mobile phone since it appears to be verizon. Thanks in advance for any info.
After 8 unsuccessful attempts to send a notification for subscription [HgBleC1jYXMtMDMuYWQuZ2VvcmdpYWhlYWx0aC5lZHUQAAAANvCUrDE3bUay9bOtG2JMfJp5cKcqyc4I] against endpoint [http://email-verizon.seven.com:7877/notify/nf_id24356/ex2k7/calendar/1818254/], the subscription has been removed. Details: WebException: Unable to connect to the remote server Status: ConnectFailure at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at Microsoft.Exchange.Services.Core.NotificationServiceClient.CreateSendNotificationRequestAsync(IAsyncResult requestAsyncResult)
Všechny reakce
-
9. března 2012 21:19Use the Log Parser Studio - http://blogs.technet.com/b/exchange/archive/2012/03/07/introducing-log-parser-studio.aspx. Very useful for reading analyzing logs.
JAUCG
- Navržen jako odpověď Fiona_LiaoMicrosoft Contingent Staff 13. března 2012 9:23
- Zrušeno navržení jako odpověď Russ Burden 13. března 2012 13:50
- Navržen jako odpověď Fiona_LiaoMicrosoft Contingent Staff 22. března 2012 8:54
- Zrušeno navržení jako odpověď Russ Burden 22. března 2012 12:45
-
9. března 2012 23:31Generally these occur if you;re using BlackBerry/BES, Entourage or UM? Which
uses EWS. Do you ?Sukh
-
13. března 2012 13:53
We do use BES, and we have some users using Entourage (I dont see why a MAC client would be referencing a verizon java client). When it comes to BES though, how do I locate which user is causing this error?
-
13. března 2012 14:44
Use the Log Parser Studio to go through your IIS logs to look for who is connecting. Take a look at this thread as it appears to reference a rogue device connecting from www.seven.com:
JAUCG
- Navržen jako odpověď Fiona_LiaoMicrosoft Contingent Staff 22. března 2012 8:54
- Zrušeno navržení jako odpověď Russ Burden 22. března 2012 12:45
-
13. března 2012 17:35Any tool which can parse IIS log files.
Sukh
-
13. března 2012 20:04
Do the IIS log files actually list credentials? Unfortunately, our exchange environment is behind proxy load balancers so all exchange sees is the IP address of the load balancer.
-
13. března 2012 20:11
yep, they should do.
I would then go to the load balancer and check the connections there.
Sukh
- Upravený Sukh828Microsoft Community Contributor 13. března 2012 20:12
- Navržen jako odpověď Fiona_LiaoMicrosoft Contingent Staff 22. března 2012 8:54
- Zrušeno navržení jako odpověď Russ Burden 22. března 2012 12:40
-
14. března 2012 15:33Log Parser Lizard is much better GUI for Logparser than LPS
-
22. března 2012 15:30Alright, I have gotten LPL, it works great, but I cannot find any entries in the IIS logs that have any relation to the subscription error I am seeing. Any suggestions on how to search, I did a search through all IIS logs for verizon since the errors contain verizon in the URL. The only items that were returned were email addresses that contained verizon.
-
22. března 2012 21:02What did the load balancer logs show?
Sukh
-
22. března 2012 21:23I had the admin of the load balancers show me what logs they have and it does not have details, he says they only log the service state for the VIP, and they do not log connections, etc... I find this hard to believe, but I haven't found anything else to refute his claim.
-
23. března 2012 16:24What kind of load balancers do you have? Do you have the manufacturer, version of the software?
JAUCG
-
30. března 2012 15:54They are Barracuda 440s, but as for the version, I don't know that at the moment.