The URL for this file is too long for the application

One of our business owners has reported an issue “SharePoint reporting these errors when I open an Excel file, you can support me in check if not missing any site configuration.”

Error #1:

The URL for this file is too long for the application.  A temporary copy of this file will be opened on your computer.  You must save this copy as a new file. – This is the most common one where many levels of nested sub folders in a library.  If your folder paths start exceeding 120 characters by themselves, it's time to reorganize your content folders.

Error #2:

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.

Troubleshoot issues with Windows SharePoint Services.

Error #3:

The URL for this file is too long for the application.  A temporary copy of this file will be opened on your computer.  You must save this copy as a new file

I think this is an old (in fact very old) / generic error message which come while editing the office documents. Let’s try to understand a little background behind this issue!

What’s the cause behind this issue?

Here is the reference: http://support.microsoft.com/kb/894630

What the above article saying?

This behavior occurs if the number of characters in the URL exceeds the maximum number of characters that is supported for URLs in SharePoint Server 2007 / 2010, in SharePoint Portal Server 2003, and in Windows SharePoint Services.

To determine the length of a URL, SharePoint Server 2007, SharePoint Portal Server 2003, and Windows SharePoint Services convert the string in the URL to Universal Character Set (UCS) Transformation Format 16 (UTF-16) format, and then count the number of 16-bit characters in the string. A URL that contains more than 260 characters is not supported.

Additionally, a URL that contains one or more of the following components is not supported:

1.    A folder name that has more than 256 UCS-2 characters

2.    A file name that has more than 128 characters

More details on “Understanding URL and path lengths”, “URL path and restrictions”, “Resolving URL length problems”:

http://technet.microsoft.com/en-us/library/ff919564(v=office.14).aspx

Resolution:

Make sure that the names of folders and of files do not exceed the maximum lengths that are supported for URLs in SharePoint Server 2007, in SharePoint Portal Server 2003, and in Windows SharePoint Services.

Workaround:

Reduce the SharePoint URL’s, How to do this? – Here is the reference:

https://portal.slac.stanford.edu/sites/inc_public/pages/how-to-shorten-url.aspx

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Note:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Reference:

http://sharepointknowledgebase.blogspot.com/2013/02/url-path-length-restrictions-sharepoint.html

Product applies to:

·         SharePoint 2010

·         SharePoint 2013

Remove quick launch in SharePoint 2013

I think this is the most common request for end users in which they want to remove the quick launch from the site in SharePoint 2013!

Note:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

So thought of sharing this article with all of you so that everybody can get the benefit of the same:

Here is the script that you are looking for!

/* Hide quick launch bar */

#sideNavBox {

display: none;

}

/* Hide quick launch bar */

#contentBox {

margin-left:20px !important;

}

If you don’t want to go for code approach then here are some other ways!

To enable or disable Quick Launch through the user interface

1.    Click Site Actions, and then click Site Settings.

2.    Under Look and Feel, click Tree view.

3.    To display the control, select the Enable Quick Launch check box. Or, to hide Quick Launch, clear the check box.

To enable or disable Quick Launch using SharePoint Designer

1.    Open the website in SharePoint Designer 2010.

2.    On the site settings page, under Settings

3.    Select the Display Quick Launch check box to enable the menu.

4.    To hide the menu -> clear the check box

5.    Click File, and then click Save to save the change.

If you have any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Open Videos in a new window/tab - SharePoint 2013

New digital asset content types, Thumbnail–centric views, Image previews, Automatic metadata extraction for image files, Podcasting support through RSS – You must be wondering what’s this? J Quite obvious! These are all the features of asset library which is there in SharePoint 2013.

Note:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Asset Library: Additional functionality to support the storage and organization of rich media, such as images, videos, or audio files.

Every time I tried opening the video files, they opened in the same window which I don’t want, there has to be a separate window in which I can open & view these video files!

How to do this? – Thank you for reading this article as this will give you the exact guidelines to achieve this!

There are two ways to achieve this end result:

1.    Out of box way | Default functionality

2.    Programming way

Out of box way:

1.    Open your asset library

2.    Change the view options

3.    Switch to “All Assets” view

4.    Right click on the Video file

5.    Open in a new window

Programming way:

Two references which are pretty awesome and useful too!

http://365.webbrewers.com/blog/Lists/Posts/Post.aspx?ID=9

http://www.eliostruyf.com/adding-a-custom-action-to-a-callout-in-sharepoint-2013/

http://junestime.wordpress.com/2013/02/26/javascript-open-links-in-new-windowtab-in-sharepoint-2010/

I hope the above information will be helpful for all of you! In case of any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Product applies to:

SharePoint 2013

References: 

http://technet.microsoft.com/en-us/library/ee414275(v=office.15).aspx

