Vinit`s SharePoint Space

Hide Ribbon for Anonymous users SharePoint 2013

2013-04-27T11:32:50Z

You might have thought to hide Ribbon from the Anonymous users due to security reason,

In SharePoint 2010 it was simple to modify the master page and that's done, In SharePoint 2013 there has been some changes and we no more need to modify the master page directly, every thing is simplified in 2013 and we just need to modify the concern html page and that should be done.

Every master page in 2013 would have it concerned html page eg for Seattle.master we have Seattle.html

for oslo.master we have oslo.html page which in turn controls the master page and its tags.

Html page has tags that start with  and  that show markup inside these tags and in some cases what you would find in the final corresponding master page.

So lets get to the action on what need to done in these html page.

1. Open the html page in SharePointDesigner 2013 or open the site through explorer and open it using your favorite html page editor.

2. Look for <Div Class =”ms-belltown-anonshow”>

…..

</div>

3. When we add the following markup enclosed in the  and <!--ME:—> tags,

<!—MS:<SharePoint:SpSecurityTrimmedControl runat=”server” permission=”AddandCustomizepages”>—>

….

</div>

<!—MS:</SharePoint:SpSecurityTrimmedControl>—>

the design manager will create the corresponding master page with the correct functionality of hiding the Ribbon for an anonymous user.

For list of permission you can refer to

http://msdn.microsoft.com/en-ca/library/microsoft.sharepoint.spbasepermissions.aspx

Technorati Tags: Hide Ribbon,SharePoint 2013,maste page

Unable to access Personal Site after backup and restore of mysite SharePoint 2010

2013-04-26T19:48:00Z

Issue: When we backup the mysite data and restore on new SharePoint 2010 farm, we sometime are unable to access my content page.

If we check in ULS we see

3wp.exe (0x0A3C) 0x1330 246 7hz8 Medium My Site: PersonalSpaceRedirect: Unknown error: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.SharePoint.Portal.WebControls.PersonalSpaceRedirect.RedirectToGlobalPrivatePage() at Microsoft.SharePoint.Portal.WebControls.PersonalSpaceRedirect.LoadControl(Object sender, EventArgs a).
01/06/2010 18:59:36.52 w3wp.exe (0x0A3C) 0x1330 246 79gk Medium My Site: PersonalSpacePublicRedirect: User was redirected to here from 'http://[server]/personal/[user]/default.aspx', but should have gone to 'http://[server]/sites/mysite/_layouts/MySite.aspx'.

So the issue happens because the User ID for the profile does not match and causes the redirect to fail to personal site collection.

Resolution and explanation :

In a normal SharePoint environment, the user is the owner his own my site. If the user is owner of the my site and the access to the profile store is also correctly granted the relink of the old my site with the new user profile should work automatically. When the user opens the first the his old my site, SharePoint will automatically find the profile of that specific user in the profile store and gather the new Profile ID (named User ID). This ID will be written in the property bag of the my site web(urn:schemas-microsoft-com:sharepoint:portal:profile:userprofile_guid). In the profile store, we also update the Personal Site property for that user and so the re-link is done. In our case the user was not able to do these type of modifications due to permission issues, therefore the My Site Web Property was not repaired, so that the mysite was pointing still to the old profile id. In the profile store we were also not able to add this relative url to the "Personal Site" property. So we can re-link the my sites with the profiles using powershell, by adding the new profile id in the property bag of the my site:

$web = get-spweb http://mysiteurl/personal/userid

$web.SetProperty("urn:schemas-microsoft-com:sharepoint:portal:profile:userprofile_guid", "USER Profile ID") $web.Update()

The new user profile id can be looked up in the Profile DB directly, however this is only recommended with the help of MS support:

select * from [Profile DB].[dbo].[UserProfile_Full] (nolock) where NTName = 'domain\user'

and second action is to

go ahead and delete the user profile from user profile store and then click on my content, this should create a new profile with the correct ID.

Central admin-> application management-> mange service application-> user profile application –> mange user profile-> search for the user and delete it.

Technorati Tags: Sharepoint 2010,My content,mysites,"My Site: PersonalSpaceRedirect: Unknown error: "

Newsfeed Error - A Required SharePoint Feature is not enabled , SharePoint 2013, FBA site.

2013-04-23T17:15:50Z

There was a recent issue when a User clicks on the newsfeed there is nothing there, when they switch from following to everyone they following error is displayed

"SharePoint returned the following error: A required SharePoint feature is not enabled. Internal type name: Microsoft.Office.Server.Microfeed.MicrofeedException. Internal error code: 46. Contact your system administrator for help in resolving this problem."

When I go to "about me" it still states "We're almost ready" underneath my Bio, and if I goto tasks "something went wrong" when it tries to load the page

The errors I still see are as follows

in the Application Log:

This appears intermitantly

"The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 8e2b6939-813f-4798-b473-37b891a4ad2d) threw an exception. More information is included below.

Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running ."

Resolution:

Issue happens for the user whose value personal site capabilities shows “0” and in order to have feeds and other featured working we need the value as “14”

To fix the issue we need to follow either of below action plan.

1) This can be done - user profile service application - mange user profiles -> search for the user -> look for personal site capabilities and update the value to 14 and save it.

2) I have a PowerShell which can help us to update affected users values form 0 to 14.

#Set up default variables

#My Site URL

$mySiteUrl = "http://spf1/my/"

#The part of the picture URL you are trying to find

$currentValue = "0"

#The value that will replace the above

$newValue = "14"

#The internal name for Property

$upAttribute = "SPS-PersonalSiteCapabilities"

#Get site objects and connect to User Profile Manager service

$site = Get-SPSite $mySiteUrl

$context = Get-SPServiceContext $site

$profileManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context)

$profiles = $profileManager.GetEnumerator()

foreach ($userProfile in $profiles)

{

if ($userProfile[$upAttribute].toString() -ne 14 )

{

if ($userProfile.AccountName -like "i:0#.f|ldapmember|achavda")

{

$newvalue = $userProfile[$upAttribute].toString()

$newvalue = $newvalue.Replace($currentURLValue, $newURLValue)

$userProfile[$upAttribute].Value = $newvalue

$userProfile.Commit()

}

}

Technorati Tags: Sharepoint 2013,neewsfeeds,FBA,A Required SharePoint Feature is not enabled

Migrate SharePoint designer workflow from SharePoint 2007 to SharePoint 2013

2013-04-21T04:22:00Z

There has been instances when you plan to upgrade SharePoint 2007 to SharePoint 2013 which has custom workflows which are designed by SharePoint Designer.

If we follow the straight upgrade process like upgrade the database from 2007 to 2010 and then upgrade to 2013 you will not be able to edit the workflow nor update them.

Here is the process which need to be followed to make sure we can continue using those workflow in 2013 and can update and edit them without issues.

1. Take the back of the content DB from the SQL server.

2. Restore the backup on SQL server for the SharePoint 2010 farm.

3. Create a new claims based web application.

4. Attach the content database to this web application – mount-spcontentdatabase

and make sure we follow the process to migrate the users from classic to claims, reference -http://technet.microsoft.com/en-us/library/gg251985.aspx

5. open the site in SharePoint Designer and edit the workflow and republish it.

we have to do this because sharepoint designer 2007 workflow are aspx based and 2010 will be form based and hence the upgrade needed.

6. Now take a backup of the database and restore it on 2013 SQL server farm.

7. Attach the database to SP2013 web application using the command mount-spcontentdatabase.

8. Open the site in designer and we should be able to edit and update the workflow.

How to use to custom SQL attribute store to generate claims and authorize user.

2013-04-15T09:37:00Z

This blog will help you to understand how you can configure ADFS to use SQL to use the value from the table and generate token and authorize the user.

Before moving ahead you require your ADFS setup and running.

You can refer this blogs which helps you to configure ADFS 2.0 with SharePoint 2010

http://blogs.technet.com/b/speschka/archive/2010/07/30/configuring-sharepoint-2010-and-adfs-v2-end-to-end.aspx

Follow the steps below to configure SQL and ADFS and SharePoint server.

Create a new Database by name : Peoplestore
Create a new table named :Attribute
Create columns eg: User ID, Logon, Department\Organization\Firm
Add values to it:

Eg :

Note: Make sure we have proper permission on the Database created

Here proper permission means the ADFS account should be able to access this SQL database. We don’t need write access, a read access to the DB will be more than enough.

if you face issues with generating claims, you can check the event viewer on ADFS server for the event related to permission and grant the required permission on the DB.

On ADFS server

Add SQL attribute store

Imp note : Display Name: SQL

Modify Relying party trust
Edit claim rule.
Add a new claim rule
Claim type :

Customer rule
Claim rule language
Ref: http://technet.microsoft.com/en-us/library/ee913566(WS.10).aspx
For Conditions under claim rule
Ref:http://technet.microsoft.com/en-us/library/dd807118(WS.10).aspx
Eg : claim rule

c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname"] => issue(store = "sql", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/Firm"), query = "SELECT Firm from dbo.attributes where logon = {0}", param = c.Value);

On Sharepoint Server

Set up claims mapping for "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/firm
$token = Get-SPTrustedIdentityTokenIssuer
Add new claim type
$token.ClaimTypes.Add(http://schemas.xmlsoap.org/ws/2005/05/identity/claims/Firm)
Add claim type mapping
$firmclaim = New-SPClaimTypeMapping -IncomingCLaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/Firm" -IncomingClaimTypeDisplayName "Firm" -LocalClaimType http://schemas.xmlsoap.org/ws/2005/05/identity/claims/Firm
To add claim type to our issuer
$firmclaim | Add-SPClaimTypeMapping -TrustedIdentityTokenIssuer $token

In case you want to use a new web application and use the same SAML token provider

Add URI
$uri = new-object System.Uri(https://sunshine.vinit.com)
$token.ProviderRealms.Add($uri, "urn:sharepoint:sunshine")
$token.Update()

You are done now, how to verify

On Claims enabled site, create a new document library

Break the permission and add Microsoft as the claim.

Login to site with the rakeshsa, we should be able to see document library, login with Adam and the document library will be security trimmed.

To verify if you have got the correct claim, here is the wsp package which can you help you.

Steps remains same on how to deploy the WSP package.

In short, deploy the package, activate it, use the webpart on newly created page( just to avoid messing up with default.aspx)

And then you should be able to see the claims, attached below is the WSP package.

Output should like something like this

FAST ESP - LOGTRANSFORMER fails with "process logtransformer ports are already in use"

2013-04-15T09:02:04Z

Issue : LOGTRANSFORMER fails with "process logtransformer ports are already in use"

Assessment/Resolution:

Looking in to LOGTRANSFORMER.log file
**************************************************************
java.io.IOException: There is not enough space on the disk
[2013-03-03 16:25:15,066] ERROR org.quartz.core.ErrorLogger: An error occured while marking executed job complete. job= 'lql.periodLqlJob' (FastLogTransformer_Worker-0)
org.quartz.JobPersistenceException: Couldn't update job data: ERROR: could not extend relation 1663/10820/52439: No space left on device [See nested exception: org.postgresql.util.PSQLException: ERROR: could not extend relation 1663/10820/52439: No space left on device]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggeredJobComplete(JobStoreSupport.java:1933)
at org.quartz.impl.jdbcjobstore.JobStoreTX.triggeredJobComplete(JobStoreTX.java:1279)
at org.quartz.core.QuartzScheduler.notifyJobStoreJobComplete(QuartzScheduler.java:1489)
at org.quartz.core.JobRunShell.completeTriggerRetryLoop(JobRunShell.java:384)
at org.quartz.core.JobRunShell.run(JobRunShell.java:268)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
* Nested Exception (Underlying Cause) ---------------
org.postgresql.util.PSQLException: ERROR: could not extend relation 1663/10820/52439: No space left on device

[2013-03-03 17:15:33,794] ERROR com.fastsearch.esp.logtransformer.harvest.download.DownLoader: Failure during logharvesting (FastLogTransformer_Worker-0)
com.fastsearch.esp.logtransformer.harvest.download.DownloadException: Unable to obtain list of node controllers Unable to obtain list of active modules with name NodeControl from configserver XmlRpc[interface com.fastsearch.esp.logtransformer.harvest.download.qrserver.IConfigServer/com.fastsearch.esp.logtransformer.harvest.download.qrserver.ConfigServerMapping -> http://fast.vinit.com:16005/RPC2]
at com.fastsearch.esp.logtransformer.harvest.download.qrserver.FdsBackendHelper.getAllNodeControllers(FdsBackendHelper.java:76)
at com.fastsearch.esp.logtransformer.harvest.download.qrserver.FdsBackendHelper.getNodeControllersForQrservers(FdsBackendHelper.java:168)
at com.fastsearch.esp.logtransformer.harvest.download.qrserver.FdsBackendHelper.getAllQrserverHostAndNodeControllers(FdsBackendHelper.java:126)
at com.fastsearch.esp.logtransformer.harvest.download.DownLoader.runBatch(DownLoader.java:95)
at com.fastsearch.esp.logtransformer.scheduler.HarvestJob.execute(HarvestJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: com.fastsearch.esp.logtransformer.harvest.download.DownloadException: Unable to obtain list of active modules with name NodeControl from configserver XmlRpc[interface com.fastsearch.esp.logtransformer.harvest.download.qrserver.IConfigServer/com.fastsearch.esp.logtransformer.harvest.download.qrserver.ConfigServerMapping -> http://fast.vinit.com:16005/RPC2]

Resolution:

Stop the LOGTRANSFORMER via NCTRL and made sure all the java.exe and javaw.exe files are not running for the FASTADMIN user
Then NCTRL STOP LOGTRANSFORMER, killed all java.exe and javaw.exe running by the fastadmin

Start all the services with NCTRL start
Then started the LogTransformer with nctrl; It should start successfully and the logs, scraps should get generated as well.

How to Change the Primary address for Office 365 Notification.

2013-04-15T08:32:00Z

Issue Definition: On the o14 MOP portal, while trying to create a new user as an administrator, there is
an option to enter alternate email address. When we try to add a non *.onmicrosoft.com email account , which is registered as a vanity domain. This
email address is considered as Office 365 email address and the process does not go through.

Assessment:

When you setup and integrate your on-premise domain with online, the address space gets registered. Hence any email address with
this alternate domain address space is considered O365 email address. This is the correct behavior, if we had an exchange online mailbox setup. However,
since the domain purpose of this vanity domain is just SharePoint, you should be able to use your on-premise address as alternate email address. This is a by
design behavior. However, the workaround available to meet this requirement is
:

We will need to the use the Windows Azure powershell
for the same.

1. Login to windows azure powershell

2. Get the UserPrincipalName for the account for which
he wants to change alternate email address.

3. Run on the command : Set-MsolUser
-UserPrincipalName user@yourdomain.onmicrosoft.com
-AlternateEmailAddresses user2@yourvanitydomain.onmicrosoft.com

Alternateemailaddresses can be your vanity domain email address also.

You can download and install the windows azure PowerShell from here:

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

Name columns missing information on reports library after migration from SharePoint 2007 to SharePoint 2010

2012-04-15T01:41:00Z

Issue

If we are upgrading from from MOSS 2007 to SP 2010 and you have lot of reports library in 2007. After migration you might see File names are missing in the Current reports view of all our Reports Libraries (/ReportsLibrary/Forms/current.aspx) in SP 2010.

In the library settings for the Reports Library, the Name column is associated with Name (link to report with edit menu). The same association used to works fine in MOSS 2007, but not in SP 2010.

Cause:

If we compare the 2007 reports library and 2010 reports library we see that for reports content type in 2007 we used “ReportLinkFilename” for the Name field which is not present in SharePoint 2010.

As this information or reference is not present in 2010 we will observer this behaviour on all migrated reports library content.

Fix:

As of now we don`t have way to get “ReportLinkFilename” reference in SharePoint 2010. However what we can do it instead of using “ReportLinkFilename” we can use “LinkFilename” for the Name column and update all the current reports view.

