The Acumen software design blog provides you with helpful articles about SharePoint.

Several web sites provide a good overview.

Official Microsoft SharePoint Overview

Microsoft SharePoint Wikipedia

01/05/2015 13:32:00.65  OWSTIMER.EXE (0x06CC)             0x0760  SharePoint Portal Server              User Profiles      d22b                High       Failure retrieving application ID for User Profile Application Proxy ‘User Profile Service Application Proxy’: Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does not have d4b21338-a0b4-40f2-9e07-1642409d1f34     at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()     at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_AppID()           1fdcdc9c-a0a0-c0c4-5a6c-67586a3db558

SharePoint

The MOST IMPORTANT THING about SharePoint:

Open ULSViewer.  Find an entry that has a category of User Profiles.  Right-click and Quick Filter for Category=User Profiles

This will show you everything related to the User Profile Synchronization process.

We deleted and recreated our User Profiles Application Service (we destroyed our database because user my sites had no meaningful information.)

We changed the Application Pool account from NETWORK SERVICE  to our farm account.  We validated all the permissions as stated here: http://www.harbar.net/articles/sp2010ups2.aspx

The next fix was to go to Central Administration->Manage Service Applications.  Select User Profiles Application Service.  Click Permissions in the ribbon.  Add the service account.

For more information on how Acumen can help with our other software needs, contact us today!

Migrate SP

Migrate SP

After doing a migration upgrade of SharePoint 2010 to SharePoint 2013, search failed with:

Sorry, something went wrong.

A correlation id is provided.

We checked our Content Sources from Central Administration->Manage Services on Server->SharePointServer Search->Search Service Application->Content Sources and found that Full Crawls had completed successfully.

You will find a TON of log enties for that correlation id, so finding the root cause is daunting.  Buried in the results you will find a 500 Service Unavailable error connecting to the Metadata Management Service.

In the Search Service Application, we saw that in Queries and Results->Search Dictionaries, we had an error:

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

We verified that the IIS->Application Pool had all pools started.

We verified that Central Administration->Manage Services on Server->Managed Metadata Web Service was started.  (This service is generating the 500 Service Unavailable.)

We then found that when we select Central Administration->Manage Service Applications->Managed Metadata Service Application (your name may be slightly different) and click Properties from the ribbon, we saw the same error shown in Search:

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

Migrate SP Solution

There are a lot of suggestions for solving this, but we fixed ours when we:

In Central Administration->Manage Service Applications, we deleted the Managed Metadata Service Application Proxy and the Managed Metadata Service Application.  (Don’t delete the data when you do this or you will lose your SQL Server database.)

We then repeated our PowerShell actions from the migration/upgrade:

$applicationPool = Get-SPServiceApplicationPool -Identity ‘SharePoint Web Services default’

$mms = New-SPMetadataServiceApplication -Name ‘Managed Metadata Service Application’ -ApplicationPool $applicationPool -DatabaseName ‘Managed Metadata Service_Acumen’

New-SPMetadataServiceApplicationProxy -Name ‘Managed Metadata Service Application Proxy’ -ServiceApplication $mms -DefaultProxyGroup

Change your Name and DatabaseName values.

Our first search test failed, but while we were watching the ULS Viewer, we saw lots of entries with the same correlation ids.  We tried search again after about 3 minutes and it worked.

For more information about how Acumen can help with your IT needs, contact us today!

SP 2010

SP 2010

This error can occur during an upgrade if the path in the Content Source doesn’t include file://

In the Content Source:

Delete the path and save.

Reenter Content Source, add path back and save.

Content will now search

For more information about how Acumen can help you with SharePoint 2010, contact us today!

For additional help, contact Microsoft Support:

https://support.microsoft.com/en-us

SharePoint

SharePoint

Problem:

When I delete a Web Application from Central Administration, I cannot create a Web Application at the same address.  I also see that the IIS folder does not disappear:

C:\inetpub\wwwroot\wss\VirtualDirectories\mySite443

I try to delete the folder by hand, but the following file is locked:

Microsoft.SP.WorkflowServices.ApplicationPages.dll

It give an error:

The process cannot access the file

‘C:\inetpub\wwwroot\wss\VirtualDirectories\mySite443\_app_bin\Microsoft.SP.WorkflowServices.ApplicationPages.dll’ because it is being used by another process

SharePoint Solution:

Some people suggest iisreset, but the process is actually locked by PowerShell with SP extensions.

Close all PowerShell and delete the file.

For more information about how Acumen can help with your other Software needs, contact us today!

After performing a SharePoint 2013 upgrade we were having trouble with our search functions and got a rather generic error message. After much work we were able to solve the problem.

