Posts

Showing posts from February, 2015

HTTP 401.1 - Unauthorized: Logon Failed

When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following: HTTP 401.1 - Unauthorized: Logon Failed This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address. Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected. Additionally, an event message that resembles the following event message is logged in the Security Event log. This event message includes some strange characters in the value for the Logon Process entry: Event Type: Failure Audit Event Source: Security Event Category: Logon/Logoff Event ID: 537 Date:

HTTP Error status code in IIS 7.0, IIS 7.5, and IIS 8.0

By default, IIS 7.0, IIS 7.5, and IIS 8.0 put log files in the following folder: inetpub\logs\Logfiles This folder contains separate directories for each World Wide Web website. By default, the log files are created in the directories daily, and the log files are named by using the date. For example, a log file may be named as follows: ex YYMMDD .log The HTTP status codes This section describes the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 use. Note  This article does not list every possible HTTP status code as dictated in the HTTP specification. This article includes only the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 can send. For example, a custom Internet Server API (ISAPI) filter or a custom HTTP module can set its own HTTP status code. 1 xx - Informational These HTTP status codes indicate a provisional response. The client computer receives one or more 1 xx responses before the client computer receives a regular response. IIS 7.0, I

website error messages HTTP errors

HTTP errors are sent to your web browser from a website if a problem is encountered when trying to view a webpage. If the webpage can't be displayed, Internet Explorer will display either the actual error page sent by the website or a friendly error message built into Internet Explorer. Here are some of the most common errors and ideas for how to solve the problem that's causing them. The following table lists the most common HTTP errors that Internet Explorer displays. For information about HTTP protocols, error codes, and causes, go to the World Wide Web Consortium (W3C) website. HTTP error message What it means The webpage cannot be found (HTTP 400) Internet Explorer is able to connect to the web server, but the webpage can't be found because of a problem with the web address (URL). This error message often happens because the website address is typed incorrectly. Make sure the address is correct and try again. The

Hidden List SharePoint

Enter page web part maintenance mode Append ?contents=1 to the URL of the page for which you want to enter maintenance mode, for example: http://site/page.aspx?contents=1 Enter page edit mode Including system pages, such as view or edit pages: NewForm.aspx, EditForm.aspx, AllItems.aspx, etc. In Internet Explorer’s URL bar type: javascript:MSOLayout_ToggleLayoutMode(); or javascript:MSOTlPn_ShowToolPane(‘2′); Heads up: There is one thing you must seriously consider before editing a system page. This lesson I learnt the hard way from exposing modified edit pages to end-users. When you modify a previously read-only system page, such as a view or edit form, through the shortcut explain above, you make it available for editing to anyone who has contribute rights on that library or list. Hence that page becomes vulnerable to accidental changes by non-power users, because previously hidden Edit Page menu will be visible to them in Site Actions menu. Access administration

Importing and Exporting Search Configuration Settings in SharePoint 2013

It is often useful when you do SharePoint development to be able to deploy indexed and managed properties and property mappings in a repeatable way across environments. In SharePoint 2010 we did this as part of our PowerShell provisioning, but things have changed a bit in SharePoint 2013. Not only have the managed properties changed quite a bit with the introduction of Managed Navigation, but also as a developer and architect you really need to think Cloud First if you want your deployment frameworks to work both on premises and in the cloud. In the Client Side Object Model (CSOM) there is a framework for managing search settings, namely the  SearchConfigurationPortability class. This class makes it possible to import and export search configuration settings as XML. This includes Crawled Properties, Managed Properties and Mappings, but also Query Rules, result types etc. Here is some sample PowerShell code to export the search configuration settings to XML:  [reflection.ass

Content Type Hub (CTH) SharePoint 2013

Image
What is a Content Type? According to Microsoft, A content type is a reusable collection of metadata (columns), workflow, behavior, and other settings for a category of items or documents in a Microsoft SharePoint Foundation 2010 list or document library. Content types enable you to manage the settings for a category of information in a centralized, reusable way. Example: * Imagine a business situation in which you have three different types of documents: expense reports, purchase orders, and invoices. * All three types of documents have some characteristics in common; for one thing, they are all financial documents and contain data with values in currency. Yet each type of document has its own data requirements, its own document template, and its own workflow. * One solution to this business problem is to create four content types. * The first content type, Financial Document, could encapsulate data requirements that are common to all financial documents in the organization.

Object Cache Accounts

Many administrators when they first configure SharePoint 2010 and hit a Web Application for the first time are likely to see a recurring event in the event log stating that the object cache has not been configured correctly. The specific error is as follows: Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources . This is essentially telling you that you have missed a manual configuration step in which you need to run some PowerShell to set two accounts for SharePoint to use to access the object cache: function Set-WebAppUserPolicy($webApp, $userName, $userDisplayName, $perm) {     [Microsoft.SharePoint.Administration.SPPolicyCollection]$policies = $webApp.Policies     [Microsoft.SharePoint.Administration.SPPolicy]$policy = $policies.Add($userName, $userDisplayName)     [Microsoft.SharePoint.Administration.SPPolicyRole]$policyRole = $webA

Unattended Accounts

* There are some services, specifically the Visio Services Service Application, the Excel Services Service Application, and the PerformancePoint Service Application, that allow us to set an account that we can use for access data sources behind the scenes. These are called unattended access accounts. * To set these accounts we must create a new target application in the Secure Store Service Application and associate the target application’s ID with the appropriate Service Application. * The following PowerShell code demonstrates how to do this for the Visio Services Service Application (the Excel Services Service Application is virtually identical and just uses cmdlets specific to Excel rather than Visio; PerformancePoint is a lot simpler): #Get the Visio Service App $svcApp = Get-SPServiceApplication | where {$_.TypeName -like "*Visio*"} #Get the existing unattended account app ID $unattendedServiceAccountApplicationID = ($svcApp | Get-SPVisioExternalData).Unattend

AppFabric Caching and SharePoint

Image
What is a cache? A cache is a local, non-authoritative copy of data created and/or stored authoritatively elsewhere. Because retrieval of the data from its authoritative source is an expensive operation, instead of retrieving it freshly each time it’s needed, previous copies of the data are retained and used for subsequent needs. Reasons to avoid the authoritative operation include: * Network latency and delays . The data may be stored across relatively slow network links or require multiple intermediate hops to be retrieved. Rather than retrieving it for each request, a copy is stored nearby. An example of this in SharePoint is the BLOB cache; BLOBs from content databases are stored locally on front-end servers to avoid the need for further network trips to SQL. * User mediation required . The user may have to participate in retrieving the data, such as via authentication prompts and browser redirects. Imagine if a user had to undergo the three-legged process of WS-Federatio