Here is a sample powershell script which will scan all your webs in site collection and look for reports library and update this information.

I would recommend to take a working back of site collection before using the script.

If you want to confirm that behaviour on one of reports library..you can try these steps to check

Edit the “Current reports “ view and uncheck the Name column( link to report with edit menu) and check the Column Name(linked to document with edit menu) and check the behaviour.. if this is something what you are looking for.. you can use the script below.

$site= Get-SPsite http://moss2010-1

foreach ( $web in $site.allwebs )
{
    $lists = @{}
    $count = 0
    foreach($list in $web.lists)
    {
        If ($list.TemplateFeatureId -eq "2510d73f-7109-4ccc-8a1c-314894deeb3a") #this is report library GUID
        {
            $lists.add($count++, $list.ID)            }
    }

    foreach ( $value in $lists.Values )
    {
        $list = $web.lists.GetList( $value, $false )
        $view = $list.Views['Current reports'] # getting the current view in variable
        write-host $list.Title
        try
        {
            $view.ViewFields.delete('ReportLinkFilename')      # we are using try block as we are not sure about the OOB lists if they have this link
        }
        catch
        {
            Write-host "Field not found" # if it does not have it will fail and print this error message
            continue
        }
        write-host "Executing updates..." # this is where when we come out of try loop and execute the remaining stuff
        $view.ViewFields.Add('LinkFilename')
        $view.ViewFields.MoveFieldTo('LinkFilename',1)
        $view.Update()
    }

}

