SharePoint Admin Roles

In a nutshell, the SharePoint Administrator should be responsible for some activities. In the table below I tried to split the customer and the SharePoint Admin roles.

Feel comfortable to share your opinion.

:-)

Simple Responsabilty Matrix for SharePoint Roles:

STEP	ACTIVITY DESCRIPTION	PERFORMED BY SP TEAM	PERFORMED BY THE CUSTOMER
1	SharePoint Farm configuration	X
2	SharePoint Farm Administration	X
3	SharePoint Services Application configuration	X
4	Development of Worflows		X
5	Development of solutions		X
6	Deploy of solutions	X
7	Give the appropriate site collection permissions (First and Second SC Adm)	X
8	Aditional site collection permissions		X
9	Managing SharePoint sites permissions		X
10	Create Web Applications	X
11	Create Site Collections	X
12	Provide the Architeture of farm		X
13	Provide the Architeture of Services Applications		X
14	Troubleshooting SharePoint infrastructure problems	X
15	Edit web.config files		X
16	Update web.config file (copy web.config file to its application)	X
17	Responsible for management the web application content		X
18	Provide the infrastructure to Backup the Farm	X
19	Performe Backup/Restore the Farm	X
20	Performe Backup/Restore of Site Collections	X
21	Performe moving/copying sites	X
22	Managing and checking the overall server health and functionality	X
23	Setting up auditing for SharePoint Site Collections		X
24	Guidance for governance of SharePoint farms and Web Applications		X
25	Guidance for Site Collections Quotas		X
26	Setting up quotas for Site Collections	X
27	Apply SharePoint patches and cumulative updates	X
28	Request to apply SharePoint patches and cumulative updates		X
29	Regularly analyzing SharePoint content and storage	X
30	Monitoring SharePoint trends (e.g. site usage and growth, disk space usage and growth)	X
31	Setting up alerts and enforcing policies	X
32	Guidance for alerts and enforcing policies		X
33	Update binaries for some application (copy files to some application)	X
34	Edit binaries for some application (files to some application)		X
35	Write PowerShell Scripts to manage SharePoint	X

SharePoint Products Configuration Wizard – Tip

When you will run the “SharePoint Products Configuration Wizard” on a farm that has large databases (greater than 100GB), it’s advisable to change the recovery mode of all SharePoint databases to simple mode, avoiding a possible storage overflow in database log files or disk unit.

After that, adjust the recovery mode of each database following your enterprise rules or the Microsoft recommendation at link http://technet.microsoft.com/en-us/library/cc678868(v=office.15).aspx

Cheers ;-)

PowerShell to check all the Farm Solutions Status different of “Deployed”

Initially, that solution was deployed with success on that farm, but for a weird reason that we couldn’t found out the why, that solution begun displaying an error on its status, as described on the screen shot below:

Based on this scenario, we decided to build a PowerShell to check all solutions status on our farms. If it find some solution with error status, it will create a log file pointing the name and the status of the solution and send by email this alert for the administrators.

Here is the PowerShell code:

####################

Add-PSSnapin Microsoft.SharePoint.PowerShell -EA 0

$ServerName = $env:computername

function sendMail($MailMSG) {
#Write-Host “Sending Email”
$attach = new-object Net.Mail.Attachment($MailMSG)

###First, the administrator must change the mail message values in this section
$FromAddress = “adm-web@sharepoint.com.br” #change by your email address
$ToAddress = “adm-web@sharepoint.com.br”      #change by your email address

$MessageSubject = “$ServerName – Alert – Solution Undeployed on Farm”
#$MessageBody = $MailMSG
$MessageBody = “Please verify the attached”
$SendingServer = “smtp.yourcompany.com”         #change by your smt server
###Create the mail message
$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody
$SMTPMessage.Attachments.Add($attach)
###Send the message
$SMTPClient = New-Object System.Net.Mail.SMTPClient $SendingServer
$SMTPClient.Send($SMTPMessage)
$attach.dispose()
}

# Get current date and format it to avoid invalid characters such as “/” and “:”

