Tuesday, March 29, 2011
SharePoint Max URL Size
SharePoint Max URL Size Recently, we've had some discussions about the question whether the SharePoint 260 character URL limit is still in effect in SharePoint 2007. We thought we might write a little blog post about it providing an overview of some facts about SharePoint size limits... A site name is allowed to consist of a max length of 128 characters. You can create multiple sub sites but the maximum URL length of a sub site is 237. This length excludes the part apparently reserved for system files and folders. If you try to create a new page the system path /_layouts/newsbweb.aspx is added to the URL, which makes a total of 260 characters. After reaching that limit, you can still add lists and have subfolders in them. The max length of a doc library name is 255 characters. The max length of a folder name is 123 characters. The max length of a SharePoint URL including lists and folders is 256, excluding system files (for example, /Forms/AllItems.aspx). The max length of a SharePoint URL does not include the querystring portion. The max limit of the querystring portion depends on browser limitations. For example, MSIE 6 supports a total of 2047 characters (almost 2K), FireFox doesn't really seem to have a limit. To make our testing a little bit easier, we wrote a little tool called the 'URL Length Checker'. Everybody is welcome to download it and use it within their own test scenarios. The tool requires the presence of the .NET 2.0 framework. Download the URL Length Checker or download it's source.
Wednesday, March 23, 2011
URL's to Access SharePoint Pages
Here are some URL's to access pages in SharePoint. These URL are helpful to save time and hassles of clicking many times to reach a speicfied page:
The URL's are grouped based on the major functioanlity area:
Users and Permissions:
People and Groups: _layouts/people.aspx
Site Collection Admins: _layouts/mngsiteadmin.aspx
Advanced Permissions: _layouts/user.aspx
Master Pages: _Layouts/ChangeSiteMasterPage.aspx
Look and Feel:
Title, Desc, and Icon: _layouts/prjsetng.aspx
Navigation: _layouts/AreaNavigationSettings.aspx
Page Layout and Ste Templates: _Layouts/AreaTemplateSettings.aspx
Welcome Page: _Layouts/AreaWelcomePage.aspx
Tree View: _layouts/navoptions.aspx
Top Nav Bar: _layouts/topnav.aspx
Site Theme: _layouts/themeweb.aspx
Reset to Site Definition: _layouts/reghost.aspx
Searchable Columns: _Layouts/NoCrawlSettings.aspx
Site Content Types: _layouts/mngctype.aspx
Galleries
Site Columns: _layouts/mngfield.aspx
Site Templates: _catalogs/wt/Forms/Common.aspx
List Templates: _catalogs/lt/Forms/AllItems.aspx
Web Parts: _catalogs/wp/Forms/AllItems.aspx
Workflows: _layouts/wrkmng.aspx
Master Pages and Page Layouts: _catalogs/masterpage/Forms/AllItems.aspx
Regoinal Settings: _layouts/regionalsetng.aspx
Site Administration
Site Libraries and Lists: _layouts/mcontent.aspx
Site Usage Report: _layouts/usageDetails.aspx
User Alerts: _layouts/sitesubs.aspx
RSS: _layouts/siterss.aspx
Search Visibility: _layouts/srchvis.aspx
Sites and Workspaces: _layouts/mngsubwebs.aspx
Site Features: _layouts/ManageFeatures.aspx
Delete This Site: _layouts/deleteweb.aspx
Site Output Cache: _Layouts/areacachesettings.aspx
Content and Structure: _Layouts/sitemanager.aspx
Content and Structure Logs: _Layouts/SiteManager.aspx?lro=all
Search Settings: _layouts/enhancedSearch.aspx
Site Collection Administration
Site Templates: _catalogs/wt/Forms/Common.aspx
List Templates: _catalogs/lt/Forms/AllItems.aspx
Web Parts: _catalogs/wp/Forms/AllItems.aspx
Workflows: _layouts/wrkmng.aspx
Master Pages and Page Layouts: _catalogs/masterpage/Forms/AllItems.aspx
Regoinal Settings: _layouts/regionalsetng.aspx
Site Administration
Site Libraries and Lists: _layouts/mcontent.aspx
Site Usage Report: _layouts/usageDetails.aspx
User Alerts: _layouts/sitesubs.aspx
RSS: _layouts/siterss.aspx
Search Visibility: _layouts/srchvis.aspx
Sites and Workspaces: _layouts/mngsubwebs.aspx
Site Features: _layouts/ManageFeatures.aspx
Delete This Site: _layouts/deleteweb.aspx
Site Output Cache: _Layouts/areacachesettings.aspx
Content and Structure: _Layouts/sitemanager.aspx
Content and Structure Logs: _Layouts/SiteManager.aspx?lro=all
Search Settings: _layouts/enhancedSearch.aspx
Site Collection Administration
Search Scopes: _layouts/viewscopes.aspx?mode=site
Search Keywords: _layouts/listkeywords.aspx
Recycle Bin: _layouts/AdminRecycleBin.aspx
Site Collection Features: _layouts/ManageFeatures.aspx?Scope=Site
Site Hierachy: _layouts/vsubwebs.aspx
Portal Site Connection: _layouts/portal.aspx
Site Collection Audit Settings: _layouts/AuditSettings.aspx
Site Collection Policies: _layouts/Policylist.aspx
Site Collection Cache Profiles: Cache%20Profiles/AllItems.aspx
Site Collection Output Cache: _Layouts/sitecachesettings.aspx
Site Collection Object Cache: _Layouts/objectcachesettings.aspx
Variations: _Layouts/VariationSettings.aspx
Variation Labels: _Layouts/VariationLabels.aspx
Recycle Bin: _layouts/AdminRecycleBin.aspx
Site Collection Features: _layouts/ManageFeatures.aspx?Scope=Site
Site Hierachy: _layouts/vsubwebs.aspx
Portal Site Connection: _layouts/portal.aspx
Site Collection Audit Settings: _layouts/AuditSettings.aspx
Site Collection Policies: _layouts/Policylist.aspx
Site Collection Cache Profiles: Cache%20Profiles/AllItems.aspx
Site Collection Output Cache: _Layouts/sitecachesettings.aspx
Site Collection Object Cache: _Layouts/objectcachesettings.aspx
Variations: _Layouts/VariationSettings.aspx
Variation Labels: _Layouts/VariationLabels.aspx
Translatable Columns: _Layouts/TranslatableSettings.aspx
Variation Logs: _Layouts/VariationLogs.aspx
Site Settings: _layouts/settings.aspx
Variation Logs: _Layouts/VariationLogs.aspx
Site Settings: _layouts/settings.aspx
MOSS Search - Content for this URL is excluded
I recently faced this strange issue, some of the content in a site was not getting searched, no error. I executed full crawl several no. of times, but without success. Then I saw this warning in the crawl logs: "Content for this URL is excluded by the server because a no-index attribute".
Well for some items that were not being crawled the reason was my crawl rule was such, but for others like subsites itself could not understand what could be the cause.Then I looked into search visibility of those sites, and found that indeed the option for this web to appear in search results was set to NO. How simple, but it took me 3 hours to come to that setting :)
http:///SiteURL/_layouts/srchvis.aspx Sometimes critical problems have simple solutions!!!
Well for some items that were not being crawled the reason was my crawl rule was such, but for others like subsites itself could not understand what could be the cause.Then I looked into search visibility of those sites, and found that indeed the option for this web to appear in search results was set to NO. How simple, but it took me 3 hours to come to that setting :)
http:///SiteURL/_layouts/srchvis.aspx Sometimes critical problems have simple solutions!!!
Wednesday, March 9, 2011
Browser Crashes when Opening Office Documents from SharePoint
Browser Crashes when Opening Office Documents from SharePoint
Are you experiencing browser crashes when accessing Office Documents in SharePoint? Something like this:
I recently encounted an issue where Internet Explorer 6 and 7 would crash when opening Office documents on SharePoint 2003. Since it didn't happen to all users, it was pretty obvious that some client configuration was incompatible with the component SharePoint uses to open Office documents.
Have you ever noticed a special dialog is diplayed when you click on a Word document in a document library?
Under the hood, this dialog is displayed by an ActiveX control. If you view the source of a document library page, you will see the SharePoint.OpenDocuments component being called.
For example:
var url='http://moss2007/sites/documents/projectscopestatement.doc';var od3 = new ActiveXObject('SharePoint.OpenDocuments.3');od3.ViewDocument3(window,url,3,'');
What is the cause of this problem?
As it turns out, some users had all or parts of Office 2007 installed such as SharePoint Designer. Office installed a component, "owssup.dll" that causes the issue.
How do you fix it?
Update: Download the hotfix from Microsoft here.
Here are the steps prior to the hotfix:
1.) In Windows Explorer, navigate to C:Program FilesMicrosoft OfficeOffice12
2.) Delete owssup.dll. Make a backup if you are uncomfortable with this step
3.) Run the Office diagnostics by selecting Start > All Programs > Microsoft Office > Microsoft Office Tools > Microsoft Office Diagnostics. This tool will find the mising component and install the "correct" version.
For those users that are unable to complete these steps, the workaround is to right click Office documents and select Save As until it can be resolved.
Are you experiencing browser crashes when accessing Office Documents in SharePoint? Something like this:
I recently encounted an issue where Internet Explorer 6 and 7 would crash when opening Office documents on SharePoint 2003. Since it didn't happen to all users, it was pretty obvious that some client configuration was incompatible with the component SharePoint uses to open Office documents.
Have you ever noticed a special dialog is diplayed when you click on a Word document in a document library?
Under the hood, this dialog is displayed by an ActiveX control. If you view the source of a document library page, you will see the SharePoint.OpenDocuments component being called.
For example:
var url='http://moss2007/sites/documents/projectscopestatement.doc';var od3 = new ActiveXObject('SharePoint.OpenDocuments.3');od3.ViewDocument3(window,url,3,'');
What is the cause of this problem?
As it turns out, some users had all or parts of Office 2007 installed such as SharePoint Designer. Office installed a component, "owssup.dll" that causes the issue.
How do you fix it?
Update: Download the hotfix from Microsoft here.
Here are the steps prior to the hotfix:
1.) In Windows Explorer, navigate to C:Program FilesMicrosoft OfficeOffice12
2.) Delete owssup.dll. Make a backup if you are uncomfortable with this step
3.) Run the Office diagnostics by selecting Start > All Programs > Microsoft Office > Microsoft Office Tools > Microsoft Office Diagnostics. This tool will find the mising component and install the "correct" version.
For those users that are unable to complete these steps, the workaround is to right click Office documents and select Save As until it can be resolved.
Saturday, March 5, 2011
http://go.microsoft.com/fwlink?LinkID=96177
Issue Details:
While trying to install WSS 3.0 SP1 (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx) the installation get stuck at task 9 of 10 of SharePoint Products and Technology Configuration Wizard. When tried to access the server, encountered the following error:
Server error: http://go.microsoft.com/fwlink?LinkID=96177
When look into the “Event Viewer”, found the following error description:
The schema version (3.0.149.0) of the database DATADATABASE_NAME on DATABA_SESERVER_NAME is not consistent with the expected database schema version (3.X.X.X) on DATABASE_NAME. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.
Resolution:
The first thing we did was either remove content database from the web application which are having the error or Detach the database. This doesn’t seem to work. So we run the command
stsadm –o upgrade –inplace –url Central_Administration_URL –forceupgrade
and we were back in the business.
While trying to install WSS 3.0 SP1 (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx) the installation get stuck at task 9 of 10 of SharePoint Products and Technology Configuration Wizard. When tried to access the server, encountered the following error:
Server error: http://go.microsoft.com/fwlink?LinkID=96177
When look into the “Event Viewer”, found the following error description:
The schema version (3.0.149.0) of the database DATADATABASE_NAME on DATABA_SESERVER_NAME is not consistent with the expected database schema version (3.X.X.X) on DATABASE_NAME. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.
Resolution:
The first thing we did was either remove content database from the web application which are having the error or Detach the database. This doesn’t seem to work. So we run the command
stsadm –o upgrade –inplace –url Central_Administration_URL –forceupgrade
and we were back in the business.
Subscribe to:
Posts (Atom)