Save the all this is information in a notepad and save as reportviewfix.ps1 and run it from SharePoint PowerShell

How to get back the SharePoint WebServices applicaion in IIS if deleted, SharePoint 2010

2011-05-13T22:28:01Z

Technorati Tags: Sharepoint 2010,Sharepoint WebService Application,web service

In SharePoint 2010, if you have deleted or some how removed the Sharepoint Webservice site unknowingly.

its hard to get it back, in spite of running psconfig we would not able to get the SharePoint Webservice back.

It is the same SharePoint webservice application which we see in Sharepoint 2007

Here is is powershell script which can help us to get all the running service back under IIS with their GUID.

$webservice = [System.Type]::GetType("Microsoft.SharePoint.Administration.SPIisWebServiceSettings, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c")

$Instance = $webservice::Default

$Method = $werbservice.GetMethod("ProvisionLocal", "Instance, NonPublic", $null, @(), $null)

$Method.Invoke($Instance, $null)

$Method = $webservice.GetMethod("Provision", "Instance, Public", $null, @(), $null)

$Method.Invoke($Instance, $null)

Once we are done with about script we should have “SharePoint Web Service” under IIS with only few information.

now we need to get all the respective VD in IIS.

Get-SPServiceApplication | ForEach-Object {$_.Provision()}

Above steps should helps us to get the missing VD and Sharepoint Webservice back in IIS.

Invalid search result URLs prevent items from being opened in IIS7 based servers

2011-03-12T07:24:01Z

When we have discussion list to store many C++ related topics. Many list items use "C++" as part of their title.
After performing a search of the "C++" keyword in the search centre the results' links for items with C++ in their title. We a user clicks on the link he get the "404 error" because the target page cannot be opened.

Example of search result URL that fails
http://xxx/Lists/hello/this%20du%20C%20et%20du%20C++%20by%20test

Why this happens :

The URL from the search result page does not encode the "++".

IIS 7 by default blocks any url which has special character like “++” in them.

How to fix it:

Applications that require the use of the “+” character in the URL path can disable this validation by setting the allowDoubleEscaping attribute in the system.webServer/security/requestFiltering configuration section in the application’s web.config. However, this may make your application more vulnerable to malicious URLs:

<system.webServer>

</security>

</system.webServer>

Technorati Tags: "++" special character,IIS7,allowdoubleescaping,"404 error"