$today=Get-Date -format “MM-dd-yyyy HH.mm.ss”

# Replace with your script location

$Location=”D:\Softwares\CheckFarmSolutionScript”

# Replace with your desired log file location + name

$logFile=”$Location\LogSOLUTIONS.log”

If (Test-Path $logFile){
Remove-Item $logFile -Confirm:$false
}

function List-Solutions()
{
$farm = Get-SPFarm
foreach ($solution in $farm.Solutions)
{

if($solution.Deployed -eq $false){
Write “Solution Verification started at $today” >>$logFile
Get-SPSolution -identity $solution.Name >>$logFile

}
}
}

#call the function List-Solutions

#test if the log file exists, If yes, send an email

If (Test-Path $logFile){

sendMail($logFile)

}
####################

Cannot start service SPAdminv4 on computer – SharePoint 2010 Administration

If you’ve experienced this error (System.InvalidOperationException, “Cannot start service SPAdminv4 on computer ‘.’) after installing/rebooting a SharePoint 2010 server and failing consistently at the SharePoint 2010 Products Configuration Wizard, then this is likely to help:

(1) Browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

(2) In this directory Create a file called “WSSADMIN.EXE.CONFIG“

(3) Populate it with the following:

<configuration>

      <runtime>

<generatePublisherEvidence enabled=“false”/>

      </runtime>

</configuration>

(4) Start the “SharePoint 2010 Administration” services again

Now everything should be working….

This disables checking for CAS (Code Access Security) publisher policy. MSDN article, http://msdn.microsoft.com/en-us/library/bb629393.aspx

More details, read http://blogs.msdn.com/johan/archive/2009/11/12/make-sure-you-have-an-internet-connection-when-using-signed-assemblies.aspx and http://blogs.msdn.com/dsvc/archive/2008/06/24/troubleshooting-startup-issues-with-managed-application-having-authenticode-signature.aspx

HOW TO: Como Habilitar o Developer Dashboard no SharePoint 2010

Developer Dashboard  é um novo recurso do SharePoint 2010 que vem para facilitar a vida do desenvolvedor e do responsável pelo bom desempenho e melhor experiência para o usuário final. Este recurso mostra quanto tempo uma página demorou para ser carregada e quais componentes foram carregados, sendo muito útil quando os usuários reclamam de lentidão, podendo assim, agora classificar o que seria e aonde esta “lentidão”, de forma mais fácil e rápida.

Solução:

Por default, este recurso vem desabilitado. Para habilitar, você pode utilizar o stsadm ou Windows PowerShell.

Para habilitar, usando STSADM, vá em Start > Microsoft SharePoint 2010 Products, clique em SharePoint 2010 Management Shell, e entre com o seguinte valor:

Stsadm –o setproperty –pn developer-dashboard –pv [modo]

Em [modo] , escolha a forma que você quer que ele funcione. Você pode escolher uma das três opções:

• On – significa que o Developer Dashboard  será sempre exibido
• Off – significa que estará desabilitado
• Ondemand – significa que o Developer Dashboard  será exibido, mas não estará ativo, apenas quando precisar você deve ativá-lo clicando no seu ícone.

Ao habilitar este recurso, todas as páginas irão conter um ícone do Dashboard, como mostrado na imagem, porém, só os administradores do Site Collction poderão ver.

Caso tenha escolhido o modo ondemand, você pode habilitá-lo quando necessário apenas clicando sobre o ícone dele.

Figura 1: Representação do ícone

Quando habilitado, ele trará uma página com os resultados para análise.

Figura 2: Exibindo as informações

Agora basta você realizar suas análises.

Conclusão

Esta função é muito útil para os desenvolvedores para que eles possam entregar aplicações que funcionam corretamente sem ter problemas posteriores e também ajuda a detalhar o como a página e as web parts estão se comportando.

Mais referências:

http://larahvidotti.wordpress.com/2011/01/14/como-habilitar-o-developer-dashboard-no-sharepoint-2010/

Daylight saving time ended and Sharepoint still off by 1 hour

The daylight saving time ended, but SharePoint still saving all items which require a date time stamp reference with 1 hour less (in my case).

