December 2009


One annoying side effect when you convert a standard SharePoint view to XSLT is that when you mouse-over the link column, it will cause the view to jump around in the browser. This seems to be something to do with how the layout in XSLT converts some of the functionality in a standard SharePoint view.

My workaround for this problem is to just drag the width of the header of the link column, in my case the standard Title column.

In this way, the view then becomes stable.

Advertisements

I now have a perfect installation of the SharePoint 2010 Beta working on my laptop under Windows 7 Enterprise. (Well, when I say perfectl, we will have to wait and see, but at least the Configuration Wizard got to Step 10 successfully and did not throw any more errors). This fixed the problem I reported a couple of days ago concerning the Managed Metadata service.

Looking in more detail, the Datasheet view in a standard team site gives the following error:

Don’t know for the moment, what might be causing this, but will keep investigating.

The following page on Microsoft Technet contains a series of links to files to download as prerequisites to the installation of SharePoint 2101 Beta:

http://technet.microsoft.com/en-gb/library/cc262485%28office.14%29.aspx

The link to download the installer for Microsoft SQL Server 2008 Analysis Services ADOMD.NET is as follows:

http://go.microsoft.com/fwlink/?LinkId=130651&clcid=0x409

But the file is only 4,461 Kb which seems to indicate it is the x86 version. The following page lists three versions for x86m x64 and IA64, so I would imagine the x64 version is required for SharePoint 2010.

Though the file name is the same, it is not the same size, at 6,938 Kb.

http://go.microsoft.com/fwlink/?LinkId=130652&clcid=0x409

If you have an Internet connection when you are doing the SharePoint install the correct file will be downloaded but if you do not have a connection, which is the case in many enterprise environments, then you need to download the correct version of the file.

One of the most heartily cheered announcements at the Microsoft SharePoint Conference in Las Vegas this year was the news that SharePoint 2010 can be installed directly on Window 7 as a development environment.

Now the Beta is out, SharePoint enthusiasts are beginning to get their hands dirty, installing and configuring the new software. In the case of Windows 7, the process is not straightforward as a number of steps have to be carried out by hand and the Install Prerequisites step cannot be run from the install file.

A full list of the steps and the files which need to be pre-installed is available here on MSDN.

In my case, though I had edited the Config.xml file as required, I was still asked for a product key, which fortunately is hard-coded in the file and can therefore be copied and pasted and so the install proceeds. The SharePoint Configuration Wizard failed when I reached Step 8 with a message about being unable to install SQL sample data. I will have to take the time to look into the log files to resolve this problem, but it has not prevented SharePoint 2010 from running. There are a number of issues that have come to the surface however, and these may or may not be related to the configuration failure. For example, the Managed Metadata Service is not available:

The Business Data Connectivity proxy does not start, due to a problem with the configuration of the Load Balancer:

I will no doubt discover more problems as I go along, either real problems in the Beta or difficulties stemming from my install process. In order to compare scenarios, I will carry out an install of the SharePoint 2010 Beta on a Hyper V virtual Server 2008 and see how things look. One thing I have noticed is that unfortunately, the Office Web Apps functionality is a separate install and is currently available only for Server 2008 and not Windows 7.

More install instructions here including Product Keys, should you need them.

If you get the error message above, there is a fix:

Failed to create sample data.
An exception of type Microsoft.Office.Server.UserProfiles.UserProfileException was thrown.¬† Additional exception information: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56)
Microsoft.Office.Server.UserProfiles.UserProfileException: Unrecognized attribute ‘allowInsecureTransport’.

This error is caused by a known issue with Token Authentication and WCF. A fix has been released and is now available  at http://go.microsoft.com/fwlink/?LinkID=166231. The trick seems to be to re-run the SQLServer2008-KB976761-x64 patch before re-launching the SharePoint configuration wizard each time. This worked for me.