All Posts

All Posts (543)

• 

  Published on

  2016-02-07 9:36 a.m.

  Authors

  koskila

  Tags

  asp-netazurecode-firstcefef6mvcmvc5

  Fixing "An error occurred while updating the entries" while running code-first migrations in MVC 5 app

  This post describes an issue with EF's code-first migrations, when mapping between DB's DateTime (datetime2) and C#'s DateTime simply fails, and results in the Update-Database cmdlet failing, too. It is more or less a prime example of a situation, where the error itself tells very little about the actual issue, and since debugging code-first migrations is kind of difficult ( see the best tips for that here! ), it's cumbersome to investigate.

  Read more →
• 

  Published on

  2016-01-29 9:52 p.m.

  Authors

  koskila

  Tags

  azurenetworksqlvisual-studio

  Fixing error "Cannot open server - - requested by the login. Client with IP address - - is not allowed to access the server." in Azure deployments from Visual Studio

  This article explains how to work your way around the exception 'Cannot open server - requested by login...' The issue is caused by Azure's firewall logic, which might sometimes appear a little bit overzealous for simple development workloads, and might stop you from accessing your databases from your development machine. But just as everything else in Azure, the firewall exists for a reason, and working with it just requires a couple of extra clicks, is all.

  Read more →
• 

  Published on

  2016-01-21 1:37 p.m.

  Authors

  koskila

  Tags

  on-premisespowershellsharepoint-2010sharepoint-2013sharepoint2016sharepoint2019uls

  Using PowerShell to set ULS logging level to "extra verbose" to catch all the events in the logs

  This blog post describes how to set SharePoint's ULS level to "Extra Verbose" (VerboseEx) using PowerShell. This is not possible using the browser UI, so some POSH magic is required! Luckily, it's quite straightforward, but to avoid filling your hard drive(s) with huge log files, you should reset the level when you're done debugging! Description of the solution By default, ULS logging is somewhat non-detailed. This means that a lot of data that could be used to debug issues is omitted.

  Read more →
• 

  Published on

  2016-01-05 12:02 p.m.

  Authors

  koskila

  Tags

  powershellsharepoint-2010sharepoint-2013sharepoint2016spweb

  Using PowerShell to modify anonymous access permissions on SharePoint On-Premises

  This post is about managing Anonymous Access on a SharePoint site (SPWeb) using PowerShell commandlets. It's often a lot more feasible and even easier than using the browser interface! In some cases, it's borderline impossible to avoid it anyway - since accessing the GUI switch might not be possible. Description Assume you have a site collection that you have published to the whole world.

  Read more →
• 

  Published on

  2015-11-17 9:12 a.m.

  Authors

  koskila

  Tags

  deploymentfull-truston-premisessharepoint-2010sharepoint-2013wsp

  Powershell Error: Cannot uninstall the LanguagePack 0 because it is not deployed.

  Have you ever run into this, very non-descriptive and weird SharePoint error message "Cannot uninstall the LanguagePack 0 because it is not deployed"? You could encounter it while running some PowerShell scripts - most typically when trying to update a wsp solution. I have, and luckily often easily solved! Symptoms Assume you're trying to install, update or uninstall a SharePoint solution (.

  Read more →
• 

  Published on

  2015-10-20 1:23 p.m.

  Authors

  koskila

  Tags

  asp-netdeploymentfull-trustiissharepoint-2010sharepoint-2013sharepoint2016

  "Server Error in '/' Application" or "Parser Error" - it's actually a malformed web.config killing your ASP.NET-application or SharePoint

  This post describes how to resolve a kind of cryptic and oddly misdescriptive error message about Parser Error on your ASP.NET application or (an On-Premises) SharePoint site. I ran into this after deploying wsp-packages to a SharePoint farm, but you can apparently get this on ASP.NET MVC sites, too. The error doesn't actually tell you what's wrong, so figuring it out took a while. Though hopefully, it helps you!

  Read more →
• 

  Published on

  2015-10-01 7:16 a.m.

  Authors

  koskila

  Tags

  sharepoint-2010visual-studiovisual-studio-2010

  Visual Studio 2010 fails to show the design view of an aspx-page

  This post is about solving the issue with Visual Studio 2010 failing to show the design view of an .aspx-page. Luckily, it's an easy and pretty classical fix. Symptoms Whilst trying to view or edit an aspx-page in design mode within Visual Studio 2010, the window is just plain empty and there's little you can do about it - selecting view markup or hitting F7 may not do anything, and restarting the Visual Studio doesn't help.

  Read more →
• 

  Published on

  2015-09-21 1:38 p.m.

  Authors

  koskila

  Tags

  full-truston-premisessharepoint-2010sharepoint-2013sharepoint2016wsp

  The quickest way to download all the wsp-packages in a SharePoint farm

  Sometimes - pretty often in the good old on-premises world, actually - you'll need to have a copy of all the packages that are deployed to a certain farm. So - how to download all of the deployed farm solutions (essentially, cabinet files renamed to .wsp) from a farm? Luckily, it's quite easy! Solution To download all deployed farm solutions (wsp-packages) from a SharePoint farm is pretty simple using PowerShell. No need to download individual packages through cumbersome interfaces!

  Read more →
• 

  Published on

  2015-09-03 3:27 p.m.

  Authors

  koskila

  Tags

  azuredeploymentfeature-frameworkfull-trustmsbuildsharepointsharepoint-2010visual-studiovisual-studio-2010visual-studio-2013visual-studio-2015visualstudio2017visualstudio2019webjob

  Fixing the error: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."

  This post describes a few different ways of fixing the "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters." error. One can encounter this issue when trying to package/publish a SharePoint solution, web site, or an Azure Webjob. Symptoms Visual Studio throws the following error when packaging a SharePoint solution to a .

  Read more →
