Deploy to Hostheader Error

 

I added the host header to the Hosts file as described in some blogs. Unfortunately SharePoint started asking me for my credentials.

The solution was to delete the entry from the hosts file and extend the web application site with the server name.

The trial period for this product has expired.

 

Recently after some windows updates i got this error on my SharePoint sites.

In the SharePoint Log-files I found this error:

Failure checking user access permissions for User Profile Application Proxy 'User Profile Service Application'. Exception: Microsoft.SharePoint.SPException: The trial period for this product has expired.

I found this Blogentry

So I tried first the solution at the end of the article, becose the first one semed to be awkward. I did this

psconfig -cmd secureresources

Still the same error, even after an iisreset and a server restart.

I found there in the comments a link to a technet entry and then found the solution:

Workaround: In central admin go to "Central Admin" => Monitoring => "Review Rule Definitions" => click on "Trial period for this product is about to expire" rule under configuration and edit it. Uncheck the "Enabled" checkbox.

So I did this.

Still the same error even after iisreset.

So I got back and tried the first Ugly solution.

Still the same error even after iisreset.

In the IIS I found this:

So I started the The web Services Application

Still the same error even after iisreset.

And I’m still searching for a solution.

Finally I looked in SharePoint central Administration – Upgrade and Migration - Convert farm license type. And there I found the problem:

After an iisreset everything went well.

Sometimes error messages are really what they seems to be. Even Microsoft error Messages.

"The Workbook cannot be oppened." in SharePoint 2013

Last Week I installed SharePoint 2013 for a customer. After installation I got the same error with the Excel Web Part as described in this Post.

I tried the proposed Solution:

$webApplication = Get-SPWebApplication "http://intranet "
$webApplication.GrantAccessToProcessIdentity("Domain\serviceAccount")

In the PowerShell-Window the Script the powershell command seemed to be executed succesfully but nothing changed. A look in the SQL Management Studio confirmed that no permissions has been granted for the Service Account. 

After a second look at the Content Database permissions I understood the problem. My Admin Account was not db_owner on the Content_Database because I was added afterward. I asked the main Administrator to execute the above Commands, and everything worked well. 

So if you add a new Administrator to the Farm-Admins, don't forget that this account will not have all permissions Granted as you think.

SharePoint 2010 Cumulative Updates installation order

Are you about to update your outdated SharePoint 2010 installation and wondering if you need to apply all Cumulative updates in release order or just the latest one? The answer is: Just the latest one. That’s why it’s called Cumulative Updates, they include all previous fixes since the last Service Pack.

More information on the technet site

Debug a Silverlight application in a SharePoint WebPart

If you want to debug a Silverlitght Application in a SharePoint Silverlight web part read this article, it's really helpfull:
How to: Use a SharePoint Project to Deploy a Silverlight Application

Central Administration prompts for password

Before you start digging for complex reasons try this one: Add the Central Administration site to the Local Intranet Sites on the Application Server, this should solves the problem in most of the cases.

Clear WebConfigModifications using powershell

While playing arround with the SPWebConfigModification Class I added some wrong entries to the web.config. These entries where added every time I activated or deactivated my feature. It seemed the WebConfigModifications of the WebApplication object had some corrupt entries. So I found this blog. David Petersen explains how to clear these WebConfigModifications using code in a console application.

This was very helpfull and solved my Problem. But instead of creating a console application I simply made a PowerShell Script. The code is basically the same but I wanted to add it here for those who are still afraid of using PoweShell. Don't be. Powershell just rocks ;)

$siteUrl = "http://yoursiteurl/";

$site = $gc | Get-SPSite -Identity $siteUrl

[Microsoft.SharePoint.Administration.SPWebApplication]$webApp = $site.WebApplication

$webApp.WebConfigModifications.Clear();

$webApp.Update();

[Microsoft.SharePoint.Administration.SPWebService] $service =[Microsoft.SharePoint.Administration.SPWebService]::ContentService

$service.WebConfigModifications.Clear();

$service.Update();

$service.ApplyWebConfigModifications();

Finally just be careful because this code removes all modifications not only yours. So don’t use it on productive environments.