How To Code

SharePoint: List does not exist after adding Data Form Web Part to a page

2012-01-20T11:15:00.001+02:00

Problem:

After checking in your Page Layout containing a Data Form Web Part and changing the page layout of the publishing page you get error:

List does not exist.
The page you selected contains a list that does not exist. It may have been deleted by another user.

Specifically, your DFWP uses SharePoint List located on another site.

Solution:

SharePoint Designer has been helping you during the checkin process and has added two attributes to the Data Form Web Part: ListId and ListName. Remove those and you're good to go.

<WebPartPages:DataFormWebPart runat="server" Description="" Title="Contacts" ... ListId="SOMEGUID" ListName="{SOMEGUID}" ...>

THIS MIGHT NOT BE RELEVANT: It may have also added duplicate ParameterBinding with correct list GUID, but incorrect Name. Should be "ListID". <ParameterBinding Name="ListId" Location="None" DefaultValue="SOMEGUID"/>

Note You need to keep removing those every now and then as they keep reappearing.

SharePoint: Filter Data Form Web Part using Metadata value of current Publishing Page

2012-01-20T00:50:00.001+02:00

Challenge:

On a Welcome Page of a Publishing Site I had few Managed Metadata fields. I was to implement a functionality that would fetch items from a list located on another site and filter the items using value of a metadata field of the current Welcome Page.

The idea is brilliant: there is a customer site, and there is a common list of contacts. Due to requirements, one common contacts list was preferred, so I decided to map contacts to customers by adding Metadata to contact AND to the same Metadata customer Welcome Page.

Solution:

As you cannot reference page field values in DFWP like it is done with CQWP, you must use Control parameter in Location attribute inside your ParameterBinding node (thank you Tomas Breen).

<ParameterBinding Name="Customer" Location="Control(CustomerName,ItemFieldValue)" DefaultValue=""/>

Customer above is the name of the parameter you will use in XSL. CustomerName is the ID of the Control on the Page Layout that contains the value you want to use as a filter. ItemFieldValue is the magic word I had to look for way too long.

Then, in the xsl:stylesheet of your DFWP, you will have

<xsl:param name="Customer" />

and finally you will do the filtering like this

<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[@Customer= substring-before($Customer, '|')]"/>

Note that @Customer is the value of the Customer metadata field of one of the list items we're about to display. $Customer is the xsl:param that contains the value from the Customer metadata field of the current Welcome Page. Substring is done because Welcome Page metadata value comes in the form CompanyX|GUID.

Not yet working? No, because what is still missing is the actual CustomerName control that will contain the Customer value of the current Welcome Page. In my case I used TaxonomyFieldControl and added the ID attribute. You could also use SharePointWebControls:FieldValue, or SharePointWebControls:ListItemProperty, but TaxonomyFieldControl allows editing of the value when in Edit mode and I needed that.

<Taxonomy:TaxonomyFieldControl FieldName="becb57f8-ac0e-45b1-a0b4-e5fa71c0d7fa" ID="CustomerName" runat="server"></Taxonomy:TaxonomyFieldControl>

Note that you will not be able to preview the functionality in SPD. You will have to browse to the page to see your beautiful markup magic.

SharePoint 2010: The data source control failed to execute the insert command.

2012-01-09T19:09:00.001+02:00

Problem:

When modifying a Form of a list with SharePoint Designer 2010, at some point you might get error:

Error while executing web part: System.ArgumentException: Value does not fall within the expected range

The data source control failed to execute the insert command.

This may only occur with a specific type of List Form (New, Edit,Display).

Solution:

While there can be many causes for this generic error message, in my case the first parameter or ddwrt:DataBind function inside the SharePoint:FormFields element was 'i' and I was working with an Edit Form. Changing it to 'u' as it was with every other FormField fixed the issue.

