QuickSteps

This book I would really like to bring to your attention because of two reasons. It’s cheap and simple. I like it a lot because it explains all the basic principles of SharePoint for end user who never used SharePoint before. It got all kind of nice pictures and everything is explained step by step.

I recommend to give this book to all the site owners or pleople who join your implementation project. It will really help. Disclaimer: I don’t know the author or own any stocks.

Here is an easy link for Dutchies who would like to order.

 

HRESULT: 0X80041050 error – ForeFront

This morning I arrived at the office and was welcomed with a nice error messages with as a result that none of our users could access the intranet. Luckily I had enabled the custom error messages in the web.config file so I got some clues.

Below is the error that was displayed and as it turned out later it was caused by Microsoft ForeFront.

After checking the Event logs and the ULS logs from SharePoint I did some Google and stumbled upon  this blog from Will Pritchard. He made these two brilliant SQL Queries that made me happy again.

Query to see if you have any problems. If yes you can be happy this time, if no you’re back to square one.

select *
from AllDocs
where (VirusStatus > 0) and (VirusStatus is not null)

Query to fix the problem

update AllDocs
set VirusStatus = null
where (VirusStatus > 0) and (VirusStatus is not null)

In the end it turned out that the problem was caused by Microsoft ForeFront Security which has flagged my custom.masterpage as a virus. So boys and girls now we know whenever we see a HRESULT: 0X80041050 error we can relax and thank Will.

Problems while creating a Shared Service Provider

The other day I was at a client and had to create a new SSP (Shared Service Provider) for their MOSS 2007 environment. I did this a hundred times so I started with my famouse smile. After creating the SSP I got an error that it was created but not functioning fully and would try so now and than to see if I fixt the problem.

WTF?

Their was one small catch here that I never seen before. The client was part of an Active Directory that shared multiple domains. Their for I had to login with username@aliasdomain. After many coffees, auches and almost grey hairs I got in tough with Paddy a SharePoint specialist from Microsoft who found the key to solve this mistery. He found out that the account for the application pool in IIS (Internet information Server) was resolved as DOMAIN\username@aliasdomain when the SSP thried to create itself.

This gave a major problem. As soon as I changed the pool accounts true operations >> service accounts from the central administration console, to username@aliasdomain the SSP finished his final creation and was ready to use. I’ve could have used the pre windows 2000 name as well DOMAIN\username_aliasdomain but the problem here is that the final part of the name is broken off as their are to many caracters.

Anyways It worked and made me happy from now on if I get in tough with alias domain hosing I recomend to shorten the domain names manually to username@aliasdomain.

Paddy, thanks again.