This tutorial is really really cool. It talks about the various options we have to handle large lists in SharePoint 2010.
http://office.microsoft.com/en-us/sharepoint-server-help/sharepoint-lists-v-techniques-for-managing-large-lists-RZ101874361.aspx
In summary, we can make use of folders, views, column indexing and Key Filters (metadata based filters) to manipulate large lists.
Additionally we can also use Excel, Access or SharePoint WorkSpace to take the large lists offline to manipulate it.
Showing posts with label Issue. Show all posts
Showing posts with label Issue. Show all posts
Sunday, June 9, 2013
Wednesday, January 23, 2013
Error when trying to create a new Data Source (Data Connection) in PerformancePoint
If you get an error while trying to select a data source is Dashboard Designer, that may be because you have not associate the PerformancePoint Service App to the Web Application which hosts your site collection.
Thursday, January 10, 2013
Internet Explorer 10 doesn't like SharePoint 2010
Well that's by default. You won't be able to do a few things on your IE10 when you access a SharePoint 2010 site.
To make it "like" SharePoint, you can add the SharePoint 2010 sites in the "Compatibility View Settings" of you IE10.
Steps:-
1. On your IE, go to Tools -> Compatibility Settings
2. Key in the "SharePoint site url" (if its not there) in the "Add this website" box
3. Click Add, then Close.
4. Refresh you page or restart IE.
To make it "like" SharePoint, you can add the SharePoint 2010 sites in the "Compatibility View Settings" of you IE10.
Steps:-
1. On your IE, go to Tools -> Compatibility Settings
2. Key in the "SharePoint site url" (if its not there) in the "Add this website" box
3. Click Add, then Close.
4. Refresh you page or restart IE.
Thursday, August 9, 2012
Error while running PSCONFIG in SharePoint 2010
When we are applying SP1 or any other patches, we need to run psconfig command to update the SharePoint databases. Installing the patches only installs the binaries on the SharePoint server. After installing the patch, we need to synch up with the SharePoint database. That is where we need PSCONFIG.
However, due to some reason, you may encounter some issue. Log file may not be that informative. One possible cause of upgrade (when you run psconfig, it upgrades the database with some details) error is that features didn't get installed properly or got messed up when you apply a patch.
If you get error running psconfig, try the below. It helped for us. By the way, make sure you are running this command using your farm account.
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
However, due to some reason, you may encounter some issue. Log file may not be that informative. One possible cause of upgrade (when you run psconfig, it upgrades the database with some details) error is that features didn't get installed properly or got messed up when you apply a patch.
If you get error running psconfig, try the below. It helped for us. By the way, make sure you are running this command using your farm account.
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Saturday, July 28, 2012
Understanding SharePoint 2010 Permissioning
Every now and then, I get help request on permission related issues. You may have encountered or heard about some of the issues listed below:-
i) “I have already granted permission to ABC to this folder but he says he dont see the files in it”.
ii) “I have already granted permission to ABC to this folder but he gets access denied”. Huh ??
worst still ..
iii) “Her document is lost/missing !!! Please retrieve it for me” or “This SharePoint link is broken”
The first 2 are quite straight forward but the 3rd one is a bit tricky. It may mean the file/document was actually or accidentally deleted. It may also mean, as in some cases, incorrect permission assigned or existing permission purposely or accidentally removed.
So what's up ?? First, let's look at the basics.
# 1 : There are four areas where we can set permission
# 2 : Two types of permission settings
# 3: Common permission levels (not all are shown here)
1. Full control - Highest permission level
2. Contributor
3. Read - Lowest permission level
So far so good ?? Let's take some quiz.
Quick quiz # 1:
Question: What happens is I assign different permission levels to the same person different at the same area?
Answer: If you assign different permission levels to the same person in the same area, the highest permission will take effect.
Example: Let’s say, I have a site called Fun and I give ABC contributor access (direct permission). ABC now has contributor access. Then, if I add ABC to the site owner group (which has full control), ABC will have full control on this site.
Quick quiz # 2:
Question: What happens if I assign the same person different permissions in the lower area as compared to a higher area (unique permissions configured)?
Answer: If you assign a different permission level to the same person in the "lower area", the lower area setting will take effect.
Example: Let’s say, I created a subsite “More Fun” under the site “Fun”. I make it a subsite with unique permissions and I don’t add (in other words, I removed) ABC from the subsite owner’s group and don’t give him any kind of access to this subsite. Effectively ABC will not even know the subsite exists. He won’t see it. So it doesn’t matter what is the setting on the higher level area, the lower level area setting will take effect.
Note: This also means that if you create a subsite (or document library, folder or file) with unique permission and accidentally remove your own access from it, you won’t be able to access it or see it.
Okay now, let’s get back to the issues.
Issue # 1: “I have already granted permission to Alan to this folder but he says he don’t see the files in it”.
Explanation: ABC was given access to the folder. That means he will see all the files in it that has inherit permission defined. He will not see any documents that have unique permission configured. So if you have any document with unique permission, you need to specifically grant ABC access to them as well. Quite troublesome ha?? I couldn’t agree more with you on this. But this is how permission works (and should work) in SharePoint.
For example, below is a document library which has 2 documents in it.
I have set the first document (titled SharePoint Replication) to have unique permission and didn’t give ABC permission to it. So when ABC come to this document library, he will see it as below,
Issue # 2: “I have already granted permission to ABC to this folder but he gets access denied”. Huh ??
Explanation: If you grant access to ABC to a document library, he can only see and access all the folders and documents that reside under that document library that has inherit permissions setting. If ABC is trying to click a link that points to any folder or document under a folder that has unique permission (and he was not given permission to it) , he will get the Access Denied message. Makes sense? Different symptom but same reason as Issue # 1.
By now, you would have gathered that Issue # 3 has been explained above. It’s just different symptom for the same reason.
Next logical question would be : - What would be the best practice to avoid all these confusions and issues ?
Well the answer is quite straight forward:- Configure permissions at site and document library only unless there is a strong reason for configuring unique permission at the lower levels (folders, sub folders and documents). Unique permissions give us the flexibility. But this flexibility has its downside. It can be confusing at times.
Do you know you can create additional document libraries and give them unique permissions? You don’t have to live with the pre created Shared Documents!!
If you still have very strong reasons to apply unique permission at folder, subfolder and document levels, by all means, go ahead. But be sure to click on the Show me uniquely secured items of this list to identify all the unique folders and documents and assign permissions accordingly.
In our example, you will see the below screen. So you need to click on the “manage permissions” link and assign permissions accordingly.
Happy reading and have a productive day ahead !!
i) “I have already granted permission to ABC to this folder but he says he dont see the files in it”.
ii) “I have already granted permission to ABC to this folder but he gets access denied”. Huh ??
worst still ..
iii) “Her document is lost/missing !!! Please retrieve it for me” or “This SharePoint link is broken”
The first 2 are quite straight forward but the 3rd one is a bit tricky. It may mean the file/document was actually or accidentally deleted. It may also mean, as in some cases, incorrect permission assigned or existing permission purposely or accidentally removed.
So what's up ?? First, let's look at the basics.
# 1 : There are four areas where we can set permission
# 2 : Two types of permission settings
# 3: Common permission levels (not all are shown here)
1. Full control - Highest permission level
2. Contributor
3. Read - Lowest permission level
So far so good ?? Let's take some quiz.
Quick quiz # 1:
Question: What happens is I assign different permission levels to the same person different at the same area?
Answer: If you assign different permission levels to the same person in the same area, the highest permission will take effect.
Example: Let’s say, I have a site called Fun and I give ABC contributor access (direct permission). ABC now has contributor access. Then, if I add ABC to the site owner group (which has full control), ABC will have full control on this site.
Quick quiz # 2:
Question: What happens if I assign the same person different permissions in the lower area as compared to a higher area (unique permissions configured)?
Answer: If you assign a different permission level to the same person in the "lower area", the lower area setting will take effect.
Example: Let’s say, I created a subsite “More Fun” under the site “Fun”. I make it a subsite with unique permissions and I don’t add (in other words, I removed) ABC from the subsite owner’s group and don’t give him any kind of access to this subsite. Effectively ABC will not even know the subsite exists. He won’t see it. So it doesn’t matter what is the setting on the higher level area, the lower level area setting will take effect.
Note: This also means that if you create a subsite (or document library, folder or file) with unique permission and accidentally remove your own access from it, you won’t be able to access it or see it.
Okay now, let’s get back to the issues.
Issue # 1: “I have already granted permission to Alan to this folder but he says he don’t see the files in it”.
Explanation: ABC was given access to the folder. That means he will see all the files in it that has inherit permission defined. He will not see any documents that have unique permission configured. So if you have any document with unique permission, you need to specifically grant ABC access to them as well. Quite troublesome ha?? I couldn’t agree more with you on this. But this is how permission works (and should work) in SharePoint.
For example, below is a document library which has 2 documents in it.
I have set the first document (titled SharePoint Replication) to have unique permission and didn’t give ABC permission to it. So when ABC come to this document library, he will see it as below,
Issue # 2: “I have already granted permission to ABC to this folder but he gets access denied”. Huh ??
Explanation: If you grant access to ABC to a document library, he can only see and access all the folders and documents that reside under that document library that has inherit permissions setting. If ABC is trying to click a link that points to any folder or document under a folder that has unique permission (and he was not given permission to it) , he will get the Access Denied message. Makes sense? Different symptom but same reason as Issue # 1.
By now, you would have gathered that Issue # 3 has been explained above. It’s just different symptom for the same reason.
Next logical question would be : - What would be the best practice to avoid all these confusions and issues ?
Well the answer is quite straight forward:- Configure permissions at site and document library only unless there is a strong reason for configuring unique permission at the lower levels (folders, sub folders and documents). Unique permissions give us the flexibility. But this flexibility has its downside. It can be confusing at times.
Do you know you can create additional document libraries and give them unique permissions? You don’t have to live with the pre created Shared Documents!!
If you still have very strong reasons to apply unique permission at folder, subfolder and document levels, by all means, go ahead. But be sure to click on the Show me uniquely secured items of this list to identify all the unique folders and documents and assign permissions accordingly.
In our example, you will see the below screen. So you need to click on the “manage permissions” link and assign permissions accordingly.
Happy reading and have a productive day ahead !!
Friday, November 25, 2011
SharePoint 2010 Survey Issue
My user complained about an issue yesterday. Users not able to submit responses to her survey.
Below is the error.
When I checked the survey question's setting, I found the “Enforce unique values:” was set to Yes. I changed to No and issue was resolved.
Below is the error.
When I checked the survey question's setting, I found the “Enforce unique values:” was set to Yes. I changed to No and issue was resolved.
Thursday, November 10, 2011
Error while visual upgrade
After mounting MySites DB, we performed the visual upgrade using the commands below:
$webapp = Get-SPWebApplication <web apps url>
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }
but encountered the below error
Exception calling "VisualUpgradeWebs" with "0" argument(s): "Access is denied.
(Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
At line:2 char:22
+ {$s.VisualUpgradeWebs <<<< () }
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
This is because at least one or more of the site collections are in read-only.
To find out which ones, run the commands below
$webapp = Get-SPWebApplication <web apps url>
foreach ($s in $webapp.sites)
{$s | Get-SPSite | Where {$_.readonly -eq "true" }} ; readonly is the column name !!
We then need to unlock those sites
Set-SPSite -Identity <site collection url> -LockState unlock
$webapp = Get-SPWebApplication <web apps url>
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }
but encountered the below error
Exception calling "VisualUpgradeWebs" with "0" argument(s): "Access is denied.
(Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
At line:2 char:22
+ {$s.VisualUpgradeWebs <<<< () }
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
This is because at least one or more of the site collections are in read-only.
To find out which ones, run the commands below
$webapp = Get-SPWebApplication <web apps url>
foreach ($s in $webapp.sites)
{$s | Get-SPSite | Where {$_.readonly -eq "true" }} ; readonly is the column name !!
We then need to unlock those sites
Set-SPSite -Identity <site collection url> -LockState unlock
Monday, April 18, 2011
Exception from HRESULT: 0x80040D1B error was displayed when trying to access the search settings from SSP
If you get this error -->
Exception from HRESULT: 0x80040D1B
when you try to access the search settings from SSP, check whether you have any duplicate entries in
\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{site GUID}\Gather\Portal_Content\Extensions\ExtensionList.
If you do, remove it, stop and start the MOSS Search service again.
I accidentally created duplicate entries in the list above when deployed PDF iFilter and got the error above.
Below is what you will see in your event viewer,
--------------------------------
The gatherer object cannot be initialized.
Context: Application '<>_SSP_Admin', Catalog 'Portal_Content'
Details:
A duplicate extension entry exists in the registry. The duplicate extension should be deleted, but all other extensions are unaffected. (0x80040d0b)
-------------------------------------------
Exception from HRESULT: 0x80040D1B
when you try to access the search settings from SSP, check whether you have any duplicate entries in
\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{site GUID}\Gather\Portal_Content\Extensions\ExtensionList.
If you do, remove it, stop and start the MOSS Search service again.
I accidentally created duplicate entries in the list above when deployed PDF iFilter and got the error above.
Below is what you will see in your event viewer,
--------------------------------
The gatherer object cannot be initialized.
Context: Application '<>_SSP_Admin', Catalog 'Portal_Content'
Details:
A duplicate extension entry exists in the registry. The duplicate extension should be deleted, but all other extensions are unaffected. (0x80040d0b)
-------------------------------------------
Friday, April 1, 2011
No users in SharePoint 2010 after successfull profile import
Well, to start with, to say it is successful is misleading but that is the scenario we faced.
In our brand new SharePoint 2010 farm, we configured profile synch from AD. Everything looks cool but no users was found. Not sure where they are going but the data is simply not in the user profile store. Luckily google and technet forum helped :-). No error messages and no clue until I came across a technet post which I believe was written for SharePoint 2007 but I gave it a try.
But first, try to search for the users. SharePoint 2010 does not list the users. You need to search for them. Just type any letter and search. If no values returned, then you can try the below steps.
This what I did
1. From the Admin Tools --> Servicess Stopped the SharePoint Timer service
2. From the Central Admin --> Services on Server, stopped both the User Profile Service and User Profile Synchronization Service
3. Navigated to the C:\ProgramData\Microsoft\SharePoint\Config\<GUID> folder
4. Removed all the other xml files
5. Edited the cache.ini file to replace the value with 1 and saved the file
6. Started back the SharePoint Timer service, waited till all the xml files were recreated and the number on cache.ini file return to its original value
7. Started back the User Profile Service and User Profile Synchronization Service
8. Then under CA --> Application Management --> Manage Service Application --> User Profile --> Start Profile Synchronization
9. Waited and it worked :-)
10. The users will not be listed. You need to search for them.
Ref: Technet forum post
In our brand new SharePoint 2010 farm, we configured profile synch from AD. Everything looks cool but no users was found. Not sure where they are going but the data is simply not in the user profile store. Luckily google and technet forum helped :-). No error messages and no clue until I came across a technet post which I believe was written for SharePoint 2007 but I gave it a try.
But first, try to search for the users. SharePoint 2010 does not list the users. You need to search for them. Just type any letter and search. If no values returned, then you can try the below steps.
This what I did
1. From the Admin Tools --> Servicess Stopped the SharePoint Timer service
2. From the Central Admin --> Services on Server, stopped both the User Profile Service and User Profile Synchronization Service
3. Navigated to the C:\ProgramData\Microsoft\SharePoint\Config\<GUID> folder
4. Removed all the other xml files
5. Edited the cache.ini file to replace the value with 1 and saved the file
6. Started back the SharePoint Timer service, waited till all the xml files were recreated and the number on cache.ini file return to its original value
7. Started back the User Profile Service and User Profile Synchronization Service
8. Then under CA --> Application Management --> Manage Service Application --> User Profile --> Start Profile Synchronization
9. Waited and it worked :-)
10. The users will not be listed. You need to search for them.
Ref: Technet forum post
Wednesday, March 30, 2011
Setting up Adobe PDF iFilter 9 for SharePoint 2007
I am posting this for my own future reference :-p and other newbies like me :-).
I downloaded the Adobe Pdf iFilter from here. And then followed the instructions.
But I got error (below)
Crawled (The filtering process could not process this item.This might be because you do not have the latest file filter for this type of item. Install the corresponding filter and retry your crawl. )
So when I googled around, I was pointed to many forums and blogs on how to overcome the error. I find this article very informative especially when it mentioned about checking the second registry key.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf]
But after I made the changes, I was still getting the error. After troubleshooting for a while. I found out that I made a silly mistake !! I forgot about the curly brackets. I changed the registry values for the two keys above to {E8978DA6-047F-4E3D-9C78-CDBE46041603} and it works perfectly now.
I downloaded the Adobe Pdf iFilter from here. And then followed the instructions.
But I got error (below)
Crawled (The filtering process could not process this item.This might be because you do not have the latest file filter for this type of item. Install the corresponding filter and retry your crawl. )
So when I googled around, I was pointed to many forums and blogs on how to overcome the error. I find this article very informative especially when it mentioned about checking the second registry key.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf]
But after I made the changes, I was still getting the error. After troubleshooting for a while. I found out that I made a silly mistake !! I forgot about the curly brackets. I changed the registry values for the two keys above to {E8978DA6-047F-4E3D-9C78-CDBE46041603} and it works perfectly now.
Friday, July 9, 2010
SharePoint 2007 Search Issues Troubleshooting
Are you having any search related issues? Try the troubleshooting steps below and see if it helps you to identify the cause.
1. Check if search services are running.
If not --> restart it by going to Central Admin -> Operations -> Services on Server
2. Check if content db is assigned to a index server.
If not --> Application Management > Content Databases > Select the content database
3. If search is running and content db is assigned correctly but you can see any results, then check if indexing/crawling is still running. if yes, you have to wait till it completed before doing your search again.
4. If still cannot search, then try running FULL index again. You may need to delete existing index files and run full index again either by
i) using UI - SSP Search config
ii) using stsadm commands
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm –o spsearch –action fullcrawlstop
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm –o spsearch –action fullcrawlstart
5. You should also check if the file file ext is included in files to be indexed (in SSP Search config). Note that not all files are indexable or included in indexing.
6. Additionally, check the search visibility under Site Actions > Site Settings > Search visibility to check whether that particular site and its contents are included in crawling
7. It can be a crawler access issue. If yes, Reset the rights of the crawler account to the content database thru SQL Enterprise Mgr/Mmgt Studio and/or check the check web application policy whereby the crawl account must have "Full Read" access.
1. Check if search services are running.
If not --> restart it by going to Central Admin -> Operations -> Services on Server
2. Check if content db is assigned to a index server.
If not --> Application Management > Content Databases > Select the content database
3. If search is running and content db is assigned correctly but you can see any results, then check if indexing/crawling is still running. if yes, you have to wait till it completed before doing your search again.
4. If still cannot search, then try running FULL index again. You may need to delete existing index files and run full index again either by
i) using UI - SSP Search config
ii) using stsadm commands
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm –o spsearch –action fullcrawlstop
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm –o spsearch –action fullcrawlstart
5. You should also check if the file file ext is included in files to be indexed (in SSP Search config). Note that not all files are indexable or included in indexing.
6. Additionally, check the search visibility under Site Actions > Site Settings > Search visibility to check whether that particular site and its contents are included in crawling
7. It can be a crawler access issue. If yes, Reset the rights of the crawler account to the content database thru SQL Enterprise Mgr/Mmgt Studio and/or check the check web application policy whereby the crawl account must have "Full Read" access.
Subscribe to:
Posts (Atom)