Interview Questions administrator

Best SharePoint administrator Interview Questions and Answers with topic wise:


Recycle Bin | MMS | ManagedVsCrawledProperties |
Showing posts with label SharePoint 2010. Show all posts
Showing posts with label SharePoint 2010. Show all posts

Saturday, September 5, 2015

SharePoint list view web address is not displaying the absolute URL

Issue: SharePoint list web address is not displaying the absolute URL:

Description: Recently, we migrated SharePoint 2010 applications to 2013. While doing content validation in SP2013 to check whether all the metadata is migrated properly, we found an issue that most of the list web address is not showing the complete view URL. It is just showing web application URL.

Solution: You will face such type of issues if no view set as by default to the list. Check the list views and set any of the view by default and check, it will show the complete view URL.

Regards,
Sasi Kumar Reddy
sharepointquicksolutions.blogspot.in





Friday, June 19, 2015

Solve edit page not working issue


Edit the sharepoint page:

Append the below one to the url if you are unable to edit the sharepoint pages and then now try to click on edit page option. problem solved.

?toolpaneview=2

Example:

URL: http://abc.com/sitepages/Home.aspx?toolpaneview=2

Please let me know for any issues.

Regards,
Sasi Kumar Reddy


Saturday, May 16, 2015

ExportVsImport: SharePoint interview questions with answers

Export and Import limitations:
Major drawback: The export/import does not preserve workflows instances, associations, history and tasks. Every workflow association must be recreated and there is no way to restore the running instances from original site.
If publishing feature is enabled in source site and same should be applicable for targeted site also.

How can we do the export/import of site, list and libraries along with versioning?
Use the [-IncludeVersions] option to instruct PowerShell to include version information of items in the export file.
Example:
Export-SPWeb -Identity http://sharepoint/site -Path "E:\exports\MySite.cmp" -IncludeVersions ALL

Export the sites, lists and libraries?
To export/import a specific list or library, provide the full URL to the list or library, otherwise PowerShell will import/export the site if the URL is to the main site location.
Include the [-IncludeVersions] option to instruct PowerShell to include version information of items in the export file.
Include the [-NoFileCompression] option to turn off file compression; this makes for a faster export but larger files on disk.
Include the -haltonfatalerror or -haltonwarning options to stop the import\export process in the event of an error or warning.
In SharePoint 2007, administrators could export and import sites only, using STSADM

Export and Import use in sharepoint?
Backup-SPSite is generally used when you want to replicate the entire site collection (including all subsites) to an existing web application.
Export-SPWeb is generally used when you want to replicate just a single subsite to an existing site collection.
From SP2010 onwards, you can export a site, lists and library through either central adminitrator or poweshell but we can only way to do import is through powershell.

Limitations:
Workflows are not included when we export/import contents of sites, libraries, or lists means Export-SPWeb does not export the running workflows.
Export-SPWeb:
Paramaters:  NoFileCompression,

Note: The NoFileCompression parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter will result in a backup folder being created instead of a compressed file. If you use the NoFileCompression parameter in the Export-SPWeb command, you must also use it when you import the content by using the Import-SPWeb command.
includeusersecurity : Do not forget to use includeusersecurity parameter in both export and import if you wish to preserve information relative to permissions and other properties such as documents authors.

Friday, April 3, 2015

Restore-SPSite problems in sharepoint

I have a requirement change the site collection URL (path based). Best recommended way to change the site collection URL in sharepoint 2010 is backup and restore. I followed the same, first I took the backup and then trying to restore the same but it giving exception.

Observation: Restoration fails if any of the URL characters exceed the limit of 260 characters. So, please check the URL characters before proceeds with backup and restore.

Below script will give the accurate results of the URL characters:

Step1:  connect to the DB server and then select the content DB

Step2: Run the script

SELECT
   ([DirName]+ N'/'+ [LeafName]) AS [FullRelativePath],
   LEN([DirName]+ N'/'+ [LeafName]) AS [Length]
