Push notification configuration problem

Question

I have the problem to make to work of the examples of push notification. I have not found an example complete working. The problem task depends on the configuration on the PC of the web service that would have to send the messages. Someone can say to me how make or finding an example working?

Thanks

Answer 1

Please be more specific. What examples are you trying?

Javier Andrés Cáceres Alvis
MVP Windows Phone
http://speechflow.spaces.live.com/

Answer 2

there is a very complete and working sample here: http://channel9.msdn.com/learn/courses/WP7TrainingKit/WP7Silverlight/UsingPushNotificationsLab/

it contains both a sample phone project and a test application for sending notifications.

the only issue i have found is that tile notifications with remote images do not work (the sample uses local images and does work). i have not been able to create or find a working example of remote image tile notifications.

Answer 3

with the example in channel9 when I start the WheaterService I have the follow exception:

Could not start service host. HTTP could not register URL http://+:8000/RegistratorService/. Your process does not have access rights to this namespace

I also change the right:
netsh http add urlacl url:http://+:8000/RegirstatorService user=<name of computer>\<administrator user>

I run as Administrator Visual Studio 2010

Thanks

Answer 4

Hi,

know the web service is started and if I put this url http://localhost:8000/RegirstatorService/Register?uri=http://www.microsoft.com in my IE (on PC and on Emulator) the webservice responde correctly.

The problem now is that the client continue to stay in status : Channel open requested. Why?

Answer 5

Hi Claudio,

  Do you still require assistance with this sample, or have you been able to get it working now?

Thanks,

---

Jonathan Tanner | Microsoft | Windows Phone 7 Support

Answer 6

Hi

I have the same problem as Claudio.

Question:

httpChannel.Open();

Should fire "ChannelUriUpdated" after it openned the channel, right? That's what is not happening on my Emulator device.

Btw. where does httpchannel connect to? To a MS-Server? then I get an URL back, and with that I am subscribing to my service, correct?

I just dont get an URI back from httpChannel.Open().

The interesting thing is: When I now restart the application, and search for an existing httpchannel, he finds one - before he did not. So a channel gets setup, but I dont get the URI back from it...

Answer 7

Hm, on my other PC which has the exact same configuration and same Firewall, it is working...

Strange though...

Answer 8

Hi All,

 

I am also getting the same problem as Claudio.

I run the sample code provided at "http://channel9.msdn.com/learn/courses/WP7TrainingKit/WP7Silverlight/UsingPushNotificationsLab/" in the emulator.

But the client always stay in the status : "Channel Open Request". There is no exception thrown when it calls httpChannel.Open().

It never comes to the ChannelUriUpdated event handler, which it should come if the channel opens successfully.

Please help me if anybody knows the solution of this problem.

 

Please note that my system uses proxy. But I have setup SOCKS proxy as mentioned in the documentation. Also I wait for more than 2 minutes after the emulator boots up.

 

Thanks.

Answer 9

Hi All,

Topic of this thread is a old wine in new bottle. There were many, many, many threads on this topic. The real issue is that PUSH NOTIFICATIONS AT THIS MOMENT U-N-S-T-A-B-L-E & U-N-R-E-L-I-A-B-L-E.

Just search for "esm_51 push notifications", you will get at least 3 threads which I have either started or have subscribed to. The WP7 Training Kit code doesn't work as it is. Everyone has got trouble at different stage of this app. Unfortunately no one from the MS team is responding to this issue.

Answers to few of the issues raised here are:

1. The notifications make a round trip to push.live.net.
2. There are some issues with proxy setup on WP7.
3. At lease one person said that it worked perfectly after making two modifications, but didn't cite whtat they are. Check this thread: http://social.msdn.microsoft.com/Forums/en-US/windowsphone7series/thread/bf201c8f-8410-4142-b233-b3a6d4944925.
4. Several developers have stuck at different places.

Everyday, I run the app once or twice, in the hope that someday the wisdom will dawn on me either to stop worrying about it or solve it. Rubik's Cube was much simpler to solve.

-- ThanQ...

 

Answer 10

Hi ESM_51,

 

Thanks for the useful info.

It seems that many people has passed the phase where I am stuck now (This is very initial phase). Moreover this is happening every time for me the same way. So I doubt whether I am missing anything.

 

I took the capture of HTTP request/response between my system and push.live.net.

Following is a capture of HTTP Get request and response to/from push.live.net:

HTTP Request:

HTTP HTTP:Request, GET http://push.live.net/Bootstrap/v01, Query:client=WM7.0&DeviceID=07EBA7B32DD741693AE6CEAB35F4E224A566BEAC {HTTP:45, TCP:44, IPv4:43}

 

Frame: Number = 86, Captured Frame Length = 323, MediaType = ETHERNET

Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[00-00-5E-00-01-6A],SourceAddress:[00-1D-7D-21-09-C9]

Ipv4: Src = 107.109.107.21, Dest = 107.108.85.10, Next Protocol = TCP, Packet ID = 9123, Total IP Length = 309

