Mesh-enabled Web Apps throwing "Service Unavailable" with Live Framework Client

Question

If there was something deployed, I haven't received it. Is there somewhere specifically I need to go in order to get it? I am still getting the 500 errors, and I am still unable to control whether or not an application has an icon on my desktop (I have apps on my Live Desktop that do not have icons on my regular desktop).

So, three problems that I am _still_ encountering:

1. Double-click an application on my Vista desktop (not Live Desktop). It launches the MeshAppLauncher.exe (or whatever it's called). I then see a 500 HTTP error in the main application window and my Live Mesh client in the systray switches to the logged out state.

2. There are apps in my mesh that don't show up on my Vista desktop, and there's no way to "push" a new icon to my desktop - desktop icons are not sync'ing.

3. Regardless of the icon that I've associated with my application, I still only see the Live Mesh "cube" icon on my Vista / XP desktop.

As of 5 minutes ago, my version of the mesh (developer) client is 0.9.3427.2.

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 1

I found out how to get the latest build of the Live Framework client and I'm now running that. I no longer have any desktop icons on my desktop for Mesh applications and double-clicking the application icon from inside the Live Desktop is actually producing a "service unavailable" error right now.

Also, using the .NET API to connect to my local mesh returns a 404 error when I attempt to enumerate the MeshObjects.Entries collection. I get a service unavailable error when I attempt to launch applications from the Live Desktop.

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 2

Thanks Kevin for reporting the issues. The announcement thread has the steps for the updating your Live Framework Client. Live Framework Client does not do Auto Update as yet.

Questions:
a) the Live Framwork Client as well as SDK version should be 0.9.3519.1 - can you please confirm this information? I saw you mention that you have version 0.9.3427.2 - this is the older version of the client.

b) for "Service unavailable" error - are you able to consistently repro this? Can you please collect the logs and send it to [e-mail] We will have engineers take a look at this.

after you have collected the logs and e-mailed - May I suggest following:
a) Uninstall Live Framework Client

b) Install Live Framework Client version should be 0.9.3519.1

c) Run your apps once from Live Desktop and wait until your apps and data is sync'd into Live Framework Client

The above may be inconvenient, however might unblock you with your work. Hopefully this helps, let us know!

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 3

Kevin - i split up this thread from the original one. The original thread can still be accessed from following link:
http://social.msdn.microsoft.com/Forums/en-US/liveframework/thread/5d57714e-1715-400a-8101-83b41e82574a

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 4

I am on the new version of the client, 0.9.3519.1

I cannot run the applications from Live Desktop because I get Service Unavailable in an XML envelope.

I am also experiencing a problem where attempts to enumerate meshObjects by the .NET client API on the local LOE (via .ConnectLocal()) fails with a 404 error.

So currently, on the new, current version:

1. Desktop icons for Live Desktop applications are not appearing on my desktop
2. Desktop icons for Live Desktop applications only appear as the "cube" , not as the artwork I've uploaded.
3. Attempting to run Live Desktop applications results in an XML message displaying "Service unavailable"
4. Still experiencing the "index.html" problem from Firefox when launching Live Desktop applications
5. And this worries me the most, "The Windows live network is unavailable" message is preventing me from logging into the developer Live Desktop right now.

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 5

 
Thanks for reporting the issues - we are investigating this issue as will update all as we make progess.

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 6

The operational issue has been resolved. Please try again.

Also, LOE.ConnectLocal() will require appropriate configuration on your VPC.

(As per your other thread at: 
http://social.msdn.microsoft.com/Forums/en-US/liveframework/thread/ec74fec2-ab04-468f-8829-27b3746f4f85)

 

---

(This post is provided "AS IS" with no warranties, and confers no rights.)