After doing a migration upgrade of SharePoint 2010 to SharePoint 2013, search failed with:

Sorry, something went wrong.

A correlation id is provided.

We checked our Content Sources from Central Administration->Manage Services on Server->SharePointServer Search->Search Service Application->Content Sources and found that Full Crawls had completed successfully.

You will find a TON of log enties for that correlation id, so finding the root cause is daunting.  Buried in the results you will find a 500 Service Unavailable error connecting to the Metadata Management Service.

In the Search Service Application, we saw that in Queries and Results->Search Dictionaries, we had an error:

Managed Meta Data Error

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

We verified that the IIS->Application Pool had all pools started.

We verified that Central Administration->Manage Services on Server->Managed Metadata Web Service was started.  (This service is generating the 500 Service Unavailable.)

We then found that when we select Central Administration->Manage Service Applications->Managed Metadata Service Application (your name may be slightly different) and click Properties from the ribbon, we saw the same error shown in Search:

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

There are a lot of suggestions for solving this, but we fixed ours when we:

In Central Administration->Manage Service Applications, we deleted the Managed Metadata Service Application Proxy and the Managed Metadata Service Application.  (Don’t delete the data when you do this or you will lose your SQL Server database.)

We then repeated our PowerShell actions from the migration/upgrade:

$applicationPool = Get-SPServiceApplicationPool -Identity ‘SharePoint Web Services default’

$mms = New-SPMetadataServiceApplication -Name ‘Managed Metadata Service Application’ -ApplicationPool $applicationPool -DatabaseName ‘Managed Metadata Service_Acumen’

New-SPMetadataServiceApplicationProxy -Name ‘Managed Metadata Service Application Proxy’ -ServiceApplication $mms -DefaultProxyGroup

Change your Name and DatabaseName values.

Our first search test failed, but while we were watching the ULS Viewer, we saw lots of entries with the same correlation ids.  We tried search again after about 3 minutes and it worked.

SharePointSharePoint

When running SharePoint 2013 it is possible that you will run into a problem with UL entries and be unable to view them with the ULSViewer. The situation is easily resolved.

You must activate ULS logging in SharePoint Central Administration->Monitoring->Configure diagnostic logging.

 

 

 

SharePointSharePoint

Using SharePoint 2013 after an upgrade you might run into a situation where the crawl refuses to work because of privilege problems. This can result from the crawl account not having particular rights. Here is how you solve it.

SharePoint Solution:

The crawl account did not have sufficient privileges to access the security attributes of this file or folder. Ensure the crawl account has the ‘Manage auditing and security log’ privilege.

This can happen during an upgrade if the path in the Content Source doesn’t include file://

In the Content Source:

  1. Delete the path and save.
  2. Reenter Content Source, add path back and save.
  3. Content will now search

 

For more information on how Acumen can help with your other Software needs, contact us today!

SP Web App

SP Web App

When I delete a Web Application from Central Administration, I cannot create a Web Application at the same address.  I also see that the IIS folder does not disappear:

  • C:\inetpub\wwwroot\wss\VirtualDirectories\mySite443

I try to delete the folder by hand, but the following file is locked:

  • Microsoft.SharePoint.WorkflowServices.ApplicationPages.dll

It gives an error:

  • The process cannot access the file
  • ‘C:\inetpub\wwwroot\wss\VirtualDirectories\mySite443\_app_bin\Microsoft.SharePoint.WorkflowServices.ApplicationPages.dll’ because it is being used by another process

Some people suggest iisreset, but the process is actually locked by PowerShell with SharePoint extensions.

Close all PowerShell and delete the file.

I was recently working with one of my SP 2010 Lists and found that tab category List Tools with the Tabs of Items and Lists was missing. It wasn’t too hard to find the problem but I couldn’t find anywhere that gave you step-by-step instructions on how to fix it.

MissingTabs SP

 

The problem is that a Content Editor Webpart was added to the List Page but was left blank. Essentially, someone accidently added an extra webpart but didn’t populate it with any actual data. All the advice I found suggested removing the extra web part. I didn’t know how to do this.

Here’s how

  1. Navigate to the List in question (not a Page displaying the list, but the list itself)
  2. From the Site Actions drop-down (upper left) choose Edit Page
  3. Click the arrow (upper right) of the offending Content Editor Webpart and choose Delete
  4. Then, click the Page Tab
  5. Click Stop Editing

You should now see your tabs where they belong! Hooray.

For more information about how Acumen can help with your SharePoint needs, contact us today!

For additional help, contact Microsoft Support by clicking the link below:

https://support.microsoft.com/en-us