FROM
   [dbo].[AllDocs]
ORDER BY
   [Length] DESC


Note: If any of the URL characters exceeds the 260 characters, please make it below and then try to do the back up and restore.

-Thanks,
Sasi kumar Reddy

Thursday, April 2, 2015

Solving access denied login for site collection administrators

Recently we migrated the applications from sharepoint 2007 to 2010. Once it’s done, we tried to browse the application but it is giving access denied error. Initially I thought it was due to access issue but I am the primary site collection administrator to that application.

Workaround:  Check status of the content DB whether it is in read-only or not locked stage. If it is in read-only, change it to “Not locked” and then save it.

Now try to browse the application and this time you can able to browse.

Regards,
Sasi Kumar Reddy




Tuesday, February 24, 2015

Crawled Vs Managed properties: Search


  1. How to create crawled and managed properties?
  2. Are managed properties works at web application, site collection and site level?
  3. How to map crawled properties with managed properties?
  4. When full crawl is required?
  5. Automatically creation of managed properties not supports what are all data types?
  6. New features introduced in SP2013?
  7. Is full crawl required for each map between crawled and managed property?
  8. Difference between creating crawled property at SSA level and site collection level?
  9. I have created one managed property of type “Text”. As per the current requirement I want to change it “Choice”. Is it possible?
  10. I have created one site column of type “Single line of text”. As per the new feature introduced from the sharepoint 2013, automatically managed property will create for each site column creation. So far everything is clear. Now my question is will change the data type of managed property as changed at the site column level?
  11. I have two different lists in site and there is one common field in both the list. Now, I want to map that field to the managed property?
  12. Limitations on automatically creation of managed property for the site columns?

New features introduced on managed and crawled properties in SP2013?

From SP2013 onwards, only site columns that contain values will automatically become managed properties when they are crawled and full crawl is required.
In sp2010, whenever a new item was discovered during a crawl, users would have to manually create a new managed property, and map this to the corresponding crawled property.

What is the use of creating managed properties and why mapping required to the crawled properties?
Crawled properties are useless(means can’t be searchable/not us in Refinable)  without mapping it to the Managed properties and next point why mapping required is we can assign behaving similar ways of crawled properties to one managed properties.
To include the content and metadata of crawled properties in the search index, you map crawled properties to managed properties.

Example: Modified By, Created By and Author crawled properties behaves in similar way. Rather performing individual assign all 3 to one managed property called “Author” [see the below image]



Is full crawl required for each map between crawled and managed property?
Yes, Full crawl should be required.

When full crawl is required?
When you create a new managed property, or when you change certain settings on existing managed properties, a full crawl must complete before the managed property and its value is included in the search index.
When you have changed a managed property, or when you have changed the mapping of crawled and managed properties, the site must be re-crawled before your changes will be reflected in the search index. Because your changes are made in the search schema, and not to the actual site, the crawler will not automatically re-index the site.

Are managed properties works at web application, site collection and site level?
At site collection level.

Automatically creation of managed properties not supports what are all data types?
Managed properties are created automatically for site columns that contain values during crawl and it’s mapped to crawled properties (Note: All spaces are removed). But automatic creations of managed properties are not supported for the following site column types:

  • Lookup
  • Calculated
  • Task outcome
  • Summary Links data
  • Rich media data for publishing
Difference between creating managed properties at site collection level and SSA level?
Big differences between managed properties created in the site collection versus the SSA are that when you create new managed properties in the site collection they have the below limitations you should be aware of:

  • They can only be text and Yes/No
  • They cannot be sortable
  • They cannot be refinable
  • They cannot allow multiple values


I have created one site column of type “Single line of text”. As per the new feature introduced from the sharepoint 2013, automatically managed property will create for each site column creation. So far everything is clear. Now my question is will change the data type of managed property as changed at the site column level?
I have created a site column name:
Column name: MyDateTimeCol
Managed property Name: MyDateTimeColOWSDATE
And changed the date time column type to “Choice”
Column name: MyDateTimeCol
Managed property name: MyDateTimeColOWSCHCS
Note: What I observed is managed property will create for each field type change.
Auto-generated managed property is by default non-refinable.