• 

  Published on

  2015-08-07 2:31 p.m.

  Authors

  koskila

  Tags

  office-365sharepointsharepoint-2013sharepoint2016sharepoint2019sharepoint-online

  How to log into SharePoint as a different user

  SharePoint Server 2013, 2016, and 2019 versions don't have that old and familiar "sign in as a different user" option in the site menu, and for the time being, nor does SharePoint Online . However, sometimes it's very useful functionality to have, so it's a bit weird Microsoft chose to get rid of the option. This post outlines a method that I've found to work quite well for making SharePoint ask for credentials so that you can use another account to then log in!

  Read more →
• 

  Published on

  2015-07-22 9:33 a.m.

  Authors

  koskila

  Tags

  internet-exploreroffice-365sharepoint-2010sharepoint-2013

  Identifying IE11 compatibility mode in SharePoint

  In this post, I describe how you can figure out if IE11 (Internet Explorer 11) has jumped into compatibility mode. You will run into this requirement every now and then when trying to figure out some SharePoint browser compatibility mess-up. This is quite frequent because in compatibility mode IE does its best to screw up your CSS.

  Read more →
• 

  Published on

  2015-07-02 9:20 a.m.

  Authors

  koskila

  Tags

  cfull-trustsharepoint-2010sharepoint-2013threading

  The simplest way to create a thread on SharePoint

  This post describes the easiest (probably) and most straightforward way of creating a new Thread in your SharePoint (or any other .NET) server-side/desktop code. Solution Let's face it - one should not create new Threads lightly when developing SharePoint solutions, but sometimes it is difficult to avoid. Or sometimes it's just the simplest way to get around weird framework limitations.

  Read more →
• 

  Published on

  2015-06-27 4:47 p.m.

  Authors

  koskila

  Tags

  cfull-trustsharepoint-2010sharepoint-2013sharepoint2016spweb

  How to properly use SPWeb.AllowUnsafeUpdates

  At times you may need to allow unsafe updates for SPWeb objects in order to get your code to run. This, in SharePoint's C# full-trust code, is done by setting SPWeb.AllowUnsafeUpdates to true. However, as this is an exception to security settings, you should generally avoid it. When you can't, it is good practice to limit the change to as small a scope as possible. This is true even though the setting only persisted for the duration of the request (unless the SPWeb object was gotten from SPSite.

  Read more →
• 

  Published on

  2015-06-20 9:41 a.m.

  Authors

  koskila

  Tags

  feature-frameworkfile-not-foundsharepoint-2010sharepoint-2013

  "File not found"error when trying to activate a custom feature on SharePoint

  This post is about fixing one of the most annoyingly unspecific errors that you can get when activating (Feature Framework) features on SharePoint - "File not found" . Whatever that might mean, right? Problem Ugh. A plain and simple "File not found" is one of the more annoying errors one can stumble upon when trying to activate a feature.

  Read more →
• 

  Published on

  2015-06-13 8:55 a.m.

  Authors

  koskila

  Tags

  debuggingiisvisual-studiow3wpwindows

  Attaching the Visual Studio debugger to the right IIS worker process

  Every now and then comes the time when you'd actually need to debug something, and then you'll likely be using your Visual Studio to attach the debugger to one or more processes. Using CKSDev to attach to all IIS worker processes (w3wp.exe), or if you don't use CKSDev, just pressing ctrl+p and selecting the processes from the list, is often a good enough solution. However, sometimes that makes your dev box sluggish, or maybe catches exceptions from code you're not wishing to debug at the time.

  Read more →
• 

  Published on

  2015-06-05 3:25 p.m.

  Authors

  koskila

  Tags

  cfull-truston-premisessharepoint-2010sharepoint-2013sharepoint2016

  Programmatically creating readable internal names for new SharePoint fields

  This post is about a small programmatic workaround to creating new SPFields for SPLists in SharePoint with human-readable internal names. This is mainly a usability improvement for your editors (and doesn't change your life that much), but they should appreciate it at the very least! In short, I'll show you how to avoid SharePoint's dirty encoding (like replacing a space with "_x0020_"). This applies when you're using server-side code to generate fields.

  Read more →
• 

  Published on

  2015-05-31 8:52 a.m.

  Authors

  koskila

  Tags

  configurationhostsnetworkwindows

  Troubleshooting guide for Windows hosts file

  This post describes how to fix possible issues with the Windows hosts file. I'll first document how to find the damn file, and then go through a bunch of options on what to check and how to fix different possible issues. Opening the hosts -file First of all, the host's file location is usually: C:\Windows\System32\drivers\etc\hosts (link may or may not work depending on your security settings and browser version, but you can always copy-paste it to your text editor's "Open"-dialog...

  Read more →
• 

  Published on

  2015-05-28 8:41 a.m.

  Authors

  koskila

  Tags

  authenticationiison-premisesregeditsharepoint-2010sharepoint-2013windows-authentication

  Windows Authentication fails on SharePoint for all hostnames (other than localhost)

  This post describes how to fix Windows Authentication on a SharePoint server that is failing on other local addresses other than localhost. Symptoms You get the standard Windows/Basic Authentication prompt when accessing your SharePoint site, but the site won't accept your credentials when you are accessing the site using an address like http://website. However, using an address like http://localhost works fine (but of course may cause other problems).

  Read more →