Answered by:
Load operation failed for query 'GetAuthenticationInfo'. Exception of type 'System.ServiceModel.DomainServices.Client.DomainOperationException' was thrown.

Question
-
Hi,
I've been searching everywhere, however I'm unable to figure out what my application's problem is.
It works perfectly fine on my local machine, I set it up to be deployed to a 2008 R2 box running IIS7, all of the services are running.
I have a second 2008 r2 box that is the sql server.
I deploy without any problems, regardless of importing the application, publishing it remotely, web or desktop application.
I get the error listed in the title, I run fiddler on my computer and I find nothing that talks about any error.
I've got the application pool set to .net 4.0, I have windows authentication enabled, anonymous,asp.net and forms authentication disabled.
enabling the Trace and looking in there provides no information either...
Wednesday, February 6, 2013 4:49 PM
Answers
-
figured out what it was finally, it was simply a control for SSRS that wasn't on the server I was deploying to, not sure how this happened, but it wasn't deployed either to the server so when it tried to load it, it crashed with the error in the title of this post.
So if anyone finds this error and is doing anything with SSRS this is likely why.
- Marked as answer by RSHILLSHOOTER81 Thursday, February 7, 2013 11:59 PM
Thursday, February 7, 2013 11:59 PM
All replies
-
Try attaching the VS debugger to the w3wp.exe process (the IIS worker process). Configure VS so that "Enable Just My Code" is turned off and set it to break on all exceptions. Then launch your client app. There may be a few harmless exceptions thrown before you get to what looks like it could be the real issue. If you don't have VS installed on the IIS machine, you can setup remote debugging: How to: Set Up Remote Debugging.
- Edited by Yann DuranModerator Thursday, February 7, 2013 12:08 AM Fixed link text
- Proposed as answer by Yann DuranModerator Thursday, February 7, 2013 12:08 AM
Wednesday, February 6, 2013 7:46 PM -
i'm being told that i don't have the ability to look at the lightswitch code?Wednesday, February 6, 2013 9:22 PM
-
You're not going to be able to see the code but you should be able to see the messages from exceptions that are thrown. That's what will help determine what's wrong.Wednesday, February 6, 2013 10:23 PM
-
we never find anything minus the few harmless exceptions thrown.
I notice nothing that looks serious. We made a simple program with barely anything in it, tried to deploy it same problem still...
We have tried using no authentication, windows authentication.
Never any errors outside of the one it throws. Oddly enough if you publish the desktop application, the program opens says loading... then goes to a blank screen, no errors.
Thursday, February 7, 2013 3:22 AM -
When that happens, it's usually an unhandled exeption, somewhere in the application initialisation code, or in the code of the main form. Instead of bubbling up the exception, LightSwitch seems to swallow it & silently fail to go any further.
Oh, it could also be in the code of an extension.
Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful. By doing this you'll help others to find answers faster. Thursday, February 7, 2013 8:29 AMModerator -
one thing i've noticed is that the application itself is set to windows authentication and it's also set to allow any authenticated windows user.
Authentication itself on IIS is set to Windows Authentication.
We have got it to prompt for a user/password, however when you type in the user/password (that is my own login) it comes back and asks for the user/password again.
Not sure what it wants from me lol
Thursday, February 7, 2013 4:19 PM -
figured out what it was finally, it was simply a control for SSRS that wasn't on the server I was deploying to, not sure how this happened, but it wasn't deployed either to the server so when it tried to load it, it crashed with the error in the title of this post.
So if anyone finds this error and is doing anything with SSRS this is likely why.
- Marked as answer by RSHILLSHOOTER81 Thursday, February 7, 2013 11:59 PM
Thursday, February 7, 2013 11:59 PM