Thursday, March 25, 2010

Stsadm -o migrateuser Generates Error "Object reference not set to an instance of an object"

I have been involved in some migration tasks for SharePoint, that includes changing of the domain name. SharePoint has quite easy ways of doing migration, as long as you don't meet some strange error messages (hey, I think this applies to any migration!). I will discuss about the data migration in more detailed, hope by next post (however, if you need some information for data migration in SharePoint, please feel free to drop comment).

So, once you meet strange error message, the data migration is not that easy anymore. One error message that keeps me busy doing research is running stsadm -o migrateuser -oldlogin [oldloginname] -newlogin [newloginname] -ignoresidhistory, that return error "Object reference not to set to an instance of object". I just found out recently that it's actually caused by one SSP with status "Unprovisioning". What I need to do is just to delete this SSP, and, voila, the stsadm migrate user command runs succesfully. =

However, it's not a smooth journey to delete this "Unprovisioning" SSP either. The command that save me is stsadm -o deletessp -title [sspname] -force. The first time I executed this, the command hang for very long time. I try to restart the server, and first thing after restart is to execute this command, and it succeeds.

Tuesday, March 09, 2010

SharePoint doesn't work well with IPv6

I have just setup a new server farm for SharePoint. After finish installation for all server farm, I start configuring the Shared Service Provider, include activating SharePoint Search. Once the Search turned on, the whole SharePoint site is inaccessible from the server that hosts the Central Administration, all other Web Front End is ok. The page just displayed 503 - Service unavailable. IIS showed that Application Pool has been stopped, so I start it again, but everytime there is a request to the site, the Application Pool stop again.

After checking through the forum and all blogs, it turns out the evil here is the IPv6 is enabled. After turn IPv6 off, all the site work properly again. Damn.. wasted almost 1 hour close to midnight..