<SharePoint:FormField runat="server" id="ff1{$Pos}" ControlMode="Edit" FieldName="Esittaja" __designer:bind="{ddwrt:DataBind('u',concat('ff1',$Pos),'Value','ValueChanged','ID',ddwrt:EscapeDelims(string(@ID)),'@Esittaja')}" />

Explanation:

DataBind operation type parameters (the first parameter) are listed below:

'i' stands for INSERT,
'u' stands for UPDATE,
'd' stands for DELETE.

More about ddwrt:DataBind syntax can be found from Bryan's article.

Office 365 domain verification with Joker.com

2011-12-15T12:57:00.001+02:00

CHALLENGE:

I'm using joker.com domain registrar and Office 365 needed to verify that I'm the owner of the domain. This is done by either adding TXT or MX record to the DNS records at joker.com (domain registrar).

TXT is the preferred method in order to minimize risks of causing issues in mail delivery if one manages to type in incorrect values for the MX record (in Finnish: ryssiä).

THOUGHTS:

In my (test) scenario I wanted to register intra.jussipalo.com.

Office 365 instructs the following:

In the TXT box for the domain, type the following: @

In the Fully qualified domain name (FQDN) or Points to box, type the following: MS=ms12312312

Where it asks for TTL information, type the following: 1 Hour

Now, in Joker.com, I only have the fields Host and Description:

Host field didn't accept @.

SOLUTION:

In Host field, type in the third level portion of the domain name, in my case intra. In Description, type in the MS=ms12312312.

Save and accept the changes and wait for some time (for me it took maybe 1-2 hours) and you can successfully verify the domain in O365 admin console.

SharePoint Online: You can use your custom domain name, but...

2011-12-15T12:43:00.001+02:00

Keep the following things in mind:

You cannot use custom domain name in your private (=HTTPS) SharePoint Online sites.
What you will can use for your private site depends...you can only hope that https://yourcompanyname.sharepoint.com is available, otherwise you will end up with https://notquitemycompanynamebutthiswillhavetodo.sharepoint.com
intra.yourdomain.com CNAME notquitemycompanynamebutthiswillhavetodo.sharepoint.com won't help you either, because you cannot modify AAM settings of your SharePoint Online sites.

What you can do to ease end user's life of they wish to use their custom domain name is to

Create public SharePoint Online site with the custom domain name and redirect users to actual private site
PROs: You can do it with SharePoint Online's Redirect page layout
CONs: You will use up your one and only public SharePoint Online site slot
If you have any other servers with web sites you can host intra.yourdomain.com web site there and have a simple HTTP redirect from that web site to yourcompanyname.sharepoint.com
PROs: You won't use up public web site slot in SharePoint Online
CONs: You will need to have web server somewhere where you can implement the HTTP redirection.

SharePoint: How to clear Metadata and People Editor fields using jQuery

2011-11-30T13:05:00.001+02:00

Challenge:

NewForm and EditForm of a custom SharePoint list contain Managed Metadata field and People Editor fields. I need to be able to clear the field values dynamically based on what selections the user makes when filling the form.

Just hiding the fields is not good as I don't want to include an additional column only for storing the value of the radiobutton selection.

Solution:

This is possible by using few Javascript tricks, and as I'm most familiar with jQuery I decided to use it to accomplish the goal. There are few hidden fields you need to modify in addition to the visible elements.

First you need to surround the fields with DIV's so that it is easier to reference the correct elements.

<asp:RadioButton runat="server" id="presenterSisainen" Text="Sisäinen" GroupName="presenter" />
<div id="presenterUserDiv" style="display:none;">
<SharePoint:FormField ... />
<SharePoint:FieldDescription ... />
</div>
<asp:RadioButton runat="server" id="presenterAsiakas" Text="Asiakas" GroupName="presenter" />
<div id="presenterMetadataDiv" style="display:none;">
<SharePoint:FormField ... />
<SharePoint:FieldDescription ... />
</div>

To clear Metadata field, do this:

