Tag Archives: How To

Error: Load operation failed for query ‘GetAuthenticationInfo’.

How to solve the error: Load operation failed for query ‘GetAuthenticationInfo’ when deploying a LightSwitch 2012 application to a Windows Server 2008 R2 using IIS.

Scenario: The following error message appears in browser instead of the expected LightSwitch-based web application. The application has been developed using Microsoft LightSwitch in Visual Studio 2012. The application works as expected on the development machine but fails to run in a Microsoft Windows Server 2008 R2 environment even though the LightSwitch server side prerequisites has been installed.

Load operation failed for query ‘GetAuthenticationInfo’. [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.30214.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

Sample Screenshot:

LightSwitch_Error_Screenshot

After some troubleshooting it turns out that it is because the wrong version of WCF Data Services for OData had been installed. The proper version for a Visual Studio 2012 based LightSwitch application is WCF Data Services 5.0 for OData V3 and it is available for download here:
http://www.microsoft.com/en-us/download/details.aspx?id=29306

After installation and a web site restart the application worked as expected.

How to: run a 32 bit web application on a SharePoint 2013 Server

When installing a separate 32 bit web application in a SharePoint 2013 Farm the new application might fail to load and give a general 503 Service Unavailable error message. When looking in IIS manager, the Application Pool for the new app would be in the stopped state.

The following error messages might be visible in the Event log…

For the new 32 bit web application

event_error_message

Event ID 5002 – Error <date and time> WAS 5002 None

Application pool ‘<App Pool Name>’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.

And

Event ID 5139 – Warning <date and time> WAS 5139 None

A listener channel for protocol ‘http’ in worker process ‘<process number>’ serving application pool ‘<App Pool Name>’ reported a listener channel failure. The data field contains the error number.

 For SharePoint 2013

Event ID 2282 – Error <date and time> IIS-W3SVC-WP 2282 None

The Module DLL ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\isapi\spnativerequestmodule.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

The Microsoft link for the issue will only redirect you to the www.iis.net web site.

Solution / work around

The solution to this issue is to enable 32 bit applications to be loaded together with SharePoint and ask the SharePoint Module to only load in 64 bit mode. This can be done by running the following command, located in the %WINDIR%\System32\inetsrv\ folder:

appcmd.exe set config -section:system.webServer/globalModules /[name=’SPNativeRequestModule’].preCondition:integratedMode,bitness64

More information on configuring IIS can be found here: http://technet.microsoft.com/en-us/library/cc627313.aspx

Hat Tip to my colleague Markus Lind for pointing this out.

Unable to open SharePoint Online document library in File Explorer

Introduction

SharePoint features a very useful function that enables users to open a document library as if it is a normal folder inside File Explorer. This would give the user access to normal file operations such as copy, move etc.

fileexplorer-english

Look and feel of Open with Explorer in SharePoint 2013 in English

fileexplorer-swedish

Look and feel of Öppna med Utforskaren in SharePoint 2010 in Swedish

Issue

When using Windows 7 and Internet Explorer 10 to open a document library the following error message appears and the library does not open in File Explorer:

fileexplorer-errormsg-english

We’re having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.

A similar error message in Swedish:

fileexplorer-errormsg-swedish

Klienten har inte stöd för att öppna den här listan med Utforskaren.

Solution

Update: There is now a hotfix available at: http://support.microsoft.com/kb/2846960 that should solve the issue for Windows 7 and IE10.

Not really…

At the moment this is a known issue with Internet Explorer 10 in Windows 7. The suggestion from Microsoft is to de-install IE10 and use an earlier version. Another option would be to upgrade to Windows 8.

Unfortunately my current PC (HP EliteBook 8540w) does not support Windows 8, and Internet Explorer 9 isn’t really an option anymore.

Read more at the Microsoft support site: http://support.microsoft.com/kb/2835527

More supporting information here: How to use the “Open with Explorer” command and how to troubleshoot issues with this option in SharePoint Online – http://support.microsoft.com/kb/2629108

This is posted as a follow up to my post on how to get explorer view to work in SharePoint 2010: http://www.stefanjohansson.org/2012/01/how-to-get-explorer-view-to-work-in-sharepoint-2010/ – obviously this won’t cut it in the above scenario.

Workarounds for problems using Jetpack and https on Azure Websites

This entry is part 5 of 7 in the series Blog Meta

This is a follow up post on: Moving the blog to azure web sites: http://www.stefanjohansson.org/2013/05/moving-the-blog-to-azure-websites/

2013-07-09: Update 2 – As of Version 2.3.1 the Jetpack plugin and the WordPress cloud have  been updated to support more SSL scenarios. Jetpack should now work without issues and configuration changes. The post below is still valid for other connected systems that doesn’t like mismatched SSL certificates.

Introduction

One key feature missing from Azure Web Sites is the possibility to run your own SSL certificate for encrypted https traffic.

2013-06-03: Update 1 – https, SSL and certificates for custom domain names are now launched and available (for sites running in “reserved mode”) – read more here: http://www.windowsazure.com/en-us/develop/net/common-tasks/enable-ssl-web-site/ The information below still applies in case you don’t want to use a reserved mode site.

This pretty much disables it for any real business use whatsoever.

Every single professional I have spoken with regarding this have chosen alternate solutions for their projects and tests. As usual a key problem here is no official words on availability and firm delivery dates to relate to. Finding a blog post or discussion thread where someone says it might be available as a feature in the future just doesn’t enable project budgets to be spent on Azure Web Sites even for tests and explorations.

Continue reading

How to: move or remove the “Leave A Reply” link in the Twenty Twelve theme

This entry is part 4 of 7 in the series Blog Meta

This post describes how to move or remove the “Leave a reply” link that appears below the post heading in the Twenty Twelve theme for WordPress.

before

Link placement before edit…

The fastest and easiest way for a self hosted blog is to simply override the CSS styles that governs the link by editing the custom CSS that is part of WordPress:

wordpress_css

Link to Edit CSS in the WordPress admin site.

By adding the following CSS styles the link is moved:

#content .post {
    position: relative;
}

#content .comments-link {
    position: absolute;
    bottom: 1em;
}

#content .post {
    padding-bottom: 3em;
}

 

css

(The first two rules moves the link to the bottom, the last one adds some padding that I felt was needed)

The result is that the “Leave a reply” link is below the post, as seen below:

after

Link placement after edit…

If you rather not have the link at all, it is easily removed by adding the following CSS:

#content .comments-link {
    display: none;
}

 

cssnodisplay

Result after display:none;

nolink

The actual comments box is still visible and available in the post itself in case you still want to be able to get comments on posts.