SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Tuesday, May 24, 2011

Windows 2008 R2 Has No SMTP!

Yes - you probably have found this out by now - not reallly sure why Microsoft decided to leave it out (maybe to get you to buy Exchange) but if you are doing SharePoint or other type of app that needs SMTP (and you don't have Exchange) you are stuck...however, there is a quick solution.

Follow these instructions: http://technet.microsoft.com/en-us/library/cc772058(WS.10).aspx

Also, Visendo makes a free SMTP Extender for Windows 2008 - you can find it here:

http://www.visendo.com/en/default.aspx

Friday, May 20, 2011

SharePoint 2007 with SQL 2008 Not indexing all content

Having trouble with 2008 Search and SharePoint 2007 not indexing all your content? The problem might be that you are missing the Microsoft Filter Pack - Here's your answer:

http://support.microsoft.com/?id=946336

Thursday, May 12, 2011

SharePoint 2007 Error On Database Attach - SPContentDatabase has been upgraded

Trying to upgrade/move a MOSS Farm using the database attach you recieve the message:

The specified SPContentDatabase has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object

But you say, it's the same version or may you did the Slipstream process w/SP2 already and it worked fine?

If you've not run the WSS and MOSS SP2's, do so and it will fix the problem. If you used the Slipstream process outlined by Microsoft - surprise, it's not clear from the document you need to do BOTH WSS and MOSS - install WSS V3.0 SP2 and you'll be off and running.

Friday, May 6, 2011

SharePoint not getting correct Domain name in User Profile Service

Came across this issue with a client in which the internal name of the domain was being loaded into User Profiles - as in internal\name instead of domain\name; forgot where I got to a post about this so I am reposting here.

The reason for the issue is that the NetBIOS Domain Names are not imported by default, thus internal\. There is a fix through Powershell however if you have just discovered this, here are some tips:

1) If you have already imported but have just installed, drop the User profile service and recreate - the change below MUST BE DONE BEFORE YOU IMPORT!

2) If My Sites are active, you cannot do drop the UPS so you that so you will to rely on running the full import a few times to get it right (I've had difficulties with this working everytime)

Login to the server running Central Administration using the SharePoint Farm Account then go to Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell - when the Powershell window opens, enter in the following command:

Get-SPServiceApplication
  (List of Service Applications and their Id's (GUIDS))

Locate the User Profile Service and copy the GUID under the Id column then enter:

$UPA = Get-SPServiceApplication –Id <GUID of User Profile Service Application>
$UPA.NetBIOSDomainNamesEnabled=1
$UPA.Update()

When done, return to Central Administration/User Profile Service and start the import, all should be well.

Tuesday, May 3, 2011

SharePoint, UAG and SharePoint Search

If you have difficulties getting the SharePoint Crawl to work under UAG and recieve SSL related errors in the crawl log, the problem may be your content source. Since the certificate for SSL is on the UAG server and not on the SharePoint server, Search cannot work with an HTTPS address (thus crawl fails).

Open up your content source and verify that the site URL's specified do NOT include https - drop your indexes and start a full crawl.