jQuery("#presenterMetadataDiv > span > span > input[type='hidden']").val("");
jQuery("div[title='DISPLAYNAMEOFMETADATAFIELD'] > div > span[class$='valid-text']").replaceWith("");
jQuery("#presenterMetadataDiv > span span.ms-formvalidation[role='alert']").html("");
jQuery("#presenterMetadataDiv > span > br").remove();

Note: 'DISPLAYNAMEOFMETADATAFIELD' needs to be the display name of the metadata field in question. It can contain spaces, etc. If it contains special characters such as umlauts, remember to save your .js file using UTF-8.

To clear People Editor field, do this:

j("#presenterUserDiv input[id$='HiddenUserFieldValue']").val("");
j("#presenterUserDiv span[id$='UserField']").attr("editoroldvalue", "");
j("#presenterUserDiv input[id$='UserField_hiddenSpanData']").val("");
j("#presenterUserDiv div[name='upLevelDiv']").html("");
j("#presenterUserDiv span[id$='UserField_errorLabel']").html("");

Note: You can use different jQuery selectors to achieve the same result, so above is not the only truth.

SharePoint: Some files not visible after migrating Content DB between Classic/Claims enabled Web Applications

2011-11-24T15:03:00.001+02:00

Problem:

After migrating a SharePoint 2010 Content DB to a freshly installed environment my style sheet located in /Style Library suddenly disappeared.

Well, without really thinking it through I created new .css file and renamed it to what it was and should be. I got error saying such file already exists. Say what?

Reason:

What I didn't immediately remember was that when Content DB backup was taken, it was from a Web Application that was using Classic Mode Authentication.

The new environment instead is using Claims Based Authentication. So, what was going on was that my current user account didn't see the style sheet because the file was checked out to classic-based-me instead of claims-based-me at the time when backup was taken.

In addition that file had never been checked in by classic-based-me so there was no way I could see it when logged in with claims-based-me (from SharePoint permissions perspective they are two different user identities).

Solution:

Navigate to the list in question and go to settings of that list.
On List Information screen you see "Manage files which have no checked in version"
Select the file(s) you need to gain access to and select Take Ownership of Selection
BOOM! You have regained access to the file(s)!

Is your external anonymous SharePoint site a bit too open?

2011-11-21T10:09:00.001+02:00

Problem:

Not exactly my problem, but a friendly reminder that it but might be your problem if your site is found here:

http://www.bing.com/search?q="Compatible+UI+Version(s)"+"checked out to"+site:<YOURSITEURLHERE>

Solution:

Activate ViewFormPagesLockdown feature as instructed here in MSDN.

If you’re using Publishing Portal site template, this feature is already activated, but for other templates you need to enable it manually.

The MSDN article contains also other suggestions for public facing anonymous SharePoint sites that you might want to follow.

SharePoint: CAML filtering for Managed Metadata field that is empty

2011-11-18T11:32:00.001+02:00

Problem:

How to write CAML filter that would show items where a specific Managed Metadata field is empty?

Solution:

You need to use IsNull.

LookupId=”TRUE” is optional in this case. If you include it, you are actually comparing if ID of the metadata field value is NULL. If you leave it out, you are comparing if the actual text of the metadata field value is NULL. Either way, same result.

SharePoint: How to get lookup ID of a Managed Metadata Term without having to use GetWssIdOfTerm()

2011-11-18T11:13:00.001+02:00

Problem:

In SharePoint Online (Office 365) and on-premise SharePoint, how do I get the lookup ID of a Managed Metadata Term without having to write code anad use GetWssIdOfTerm() method?

Solution:

Go to the hidden list at the root of your site collection, e.g., http://yoursite.com/lists/TaxonomyHiddenList and look at the ID field of the respective metadata item.

Further explanation on how to actually use that ID in a CAML query can be found here. It actually works in DFWP.

SharePoint: “Security validation for this page is invalid” when adding subsite programmatically

2011-11-17T22:19:00.001+02:00