Screenshot of the behavior:

1.Modify the Timezone.xml file to include the correct date and time for standard time and for daylight saving time. To do this, follow these steps:

a. Start Notepad, and then open the Timezone.xml file.

The Timezone.xml file is located in the following folder:

SharePoint Server 2013

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Config

SharePoint Server 2010

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Config

Windows SharePoint Services 3.0 / MOSS 2007

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Config

Microsoft Windows SharePoint Services 2.0

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Config

b. The contents of the Timezone.xml file should resemble the following example bellow that I will modify.

c. Locate the time zone that you want to modify. In my case was Name=”(UTC-03:00) Brasilia”

<TimeZone ID=”8″ Name=”(UTC-03:00) Brasilia” Hidden=”FALSE”>
<Bias>180</Bias>
<StandardTime>
<Bias>0</Bias>
<Date>
<Month>2</Month>
<Day>4</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</StandardTime>
<DaylightTime>
<Bias>-60</Bias>
<Date>
<Month>10</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</DaylightTime>
</TimeZone>

d. Modify the StandardTime element to specify the correct date and time for standard time. For the current time zone, change the Day fields from 4 to 3.

<TimeZone ID=”8″ Name=”(UTC-03:00) Brasilia” Hidden=”FALSE”>
<Bias>180</Bias>
<StandardTime>
<Bias>0</Bias>
<Date>
<Month>2</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</StandardTime>
<DaylightTime>
<Bias>-60</Bias>
<Date>
<Month>10</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</DaylightTime>
</TimeZone>

e. Click Save on the File menu to save your changes.

f. Clean the SharePoint cache using PowerShell on SharePoint 2010 or manually for other versions. Bellow the PowerShell script:

#PowerShell Script to clean SharePoint Configuration cache:

Add-PSSnapin -Name Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue

Stop-Service ProjectQueueService14

Stop-Service ProjectEventService14

Stop-Service SPTimerV4

$folders = Get-ChildItem C:\ProgramData\Microsoft\SharePoint\Config
foreach ($folder in $folders)
{
$items = Get-ChildItem $folder.FullName -Recurse
foreach ($item in $items)
{
if ($item.Name.ToLower() -eq “cache.ini”)
{
$cachefolder = $folder.FullName
}

}
}

$cachefolderitems = Get-ChildItem $cachefolder -Recurse
foreach ($cachefolderitem in $cachefolderitems)
{
if ($cachefolderitem -like “*.xml”)
{
$cachefolderitem.Delete()
}

}

$a = Get-Content  $cachefolder\cache.ini
$a  = 1
Set-Content $a -Path $cachefolder\cache.ini
start-Service SPTimerV4
IISRESET

########################

g. Test your environment again. Now, everything will be working right.

Good references:

http://support.microsoft.com/kb/888253/en-us

http://spinternals.blogspot.com.br/2014/01/sharepoint-powershell-script-para.html

About Doubts / Dúvidas SharePoint Blogs Central Administration regional settings in sharepoint 2010/2013

To change Regional Setting in SharePoint 2010/2013 for Central Administration web site to check and receive the correct date and time format for the performed jobs.

Regional Settings are hidden for the Central Admin site collection. However, you can get it corrected, by typing the URL (substitute mysharepointserver:2010 for your central admin web application and port).

http://mysharepointserver:2010/_layouts/regionalsetng.aspx or

http://mysharepointserver:2013/_layouts/regionalsetng.aspx

2010:

2013:

How to enable the SharePoint 2010 and 2013 Developer Dashboard

Developer Dashboard is a great tool that will help you to gathering a lot of information about some application in your farm. It was reviewed and it received a huge number of improvements. Now, the Developer Dashboard panel, it’s no longer a control on your page which only shows you information about the current request. It’s now a separate window which shows you all requests since you started the developer dashboard session.

The new 2013 Developer Dashboard depends on the Usage and Health Data Collection Service Application. So, be sure to configure it before!

Notice that there are the following options for the Developer Dashboard:

• On - SharePoint 2010: The Developer Dashboard will always be rendered at the bottom of each page SharePoint 2013: The Developer Dashboard icon will always be displayed at the top right corner. It will not be appended to each page.
• Off – SharePoint 2010 & 2013: The Developer Dashboard will not be available
• OnDemand – SharePoint 2010: The Developer Dashboard will only be appended to a page after clicking on the icon in the ribbon SharePoint. In SharePoint 2013, this mode was deprecated and replaced with On.

PowerShell

The dashboard can be enabled for your SharePoint 2010 or 2013 farm by executing the following commands in a SharePoint PowerShell window:

#Adding SharePoint Snapin
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
#cleaning the screen
cls
$cs = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$dds = $cs.DeveloperDashboardSettings
write-host “Developer dashboard Status is: “$dds.DisplayLevel

if ($dds.DisplayLevel -eq “On”) {
Write-Host “Developer dashboard is enabled.”
write-host “Do you want do disable it? (Y/N)”
$aw = Read-Host
if ($aw -eq “Y”) {
$dds.DisplayLevel = “Off”
$dds.Update()
Write-Host “Developer dashboard disabled.”
}
} else {
Write-Host “Developer dashboard is disabled.”
write-host “Do you want do enable it? (y/n)”
$aw = Read-Host
if ($aw -eq “Y”) {
$dds.DisplayLevel = “On”
$dds.Update()
Write-Host “Developer dashboard enabled.”
}
}

After that PowerShell, if you have turned “on” the Developer Dashboard and you would like to check out how it works, You need to click on the developer dashboard icon in the upper right ribbon button and the new developer dashboard window opens.

Ok, that’s it. Have a good troubleshooting.

For more information on how to use the dashboard can be found in the excellent article at http://www.zimmergren.net/archive/2010/12/18/sp-2010-developing-for-performance-part-1-developer-dashboard.aspx, where the author, describe in details how to read the report for SharePoint 2010!

This workbook is larger than the maximum workbook size allowed to be opened in the browser

 

How to change the upload size restriction (can I upload a 10mb doc/xls or a 1GB doc/xls) within Central Admin so that display a workbook in a web part (browser) using Excel Services.

1. Log in to Central Admin as a Farm Administrator
2. Click “Application Management” in the left nav.
3. Click “Manage service applications” under Service Applications.
4. Click “Excel Services Application” next to “Excel Services Application Web Service Application”  Note: not the item in grey under this (Proxy). You want the blue item.
5. 
6. Click the “Trusted File Locations” link:
7. 
8. Then, select the reports library or document library your web part is calling or where the files are.
9. Scroll down to “Workbook Properties” and change the ‘Maximum Workbook Size” if it’s set to 10mb’s try and change it to 50 or 100mb’s and save the change. Note: 20mb is the default configuration.
10. 
11. Go back to the page with the reports web part and refresh it.

    This should fix your issue with “This workbook is larger than the maximum workbook size allowed to be opened in the browser” and Excel Services in SharePoint 2010.

    Here’s a link to help you out: TechNet – http://technet.microsoft.com/en-us/library/ff191192.aspx

People Picker isn’t showing “Users” from a trusted domain in one/all Web Application or in the Central Administration

Today a customer asked me how to add the Active Directory “Domain Users” group from DomainB into a SharePoint Group hosted on a DomainA as described below:

When we try to add the AD “Domain Users” group from “DomainB” into SharePoint “Visitors” group or any other, we are not able to retrieve the correct “domain\group” as described below:

