Catastrophic failure (0x8000FFFF E_UNEXPECTED) on LightSwitch OOB app in Azure.

Question

Hey experts!

We just pushed a first test version of a LightSwitch app to Azure.  It's an OutOfBrowser LS 2012RC application in Dutch.

When trying to browse to the application, the application installs and starts up with the following exception:

The Dutch text translates (rhoughly) to: an error occured while checking on updates.  Make sure you are using the latest version of the app by removing the app via Software in Configuration Screen and then reinstalling the application.

Any ideas on how to troubleshoot this?

Cheers

Jan

---

It's your story - time to switch on the innovation. || About me || LightSwitch blog

Answer 1

We're currently still investigating this.

Sorry about the screenshot not working, but the explanation says enough so that future searches will come up with this page :-)

I currently suspect this is a duplicate of http://social.msdn.microsoft.com/Forums/en-US/lightswitchgeneral/thread/c83ddb0e-f567-4c8c-807c-5c239820d6c2/ .  We'll investigate now, and close or add additional feedback for future reference.

Cheers

Jan

---

It's your story - time to switch on the innovation. || About me || LightSwitch blog

Answer 2

Jan - can you publish/run the app if you set it to EN-US?

Answer 3

Not sure (I'm not the owner of the Azure account used to publish), but I'll ask him if the problem still persists and if it does, whether the problem is solved by setting it to EN-US.

Are you suspecting it's the bug in SL that was reported for Arabic applications?

Keep rocking LS!

Jan

---

It's your story - time to switch on the innovation. || About me || LightSwitch blog

Answer 4

Not sure if it's the same bug - but kinda hoping we don't have another one :)

Answer 5

I'm actually quite sure it's a duplicate of "http://social.msdn.microsoft.com/Forums/en-US/lightswitchgeneral/thread/c83ddb0e-f567-4c8c-807c-5c239820d6c2/ " though, although my partner in crime can't check at the moment due to Azure account limits that are reached :-)

---

It's your story - time to switch on the innovation. || About me || LightSwitch blog

Answer 6

Hi all,

I'm Jan's partner in crime, and I fixed my azure account. So I published the application again, but now with en-US culture. The same problem is still there.

Another suggestion, to disable the Microsoft.LightSwitch.RequireEncryption setting, as described in this forum thread, http://social.msdn.microsoft.com/Forums/en-US/lightswitchgeneral/thread/c83ddb0e-f567-4c8c-807c-5c239820d6c2/,  does not work. I mean, I cannot find that setting at all. This forum thread dates form May 3 2011, so it may not apply to the current azure/lightswitch versions.  

Other suggestions are very welcome!

Thanks,

Edgar Walther

www.itsmart.nl

---

Thanks, Edgar Walther

Answer 7

Indeed, this Microsoft.LightSwitch.RequireEncryption setting is not available anymore for the current LightSwitch/Azure versions. 

See this thread: http://social.msdn.microsoft.com/Forums/en-CA/LightSwitchDev11Beta/thread/334f79e9-6708-4b8e-aaad-a809cf025508

For running desktop apps from Azure you have to have a real certificate installed. 

So I'll have to figure out how to install a certificate...

2 b contd...

---

Thanks, Edgar Walther

Answer 8

Edgar - a couple options for you running OOB apps from Azure -- sorry, I missed the nuance of this being OOB earlier (the acronym has an number of meanings internally).  Anyway...

1) you need to use a certificate for your Azure cloud service that you can install into the trusted root store, one that's created for SSL.  This doesn't need to be a "real" certificate, a test one will work as long as you can install it locally in the trusted store.  Since the name on the cert you create needs to match the site that hosts the cert you either need to do a deployment upgrade for LightSwitch (so you know the GUID of your staging slot and you can use that when you create the cert) or run it out of the production slot (which has a fixed name).  This will walk you through how to create a cert. http://msdn.microsoft.com/en-us/library/ms186362(SQL.105).aspx

2) you can alternatively publish the app to an Azure Web Site, instead of an Azure Cloud Service.  The wildcard cert used by Azure Web Sites is a trusted cert.  You can read more about that here: http://blogs.msdn.com/b/lightswitch/archive/2012/06/07/publishing-lightswitch-apps-to-azure-with-visual-studio-2012.aspx

HTH