October 2006 - Posts

• Whoops. :)

  If you've been reading my articles in Advisor Guide to Microsoft SharePoint, you know how excited I am to share what I know about SharePoint Products and Technologies.  Sometimes, in that excitement, I sometimes skip over an important detail.  In the most recent issue of the magazine, one such mistake slipped in! In the last issue's Advisor Answers column, I mistakenly suggested that Outlook 2007 could synchronize changes made to documents stored in Outlook 2007's offline copy of a synced SharePoint document library.  That is incorrect: Outlook 2007 does not perform a 2-way synchronization with WSS 3.0 document libraries.  You would be responsible for saving the document back to the SharePoint site from which it originally came.  I apologize for any confusion this may have caused! If you don't have the magazine yet -- get it!  Todd Baginski and I can be seen on the very first page, in our regular column, "Advisor Answers".  In each issue, we answer common questions about SharePoint Products and Technologies.  Lately, we've focused on the new version, but fear not: We'll address existing technologies in our next column! Posted Oct 28 2006, 06:01 PM by Dustin Miller with no comments

• DCOM Errors in your Event log with MOSS 2007 B2/B2TR?

  Yeah, me too.  You might notice these alongside your "trial is expired" web site warnings.  This post might help.  It might not.  It has worked for me, so if it works for you (or doesn't), I'd really love to hear about it in the comments. Enough blabber, on with the fix: Make sure that all your application pool identities are running as domain user (or local user) accounts, not "NETWORK SERVICE".  You might get away with using NETWORK SERVICE, but generally, it's best to use actual honest-to-goodness accounts.  I can write up more reasons why in another post, but for now, take my word for it: use real local/domain accounts. On each WFE and App server in the farm, make sure that EVERY application pool user has the rights to activate the IIS WAMREG admin Service DCOM component.  How do you do that, you ask? Start -> Run -> dcomcnfg.exe Expand Component Servers -> Computers -> My Computer -> DCOM Config Find IIS WAMREG admin Service, right click on it, and select "properties" Click the "security" tab Click the "edit" button in the "Launch and Activation Permissions" group Add your application pool identity accounts here, and make sure they have local launch and activation permissions (should be the first two checkboxes). Reset IIS (Start -> Run -> iisreset) Hope for the best You might be able to simply add the application pool identities to the "Distributed COM Users" group and avoid the DCOM Config hoo-hah above, but that didn't work 100% of the time for me -- the above steps did.  Not sure why; they should, technically, give the same permissions to the app pool ID, but hey, maybe the moon wasn't in Pisces when I tried it, and so it failed.  But I digress... If this helps, great!  Let me know in the comments.  If it doesn't, BOO!  Still, let me know in the comments so I can try to track this down a bit more. Posted Oct 13 2006, 06:43 PM by Dustin Miller with no comments