Tcp: Flags=...AP..., SrcPort=17608, DstPort=HTTP(80), PayloadLen=269, Seq=1060114362 - 1060114631, Ack=2159846107, Win=16425 (scale factor 0x2) = 65700

Http: Request, GET http://push.live.net/Bootstrap/v01, Query:client=WM7.0&DeviceID=07EBA7B32DD741693AE6CEAB35F4E224A566BEAC

Command: GET

URI: http://push.live.net/Bootstrap/v01?client=WM7.0&DeviceID=07EBA7B32DD741693AE6CEAB35F4E224A566BEAC

Location: http://push.live.net/Bootstrap/v01

Parameters: 0x1

ProtocolVersion: HTTP/1.1

UserAgent:  Mozilla/4.0 (compatible; MSIE 4.01; Windows CE)

Host:  push.live.net

ProxyConnection:  Keep-Alive

Cache-Control:  no-cache

Pragma:  no-cache

HeaderEnd: CRLF

 

 

 

HTTP Response:

 

HTTP HTTP:Response, HTTP/1.1, Status: Ok, URL: http://push.live.net/Bootstrap/v01 {HTTP:45, TCP:44, IPv4:43}

 

Frame: Number = 89, Captured Frame Length = 357, MediaType = ETHERNET

Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[00-1D-7D-21-09-C9],SourceAddress:[00-24-A8-38-A3-00]

Ipv4: Src = 107.108.85.10, Dest = 107.109.107.21, Next Protocol = TCP, Packet ID = 48617, Total IP Length = 343

Tcp: Flags=...AP..., SrcPort=HTTP(80), DstPort=17608, PayloadLen=303, Seq=2159846107 - 2159846410, Ack=1060114631, Win=1041 (scale factor 0x6) = 66624

Http: Response, HTTP/1.1, Status: Ok, URL: http://push.live.net/Bootstrap/v01

ProtocolVersion: HTTP/1.1

StatusCode: 200, Ok

Reason: OK

Cache-Control:  private

ContentType:  text/plain; charset=utf-8

Server:  Microsoft-IIS/7.5

XAspNetVersion:  2.0.50727

XPoweredBy:  ASP.NET

Date:  Sat, 04 Sep 2010 10:33:15 GMT

ContentLength:  29

ProxyConnection:  Keep-Alive

Connection:  Keep-Alive

HeaderEnd: CRLF

payload: HttpContentType =  text/plain; charset=utf-8

HTTPPayloadLine: Dip:tcps://65.55.74.50:443/

 

 

The response seems to be success only. 

The above request-response is followed by few more request-response like below:

 

Http: Request, GET http://login.live.com/ppcrlcheck.srf 

Http: Response, HTTP/1.1, Status: Ok, URL: http://login.live.com/ppcrlcheck.srf 

 

Please let me know if the network capture is similar to yours or anything is missing here.

Also I would like to know if any firewall problems persist, how would I detect that problem. Any idea?

 

Thanks.

 

Answer 11

Hi WM_Quest,

I am not good at interpreting these web request and response captures. I hope someone else will able to check them.

However, I again went through your issue describing post. One thing is not clear. You said you are waiting for more than 2 minutes. Just check these:

1. After waiting (I believe 30 seconds is enough), you will have to stop the running of the project by clicking on the STOP button in the VS IDE.
2. I found that sometimes, I didn't have to go through the 30-secon-wait and stop & start the program cycle. The registration succeeds without waiting.
3. Many times, if I get the "Channel Open Requested" message and the registration doesn't succeed on the first run of the emulator, then on restarting the project run, I get "Null Reference" error.

Hope the Sep 16th release of new tools will improve the situation.

-- ThanQ...

 

Answer 12

For me, Push is working superb since 2 weeks, without any problems.

Make sure to NOT use the unlocked emulator, it will break push (and other things)

Answer 13

Hello ESM_51,

 

Thanks for the response.

Earlier I used to wait(delay) for 2 minutes before using any push notification APIs because I was not using the stop at first run technique. Now normally when I start debugging for the first time and emulator runs for the first time, I wait till the emulator boots up and then use the Stop button in VS IDE so that no push notification call happens. Again I start debugging after some time on the already running emulator. But even then channel is not openinng.

Also point no 3 mentioned by you is true. If I try to debug again on the emulator (without closing it), where I was stuck at "Channel Open Requested", I get "Null reference" error, because it finds the channel this time and tries to use the URI which is NULL.

Guess I have to wait till Sept 16th release!!

 

Thanks.

 

Answer 14

I am using the latest release tools and I am still seeing the same problem. how do we fix it.  Do we wait 1-2 minutes before using any push notification APIs ?  what is the right solution ? The status is "channel open requested"

Answer 15

Also check if you have set the multi-project start in Solution Properties. The phone project should start after the other.

One more thing. There is RTM version of WP7 Training Kit. You should try the Push Notification lab in this. Because the Beta version lab still didn't run for me. Before I could compare the two scripts, my hard disk crashed. So I am yet to check the two from my backups, if available.

I hope you will find solution in one of these.

 

---

-- ThanQ... *** Think Solutions, The Right Ones ***