Maximum upload size in SharePoint 2013

As the SharePoint can be use one of best repository tool in today’s market, we uploads so many files to SharePoint document library on regular basis and face some generic error message also “you have cross the upload limit which has been configured by web administrator” & so many others!

Today’s article is based on this “maximum upload” information and what’s under the hood? Where is this setting coming from?

Here is the information that you are looking for!

The maximum file upload size is a web application setting that specifies the maximum size of a file that a user can upload to the server. You configure the maximum file upload size for every web application by using Central Administration to specify the size of files that will be uploaded to asset libraries.

By default, the maximum video file upload size is 250 MB. You can increase the video file upload size to 2 GB.

How to change this in CA?

1.    Central Administration

2.    Application management

3.    Manage web applications

4.    Select the correct web application in which you wanna do the changes

5.    General settings (from the ribbon)

6.    You will see the section named as “Maximum upload size”

7.    Change the value as per the requirement and click OK.

8.    That’s it & you are done!

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The site collection could not be restored - Resolved!

We have a sharepoint site in our staging environment & the exact replica in production. We made few change to the staging site and tried to restore that staging site to production. But restoration never got completed and we received the below.

Error: The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space.

Troubleshooting done:

-Check the disk space on the SQL server where LDF athe nd MDF files are stored.

-Check the partition on the SQL Server in reference to data files.

-Make sure the content database has enough space allocated.

-Make sure the database does not have restrictive growth.

-Make sure to check the disk space on the SP server where restore is running. Approximately it should be 2 times the DB Size.

-Also try doing the below

Go to “SQL Server Properties-> connections” and uncheck ‘Use query governor to prevent long running queries’. Also set ‘Remote Query timed out to 0’.

Stop and restart the “Windows SharePoint service timer”

Restart the IIS.

But still i received the same error.

Resolution: There would be a possibility of existing PRD site might be orphaned. If the site is orphaned and if we try to restore upon that site, it will throw the above error.

Steps to identify the Orphan sites/Site Collection:

Step 1: Execute the below command.

stsadm -o enumallwebs -databasename DatabaseName -databaseserver  Servername  > c:\ContentDatabaseNameOrphans.xml

Step 2: XML File will be generated. It will be  displaying all the site collections and sites present in the Content DB with their GUID’s

<Site Id="3d884a5a-e739-4e2c-a919-1837b27efdeb" OwnerLogin="domain\AdminAccount" InSiteMap="False" HostHeader="www.abc.com">

<Webs Count="5">

                                 <Web Id="371a4912-4c3b-445b-a746-8a20a6f85ab8" Url="/" LanguageId="1033" TemplateName="CMSPUBLISHING#0" TemplateId="39" />

                                <Web Id="85ab183b-9210-491c-bfb3-9f96560003e7" Url="/Subsite1" LanguageId="1033" TemplateName="CMSPUBLISHING#0" TemplateId="39" />

  <Web Id="0696a632-27bc-4002-a5a7-d1c56d2a8543" Url="/Subsite2" LanguageId="1033" TemplateName="CMSPUBLISHING#0" TemplateId="39" />

                                <Web Id="3397eeae-ff35-400d-8564-ce373492eace" Url="/Subsite3" LanguageId="1033" TemplateName="CMSPUBLISHING#0" TemplateId="39" />

                                 <Web Id="7c8ac45b-d9a5-4381-9067-b891d49e6b90" Url="/Subsite4" LanguageId="1033" TemplateName="CMSPUBLISHING#0" TemplateId="39" />

                </Webs>

</Site>

InSiteMap="False" indicates site collection (www.abc.com) is orphaned. If you try to restore upon the site collection www.abc.com , you will receive “site collection could not be restored again” error.

Step 3: To remove orphan objects , I tried running the below script.

$database = Get-SPContentDatabase “Content_DB”

$database.Repair($false)

$database.update()

Note : $false parameter is used to view the list of orphan object related to the Conten DB  and $true parameter will actually delete orphan objects.

But unfortunately all the orphan object related to the site collection www.abc.com are not removed completely.

Step 4: To verify the orphan site collection is completely removed or not,Go to your SQL Server and open your database and then tables àright click on the table “dbo.AllSites” à select top 1000 rows.

Step 5: It will display the list of Site Collection’s GUID present in the database.  You need to verify the existing orphaned site collection GUID in the database(Which we found out it in step2).If it is present,  remove that using the below command.

But before executing the below command , be sure that you are deleting the correct site.

stsadm -o deletesite -siteid  "SiteCollectionGUID" -databasename “ContentDB_Name" -databaseserver "DB_ServerName" –force

After executing the above command , you can verify the site GUID is removed from  “dbo.AllSites” table.

Then try to restore the Staging back up. Now this times, restoration got completed successfully :)