Problem:

I created a Web Part that is used for creating subsites. In Web Part properties you could type in the name of the Web Template you had uploaded to solution gallery, in addition to other properties. Web Part uses RunWithElevatedPrivileges.

For the first Web Template that was used everything worked fine and subsites could be created just fine. However, the slightly modifying the Web Template lead to the dreaded security validation error:

Exception attempting to ApplyWebTemplate to SPWeb https://URLOFTHENEWWEB: Microsoft.SharePoint.SPException: The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again. ---> System.Runtime.InteropServices.COMException (0x8102006D)

Thoughts:

There wasn’t really much difference between the Web Template that was working and the one that couldn’t be used in my web part when creating subsites.

In fact, what was done in this slightly modified version of the Web Templates was to add an instance of a Document Library template that contained few custom Content Types.

What makes it interesting was that one could create new subsite using that template, if one would use normal SharePoint browser functionality for subsite creation.

As it happens every now and then, I couldn’t reproduce this issue on my development virtual server – even when using the same Web Template.

Solution:

Although it is not exactly clear why having Document Library template on a web template would break subsite creation, there is a real solution.

What had forgotten was to call SPUtility.ValidateFormDigest() before attempting to add the subsite.

Also MSDN instructs that “Either SPUtility.ValidateFormDigest or SPWeb.ValidateFormDigest should be called before a call of RunWithElevatedPrivileges, if the method passed to the RunWithElevatedPrivileges includes any write operations.”

Reason for running the validation is to prevent cross-site-scripting exploits.

   1:  SPUtility.ValidateFormDigest(); // <<<<< REMEMBER THIS!

   2:  // ...

   3:  // Create site

   4:  using (SPWeb newWeb = parentWeb.Webs.Add(

   5:        projectUrl,

   6:        projectName,

   7:        "",

   8:        Convert.ToUInt32(locale),

   9:        siteTemplate,

  10:        true, // True breaks inheritance

  11:        false))

Thanks to Arttu Arstila for helping me with this.

SP2010: Things to check if your Data Form Web Part is misbehaving

2011-11-15T12:30:00.001+02:00

Challenge:

You’re working with SharePoint Designer 2010, and trying to add Data Form Web Part to your Page Layout. There are numerous articles explaining how you should change ListID to ListName and everything should be fine.

Well, the DFWP road might sometimes be long, so here are few things I noticed that might save you a few moments especially when trying to make reusable DFWP that would reference to a list always on the site on which the Web Part is sitting in.

Solution:

You must remove attributes related to WebURL if you want to make reusable DFWP
1. Remove WebURL from WebPartPages:DataFormWebPart > ParameterBinding
  and
  SharePointWebControls:SPDataSource > (Select/Delete/Insert/Modify)Parameters > WebPartPages:DataFormParameter
You can remove SharePointWebControls:SPDataSource > (Delete/Insert/Modify)Parameters if you only use Web Part for showing items
For reusable DFWP you must remove WebPartPages:DataFormWebPart’s attributes called listname and ListID.
For reusable DFWP you must replace ParameterBindings and xsl:params ListID with ListName
1. Also remember to change the GUID to list name
If your list name contains space character, it’s OK, you can have space character in ListName attribute
NOTE! SharePoint Designer keeps adding some attributes to DFWP even if you don’t use Save. It’s enough if you just close the file and reopen it, the ListName and ListID attributes with GUID values can suddenly be in WebPartPages:DataFormWebPart node.
Always keep notepad open and copy paste your working code there
1. Before copying the working markup to notepad, make sure SPD hasn’t injected ListName and ListID GUID attributes from WebPartPages:DataFormWebPart node
Do not do this:
1. Edit Page Layout file in SPD window
2. Save file
3. Close the Page Layout file window in SPD <<<---- No, no, no!
4. Check in file in SPD
  --> SPD will insert ListName and ListID attributes into your DFWPs
