Sometimes SharePoint users notice that Multiple Upload is not available when trying to upload documents. This usually has to do with their company security settings.

The following conditions are needed to have Multiple Upload working:

1. At least Office 2003 must be installed.
2. Enable the ActiveX controls:
   2.1 Go to Internet Explorer > Tools > Internet Options > Security Tab
   2.2 Here in the "custom level' button activate/enable the Active X controls that say "Script ActiveX controls maked safefor scripting*", like in the image below:

 

 

You can also check the following:

1. Check that the Windows SharePoint Services Support component (under 'Office Tools') has been installed by the Office setup program. This installs an ActiveX control that provides functionality such as support for uploading multiple documents within IE. If it does show as installed use the Repair option so that Office setup can ensure it is installed correctly.

2. You can check if the upload ActiveX control is installed correctly by going to Manage Add-Ons in IE8 (or 7). Set the filter to show 'All Add-Ons'. Under Toolbars and Extensions look for the STSUpld UploadCtl Class and ensure it is enabled. It should have a major version of 12, for example 12.0.4518.1014 > not sure if it is this version without Office 12.

Good Luck!

Some customers might like to use Access files as they use Excel & Word files. But the *.mdb files are blocked by default.

You must unlock/unblock these files in different places: SharePoint Central Admin, IIS & eventually the .NET web.config file.

 

1. Go to Central Administration > Operations > Blocked file types

2. In a page like the image below, remove the mdb file & press OK

3. Now you can upload MDb files.

4. The problem with MDB files is that you cannot download them later on by default.

5. When trying to click of save target as in an uploaded file, you might get the following error:

   the type of page you have requested is not served because it has been explicitly forbidden. The extension .mdb may be incorrect.Please review the URL below and make sure that it spelled correctly.

 

6. Despite the fact some articles might recommend you to:

   6.1 Open IIS

   6.2  Go to Properties of the website (Root) > tab Home Directory > Button Configuration

   6.2 Now remove the following 'ISAPI' extensions map entry: ".mdb"

   6.3. This is sometimes NOT ENOUGH!

7. Change the AS.NET web.config file:

   7.1 C:\WINDOWS\Microsoft.NET\Framework\VERSION\CONFIG

   7.2 Open the Web.config file, and comment the following line in the image:

         <add path="*.mdb" verb="*" type="System.Web.HttpForbiddenHandler" validate="true"/>

 

   7.3 Don't do this, if your application is using an mdb file that can end up being downloaded and therefore leaking your DB info...

Good luck!

 

Recently came accros with the request for paging in a Content Query WebPart, because reinveing the wheel is a waiste of time. I ended bumping into this interesting webpart: Enhanced Content Query Web Part.

I ended up needing to customize some code, change the Pager webpart XSL and apply some CSS as well. But Worked beautifully after deployed & implemented.

If you want to read more general information; http://blog.mastykarz.nl/paging-content-query-web-part/.

Good Luck!

 

It seems Microsoft's intended purpose for the workflow history log disappear after 60 days.

Some customers do really want to keep their Workflow history, so here goes 3 options:

1. Disable the Workflow Auto Cleanup timer job completely
2. You can include a specific xml tag in your workflow feature.xml file that controls the number of days retained for the workflow history (max days = 9999)
3. Run a job nightly to force all the workflow history retention settings to a certain number of days (max days = 9999) >> an article was already published in this blog on how to implment such script (http://blogs.tamtam.nl/duarte/default,month,2008-08.aspx)

 

Honestly the consequences of keeping the whole workflow history is absolutely unknown. But might reduce the performance of whole portal or simple the workflow procedure. Might be noticeable after 1 year or earlier depending on the amount of workflows going on on a daily basis.

Are you going nuts after deploying your workflows & several IISRESETs and you see that it still behaves the same???

If your changes were on the designer editor (for instance changing a method for a if branch condition). After deploying your solution (or manually copying your DLL to the GAC) you need:

   1. Remove the workflow from the list that uses it
   2. Deactivate the Feature of the workflow
   3. Reactivate the feature.
   4. Re-attach the workflow to the list.

Are you see ing this error when you try to create a new page in a SharePoint site?

" List does not exist The page you selected contains a list that does not exist. "

Or are you also seeing this error when you try topen one of your pages?

"Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page."

 

Here is my non-sense solution (found after long trial and error an looking online):

1. Go to the Pages library where the file is stored

2. Create a new page, but from a different type than the pages that are failing

3. In the New Page area, select the page layout that is failing and create a test page

4. Your page is created successfully… and now you can see your pages…

A lot of trial & error… made me find this… seems a SharePoint… and not the access denied error & manage schedule errors I found before.

 

Good Luck!

 

My related search sources that helped my find this fabulous non-sense solution;

http://www.eggheadcafe.com/community/aspnet/69/10072753/list-does-not-exist-error.aspx

 http://vspug.com/camper/2007/08/27/list-does-not-exist-error-message-1-cause/

 

Most blog engines allow you to display a list of blog posts grouped by month. Unfortunately  SharePoint blog sites do not give you that ability, out of the box.

Here is a simple solution (no codding required) on how to overcome that limitation:

Download webpart

Read the original article…

The link "Save site as template" is only available under Look and Feel at the Top Level of the site collection. 
If you are trying to save a site as a template in WSS v3 or MOSS 2007 you need to append _layouts/savetmpl.aspx to your sub sites url. 

1. Supposing your subsite is:

    http://portal.moss2007.com/subsite/default.aspx

2. You would go to

    http://portal.moss2007.com/subsite/_layouts/savetmpl.aspx

     and then you would be able to save the site as a template.

Note: there might be cases where this will not work.

Good luck!

If you notice in SharedServices that:

1. the profile import is enumerating the same number (marked in yellow in the image below), the stop import is non responsive.

2. The search is crawlling for too long, gets stuck in the status "stopping" if you try to stop.

3. Your audiences are not compiling, because the import has not finished (mage below).

 

These are several syntoms that the service "Office SharePoint Server Search" is not working properly.

How to solve this?

1. In Windows, go to Administration Tools > Services

2. STOPthe service "Office SharePoint Server Search".

3. If step 2 fails, open the Windows Task Manager and kill the proccess "mssearch.exe"

4. Perform IISRESET

5. Go to Administration Tools > Services, and  START the service  "Office SharePoint Server Search".

6. Go to Share Point Central Administration > Shared Services

7. Open the User Profiles and Properties page, and verify if it is importing proper now.

 

 

Xtra suggestions:

Reset Search Index:

Now that (hopefully) everything is working fine, we should be concerned about the cause of this issue. Quite likely the search crawll got stuck at some point, and could be the cause for all this trouble. The best is to reset the current Search Index, and rebuilt it.

1. Go to Central Admin > Shared Services > Search Administration

2. Click on "Reset all crawlled content"

3. Go to "Content Sources" start manually a full crawll on the nedded content sources.

 

Good luck!

If you would like to delete Sharepoint Timer Job Definitions follow these steps:

1.  Go to Central Administration > Operations

2.  Click on Timer Job Definitions

3.  In this page go to the job that you wish to delete

4.  Copy the GUID shown in the URL field of the browser (something like below:

    http://centraladmin.company.com/_admin/JobEdit.aspx?JobId=99346da8%2D1cba%2D4691%2D8c18%2D4e257650aa72

5. Copy to NotePad and replace the %2D characters by a dash "-"

5.  Then go stsadm and run the following command:

     stsadm.exe -o deleteconfigurationobject -id <ObjectGUID>

The command stsadm.exe -o deletessptimerjob  is for deleting Shared Services timer jobs. Which rarely is needed...

 

Good luck!