Blocked File Types >> SharePoint - IIS

When you want to unblock Files Types, First you need to do in SP Central Admin and then do in IIS for the specific Web Site. In IIS you won't see all File Types you seen in SP Central Admin.

SharePoint 2007

Go to Central Admin >> Operations >> Under Security Configuration you will see "Blocked File Types". Click on it and Select the required Web Application.

_________________________________________________________________________________

SharePoint 2010

Go to Central Admin >> Applications Management >> Manage Web Applications. Select one Web Application and you will see "Blocked File Types" listed.

You need to remove the required Files Types from the "Blocked File Types", to allow them.

_________________________________________________________________________________

IIS

Open the IIS Manager, go to Sites and Select the required Site. Under IIS, you will see the option "Request Filtering". Open (double click) it.

You will see all Blocked File Types with Allowed 'False'. Make it 'True'.

List View Threshold

Displaying only the newest results below. to view all results, narrow your query by adding a filter.

Open 'Central Administration' 

Go to 'Manage Application' under 'Application Management' 

Choose the web application in which you want to make the changes 
(example : http:// spdev201:80) 

In the ribbon follow 'General Settings -> Resource Throttling' 
There you can find 'List View Threshold' is set to 5000, change the value you want.

Site Collection Features & Site Features

The default Features should be activated in the Site Collection Features & Site Features.

Then you will see many useful web parts, when you are trying to add web parts.

Site Collection Features

Site Features

Default View is missing in Libraries - SharePoint 2010

When the Default 'AllItems' View is missing in any Library, we cannot open it properly.

Open the List or Document Library in the SharePoint Designer  and create the default 'AllItems' view. Then you can open it with out any issues.

The same thing with Sites. If 'default.aspx' is missing you cannot open it even if the site is existing.

You can copy over from another site thru Site Settings >> Site Administration > Content and Structure or create one thru SharePoint Designer.

Turn Off Master Page Approval

By default, SharePoint requires administrator approval of all changes to master pages. While this is an admirable requirement in a production environment, it just gets in the way when first setting up a site. Every time I want to check in a change, I have to click out of a warning dialog, then go to a separate web page, where I have to go through a multi-step process to approve the changes.

If you have administrative access, you can turn off the approval requirement with these steps:

In the “Site Actions” menu, choose “Manage Content and Structure”.
Right-click on “Master Page Gallery” in the left menu.
Select “Edit Properties”

Select “Versioning Settings”


In the first section, you can choose whether content approval applies to that library.

In the second section, you can choose whether SharePoint should bother with minor versions or simply save major versions every time you save. Choosing “major versions only” will cut out a step whenever you save the master page.
When you’re done setting up the site, be sure to turn approval back on if multiple people will have access to the master page.

Alert Emails

Hi Friends, today we came across a creepy situation. Our Systems Team found about 1500 emails sent from our server to a single user with email Id not related to our company. 

By looking into the Notification Properties, we figured out the emails are going from our Extranet SharePoint Server. No clues whats going on.

Finally we came to know that the user is our vendor and has an external domain account thru Forms Based Authentication (EXT\abcd) from our company. 

The user is working with one of our employee and are uploading huge count of documents into a SharePoint Document Library which has alerts enabled to them for all the changes.

Query Server Is Not Responding And SharePoint Search Is Broken

Query Server Is Not Responding And SharePoint Search Is Broken

This post is in reference to my previous post regarding SharePoint Search issue. I have tried to add detailed resolution steps for that issue.

Issue: Query Server does not respond for content index propagation and SharePoint search does not work for searching new contents. It may work for searching old contents.

These steps assume following SharePoint topology:

1. SPSRVR1: Query Server and SharePoint Central Administration Site
2. SPSRVR2: Index Server and Dedicated Web Front End server for crawling
3. SPDB: Database Server – SQL Server 2005

Note: We have heterogeneous environment, where SPSRVR1 and SPSRVR2 have Windows Server 2003 Enterprise Edition with SP1-32 bit (x86) and SPDB has Windows Server 2003 Enterprise Edition with SP1-64 bit. We have installed Microsoft Office SharePoint Server 2007 Standard Edition-32 bit (x86) with SQL Server 2005 Standard Edition with SP1-64 bit.

Create a new folder (e.g. “Applications2”) on SPSRVR1 (Query Server) for content index propagation. There is no need to share it. SharePoint will do it automatically and remove sharing for “Application” folder (original location for content index propagation). It is highly recommended to create a new folder (“Application2”) at the same level as its original folder (“Application”).

Run following command on SPSRVR1 (Query Server - Search Server)

stsadm -o osearch -propagationlocation "E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications2"

Note: Do not move existing content index from old location (“Application”) to a new location (“Application2”) manually. In fact, SharePoint does it automatically once you create a new location for content index propagation and run above command

E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications on SPSRVR1 – Query Server (Currently it is 4.84 GB with the items in index = 1271197)

E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications on SPSRVR2 – Index Server (Currently it is 12 GB with the items in index = 1271197)

Above command should reinitialize Query Server for Shared Service Provider- SSP in your SharePoint Server farm. Check Search Settings from SharePoint Central Administration site. Index Server should start propagating content index to a new location on Query Server with the message stating “Propagating to new Query Server (Name of the Query Server).

Once “Indexing Status” and “Propagation Status” are idle, you should start “Full Crawl” to crawl the new contents and update the content index which will be propagated to a new location on Query Server automatically.

This should fix your issue and SharePoint search should be working fine for searching new as well as old contents after you finish “Full Crawl”.

You do not have permissions to open this file on excel services

Error Message:

“You do not have permissions to open this file on Excel Services.
Make sure that the file is in an Excel Services trusted location and that you have access to the file.”

You will see the error message when you try to view the excel file using the Excel Web Services.

Fix:

Browse to SharePoint Central Administration.
Go to the Operations tab >> Services on Server, and make sure that "Excel Calculation Services" status is started. If status is stopped, start the service.


Click on Shared Services Administration and click on default SSP.
Under 'Excel Services Settings' >> click on 'trusted file locations'

Click on 'Add Trusted File Location', using the below settings, create the Trusted File Locations.

 

Missing “Column Ordering” in SharePoint 2010 List Settings

If you’re missing the “Column Ordering” setting in your SharePoint 2010 list settings then go to:

List settings -> Advanced Settings -> “Allow Management of Content Types?”
If already yes, change the radio button to ”No” and press “Ok”.  Now check for the “Column ordering” link.

The specified file is not a valid spreadsheet or contains no data to import

I ran into an error today where when I attempted to import a spreadsheet into a list I was told "The specified file is not a valid spreadsheet or contains no data to import"

After lots of looking around with the online support guys it turned out that it was IE8 and IE9 that was blocking the function.  In case you run into this here is the solution:

• In Internet Explorer click Tools --> Internet Options.
• Click Security --> click sites --> and add the URLs of the SharePoint Site. 

Could not load file or assembly

Issue: When users try to access Site Settings or Library settings, they see the above error message. 

This causes when the Microsoft.SharePoint.ApplicationPages.dll file is missing

Solution:  The Microsoft.SharePoint.ApplicationPages.dll file (found in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\BIN) should be dragged into the GAC - Global Assembly Cache [C:\windows\assembly]. I did  this exercise on the Front - End and App Servers.

One you are done, recycle the App Pool of the Website you see the issue. 
Browse the Web Site >> Site Actions and now you will not see the above error message any more.

Crawling Issue

We stopped crawling under Shared Services Administration: Shared Services > Search Settings > Content Sources and selected one of the existing content sources .  But still it is showing "stopping " status. All the options are also disabled except "Edit" and "View Crawl Log". We are interested only in stopping the crawling of a particular "Content source" which we tried to stop. I am guessing "stsadm-o spsearch-action fullcrawlstop " would stop crawling of all content sources.

It cannot be stopped from SSP -> Manage Content Sources page in your case, you need to run this command stsadm -o spsearch -action fullcrawlstop, and reboot the server then check result again.

If you haven't done so already, try running "stsadm -o execadmsvcjobs" to flush out any jobs that are running. 

You can stop the search Service itself in Windows. 
Go to a command prompt and type "net stop osearch" 
After the service stops type "net start osearch" See if that helps.

If you still have issues stopping the Crawl, Go to Reset Crawled Content, check the 'Deactivate search alerts during reset'.

Uploading Large Files To SharePoint

We had an issue uploading large files into SharePoint. We tried all the Workarounds listed in the below tech blog. But no LUCK!!!

http://blogs.technet.com/b/praveenh/archive/2012/11/16/issues-with-uploading-large-documents-on-document-library-wss-3-0-amp-moss-2007.aspx

We found another solution working with my friend.

Go to IIS Manager >> Sites and click on the required website you have the upload issue.

Click on "Request Filtering" and under Actions click on "Edit Feature Settings"

In Maximum allowed content length field, the value will be 30000000, which is equal to 30 MB. Change it to the size you required. We changed the below number to match 1 GB.

1 GB = 1073741824 Bytes
2 GB approximately = 2147480000 Bytes

Do IISRESET once you are done.

Its working Awesome without any issues.

Bulk "Check in" of Checked Out Documents & Option to by-pass Check out Documents while Uploading.

Bulk "Check in" of Checked Out Documents 

Go to Site Actions >> Site Settings

Under Site Administration, click on “Content and Structure”

Select “Checked Out To Me” as View.

Select all the files you need to check in.

From Actions menu, select ‘Check In’

______________________________________________________________

Option to by-pass Check out Documents while Uploading.

Go to Settings >> Document Library Settings.

Under General Settings, Click on Versioning Settings

The Below Option should be “No”, if ‘Yes’, change it to “No” and click on OK.

FBA - Forms Based Authentication Tool

http://sharepoint2010fba.codeplex.com/

This is a Free Tool and good to use. We need to buy Support if needed. Chris Coulson is a good guy and his support is excellent. We found a bug and got the New Version with FIX.

If you need to allow the FBA User to use the "Change Password" option, you need to provide them READ access to the Main Site.

We fixed the error (shown below) using the solution in the link.

NT Authority\Authenticated Users vs All Authenticated Users

What is the difference between All Authenticated Users and NT Authority\authenticated users?

We have a 2010 SP1 Enterprise Farm - new install not upgrade, multiple web apps, mixed authentication models, Claims and Windows.

The Site Collections in the Claims based web apps, allow me to add both All Authenticated Users and NT Authority\authenticated users. However, the Windows based Web Apps will only allow me to select All Authenticated Users. - I assume NT Authority\Authenticated Users is only available to Claims based Web Apps.

Q3.) Which should I use in the claims web apps, All Authenticated Users or NT Authority? (I assume I must use All Authencticated Users in Windows Authenticated Web Apps, since I do not see NT Authority\authenticated users (the people picker looks different as well))

