Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Beth Massi — Thu, 11 Oct 2012 19:21:37 GMT

Hi Brian,

I see you've asked the question in the forums

social.msdn.microsoft.com/.../4f4f8c38-13de-4820-99d4-5e6cf8aa28c5

I've replied to you there. Hope that helps.

-Beth

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Brian Wolters — Wed, 10 Oct 2012 13:45:53 GMT

I am getting the dreaded: HRESULT E_FAIL HAS BEEN RETURNED TO FROM A CALL TO A COM COMPONENT when I start a LightSwitch app. Any suggestions?

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Brian — Wed, 10 Oct 2012 13:34:40 GMT

I am getting the dreaded: HRESULT E_FAIL HAS BEEN RETURNED TO FROM A CALL TO A COM COMPONENT when I start a LightSwitch app. Any suggestions?

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

NGCBSiegel — Sat, 06 Oct 2012 19:38:48 GMT

For those seeing the error: Load operation failed for query 'GetAuthenticationInfo'. The remote server returned an error: NotFound.

I was recently testing deployment scenarios under IIS and ran into this error. I thought I would post my findings and eventual solution in case you find yourself in the same position…

As of 10/6/2012, my test server was Windows 2008R2 (latest service pack) with SQL Server 2012 Standard. The IIS role was not installed.

I downloaded and ran WebDeploy 4 for the LightSwitch 2012 provisioning without SQL Express (since SQL Server was already installed on the same server). This obviously enables the IIS role.

I had no problem publishing my LightSwitch 2012 Web application along with the database.

However, when I attempted to run it, I received the error:

Load operation failed for query 'GetAuthenticationInfo'. The remote server returned an error: NotFound.

Same thing happened when attempting to browser to the web app from the server locally. After taking a quick look with Fiddler, I noticed that the failure appeared to be related to a missing Authentication request ending with ".svc". I took a quick look into the IIS script mappings and noticed that there was no mapping for anything with the extension ".svc".

Apparently, this is all realted to the ASP.net 4 dll mappings required to run the LightSwitch application. The solution (for me) was to simply go into Add/Remove programs and repair the .Net 4 extensions and .NEt 4 Client installs.

Afterwards, I noticed a whole bunch of new IIS script mappings created - including one ending in .svc.

Problem solved. After this, the LightSwitch app loaded and ran with no errors. Perhaps the order by which I enabled these components on a new Windows 2008R2 server (ie. SQL Server 2012, WebDeploy for LS 2012 – no SQL express) causes an issue with the .Net 4 IIS mappings required to support the LS application.

I hope this helps anyone running into a similar situation.

Benjamin

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Kellylee — Wed, 19 Sep 2012 15:59:07 GMT

Excellent post! This helped me a lot. I had to change my targetframework to ASP.NET v4.0.

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

SydneyWaterBoy — Wed, 18 Jul 2012 06:49:00 GMT

Really helpful, thanks...it takes us one step closer to the solution whereas before I was on a slide going backwards!

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Eric Erhardt — Wed, 06 Jun 2012 22:21:30 GMT

@Yann - Some of these tips and tricks work for 2-tier deployed apps as well. The diagnostics with "trace.axd" works but the trick is to find the port number the vslshost.exe process is listening to. I usually find the port number by going to the Task Manager -> Resource Manager -> Network tab and look under "Listening Ports" for VslsHost.exe. Once you have the port number, open a browser and navigate to "http://localhost:<port>/trace.axd".

Along those same lines, you can open your browser and just navigate to "http://localhost:<port>" and your LightSwitch app should load in the browser. Now you can use Fiddler in the same ways I described above. (Sometimes to get Fiddler to recognize localhost requests I need to say "http://localhost.:<port>" [note the period after localhost].) In order to get customErrors="off", you need to edit your web.config.

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

Yann Duran — Wed, 06 Jun 2012 00:39:18 GMT

Hi Eric,

This is a really good, well-detailed article, but it's all about LS web applications. What would you suggest for desktop (so-called 2-tier apps, even though I know that they're really still 3-tier), other than make it a web app?

Where can we look for these problems that you decribed when the app is not a web app.

Thanks,

Yann

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

ADefwebserver — Fri, 30 Dec 2011 18:49:37 GMT

When I take a LightSwitch application that is working on one computer and then try to run the Visual Studio project on another, and I get the "red X", I can fix it by opening up one of the Entities under Data sources, making a small changes, saving, then changing it back.

This will dump any sample data you may have had but it fixes the problem.

re: Diagnosing Problems in a Deployed 3-Tier LightSwitch Application (Eric Erhardt)

LightSwitch Team — Mon, 28 Nov 2011 15:47:20 GMT

@Spoonstomper - LightSwitch uses WCF Ria Services underneath the covers. WCF Ria Services will return a 404 whenever an exception occurs while trying to initialize the service. Here is some information on how to diagnose Ria Services - msdn.microsoft.com/.../ff426913(VS.91).aspx. Also, maybe enabling WCF tracing might lead you to some more information - msdn.microsoft.com/.../aa702726.aspx.

If all else fails, attaching a debugger to the w3wp.exe process and breaking on exceptions is usually my last resort to figuring out what is going wrong.

- Eric