Yep, I know...pretty quiet on this blog for the past month or so
I've been super busy and have had some personal items to take care of, but to show some link love to some of my SharePoint pals
- Joel Oleson has recently posted a few items that I feel are worth reading:
- Arpan Shah is always a great resource as well
- Everything from the SharePoint Products and Technologies team blog
- For the dev guys, be sure to check out Randall Isenhour’s Blog for the latest developer oriented content and resources for SharePoint
I'm getting more direct emails on requests for MOSS 2007/WSS 3.0 capable versions of my tools, and I hope to poor more time into those to get those taken care of as soon as possible, but my end customers have to come first. The good news, is that most of them are ready to rock and roll with V3 deployments, so that's going to help.
More to come!
- Keith
Comments
- Anonymous
October 26, 2006
Hi Keith I have been trying to migrate users from a Windows NT domain to Active Directory using spsuserutil -migrate -ignoresidhistory. The command fails each time with the warning "error migrating area contacts". When I look in the portal the area contacts actually did get migrated, and the user details are changed in the UserInfo table, but the user cannot access the portal after the migration. The log file gives further information on the problem, saying it cannot find the stored procedure dbo.sps_hMigrateAreaContactSids. I thought it might be happening because it's an NT-to-AD migration but then I tried migrating one AD account to another and got the same result. If you could suggest any fixes for this I would very much appreciate it.
- frank.
Anonymous
October 26, 2006
This is because it sounds like either a) You have a SP1 version of portal with out the appropriate hotfix b) If you do, or you have SP2 for portal installed, it did not succeed and the required stored procedure did not get updated. That's what the error message is telling you, that the portal is not patched properly in order for the Portal migration part to work correctly. It's not SPSUserUtil, but rather the environment is not setup correctly.Anonymous
October 29, 2006
Thanks Keith, I think it's neither of these. It's a new installation of SPS where we applied SP2 straight away and got no errors. I cross-checked against another new installation with SP2 and this stored procedure (along with a few more - ony finding out one at a time!) is not present on the second system either. However on a test portal that was upgraded first to SP1 and then to SP2 (the owner doesn't remember if he applied the hotfix) the stored procedures are present. regards,
- frank.