Once faced with this issue took me quite a while to figure it out. My customer had a recent AD serve rmigration to Windows 2008. Import users was working fine, but when a new property was requested to be mapped, it wa snot available anymore. See image bellow:

Note: The selection of directory service properties may be disabled if the shared service provider is in an untrusted domain or if profile import is not configured.

Note: The selection of directory service properties is disabled because the portal is in an untrusted domain or no irectory service import is configured yet.

Security Note: If you are using a high privilege account to import, you will be able to read and import directory

How was this solved?

1. Going to Shared Services >> User Profiles and Properties >. Configure profile import

2. Click on the link View import Connections

3. Edit the Import Connection

4. Specifiy a domain controller, picked a random controller,

5. Going back to the edit connection and press Auto Discover domain controller.

          

6. problem fixed.... totally random... totally worked!

 

Enjoy!

 

One of the most frustrating things in Sharepoint for developers or even administrators, is implementing a new change and then have to wait for the next time in the schedule for the Timer Job to run.
 
For those who stumble upon this typical MOSS 2007 problem, and wish a particular timer job to execute immediatly:  I created a script that helps me out with it.

Arguments: URL TimerJobname(internal name not the name you see in the CA) ContentDBGuid

Source code:Program.cs.txt (1.15 KB)

Enjoy!

I've only found this problem in SharePoint 2010. When creating site columns through a feature, the site column type User can generate Datasheet view errors later on, if you forget to add the property Type="User" in the field description:

< Field ID = " {cfede2eb-9f3b-4a6b-8bce-9880d2ea34fc} " SourceID = " http://schemas.microsoft.com/sharepoint/v3 " Name = " FieldUserName " StaticName = " FieldUserName " DisplayName = " FieldUserName " Group = " Field group " BaseType = " Text "   />

You should have done it like this:

 <FieldID="{cfede2eb-9f3b-4a6b-8bce-9880d2ea34fc}"SourceID="http://schemas.microsoft.com/sharepoint/v3"Name="FieldUserName"StaticName="FieldUserName"DisplayName="FieldUserName"Group="Field group"BaseType="Text"Type="User"/>

But now that you have deployed it live, the best way so data is not lost, is to correct this programmatically with a script:

static void Main( string [] args) {

string url = args[0];

SPSite site = new SPSite (url);

SPWeb web = site.OpenWeb();

List < SPField > fieldsList = new List < SPField >();

fieldsList.Add( web.Fields[

new Guid ( "{cfede2eb-9f3b-4a6b-8bce-9880d2ea34fc}" )] );

//you can add other User type fields where you have forgotten it.

foreach ( SPField field in fieldsList) {

Console .Out.WriteLine( "Initial value: " + field.SchemaXml);

if (!field.SchemaXml.Contains( "List=" ))

{

   field.SchemaXml = field.SchemaXml.Replace("<Field", "<Field List=\"UserInfo\" ");

   field.PushChangesToLists = true;

   field.Update();

}

}

Good luck!

After editing a masterpage, or page layout you get the following error:

"An error occurred during the processing of /_catalogs/masterpage/masterpagename.master. Code blocks are not allowed in this file. "

 

Solution:

 

1. open the web.config add the following code in <sharepoint> <safemode..>:

   <SharePoint>
    <SafeMode MaxControls="200" CallStack="false" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="false">
      <PageParserPaths>
 <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" />
      </PageParserPaths>
    </SafeMode>

  ....

2. Add the following safecontrol:

   <SafeControl Src="~/_catalogs/masterpage/*" IncludeSubFolders="True" Safe="True" AllowRemoteDesigner="True" />

 

Good luck! :)

 

This is piece of cake! Just apply the following command:

Stsadm –o setadminport –port 99999

This command will change SharePoint Central Administration v3 to run on port 9999. No need for IISRESET or reboot. Enjoy!

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!