SharePoint 2013 missing Manage services on server for farm admins

2013-07-16 / SharePoint / 1 Comments

Sharepoint is missing options for Manage services and Backup and Restores

The issue is even though the admin or group is configured as a Farm administrator inside of SharePoint 2013 the admin/group is not configured on the server as an Administrator. The group must be added as a server Admin to be able to manage these functions.

Read More

Issues with SSRS 2012 SharePoint Integrated mode and SharePoint 2010

2012-10-26 / SharePoint, SQL / 0 Comments


I continued to run into issues with Kerberos and error message like Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’ when using SharePoint Reporting Services and a SQL DB that I was reporting on a different server.


When configuring Kerberos with previous SQL versions and SharePoint it was easy to set the delegation to “Trust this user for delegation to any service”. after setting SPNs you would be good to go.

However, with SSRS 2012 things have changed and SharePoint now uses the Claims To Windows Service to get authenticated correctly. I had it half way right and the fix was to add “trust this user for delegation to specified services only” on both the Claims To Windows Account and the SharePoint SSRS 2012 account. I found a sweet video on what needs to be done here:

Read More

Upgrade SharePoint 2007 Application to SharePoint 2010

2010-09-30 / SharePoint / 0 Comments

Launch Powershell with an account that access to the sharepoint environments.
If needed add the sharepoint snapin with the command:
Add-PsSnapin Microsoft.SharePoint.PowerShell

Once the snap-in is loaded type the following:

$webapp = Get-SPWebApplication http://sitename
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }

Wait a few minutes and then the whole web application will be upgraded.
This is a one time upgrade and can not be downgraded.

Read More

Sharepoint Error 1935.An error occurred during the installation of assembly component {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}

2010-06-18 / SharePoint / 1 Comments


Received the following error when trying to install SharePoint in a WebServer Farm on Server 2008.

Error 1935.An error occurred during the installation of assembly component {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}




After troubleshooting the error and trying to install vcredist.exe both x86 and x64 bits and they too received the error. I noticed some patches were installed on the server and it looked like the server had not been rebooted. After restarting the server I was able to reinstall SharePoint.

Verify that the server is in clean install state before trying to install. You can also try to run sfc /scannow to see if it finds any problems.

Read More

SharePoint Report Error: Cannot create a connection to data source ‘dataSource1’.

2010-05-10 / SharePoint, SQL / 1 Comments

You recieve the following error when running a report from report builder.

Report Execution error the report might not be vaild or the server could not process the data.
for more information about this error navigate to the report server on the local server machine, or enable remote errors
Cannot create a connection to data source ‘dataSource1’.

An error has occurred during report processing.


In my case the problem was the login that was used when running the report did not have access to the catalog and the sql server. I granted the correct access to the databases in sql manager and the user was able to run the report.

Read More

Using NetBackup To Backup SharePoint

2010-03-23 / NetBackup, SharePoint / 0 Comments

Setup 2 Policies as you normally would and include the Backup Selection as:

Policy 1
Microsoft SharePoint Resources:\*  (This will backup the entire SharePoint farm)

Policy 2
Define the Backup Selection as a Portal / TeamSite. For example: Microsoft SharePoint Resources:\http://mysite*
Create an additional policy for each Portal / TeamSite.

Read More

Index PDFs In SharePoint 2007 64Bit

2010-03-09 / SharePoint / 0 Comments

To resolve this issue, make sure that the Adobe PDF IFilter and the .pdf file type are configured correctly on the server. To install Adobe PDF IFilter and to configure SharePoint Server 2007 to index .pdf files, follow these steps:

  1. Download Adobe PDF IFilter  from the following Adobe Web site:
  2. Download Instructions for SharePoint 2007

Attached is a icon you can use as the .gif file

Read More

Delete Shared Services Provider From SharePoint

2010-03-09 / SharePoint / 0 Comments

from the bin directory run stsadm -o deletessp -title <YourSSPTitleHere> -force

The key here is -force, depending on the situation, if you don’t add -force, your SSP won’t be fully deleted.

Read More

Installing Reporting Services 2008 SharePoint Add-on

2010-03-05 / SharePoint / 0 Comments

When installing rsSharePoint_x64.msi I always run the setup with:

“rsSharePoint_x64.msi SKIPCA=1”

This will install the files but will not configure the service. After running the SKIPCA command we can run the rsCustomAction.exe from the %temp% directory on the server with the following commands:

rsCustomAction.exe /i

You need to run this under the setup account used for SharePoint with approprate security.

This will begin to install the reporting service add-on. Once complete the dos box will prompt with:

Calling HCInstal for lcid ‘1028’
 Outcome code is: 4

Cab files installed successfully.
Stopping W3SVC service.
Starting W3SVC service.
The command completed successfully

Read More

Installing and Configuring MOSS 2007 and SQL 2008

2010-02-24 / SharePoint / 0 Comments

When installing SharePoint on the initial servers we need to do an full install as follows:

1. Install from CD ->Click Advanced

Click Complete and Finish Install

When setting a service account as the application pool you must grant DCOM permissions as follows

You may see this error – more than once – when working with your Microsoft Office SharePoint Server (MOSS) 2007 deployment. This animal / error generally shows itself after you have applied an upgrade to an existing deployment. For example, when upgrading from B2 MOSS to B2TR MOSS – or when applying a special service pack from MSFT – you may begin to see a lot of these errors pop up in the SYSTEM event log.

The error CLSID is followed by a class ID for the DCOM+ application that the service account trying to activate that application – does NOT have permission to activate.

For example, let’s say I installed MOSS on a server, and used the account mossService as the service account (a least privileged, user account you created to run the MOSS service(s))., when I get this error, I could very well see an error like the following:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID


to the user <serverName>\mossService SID (S-1-5-21-<serviceSID>). This security permission can be modified using the Component Services administrative tool.

Copy the GUID following the CLSID above, and Start–>Run–>regedit

With the registry editor open, ensure that your cursor is on the computer at the beginning of the tree (make sure you are not in the middle of some previous edit session in the registry editor).

Edit–>Find and paste in the GUID. It’ll stop at the application entry – and you will want to note the application name on the right side pane. In this example, it was the IIS WAMREG admin service that popped up.

Now, open Component Services (typically, from the server – Start–>Administrative Tools–>Component Services), expand Component Services, Computers, My Computer, DCOM Config. Scroll down and find the application (IIS WAMREG in this case). Right-Click–>Properties and select the Security tab. You’ll have some options here – the first block Launch and Activation Permissions – ensure that the Customize radio button is selected, and click Edit. Now, add your service account – giving it launch and activate – and in some requirements – remote launch / activate permission.

Restart IIS and continue on.

NOTE: This is not applicable to MOSS setups only – and hopefully this will help someone else that sees these annoying DCOM errors in their SYSTEM event log.

Read More