Archive

Author Archive

Could not load type ‘Microsoft.AnalysisServices.SharePoint.Integration.ReportGalleryView’

March 18, 2019 Leave a comment

If you ran into this issue, the first thing you need to do is check if the PowerPivot solution is deployed to the web applications. You  can do this by going to Central Administration > System Settings > Manage Farm Solutions and there you should see the solution powerpivotwebapplication.wsp. Make sure it is deployed to the correct web applications. If you are still running into issues, reinstall the rsPowerPivot addin on the frontend server where you are experiencing the issue. Uninstalling and reinstalling it makes sure all the dll’s are deployed correctly. Repairing the add-in in my case did not fix the issue.

Advertisements
Categories: Uncategorized

Deleting and restoring a site collection.

March 18, 2019 Leave a comment

Issues pop up when you delete a site collection and then want to restore it from a backup. When you delete a site collection it is not completely deleted from the content database. If at that point you try to restore it from a backup it will fail. The solution to this is quite easy, but when I saw the posts out there who propse database modifications (which is not supported by the way) I decided to put up a post.

The correct way to do it is the following:

Get-SPDeletedSite

This will give you an overview of the sites that are deleted but still  “out there”.

The property we are interested in is the site id.

Now create the content database object:

$webapp = Get-SPWebApplication https://myawesomesite.koentoso.com

$cdb = $webapp.ContentDatabases.Item(0)

Then we will force the delete of the site with the id from the previous command Get-SPDeletedSite.

$cdb.ForceDeleteSite(“8da556e0-264f-483b-a2b0-3fb1f8e33573”,$false,$false)

Now you should be able to restore your site collections without any issues.

Categories: Uncategorized

Distributed Cache Service cannot be started

March 18, 2019 Leave a comment

Today we ran into an interesting problem. The distributed cache service was no longer working. As it was a single server environment, we removed the service instance and reprovisioned it following:

http://technet.microsoft.com/en-us/library/jj219613.aspx

$instanceName =”SPDistributedCacheService Name=AppFabricCachingService”
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
$serviceInstance.Unprovision()
$instanceName =”SPDistributedCacheService Name=AppFabricCachingService”
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
$serviceInstance.Provision()

Strangely, it refused to start and went back to the services page. In the end, the following powershell fixed the distributed cache (after we re-added the spserviceinstance)

Categories: Uncategorized

SharePoint 2013 Adding Server to the Farm: Fast Growing Log Files

March 18, 2019 Leave a comment

Normally, when you are in the case of fast growing log files it means that you have verbose logging on. As in our case verbose logging was off, the issue had to be somewhere else. As we saw that all the service applications were failing on a specific server, we were able to identify that the server somehow lost the trust with the domain after restoring the snapshot. Even though we were able to log into the server (which normally should not work when the trust is gone) the trust was still failing.

The solution in our case was to reboot the server and the domain trust was sorted. Afterwards all issues were sorted and the farm was succesfully expanded 🙂

Categories: Uncategorized

CRM 2013 : Microsoft.Crm.SharedSetup.SetupException: The XML in the configuration file is not valid.

March 18, 2019 Leave a comment

CRM 2013 : Microsoft.Crm.SharedSetup.SetupException: The XML in the configuration file is not valid.

After testing our CRM 2013 installation scripts on our own environments, we decided to deploy them on the customer’s environment. As we were to expect a standard windows environment with IIS installed, we used the scripts we tested on identical environments. When we ran our scripts, we experienced the following error:

Microsoft.Crm.SharedSetup.SetupException: The XML in the configuration file is not valid. Location: F:\InstallConfigWebFrontEnd1.xml. Please fix the configuration file, and then try again. —>
System.UriFormatException: Invalid URI: The format of the URI could not be determined.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at Microsoft.Crm.Setup.Server.ConfigurationParser.ParseWebsiteSettings(XmlNode element)

As the error message states, one would check the XML file in every way to see if we did not mess up anything. In the end, we did not find anything wrong with it. What did give us a hint though, is the following part of the stacktrace:

at Microsoft.Crm.Setup.Server.ConfigurationParser.ParseWebsiteSettings(XmlNode element)

This means that something is going wrong once the setup tries to set the website from the following XML tag:

<WebsiteUrl Create=”false”>Default Web Site</WebsiteUrl>

After checking every possible option with the tags, we checked the IIS. For some reason IIS was missing it’s default web site, therefor it could not use the Default Web Site during setup. Changing the script to

<WebsteUrl Create=”true” port=80>Default Web Site</WebSiteUrl>

made setup run fine.

Categories: Uncategorized

CRM 2013 Unattended Install: Backend Installation: Check WebServerValidator: The Website does not exist.

March 18, 2019 Leave a comment

It took a while to figure this one out, given that I am not a CRM specialist. If you define that the backend server contains the DeploymentWebServiceRole, you also need to define the WebsiteUrl parameters in the xml file. If you don’t, you will get the above error that doesn’t really explain that it is missing something in the configuration file.

Categories: Uncategorized

Sorry, this site hasn’t been shared with you – Host Named Site Collections

March 18, 2019 Leave a comment

So, Host Named Site Collections are the new thing. You’ve created your web application and created a host named site collection through PowerShell. You browse to the site and it renders nicely. Yet when you expect to see the site, you get the standard SharePoint screen which tells you that you don’t have access to that site. This can be resolved easily. Check your IIS bindings. You forgot to remove them. So even though you have a DNS pointing to *.myhncsites.contoso.com and you created a site banzai.myhncsites.contoso.com your IIS bindings need to be modified so that there are no host headers defined.

Categories: Uncategorized