André Krijnen

The first of all is, when you go to a customer for a simple upgrade to SharePoint 2010 isn’t going to be easy. Why, well Rick Taylor is one of the masters of upgrading to SharePoint 2010, and now I know why he is preaching about all the mess you going to have with upgrading to SharePoint 2010.

A simple thought about upgrading isn’t going to be, why? Every customer has custom solutions, changed css’s or anything of that stuff, but it’s going to be worse. When you have Site Definitions, what is not the best practice of course it is going to be alot worse. All kinds of developers are writing and developing nice Site Definitions but when you are at the stage you want to upgrade these developers kan start all over again. Yes, because they put everything in a solution. Every complete customized lists, document libraries and blogs.

Wow, well if you are an architect or a business manager and you hear about Site Definitions and you’re upgrading to SharePoint 2010. You can think twice, and even need to save some money to hire a developer that can write all the site definitions again which are not best practice off course. Yes, why I am writing this blog, because I just started to upgrade some solution that is written if all the above mess. Customized blog pages, document libraries, lists, etc. Yes we make features and we make site definitions and we put them all in one bucket called a WSP and hopefully it will work under SharePoint 2010, because you’ll never know.

The last couple of days I was working at a customer where Kerberos was needed for SharePoint 2010. Of course I started to set the different Service Principal Names for my App Pool accounts, farm accounts, machines, etc. Not to hard to do it, but I ran everytime in a 401 error: The requsted resources requires user authentication.
Strange I thought, but yet I sended the Domain Administrator more commando’s and it didn’t help. So I checked everything, checked for duplicates, etc. Still I ran into these errors.

After some search I found out that there are some problems with IIS 7.0 regarding Kerberos, and I needed to configure the applicationHost.config to solve these issues with Kerberos. enabled the kernel activation mode, etc. But, it didn’t make any difference, rebooted several times, removed the Kernel Activation Mode and removed again the changed on the applicationHost.config.

I knew that we’ve made C-Name records and it gave me a wonderfull idea to change the C-Name records to A records. These changes where applied, and wow, in less time as expected I opened IE and opened the different web apps. In less then a second the page was displayed from my web app. When you run in these problems, change your C-Name record to A-record and it will fix all your problems with SPN’s, Kerberos and IIS 7.0

Well it was the first time I did a deployment of WSS 3.0 on Windows Server 2008 R2 at a customer… the installation went very well I could say but yet I found out that I had a strange DCOM error. Not the DCOM error I would suspect…

Type: Error
Source: DCOM
Category: None
Event ID: 10016
Description:
The application-specific permissions settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user DomainName\UserName SID {61738644-F196-11D0-9953-00C04FD919C1}. This security permission can be modified using the Component Services administration tool.

So after searching on BING.com I found out that this has the do with the DCOM IIS WAMReg admin service. Normally you would say that this has to do with the location activation of the DCOM service. But when I found out that the DCOM service couldn’t be changed I had to figure out that I had to change some settings. I knew that you can activitate the DCOM service, but Microsoft had to change this DCOM service with the new release of Windows Server 2008 R2. On BING I found out that someone had this error.

So check the blog of Wictor Wilen It saves you a lot of time to figure it out.

Today I was doing some tasks on SQL Server 2005 with SP2. I had some problems with adding jobs and getting the following error message:

Unable to cast object of type ‘Microsoft.SqlServer.Management.Smo.SimpleObjectKey’ to type ‘Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey’.

The issue was using client tools without SP2. You can’t add jobs to a SQL Server 2005 with SP2 with SQL Server 2005 RTM Client Tools.

Well finally I had the time to make a clean install for Windows 7 Ultimate x64.

It took me 1,5 half hour to be up and running again… that means Install Windows 7, full updates, Office 2007 Ultimate and MSN to work with.
Well that wasn’t to hard, except for the Realtek RTL8111 drivers for my LAN. The drivers supplied by Microsoft Update ruined the LAN connection, so I had to download new drivers from Realtek by itself.

After that I was happy that I finally installed it 🙂

Update: 10/15/2009 12:16 AM

So the first important things I’ve noticed is:

Now let’s keep playing with Windows 7.

Owwh yeah my system configuration:

CPU: AMD Phenom II X4 940
Mainboard: Gigagyte GA-MA790GP-DS4H RF3
Memory: OCZ DDR2-800 Reaper 4x2GB CL4 OCZ2RPR800C44GK
Graphics cards: 2xSapphire 4850 1GB
Disk config: 3x320gb RAID 5 for OS
Disk config 2: 3x1TB RAID 5 for DATA
Sound: Soundblaster 2 Audigy 24bit Advanced
Screens: 2x IIyama 26″

SharePoint sites using hostnames (HOSTS) with Internet Explorer 8 (IE8) have logon failures

I like to use beta programs. You can see what new functionality will be available before the product is released. But using betas of Internet Explorer is something i have a lot of bad experiences with. Currently we got a report on one of our websites that it had some problems running under Internet Explorer 8. Ofcourse i checked this in my virtual machine by installing the released version of Internet Explorer 6/7/8.

For some reason i was not able to access my SharePoint websites anymore. It kept me asking for my login over and over again. Doing some googling i found out that this issue was also under the beta release and that there is a solution. Keep in mind that this issue is still present in the released version.

It seems that Internet Explorer 8 does a loopback check. This causes SharePoint sites using hostnames (in your HOSTS file) with a logon to have logon failures.I like to use the HOSTS file, because you do not have to use specific port numbers for running your websites. Als for doing demos on events and at customers it looks better.

There are two solutions for the problem. This one i think is the best and less work:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer. (it seems that this was not needed on my virtual machine).

For more information: http://support.microsoft.com/default.aspx/kb/896861

Well I downloaded today the new trial of the new Microsoft Visual Studio 2008 Team Foundation Server 2008 ×64. I was very excited and what I did all to do install this. Well let’s write it down:

I’ve started to clean my machine with a fresh formatted drives.
I installed cleanly Microsoft Windows Server 2003 R2 ×64 Enterprise Edition
I installed IIS Server 6.0
I installed SQL Server 2005 Enterprise Edition x64 with Service Pack 2

Downloaded all the updates.

Cleanly installed .NET Framework 3.0.

Downloaded again alot of updates.

Installed Microsoft Office SharePoint 2007 Enterprise Edition for x64 systems.

I was very excited and downloaded today the full trial of Microsoft Visual Studio Team Foundation Server 2008 for x32 and x64 systems. Whoehoe. Yeah I thought that I was going to rock.

So 18 minutes downloaded for 1,3 gb of TFS 2008. And I was ready to install. Well I opened the ISO with Daemon Tools and the autorun started…

I clicked: Install Team Foundation Server.

The setup is started….
whoehoe, I’m waiting hell yeah baby
My music goes harder and harder. So I was ready to roll.

And then this happened.

The Team Foundation Server is not supported on the 64-bit versions of Microsoft Windows Server 2003 Operating System

I thought that I downloaded the x64 and x32 version of TFS. So I looked at my ISO and it says:

en_visual_studio_team_system_2008_team_foundation_server_trial_x86_x64wow_dvd_x14-29244.iso

I thought, allright, maybe there is something wrong or what. So I rebooted my machine. And started again the setup. Well it has the strange behavior or telling me that I’m an asshole and doing something wrong. So I opened the install manual of TFS and started to read the documentation.

Well the bloody manual tells me that every Windows Server 2003 operating system is supported including the bloody x64wow systems. So what the fuck happened?

I started to look at google and I found out that the fucking TFS server can only a x64 SQL Server and not a x64 Operating System. Well why don’t you tell me that earlier. Now I can fuck around with my machine again…. No fucking way that I install everything again. So I looked in my MSDN subscription for Virtual Server 2005 R2 ×64 supported. And yes there it is. I Installed this application. And I had an image ready with everything pre-installed and of course SharePoint 2007 Server on it.

Allright, I had to update this virtual server. And that only costed me about an half hour of time. Damned again. And then I came the following problem.

When I want to use my SQL Server on the local machine instead of my virtual machine I had to make a Domain. You know why? Because TFS can’t deal with workgroups. WTF!!!

Damned, there goes my monday again… Owwh and spread this word if you read this bloody blog, because now I allready hate x64 systems!!!!