There is one rather telling distinction when assigning permissions. With claims-based authentication, All Authenticated Users implicitly includes any claims providers that the SharePoint STS trusts. The scope of NT AUTHORITY\Authenticated Users scope, by contrast, a la SID, is the AD domain.

SP 2010 - Microsoft Office 2010 Upload Center Error

When you are using Office 2010 with SharePoint 2010, I recently noticed one of the users in our environment got this error message. The user was trying to make changes to a document in a SharePoint document library and trying to save it

"Your Changes were saved but could not be uploaded because of an error. You may be able to upload this file using the server web page."

The error was due to documents getting upload by Microsoft Office Upload Center. Microsoft Upload Center is and add-on that gets install with Office 2010 suite. This probably is saving document to its drafts and not letting it upload the changes. 

Method 1:

All things you have to do is as follows:

1. Open regedit.exe

2. Naviagate to following key:

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Common\Internet]
3. Click Edit Menu -> New -> DWORD with name of "FSSHTTPOff" (without quotes)

4. Click on "FSSHTTPOff" and enter value of 1

5. Close any Office Applications and browser sessions

6. Try to reopen your document (no more read only or failure to upload)

Method 2:

For starters, if you don't want it, don't run Microsoft SharePoint Workspace 2010 (what used to be called Groove). Workspace also loads the Upload Center, even if you simply start it, then cancel before doing anything. It also sets some values in the Windows registry that cause Upload Center to load again every time you restart Windows.