Do this instead:
1. Edit Page Layout in SPD window
2. Save file
3. In another SPD window in folder view check in your Page Layout file
4. Close the Page Layout file window

Finally, if you're getting the "List does not exist" error and you're code is exactly how it should be, copy the last working version of DFWP from your backup file. If you compare the working and non-working DFWP's you won't probably notice any differences; at least I didn't; so it might be enough just to cut&paste the same DFWP code back.

Visual Studio 2010: Comparing files without TFS, yes it is possible!

2011-11-10T12:16:00.003+02:00

Question:
Do I always need connection to Team Foundation Server or download some 3rd party tool in order to compare files or folders when I have Visual Studio 20XX installed?
Answer:
No. There is indeed file and folder comparison utility bundled to Visual Studio, but it is well hidden.
You can find the WinDiff.exe from C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\x64. Just make shortcut of it to Start menu, or add it to Tools menu in Visual Studio.

SP2010: This upgrade session has been stopped

2011-11-08T15:49:00.001+02:00

Problem:

After installing SP2010 SP1 and trying to run psconfigui (UI version of the Configuration Wizard) you end up with error:

[psconfigui] [SPUpgradeSession] [INFO] [11/8/2011 3:29:14 PM]: No context object
[psconfigui] [SPUpgradeSession] [ERROR] [11/8/2011 3:29:14 PM]: This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.

The only sensible error you see in PSCDiagnostics log is:

The exclusive inplace upgrader timer job failed.

Followed by generic error:

Failed to upgrade SharePoint Products.

You retry the Configuration Wizard, and you end up with same error.

Solution:

Run psconfig.exe (command line version) from command line and don’t use the graphical UI version.

Command to use: psconfig -cmd upgrade -inplace b2b -wait

WHS 2011: Remote connection to home network computers not working

2011-11-04T00:22:00.002+02:00

Problem:
When trying to connect to computers in your home network through Windows Home Server 2011's Remote Desktop Gateway feature you get error message:

Your computer cant connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance

Thoughts:
You have generated custom certificate for your domain (not self-signed), or you may have bought a real certificate but anyway you have configured to use that certificate in IIS instead of letting WHS take charge of things.

Solution:
You need to assign existing SSL certificate to the Remote Desktop Gateway manually in the RDG console. That console is not installed by default in WHS 2011, so you need to first install that role, then pick a certificate.

Not to repeat what has already been said, configure your browser to Paul Sterley's great article on how to get this done.

Microsoft Online Services: Cannot submit forms on Admin pages

2011-10-14T17:25:00.005+03:00

Problem:
When trying to work with Microsoft Online Services Administration pages at https://portal.microsoftonline.com/Admin, after submitting forms that contain text fields, you might get error:

Sorry! We can't process your request right now.
The service is temporarily offline for scheduled maintenance or we're investigating a problem. We're working to get it back online as quickly as possible.
Error code: 0.

Such form is, e.g., Service Request.

Solution:
After quite lengthy problem solving session with Microsoft support and bunch of test service requests it turns out that if you have string like <XYZ> in the text fields, submitting the form will not work.

Visual Studio Dependency Chart

2011-09-14T08:04:00.002+03:00

Having few spare minutes at the airport waiting for the plane AND downloading Windows 8 Developer Preview I thought why not investigate how my Media Center Status Application is actually structured in terms of assembly dependency.

Visual Studio 2010 provides nice way do do that. Just select Architecture –> Generate Dependency Graph and select what kind of graph you wish to generate. Below you see Dependency Chard by Assembly of my application with nice arrows leading from an assembly to another indicating how assemblies are related to each other. You can dig deeper in your assemblies by clicking the small arrows on top right of each assembly.

What I learned of my tool immediately is that I should maybe consider moving Amazon functionality to own assembly. At least that’s how I’ve done with Facebook and Twitter, so it would be more coherent to do the same with Amazon code. However, my idea is to make external web site functionality to function as plugins, and Facebook and Twitter behave the same in that regard (=getting status or updating status to/from these services).