Limitations on automatically creation of managed property for the site columns?
Limitation#1:
Managed properties are automatically created for the site columns but drawback here is they generated is always of “text” data type only.

Means by which data type if we create the site column, the managed property should create with of same type. But by default sharepoint generate the “text” data type.
Example: I have created a site column of data type “Choice”. Managed property generated for this choice column is of “Text” type.

We cannot change the types of managed properties once generated.
Example: I have created a site column of data type “Choice”. Managed property generated for this choice column is of “Text” type and then tries to change the type. Not possible.
I have created a managed property of type “Text” at SSA level and try to change the type. Not possible.

Limitation#2:
We cannot set the refinable.

I have created one managed property of type “Text”. As per the current requirement I want to change it “Choice”. Is it possible to make changes for the existing one?
Am sure it is not possible with CA. Will confirm on through PowerShell script.


How to change the type of managed property once generated/created?

Through browser it is not possible to change the type of the managed properties. Only way is through PowerShell script.


What are all the ways to create crawled properties?
Crawled properties are added automatically by the crawl components
Cannot be added via CA or search admin pages
Can be added via PowerShell script


Friday, January 23, 2015

sharepoint interview questions with answers: ListVsLibrary

<<Previous post>>

Move documents between document libraries along with versions?
You can only copy the documents to others along with major version only.

Exception: “The data source control failed to execute the update command
Got the above exception while trying to attach the file to the list item in MOSS2007
The reason for the exception is attaching file name exceeded the limit (max size limit for single file is 128 characters).

Exception: “The specified file or folder name is too long. The URL path for all files and folders must be 260 characters or less (and no more than 128 characters for any single file or folder name in the URL). Please type a shorter file or folder name”
By default, SharePoint limitation for Size of URL is 260 characters.
Microsoft recommended size limit for single file name is 128 characters and URL limit is 260 characters. 
I have uploaded one document to the document library and when I open it through browser the size of the URL is 258 characters(max limit 260) and later on I have changed the web application “http://India.com” tohttp://allindia.test.IND.com and now my the document size of the URL is 263 characters(means exceeded the limit).

As per my understanding: you can’t edit/download the document but we can view the document through browser.

Thursday, January 15, 2015

Copy/Move items from one list to another list in sharepoint

Scenario:
List AA fields: Name, Title, User Name, Religion, Qualification.
List BB fields: Name, Title, User Name, Qualification, Designation, Salary and Description
Common field names: Name, Title, user name, Qualification
Now, I want to copy the common field values from List AA to List BB.

Approach:
//Read the list item values by ID and add the common field values as new item into the another list
SPListItem spLstItemsAA = listNameAA.GetItemById(ItemID); //ItemID of List AA
SPListItem spLstItemBB = list.Items.Add();
foreach (SPListItem spLstItemAA in spLstItemsAA.ListItems)
{
       for (int i = 0; i < spLstItemAA.Fields.Count; i++)
       {
          if ((!spLstItemBB.Fields[i].Hidden) && (!spLstItemBB.Fields[i].ReadOnlyField) &&    
                                  !(customfields.Contains(item.Fields[i].Title)))
           {
               spLstItemBB [item.Fields[i].Title] = spLstItemAA [item.Fields[i].Title];
             }
        }
 }
 spLstItemBB ["Salary"] = "50k";
spLstItemBB ["Description"] = "sharepointquicksolutions.blogspot.in ";
spLstItemBB.Update();

Condition#1: !spLstItemBB.Fields[i].ReadOnlyField
Condition#2: !spLstItemBB.Fields[i].Hidden
The above 2 conditions are used for to skip the read only and hidden fields.

Note: By default, every sharepoint list and library will have the below fields.