Typemock Isolator for SharePoint

I've just found this very-very useful developer tool in Spence's blog: Typemock for SharePoint.

Typemock are offering their new product for unit testing SharePoint called Isolator For SharePoint, for a special introduction price. it is the only tool that allows you to unit test SharePoint without a SharePoint server. To learn more click here.

The first 50 bloggers who blog this text in their blog and tell us about it, will get a Full Isolator license, Free. for rules and info click here.

ISPA and Hungarian SharePoint User Group

In the last months there were a few new changes in the life of Hungarian SharePoint Community. The ISPA (International SharePoint Professionals Association) has been helping us to realize our Hungarian SharePoint User Group (HUNSUG) – the first step was that I've been ISPA Evangelizer since the beginning of September.

The International SharePoint Professionals Association (“ISPA”) is the first independent, community-run, not-for-profit organization designed specifically for SharePoint Professionals. ISPA is a professional association dedicated to the promotion and global adoption of Microsoft SharePoint Products and Technologies.  The Association provides support and guidance to the community  by establishing connections between SharePoint professionals and groups, resources, education and information.

Thanks to the ISPA, we were able to organize our first meeting at the beginning of October. (If you are interested, you can find the recorded presentations here.)

Few days ago, we announced our second event to December 11, 2008. This one will be unconventional one: first time in Hungary, we have an online presenter, Ishai Sagi, MOSS MVP from Australia. I hope, we can make a tradition with inviting foreign speakers (online or presonally) to our following events as well (next one will be in February, 2009).

And finally, the HUNSUG arrived to its next, very important station today: the ISPA registered us as an Approved User Groups, so we're in, we can join to the others around the world:

image

Linq4SP – RC2 timebomb extended

image Although the development of Linq4SP has been finished since a few weeks, unfortunately we had to be faced a few (sales and marketing based) issues during publishing it. So if you've downloaded and started to use the Linq4SP, probably you experienced an error message in the last days: "Your expiration date is reached! You need to purchase a license file to run this software."

We apologize for the inconvenience. Today a new version was uploaded, which has the same bits and no functional differences, but the time bomb is extended to January 1, 2009. You can download it from here.

We're working on the solving of our problems, and hopefully the final version can be released at the beginning of December. In a few days I'll be back with further informations.

Thanks for your understand, and let us know if there is anything we can help with.

WFE vs. Complete installation

Today I had a really interesting (and horrible but useful) experience. One of our customers has installed a brand new MOSS 2007 Enterprise farm with one server (and one other for SQL 2005), and my task was to migrate some content databases to here from another MOSS 2007 Enterprise. It seemed to be really simple, but… Oh yes, the mythical BUT!…

So, the content database was ready, new web application created, content DB attached, everything seemed well and good. Ok, the contents are ready, let's setup some custom features and set the basic MOSS features, for example search. Pretty easy, isn't it? Yes, it's not too complicated: just go to the Central Administration, open the Operations tab and choose Services on Server option –  and start the WSS Search Service, and the Office Server Search Service.

Oooops! We didn't have the second one. It was not exist in the list! Moreover, the Server roles list was disabled. Because of that, I couldn't create any SSP because it's impossible without Index server in the farm. Oh my god, what the hell can be that?…

 

I was searching and searching (unfortunately not on that new MOSS server :P ), and found nothing. I've run STSADM -osearch, but got a "No Search Service" message. I was almost crying.

My tip was that something went wrong in the operating system or in the database (yes, I'm paranoid since the .NET framework 3.5 SP1 issue…). But I was not able to found what was it. I was almost screeming – but instead that I asked my friends Bob and Paul to help me. They advised me to look after if the customer's IT guy has installed the MOSS Farm in Web Front-End (WFE) or Complete mode.

In the trace log I've found the install story and the following entry: "Setting server role to WFE."

I was screaming. The WFE installation doesn't support Indexing service on the server.

Uninstall everything, and reinstall in Complete mode, with SP1, Language Pack and everything. And yes, the Office SharePoint Server Search service was in the list and was able to be started. And of course, the Server role list was enabled, as I wanted.

image

So the conclusions: it's too easy to make a wrong choice during SharePoint installation. So be careful which option you're choosing, because after a wrong decision you have to be faced too much sucks. Basically, first of all install a Complete server, after that you can add some WFEs for that, but never do a single WFE without other servers in the farm!