Amazon is used differently, as the application only queries Amazon for additional media details, such as CD or DVD cover art. There are other services that could be used for querying cover art and other information in addition to Amazon, so conclusion is that separating Amazon code into own assembly might be right way to go so possible future plugin developers could add support for other media information services as well.

Media Center Status Application 0.6.2 released!

2011-09-03T13:34:00.001+03:00

Changes

Fixes Facebook login
Autumn cleaning - removed lots of unused code making assemblies somewhat smaller

Download

SharePoint: Organization browser not showing Manager when Manager is set using PowerShell

2011-06-23T15:52:00.001+03:00

Problem:
You are using PowerShell to set value for user’s Manager and you use email address when setting the value of the UserProfile[“Manager”].Value.

Looking at user profile, the Manager property looks correct, it even resolves domain account properly.

However, Organization browser is not showing Managers for users.

Solution:
Don’t use e-mail when setting Manager value:

$userProfile["Manager"].Value = $managerEmail

instead use manager’s account name:

$managerProfile = $profileMgr.GetUserProfile($managerEmail)
$userProfile["Manager"].Value = $managerProfile["AccountName"]

PS. CSV file we use for importing profiles doesn’t contain AD account name, that’s why I’m using email in the first place.

SharePoint: Changing user’s Manager is not reflected to Organization browser

2011-06-23T15:08:00.001+03:00

Problem:
You update user’s Manager in User Profile Properties, then you go to My Site and refresh Organization browser but change is not there.

Thoughts:
Running search incremental crawl didn’t help, nor running the various SharePoint jobs.

Solution:
Surprisingly solution was to recycle My Site application pool from IIS, and no other action was required.

SharePoint: SPUpgradeSession errors in ULS log every 8 hours

2011-06-16T10:50:00.001+03:00

Problem:
SharePoint 2010 ULS logs get bunch of error messages at around 2:00, 10:00 and 18:00. If there are more than one WFE in the farm, you will probably have the error related to every WFE.

Errors look like this:

[powershell] [SPUpgradeSession] [ERROR] [6.6.2011 9:59:01]: CanUpgrade [SPConfigurationDatabase] failed.[powershell] [SPUpgradeSession] [ERROR] [6.6.2011 9:59:01]: Exception: Login failed for user 'AD\WFESERVERNAME$'.
[powershell] [SPUpgradeSession] [ERROR] [6.6.2011 9:59:01]:
     at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
     at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
     at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
     at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
     at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
     at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
     at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
     at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
     at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
     at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
     at System.Data.SqlClient.SqlConnection.Open()
     at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection()
     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)
     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)
     at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(SPDatabase database, Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence)
     at Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.get_BuildVersion()
     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)

Workaround:
Add 'AD\WFESERVERNAME$‘ (and other WFEs if there are several) to users in SQL, but with no additional permissions (so that they’re in public role).

I will call this a workaround as I haven’t found information that would point this to be best solution mainly in terms of security. Also the actual job/task causing these errors is not yet known.

SharePoint: Importing Term Set gives error about the last line of CSV file

2011-04-14T12:56:00.001+03:00

Problem:

When importing TermSet using CSV file in SharePoint 2010, you get error:

An error was encountered while attempting to import the term set at line [LINENUMBER] of the submitted file and some data may not have been cleaned up. Please ensure that this file is a valid csv file and adheres to the correct format as in the sample file ImportTermSet.csv.

Where [LINENUMBER] is the number of the last line in your CSV file.

You have verified that CSV file is indeed valid, and there is definitely nothing wrong with the last line. Also, when removing the last line, the error persists, but contains LINENUMBER-1.

Solution:

Make sure capitalization in the terms imported in your CSV is same for all parent items. You cannot have parent items with different capitalization.

You will get the error if any parent level term capitalization doesn’t match, e.g.,