`

So, to solve this problem, we had to execute the command related with “Peoplepicker-searchadforests” (http://technet.microsoft.com/en-us/library/f3988343-c57a-4f92-b523-682b7a5e9aa8(office.12).aspx).

As our environment is configured with two-way trust, it should suffice to run the following commands:

1) stsadm -o setproperty -pn peoplepicker-searchadforests -pv "forest:domainA.local;forest:domainB.local" -url http://webapp.domainA.local

2) stsadm -o setproperty -pn peoplepicker-searchadforests -pv "forest:domainA.local;forest:domainB.local" -url http://centraladminURL

The first command, is related to web application that we are trying to add the AD group from other domain and the second, is related to SharePoint Central Administration that will allow you to resolve names when adding a web application user policy for users from a trusted domain.

If you want all web applications to behave the same way, you should to run the first command for each web application.

I hope this information could be useful for you guys.

Backup and Restore of one Site Collection using columns in Managed Metadata

Wherever you restore one site collection from one Farm to another that uses site columns linked with some termstore some errors can be showed like this:

Managed metadata columns consult the MMS service whenever we interact with data stored in these columns. If MMS is not there things can break and show unexpected behavior.

The easiest option to make things work is to restore the MMS from source farm to target farm.

You can use :

1. Export-SPMetadataWebServicePartitionData (http://technet.microsoft.com/en-us/library/ff607847.aspx) to export the MMS from source farm;

2. After that, the second steps is import  the same MMS exported in the step 1 using Import-SPMetadataWebServicePartitionData (http://technet.microsoft.com/en-us/library/ff607667.aspx ).

By using this technique the term store is available on the target as the same in the source. The sspId used internally by the Term Store and referred by Managed Metadata columns in list is retained.

Below the scripts to apply:

#Step 1 – Export MMS

If ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null )
{ Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell }

#this sets the exporting MMS ID
$mmsApp = $mmsApplication = Get-SPServiceApplication | ? {$_.TypeName -eq “Managed Metadata Service”}

$mmsproxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq “Managed Metadata Service Connection”}

Export-SPMetadataWebServicePartitionData $mmsApp.Id -ServiceProxy $mmsproxy -Path \\ebsgerh04\Backup\exportfile.bak

#Step 2 – #Import MMS

If ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null )
{ Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell }

#this sets the exporting MMS ID
$mmsApplication = Get-SPServiceApplication | ? {$_.TypeName -eq “Managed Metadata Service”}
$mmsProxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq “Managed Metadata Service Connection”}
Import-SPMetadataWebServicePartitionData $mmsApplication.Id -ServiceProxy $mmsProxy -Path “\\Sharepoint_Server\Backup\exportfile.bak” -OverwriteExisting

New-SPLogFile – Troubleshooting SharePoint Easily

If you are troubleshooting some SharePoint Environment, a good tip is start a new SharePoint Log to facilitate the error captures.

To start a new SharePoint Log follow these steps:

1) Open the SharePoint 2013 Management Shell as Administrator;

2) Type the command ant press Enter:

New-SPLogFile

3) Navigate to the drive/folder of the SharePoint log files. To check where the log files are, Open the “Central Administration”, click on “Monitoring” menu, click on “Configure diagnostic logging” menu:

4) Scroll down until “Trace log” and select the “Path” and click “Ok”:

5) Open Windows Explorer and navigate until the “Path” that you got previously. In Windows Explorer window, click on the “Date modified” column to set up descending order;

6) Open the last log file and good troubleshooting :-)

New-SPLogFile – Troubleshooting SharePoint Easily

If you are troubleshooting some SharePoint Environment, a good tip is start a new SharePoint Log to facilitate the error captures.

To start a new SharePoint Log follow these steps:

1) Open the SharePoint 2013 Management Shell as Administrator;

2) Type the command ant press Enter:

New-SPLogFile

3) Navigate to the drive/folder of the SharePoint log files. To check where the log files are, Open the “Central Administration”, click on “Monitoring” menu, click on “Configure diagnostic logging” menu:

4) Scroll down until “Trace log” and select the “Path” and click “Ok”:

5) Open Windows Explorer and navigate until the “Path” that you got previously. In Windows Explorer window, click on the “Date modified” column to set up descending order;

6) Open the last log file and good troubleshooting :-)

SharePoint Search – Crawl Troubleshooting – The item could not be accessed on the remote server because its address has an invalid syntax. ( SearchID =)

This week I faced a weird error message on my “Search Service Application“, where the crawl was not performed.

Every time the crawl would try to index data, the error message below was shown and the crawl log showed 0 (zero) success and 1(one) error Top Level…:

“http://globalintranet.mabotega.local.

The item could not be accessed on the remote server because its address has an invalid syntax. ( SearchID = F1312B59-3AE6-4121-91BD-74B774BE0D07 )”

So, I need to find out a way to check if our crawl system was functioning and the answer was the Fiddler2 (http://fiddler2.com/).

On this post, I will try to describe how to troubleshoot the SharePoint Search crawl process with the Fiddler tool to help you to check if the crawl is gathering data from the web application (web sites) set up in some content source.

In my environment I am not using Proxy on Search Configuration as shown on the screenshot below, but after set up it with Fiddler as Proxy and removed it from Search Configuration, my Search returned to crawl content for my web sites…. Too much weird!!!! Probably some dirt on my config database, I guess…. This is my only explanation….

Ok, lets finish the talk to follow the technical steps below:

SharePoint Search – Crawl Troubleshooting

Using this incredible tool called Fiddler, we are going to configure SharePoint Search to crawl through Fiddler as a Proxy so we can watch the traffic on it and check if the system is gathering data from our web sites. Using this technique you will be able to watch if the behavior of the crawl system is acting correctly or unexpectedly.

Necessary Steps:

1. Download and install Fiddler on the server running the crawl (http://fiddler2.com/). For this, follow the Next, Next, Finish process;
2. Determine which account is running the crawl. Usually it will be the Default content access account listed in Search Administration:

3. If you have Crawl Rules set up for specific content sources you may have alternate credentials specified, so check your rules and be sure you are using the correct account for testing. In my case, I don´t have it, but be sure;

4. Start the Fiddler, holding down the [Ctrl][Shift] keys and right click Fiddler to choose “Run as different user”. Log in as the Crawl Account or the account for your rule that will be checked. (If this option is not available, you may have to log out and log back in as the crawl account. Either way you need to run Fiddler as the crawl account):

In my scenario, my default access account is RBTCRAWL:

5. Once Fiddler is running choose Tools | Fiddler Options… and click the Connections tab. Note the Fiddler listens on port: setting. 8888 is the default. Ensure that it does not duplicate a port already in use by SharePoint or IIS. Close the dialog after making any necessary adjustments to the port. In my scenario, I don´t have any web site running on the 8888 port, so I leave the default;

6. Open a browser and go to http://localhost:8888 (or whatever your port number is for Fiddler) and you should see something like the following indicating that you are set up correctly.

7. To configure SharePoint to use Fiddler as Proxy, please, return to Search Administration and choose the link for Proxy Server from the System Status section. In my scenario I am not using Proxy:

8. Configure SharePoint to use Fiddler by choosing Use the proxy server specified and adding the address and port.

9. Click OK to save your settings.
10. Start the crawl for the content source that you are having issues with by choosing Content Sources. Select the content source and choose Start Full Crawl.

11. Once the crawl starts you should begin to see activity in Fiddler. In the example below I am crawling some web applications. The crawler always looks for a robots.txt file first to read the web site map (even if it was not set up). In my case I don’t have one, so Fiddler displays the 404 results for it (1). Crawling a SharePoint site you will notice that the crawler uses the “SiteData service” (2) to gather information about the site from SharePoint. Following that you will see some results for each request performed by the crawl system:

12. Once you are done testing be sure to reset the Proxy settings in the Search Application to return to the previously configuration:

13. Armed with the results of the Fiddler trace you can see the conversation that SharePoint is having with the content source that you are troubleshooting.
14. Troubleshooting SharePoint Search can be a big challenge and I really hope that this post can help you to get information if your Search are crawling or not.

Using Merge-SPLogFile – Consolidate Log files on SharePoint

According to the description of Merge-SPLogFile on Microsoft TechNet:

“Combines trace log entries from all farm computers into a single log file on the local computer.”

Let me explain how you can use this powerful command.

Basic Usage

Lets visualize a simple farm.

As the sample Farm image above we have 2 frontend servers, 1 application server and 1 database server. If you wanted to consolidated the last hour of SharePoint log entries from the front-end server and application server you would open the SharePoint Management Shell on one of the servers and type the following command:

Merge-SPLogFile –Path “E:\SPLogs\MergedLogs.log” –Overwrite

Finding Correlation ID

What the following example show is how to find the log entries for a specific correlation id:

Merge-SPLogFile –Path “S:\SPLogs\MergedLogs.log” –Correlation 3ae2a6c0-da14-43a1-afda-5bb6bbff3d43 -Overwrite

Excel calculation services – The Workbook cannot be opened

Symptom:

When you configure the Excel calculation services (ECS) on your SharePoint2010 farm it might happen that you (or latest your endusers) face some error when trying to open an excel sheet stored in a document library.

When you check your ULS logs, you will find something like:

ServerSession.ProcessServerSessionException: An exception during ExecuteWebMethod has occurred for server: http://yourserver andsomeguid/ExcelService*.asmx, method: OpenWorkbook, ex: Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSessionException: The workbook cannot be opened..

Result=Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession Exception: The workbook cannot be opened.  
at Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession.Execute WebMethodCore(WebMethodType webMethodType, WebMethodBehaviorAttribute webMethodBehavior, CommandParameter parameter, CoreWebMethod coreWebMethod)  
at Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession.Execute WebMethod(WebMethodType webMethodType, WebMethodBehaviorAttribute webMethodBehavior, CommandParameter parameter, CoreWebMethod coreWebMethod)

To solve this error, the account that is running the Excel Services application pool must have access to the content database where the PWA site resides.

To correct it, just run the script below:

$w = Get-SPWebApplication -identity “http://ourserver.domain”    # change here to the correct web application
$w.GrantAccessToProcessIdentity(“Domain\UserAccountThatRunTheExcelService”)

Ok, now all content databases hosted on this web application should have received dbowner role for that user account (Excel Service Account).

Central Administration regional settings in sharepoint 2010

To change Regional Setting in SharePoint 2010 Central Administration web site to check and receive the correct date and time format for the performed jobs.

Regional Settings are hidden for the Central Admin site collection. However, you can get to them by typing the url (substitute mysharepointserverCA:2010 for your central admin web application):

http://mysharepointserverCA:2010/_layouts/regionalsetng.aspx

An unexpected error occurred. Error 19106. – Performancepoint Dashboard Designer not working

Screenshot Error:

Error:

An unexpected error occurred. Error 19106. Exception details: System.ServiceModel.ServiceActivationException: The requested service, ‘http://epmserver:32843/a326fd7459d34025a9357a248171c3a2/PerformancePointService.svc&#8217; could not be activated. See the server’s diagnostic trace logs for more information. Server stack trace: at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.PerformancePoint.Scorecards.IBIMonitoringServiceApplication.RenderReport(Boolean proxyCacheAttempt, String& proxyCacheKey, SubstitutionList& proxyCacheSubs, DateTime& proxyCacheExpiration, String& html, String& script, WebPartContextUpdate& webPartContextUpdate, RepositoryLocation reportLocation, String renderTargetId, String availableHeight, String availableWidth, WebPartContext webPartContext, Boolean isAccessibilityMode) at Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceApplicationProxy.RenderReport(String& html, String& script, WebPartContextUpdate& webPartContextUpdate, RepositoryLocation reportLocation, String renderTargetId, Unit availableHeight, Unit availableWidth, WebPartContext webPartContext, Boolean isAccessibilityMode)

Possible Solution:

1. Restart the “Performance Point Service” from central admin

2. Perform an IISRESET

Capturar logs do Farm através de 1 servidor via PowerShell

Merge-SPLogFile -Path <String> [-Area <String[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Category <String[]>] [-ContextFilter <String[]>] [-Correlation <Guid[]>] [-EndTime <DateTime>] [-EventID <String[]>] [-ExcludeNestedCorrelation <SwitchParameter>] [-Level <String>] [-Message <String[]>] [-Overwrite <SwitchParameter>] [-Process <String[]>] [-StartTime <DateTime>] [-ThreadID <UInt32[]>]

Exemplo:

Merge-SPLogFile -Path D:\merged_log.log -Correlation 9b6b1653-baef-46a4-ace8-ff9a1f535f87

Referência:

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