Users cannot see the checked out files in the folder/ library

I Came across a Issue today wherein the user opened a ticket for the below issue

Issue : Users cannot see the checked out files in the folder/ library

Checked with the user for the url and browsed the site and yes was not able to see any files

Asked the user if he had checked in the files for the first time as it was nothing to do with the permissions of the user or any setting

He said he might have so asked him to check in the file once and then check out .
He did and there were all the files visible to the user


Resolution : Check in the files atleast once for the user to see the files in the folder / Library 

Sharepoint 2010 - Item Scheduling

Item Scheduling - Wow i liked this feature

I am not sure if everybody is aware of this new feature in SharePoint 2010 . 

* What is Item Scheduling ? 

Ans : Item scheduling is a feature which helps to publish a document/page for a specified period. This feature is available out-of-the-box for publishing sites for the Pages library. It can also be implemented in a Team Site for custom document libraries.

Prerequisites for Item scheduling 

* You need to Enable content approval on the library

* You need to enable Versioning on the Document Library both for Major and Minor versions. 

* And the Most Important thing you need to have the publishing feature enabled on the site . 

You have this feature enabled on the document library . now after selecting the document you get an option that says Item Scheduling . In which you can specify the Date and time when you want to display the document to the Users and also the End date when you want to stop displaying the document to the Users .

The document would be published as a Major version for the Users in the List view  

Understanding why we need Versioning and Content approval

 When you upload the document in the library ,The first thing that happens is it will be added as a minor version (0.1).

 Once the user wants to display the document in the library to all users, They sent a request for the document to be published. This will trigger a workflow for approval to the members of the SharePoint Approval group.
Till that time the document is marked as Pending. 

When a Approver approves the document The minor version will be changed to a major version (1.0) and the status will be marked as approved.

Now if Managing Item Scheduling is enabled

If The document Scheduling Start Date is not Immediate and current date and time has not reached the specified date and time. The status will be marked as Scheduled and the version number will remain as minor (0.1). The Document will not be Displayed to the users in the list

The timer job that Runs at the back on the server is Scheduled Approval which Looks for content that is scheduled for approval and moves it to the next stage in the process.it runs every 1 minute by default. 

It automatically switches the Status to Approved and sets version to major and the Document is displayed to the user.

If there is a specified Scheduling End Date then once the current date and time is greater, the status is marked as Scheduled and the version number is set back to highest minor release version of the previous major release.

Cannot delete a Corrupted lookup Column from the list

Issue : Just Today i came accross a issue in Which the User had a List with many columns and One of the column Which was a look up column was corrupted

used to give a error "Unknown Error"

We were not able to Delete or edit the column

After a lot of research we found a work around to delete the Column

Checked the Url and found the below

/_layouts/FldEditex.aspx?List=%7B37920121%2D19B2%2D4C77%2D92FF%2D8B3E07853114%7D&Field=Product%5Fx0020%5FDescription

Which is a wrong url it should be

/_layouts/FldEdit.aspx?List=%7B37920121%2D19B2%2D4C77%2D92FF%2D8B3E07853114%7D&Field=Product%5Fx0020%5FDescription

Just remove ex from FldEditex.aspx => FldEdit.aspx

And you will be able to get to the inside of the column where you can edit or Delete the column .

Cause - Unknown

Capacity management - List and library limits

Limit	Maximum value	Limit type	Notes
List row size	8,000 bytes per row	Boundary	Each list or library item can only occupy 8,000 bytes in total in the database. 256 bytes are reserved for built-in columns, which leaves 7,744 bytes for end-user columns.
File size	2 GB	Boundary	The default maximum file size is 50 MB. This can be increased up to 2 GB, however a large volume of very large files can affect farm performance.
Documents	30,000,000 per library	Supported	You can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.
Major versions	400,000	Supported	If you exceed this limit, basic file operations—such as file open or save, delete, and viewing the version history— may not succeed.
Items	30,000,000 per list	Supported	You can create very large lists using standard views, site hierarchies, and metadata navigation. This value may vary depending on the number of columns in the list and the usage of the list.
Rows size limit	6 table rows internal to the database used for a list or library item	Supported	Specifies the maximum number of table rows internal to the database that can be used for a list or library item. To accommodate wide lists with many columns, each item may be wrapped over several internal table rows, up to six rows by default. This is configurable by farm administrators through the object model only.
Bulk operations	100 items per bulk operation	Boundary	The user interface allows a maximum of 100 items to be selected for bulk operations.
List view lookup threshold	8 join operations per query	Threshold	Specifies the maximum number of joins allowed per query, such as those based on lookup, person/group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the object model (by not specifying any view fields), SharePoint will return up to the first eight lookups.
List view threshold	5,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at the same time outside the daily time window set by the administrator during which queries are unrestricted.
List view threshold for auditors and administrators	20,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at the same time when they are performed by an auditor or administrator with appropriate permissions. This setting works with Allow Object Model Override.
Subsite	2,000 per site view	Threshold	The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Similarly, the All Site Content page and the Tree View Control performance will decrease significantly as the number of subsites grows.
Coauthoring in Microsoft Word and Microsoft PowerPoint for .docx, .pptx and .ppsx files	10 concurrent editors per document	Threshold	Recommended maximum number of concurrent editors is 10. The boundary is 99. If there are 99 co-authors who have a single document opened for concurrent editing, any user after the 100th user sees a "File in use" error and have to view a read-only copy. More than 10 co-editors will lead to a gradually degraded user experience with more conflicts and users will have to go through more iterations to get their changes to upload successfully.
Security scope	1,000 per list	Threshold	The maximum number of unique security scopes set for a list should not exceed 1,000. A scope is the security boundary for a securable object and any of its children that do not have a separate security boundary defined. A scope contains an Access Control List (ACL), but unlike NTFS ACLs, a scope can include security principals that are specific to SharePoint Server. The members of an ACL for a scope can include Windows users, user accounts other than Windows users (such as forms-based accounts), Active Directory groups, or SharePoint groups.