Mystic Slayer's Bloggie

Well I installed a complete new infrastructure to test the first beta of Microsoft SharePoint Server 2010. So configured a SQL Server 2008 R2 CTP with Windows Server 2008 R2 EE on Hyper-V.

Everything done. And let's play with MSS 2010. Well I was happy to say that I had the option of installing a farm. Well when the installation was running I could say I was disappointed by the fact that SQL Server 2008 was installed on the APP server. So I concluded that the first installation I had no choice that SQL Server was running on the same machine.

The second conclusion is the unforsaken Ribbon of Office 2007. You have alot more options, but if you can say that everything will be worked out better? Well I can say that MOSS 2007 was allready full with bugs with the initial RTM release, and how many bugs can we have with MSS 2010? Well hopefully not that much like MOSS 2007 RTM, because we can wait again for along time to see the first SP. The naming of WSS to Foundation isn't not too bad, but if you can say if it is a Foundation?

The next thing is the fact that not ASP.NET 4.0 Beta 2 is used by MSS 2010. So we're going not upwards, but standing still with the same framework. Also noticed that you have to
use some regfixes to fix some bugs for MSS 2010. Too bad!

First conclusion:

MSS 2010 is alot faster.
MSS 2010 has .NET Framework 2.0/3.5 and not .NET 4.0
Beta and farm installation is too bad.
MSS 2010 has alot of new features and options (also Lotes Notes included).

And yet more to come.

A strange thing happend last day is that for some reason my Web Server went down in action... I couldn't explain why it happend, but I managed to gave it a rebirth of the server.

After 30 days without reboot, wow :-S It went down, and yet I cannot figure out why. Nothing changed, and I saw my logfiles and even there it didn't show anything. So, what happened then? I don't know.

Allright let's get started. Because a normal SharePoint farm will not allow you to request pages with logged in on your website. This is because MOSS will intercept every page you will ask even when you are using an Web Application. In WSS 2.0 and SPS 2003 you had to the possibility to exclude certain paths from being captured by SPS or WSS.

Well in SharePoint 2007 you can't make an exclusion in Central Administration, but you can do it by manual. How to do this is easy or not, but it's possible. You can't access pages directly in a Web Application, but you can create a Virtual Directory. Still when you access this virtual directory, SharePoint won't allow you to access this virtual directory.

Now we have to do it another way. Let's modify the web.config of your Web Application.

this is probably how your section will look like:

 
<httpHandlers>
      <remove verb="GET,HEAD,POST" path="*" />
      <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    </httpHandlers>
 

modify it to this:

 
<httpHandlers>
<!--      <remove verb="GET,HEAD,POST" path="*" />
-->
      <add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
      <add path="trace.axd" verb="*" type="System.Web.Handlers.TraceHandler" validate="True" />
      <add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
      <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    </httpHandlers>
 

Change the trust level:

 
<trust level="Full" originUrl="" />
 

Ensure that your virtual directory has it's own web.config. Without an own web.config it will inherit from your web.config in your website (of course your web.config of your web application).

The situation is following.

I have a page located in the /_Layouts/ dir. This page is the CustomLogin page and validates two ways. The first way is by a post to a security validation with a token.

 
<form name="LoginForm" action="<% =requestURL %>" method="post" enctype="application/x-www-form-urlencoded" id="LoginForm">
 

When we hit the submit button it should post data to this validation server and returns data formatted in the header.

The problem is that the posted data is not submitted, because for someone reason MOSS blocks it.

This validation server has it's own SSL certificate and the MOSS site has it's own SSL certificate.

Yes, this is fun to know for me. I saw that my blogposts are directly posted to twitter as soon as I publish them on Wordpress.

Well I found out that pages that have the Status 'Draft' and are not published still will be read by google and other sites. Probably something is wrong with the sitemap or rss feeds from Wordpress.

I shall look at this one, because I don't want to make posts that aren't ready allready are published world wide. Yet I shall find it out

Well I could find some old posts back, but still my most important pages aren't indexed. That's a pitty you know.

For example,  if you loose everything you have worked for, it is hard to accept to know that you can't have it all back.

Still the search to my blog posts in the past are my biggest concern, in the meanwhile I will be writing new ones.

Maybe it will be better then in the past.

Well I think my blog is now up and running again. It will take some time to fill my blog with usefull content, or crap things, but okay.

Finally my disks failed on me, and not 1 or 2, no 4 disks failed. Probably went something wrong with my SATA raid controller.

Hopefully I can find some old data back in the future, but still it will be hard for me to find out that a lot of returning people can't find my posts back. In the last years I've build a 2500 hundred unique visitors every month. This will hard to get that value back.