Once it's been loaded there's no simple way to get rid of it, whether you want it or not.

Rude. Very very rude.

To get rid of Upload Center for the current Windows session:

• Press Ctrl + Alt + Del then click Task Manager.
• Click the Processes tab.
• Under Image Name, find MSOSYNC.EXE. Click it to select it.
• Click End Process.
• Do the same for OSPPSVC.EXE.
• Click Yes to the Task Manager Warning message.

If you don't want to repeat this little dance every time you restart Windows, you'll need stronger medicine.

When SharePoint Workspace runs, it makes some registry settings that cause a program called MSOSYNC.EXE to run every time Windows starts. The simplest way to prevent this is to find and rename MSOSYNC.EXE to MSOSYNC.NO! (it's in the folder where Office 14 is installed, in the Office 14 subfolder.) Do that, restart Windows and the Upload Center won't be there any longer. If you want it back, you can always rename MSOSYNC.NO! back to MSOSYNC.EXE and run SharePoint Workspace to start it up again.

Note that Upload Center might still re-appear if you re-install Office or install a service pack; either would probably install a new copy of MSOSYNC.EXE to replace the "missing" one.

If you prefer, you can edit the registry to get rid of Upload Center. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupreg\OfficeSyncProcess and rename or delete the OfficeSyncProcess entry that points to the current location of MSOSYNC.EXE. If that didn't make sense to you, you probably should leave the registry alone.

Again, re-installing or updating Office will probably re-create the registry setting. And so will running SharePoint Workspace.

Of the two approaches, we'd recommend renaming MSOSYNC.EXE. It avoids the danger of editing the registry and will be more foolproof.

One last touch: you could also delete any shortcuts to SharePoint Workspace so that you don't accidentally run it again. You can always go to the Office 14 folder and double-click GROOVE.EXE to start it at will.

http://social.technet.microsoft.com/Forums/sharepoint/en-US/18069755-f6af-46bb-8c55-a4230860f57d/your-changes-were-saved-but-could-not-be-uploaded-because-of-an-error?forum=sharepointgenerallegacy

http://office.microsoft.com/en-us/starter-help/microsoft-office-2010-upload-center-HA010388348.aspx#_Office_Upload_Center

MOSS 2007 Shared Service Providers

MOSS 2007 Shared Service Providers stuck on Provisioning in Progress

This was a really annoying glitch during my setup process of Microsoft Office Sharepoint Server 2007. I have a two server farm that I was upgrading to the MOSS 2007 trial (free for 180 days) and was getting stuck while going through the initial setup process when it came time to create a shared service provider. Luckily, after I got frustrated enough, I turned to Google and was able to find an easy solution that fixed my problem right away.

The hang/error is apparently caused by the Sharepoint Timer service, and in order to fix it you must remove the timer service files. This process needs to be repeated on all servers running the Sharepoint Timer service. Here's how to do it:

1. Stop the Sharepoint Timer service. To do this, go to Administrative Tools->Services, then scroll through the list to find it. Select it and choose Stop

2. Now to delete the configuration files for the Sharepoint Timer service. Navigate to %ALLUSERSPROFILE%\Application Data\Microsoft\SharePoint\Config\ using the Start->Run box (or whatever other method you want to use to traverse the folders). GUID will be a long, random string of numbers, not literally the text GUID.

3. DO NOT delete the cache.ini file, but delete all the other .xml files you find, leaving the cache.ini file intact

4. Right click on cache.ini and choose Open With. Choose to open it with Notepad and change the number value within the file to 0 and save.

5. Restart the Sharepoint Timer service. This can be done very similarly to how you stopped it in step #1, but by clicking on Start this time instead of Stop.

Now you should be able to successfully create a Shared Service Provider. If you already had one that was stuck on "Provisioning in Progress" it should finish at this point since it continues to retry every so often.

If you still have issues, you need to restart the SEARCH and INDEX servers.