Installing SharePoint 2007/2010 with Active Directory 2000

The first order of business should be upgrading your domain controller since apparently SharePoint 2007+ doesn't play nice with this legacy version of AD (http://msmvps.com/blogs/obts/archive/2006/09/27/143844.aspx). If that's not an option before your install of SharePoint, you'll need to do the following in order to use any domain accounts for the various SharePoint service accounts (required if you're building a multi-server farm).

Disable domain digital encryption on all SharePoint servers:
  1. Navigate to Administrative Tools > Local Security Policy
  2. Expand 'Local Polices'
  3. Select 'Security Options'
  4. Navigate to the 'Domain member: Digitally encrypt or sign secure channel data (always)' item within the main display pane and right click > properties - disable.
  5. Repeat the previous step for the 'Domain member: Digitally encrypt secure channel data (when possible)' and 'Domain member: Digitally sign secure channel data (when possible)' items.
  6. RESTART ALL SERVERS (This change will not take effect until the relevant server is restarted.
This should alleviate the problems with locating domain users based on their 'friendly' Netbios name rather than SID's. Without this change you will receive the following error when trying to provide domain account credentials for the farm service account while running the SharePoint configuration wizard:

The username is invalid. The account must be a valid domain account.

In addition, when trying to add a domain account login to the Sql Server instance you will receive the following error:

Create failed for login…Windows NT user or group domain\username not found. Check the name again.

Couldn't find any documentation on the 'net regarding this obscure scenario, so I wanted to share my insight. Disclaimer: I'm not a sys-admin so I cannot comment on the security compromises that this change might introduce.

Posted on 5/12/2010 8:55:00 AM by sterlingt

Permalink | Comments (2) | Post RSSRSS comment feed |

Categories: MOSS 2007 | SharePoint 2007 | WSS 3.0

Tags:

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

"Serious XSS flaw haunts Microsoft SharePoint"

Posted on 5/4/2010 4:39:00 AM by sterlingt

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: MOSS 2007 | SharePoint 2007 | SharePoint 2007 Features | WSS 3.0

Tags:

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

(Another) Method to Achieve Many To Many Relationships with SharePoint Lists

I stumbled onto this free tool recently and thought I would add it as an addendum to my previous posting Many to Many Relationships with SharePoint Lists. The CodePlex tool doesn't simply emulate a many to many relationship like the technique I documented within my previous posting, it actually exports the data to corresponding Sql Server tables which will enforce the relationships. I haven't had a chance to actually experiment with the tool, but the literature indicates it maintains an ongoing synchronization between the originating SharePoint lists and the Sql tables. Obviously there are some potential performance implications with regard to how and when the synchronization occurs, especially when dealing with large lists/tables.

Posted on 4/28/2010 6:41:00 PM by sterlingt

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: MOSS 2007 | SharePoint 2007 | WSS 3.0

Tags:

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Event Handlers/Receivers and (InfoPath) Form Content Types

The notion of being able to attach custom code to a slew of content type events is pretty thrilling. It's like a proverbial extra layer of cream cheese frosting in one's carrot cake, whereby custom behavior can be selectively appended to content types located across multiple libraries within a site collection.

Unfortunately, it appears (to me) that such event receivers are not supported by form content types, or those that are derived from them (such as InfoPath forms). To be clear, the registration of the event receiver to the form content type is successful () as I'm able to see it within the content type's SPEventReceiverDefinitionCollection. However, the overridden methods themselves (I tried the 6 basic ones ItemAdding, ItemAdded, ItemUpdated, ItemUpdating, ItemDeleted, and ItemDeleting) are never actually executed. Registering the same exact event receiver(s) to the form library itself (whose default content type is the aforementioned InfoPath form) will successfully execute the methods.

An inability to register event receivers to the content type of an InfoPath form will severely limit the scalable application potential of such custom functionality. The SDK makes no mention of this exception; neither does the 'Event Troubleshooting' article pertaining to SharePoint event handlers.

In addition, fields promoted to library column values from InfoPath forms (and consequently mapped to their corresponding XML file content) are ReadOnly within event receivers. Unfortunately there is no error attributed to this behavior, the field updates just 'silently fail' - a discovery I made after struggling with updating the values for many hours (and finally confirming the behavior here.

I've posted these issues to both the standard MSDN SharePoint dev forum as well as the MSDN Partner Break/Fix forum, and I'll update this posting with an information I obtain.

A couple of tools and tips that come in handy for working with SharePoint event receivers:
  • http://spm.codeplex.com/releases/view/22762 - This one for viewing the SPEventReceiverDefinitionCollection's of various objects to confirm successful registration.
  • http://www.u2u.info/Blogs/Patrick/Lists/Posts/Post.aspx?ID=1547 - This one for both viewing existing registered event receivers, as well as performing the registration itself. (Note: The tool does not possess a 'Refresh' functionality so be sure to exit and application and re-start it when you've made changes to a receiver and you need to register the new version.)
  • I was never able to update event receiver functionality when using the stsadm 'UpgradeSolution' function, in spite of the fact that I could see the updated .dll within the GAC and I always deleted/re-registered the event receiver. Instead, I had to retract/delete the solution, re-add, re-deploy it, un-register the event receiver, and re-register it.
Ah - SharePoint...never a dull moment.

Posted on 4/28/2010 4:30:00 PM by sterlingt

Permalink | Comments (1) | Post RSSRSS comment feed |

Categories: MOSS 2007 | SharePoint 2007 | WSS 3.0

Tags:

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Making MOSS 2007 and WSS 3.0 play nicely with Adobe Acrobat PDF Documents


Seeing any of the following behavior when interacting with PDF documents within SharePoint?
  • The document could not be opened for editing. A Windows Sharepoint Services compatible application could not be found to edit the document.
  • There was an error opening this document. The file cannot be found.
  • Missing/blank icon for PDF documents
Add this line to one-liner to your DOCICON.XML document (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML):
<Mapping Key="pdf" Value="pdf.gif" OpenControl="SharePoint.OpenDocuments"/>

And put the corresponding pdf.gif image in the SharePoint IMAGES directory (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES).

If users are annoyed by the in-browser method with which PDF documents are opened, that setting must be changed via the Adobe Reader application itself - Edit > Preferences > Internet, uncheck the 'Display PDF in browser' box.

Posted on 4/2/2010 6:34:00 AM by sterlingt

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: MOSS 2007 | SharePoint 2007 | SharePoint 2007 Features | WSS 3.0

Tags:

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5