,,,"True",,"First level term","First second level term",,,,,
,,,"True",,"first level term","Second second level term","Third level term",,,,

will give you the error, while

,,,"True",,"First level term","First second level term",,,,,
,,,"True",,"First level term","Second second level term","Third level term",,,,

works fine.

Media Center Status Application version 0.6.2 Release Candidate is out!

2011-02-04T08:54:00.002+02:00

Fixes

Fixed Twitter login not working

New features

Option to clear XML status when there is no active media in Media Center
Option to clear XML status Media Center is closed.
Additional details of the media available in XML.

Download here

MOSS: Setting crawl logging categories to verbose

2010-12-03T10:48:00.001+02:00

Copy and paste ready list of in order to set crawl related logging categories to verbose:

Stsadm -o setlogginglevel -category "MS Search Advanced Tracing" -tracelevel verbose
Stsadm -o setlogginglevel -category "IndexerClient" -tracelevel verbose
Stsadm -o setlogginglevel -category "IndexerPlugin" -tracelevel verbose
Stsadm -o setlogginglevel -category "Arpi" -tracelevel verbose
Stsadm -o setlogginglevel -category "GatherStatus" -tracelevel verbose
Stsadm -o setlogginglevel -category "GatherSvc" -tracelevel verbose
Stsadm -o setlogginglevel -category "GatherDirMon" -tracelevel verbose
Stsadm -o setlogginglevel -category "GatherDirMonQ" -tracelevel verbose
Stsadm -o setlogginglevel -category "GathererLin" -tracelevel verbose
Stsadm -o setlogginglevel -category "GathererSql" -tracelevel verbose
Stsadm -o setlogginglevel -category "ScopesCompilation" -tracelevel verbose
Stsadm -o setlogginglevel -category "ScopesPlugin" -tracelevel verbose
Stsadm -o setlogginglevel -category "SimplePI" -tracelevel verbose
Stsadm -o setlogginglevel -category "Common" -tracelevel verbose
Stsadm -o setlogginglevel -category "RichErrorReporting" -tracelevel verbose
Stsadm -o setlogginglevel -category "PHFile" -tracelevel verbose
Stsadm -o setlogginglevel -category "PHSts" -tracelevel verbose
Stsadm -o setlogginglevel -category "PHHttp" -tracelevel verbose
Stsadm -o setlogginglevel -category "FeatureExtractorPlugin" -tracelevel verbose
Stsadm -o setlogginglevel -category "FilterDaemon" -tracelevel verbose
Stsadm -o setlogginglevel -category "FTEAdmin" -tracelevel verbose
Stsadm -o setlogginglevel -category "FTEAdmin" -tracelevel verbose
Stsadm -o setlogginglevel -category "EventLog" -tracelevel verbose
Stsadm -o setlogginglevel -category "Exceptions" -tracelevel verbose
Stsadm -o setlogginglevel -category "IDXPIEventLog" -tracelevel verbose
Stsadm -o setlogginglevel -category "IDXPIFTECursor" -tracelevel verbose
Stsadm -o setlogginglevel -category "IDXPIPerfCntr" -tracelevel verbose
Stsadm -o setlogginglevel -category "IDXPIPlugin" -tracelevel verbose
Stsadm -o setlogginglevel -category "MS Search Indexing" -tracelevel verbose
Stsadm -o setlogginglevel -category "MS Search Propagation" -tracelevel verbose

Revert to default logging level:

Stsadm -o setlogginglevel -default

Media Center Status Application version 0.6.1.1 is out!

2010-11-06T23:06:00.003+02:00

New version of 0.6.1.1 was uploaded including proper fixes. If you installed 0.6.1.1 before Nov 8th 2010, please download again and reinstall. Sorry about that!

Fixes

Displaying Twitter friends’ status updates in Media Center now work
Removed "Status" update methond from Facebook as it no longer exists in Facebook

Download here