Now that the public beta of Sharepoint 2010 is almost out, its time to start getting a glimpse of what has changed and how to address those changes. There are a couple of books available that may help you in the process. The main goal is to drink water from the fire hose and not gasp. Take a loom at this:
IT Pro:
http://go.microsoft.com/fwlink/?LinkId=167123
Have fun.
Finding good technical magazines is not allways a simple task. I’m sharing here 3 of my favourite mags distributed freely online in pdf format:
Enjoy.
Ok, the wave is out and the disclosure is public.
I strongly recommend that you take a look at the latest post on the SPTeam Blog that present the new topics with some sample images: http://blogs.msdn.com/sharepoint/archive/2009/10/19/sharepoint-2010.aspx
Here are some links to resources on the new version of the platform:
Just FYI, the Beta 2 is out and available to all MSDN subscribers. Check it out here: http://go.microsoft.com/fwlink/?LinkID=151797
Cheers 
I was trying to configure the Office Sharepoint Server Search through the central administration, but whenever I hitted the Start link I got the message:
“An unhandled exception occurred in the user interface. Exception Information: OSearch (Administrator)”.
First thought went to the service accounts configured on the several sharepoint services, but the problem persisted.
Later I figured it out. It had to do with the configuration of the Farm Search Service Account, which must be in the format DOMAIN\USERNAME.
Hope it saves you some time…
Recently I had several contacts enquiring how to perform upgrade from a Microsoft Content Management Server 2002 (MCMS2002) to a Sharepoint 2007 Publishing site. Although this is not a “click-click” process, there isn’t much to it. Or is there?
The basics:
“So, where do I start?” you may ask… I would say: “Plan it!“.
In the planning effort, you will realise:
With this in hand you can more accurately estimate and cast light into the dark zones of the process.
Use the CMS Assessment Tool to evaluate the effort involved.
Here are some references to help you getting started:
Be safe.
Almost 1 month ago, the business model for Azure was revealed.
Check it here: http://blogs.msdn.com/windowsazure/archive/2009/07/14/confirming-commercial-availability-and-announcing-business-model.aspx.
I don’t know about you, but I like to have my tools handy 
With this in mind I suggest the approach described here: http://www.sharepointdevwiki.com/display/public/How+to+integrate+SP+Dispose+Check+into+Visual+Studio+Solutions.
Simple and neet.
The public version of the June’s C.U. is finnaly out.
Direct links:
Windows SharePoint Services 3.0 June cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=971538
Office SharePoint Server 2007 June cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=971537
Post from the Sharepoint Team Blog: http://blogs.msdn.com/sharepoint/archive/2009/07/20/june-cumulative-update-packages-ready-for-download.aspx
This post may come to you in many formats:
The story is about 4 wasted hours of a team of 5, in the deployment of a critical project.
“What was the cause of that?!” you may ask… and the answer is: “A blank line!”. Actually I could add some bad words to that answer, but I’ll just leave it at that.
The project was successfully deployed, after a week of day and night effort of the team and it was finally time to load test it and get some actual readings of the capacity of the infrastructure. For the test I was using Visual Studio 2008, with a test project, all nicely configured with dynamic data sources, CSV files, a nice set of webtests and the load tests to go with it.
The project had been tested against the quality environment and everything worked smoothly. By the time I started hitting the production environment with the simplest test (load homepage with login process), I started getting 50% of 401s (access denied). OOPS! What the heck is going on?? I tried the webtest by itself (1 shot) and it went smoothly. Then I tried the load test and 50% were access denied. Lowered the number of concurrent users and the percentage was the same!? Well, we’ve started the obvious and not so obvious process:
None of these came up with unexpected information. Well, in the end that wasn’t correct, but I’ll fill in the gaps later on.
It’s time to bring in the artillery, I thought. Fired up WinDbg, which revealed nothing new, just loads of it… have you ever tried to debug a system while it was being load tested? Well, let’s just say: DON’T.
OK, by this time I was throwing out the towel. “Let’s hit another server! Probably there is some problem with this machine…”. And so we did. And the crap hit the fan again.
By now it was official: panic was setting in. Some of the members of the team were starting to roll back code, and the chaos was just around the corner.
In a desperate move, I tried hitting the quality environment again and the problem persisted. Ok we have a common denominator: my machine. This suspicious actually came true, when we used another machine to perform the test. The test came clean. And suddenly … a light at the end of the tunnel! (and it wasn’t a train heading for us…).
I use a CSV with the list of users that will logging in the application. We were using just 1 user at the time, so what would happen if there was 1 line feed too many ??? Exactly! Once in every 2 tests, there would be a test trying to login with A BLANK LINE!!!!!!!!!!!!!!!!!!!!! There it was: the magic number – 50% of access denied.
The thing is, in the IIS log files, there were some lines with the access denied and there was no username!!! But, tired as we were, we just missed it.
So, as a punch line, be rested when you are deploying a system…
PS: Thank you LM, PR, AR e RS for you support J
myTwitter
Ms SharePoint Products and Technologies Team Blog
