Hi All, I have installed SharePoint Foundation 2013 on my Windows 2012 standard server, as a prerequisite to installing FIMs.

Exchange 2013 was previously installed on this server and so some fiddling was required to alter the bindings in IIS after the SharePoint install. Fine moving on....

The SharePoint installed MS SQL Server 2008 R2 and completed.

When I attempt to install FIMs, and point it to the sharepoint instance, it complains that SQL Server Full-Text Search component is not installed.

After several attempts using various methods install, I am unable to figure out how to get that SQL component installed.

Even if I copy over the SQL Server 2008 installation files locally and run setup, the component is not available for install.

Tried also running SharePoint.exe again however the option to add that component was not available.

What am I missing?

Thanks very much

Andy

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial 13 hours 47 minutes ago

You need to add the FullText indexing feature in SQL Server installation.

Just run install again, and when you hit reach the Feature Selection screen, add the checkbox on the

• Database Engine Service
  
  
  • Full-Text Search

  https://technet.microsoft.com/en-us/library/ff512684(v=ws.10).aspx

Yes you are right, you can not install FIM on a Express Edition of SQL.

You can install the Full SQL side by side with a Express Edition and select Full-Text search in the setup.

This will not harm your Sharpoint installation.

However since you are in the install phase I would recommend to also reinstall SharePoint Foundation also use full SQL Server for that and let Sharepoint not install SQL Express.

/Peter

I am sorry, I did not read carefully.  Peter is right. 

Here are the requirements.

https://technet.microsoft.com/en-us/library/ff512684(v=ws.10).aspx

I will give it a try now thanks and let you know.

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial Monday, July 27, 2015 5:36 PM

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial Monday, July 27, 2015 5:36 PM

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial Monday, July 27, 2015 5:36 PM

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial Monday, July 27, 2015 5:36 PM

It would appear from the following thread, that SharePoint installs SQL Express version, which does not have full-text search abilities.

https://social.technet.microsoft.com/Forums/en-US/5d192dcf-cd21-4c5c-8246-1ef69023c483/installation-of-fulltext-search?forum=sqldatabaseengine

This FIMS installation is frustrating to say the least.

And this next thread suggests I have to remove SQL express and install SQL full edition.

What happens to SharePoint 2013 after that? Would I have to re-install that as well?

https://social.technet.microsoft.com/Forums/en-US/a217f7d1-5e56-4dd5-832b-d19545ab00d2/add-full-text-search-to-sql-express-2008-install?forum=sqlexpress

Thanks

• Edited by AndySpecial Monday, July 27, 2015 5:36 PM

Abandoning the install of FIM on the Exchange server itself.

Will create a new 2012 Windows Standard server (vm) and install SQL 2012 Std, then SharePoint 2013, and then FIMs.

I can not professionally express my frustration at how ridiculously complicated this is.

I can only hope that it will go smoother on a new server.

I will respectfully disagree with you.
The pre-requisites are pretty clear, and as a rule of thumb, most enterprise applications do not run on Express Edition.

Microsoft gives the Express Edition for free and if their applications did work on it, no one would by SQL licenses. :)

Thanks Nosh. To clarify it is the FIMS install I find frustrating.

As an update, the install of SQL 2012 (with Full Text Search) and SharePoint 2013 went smoothly on the new 2012 Std VM.

Now I have returned to the FIM Prerequisites and Verifications Steps and am hitting a wall again.
Perhaps you can lend some advice on the first of the four steps.

This is the same error I had on the prior server, where I abandoned the install.
I suspected the problem was trying to put too many services on the one server and having to fiddle with all the bindings... apparently not...I have the same error as before.

Installing FIM 2010 R2 on SharePoint Foundation 2013
https://technet.microsoft.com/en-us/library/jj863242(v=ws.10).aspx

Step1)  The SharePoint 2013 site collection runs in 2010 experience mode.
To verify, in the SharePoint 2013 Management command-line shell, enter the following commands and verify that the return value is 14: 

• $spSite = SpSite("http://www.contoso.com");
• $spSite.CompatibilityLevel

... I run this command in the SharePoint 2013 Mgmt shell.... note .. I called my server FIMS... and the URL I used is the Hone - Central Admin site.

PS C:\> $spSite = SpSite ("http://fims:47823/default.aspx")
SpSite : Cannot find an SPSite object with Id or Url:
http://fims:47823/default.aspx.
At line:1 char:11
+ $spSite = SpSite ("http://fims:47823/default.aspx")
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...SPCmdletGetSite:
   SPCmdletGetSite) [Get-SPSite], SPCmdletPipeBindException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetSite

Ok so I try the domain name....

PS C:\> $spSite = SpSite ("http://camis.local")
SpSite : Cannot find an SPSite object with Id or Url: http://camis.local.
At line:1 char:11
+ $spSite = SpSite ("http://camis.local")
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...SPCmdletGetSite:
   SPCmdletGetSite) [Get-SPSite], SPCmdletPipeBindException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetSite

What on earth am I doing wrong?

Thanks

Hard to tell what you have done wrong, but

Make sure SQL is compliant and SharePoint is really configured in 2010 mode.

Thanks Nosh,

Please explain what you mean by 'make sure SQL is compliant' ...with what?

and as for the second part... 'and SharePoint is really configured in 2010 mode'... Nosh I am trying to set it to 2010 mode as per the TechNet article.

So telling me to make sure it is really in 2010 mode, does not help me set it to be so.

Can anyone else weigh in please?

Thanks very much

Andy

Andy? What I mean is for sql to be the 2008sp1 or better and have he fulltext installed. Sharepoint to follow the steps on ghe guide you posted. If you are 100% aure you have done all that properly, then what step is falling, what component are you installing when it faills. Dis you install fim synchronization piece yet? Seems to me you are trying to install fim portal and have not installed fim synchronization service

Nosh, pardon me for saying this.... but you need to read what I post a bit more closely. Either that or I am not explaining myself very well. Maybe a mixture of both.

I indicated I had installed SQL 2012 with full text search, and SharePoint 2013 on a Windows 2012 server.

I also indicated I was trying to perform the SharePoint pre-requisites before installing FIMS.
I even provided the TechNet document to show what I was doing.

Anyways... I figured out what the SharePoint 2013 Mgmt shell was asking for....the correct site name:

PS C:\ > $spSite = SpSite(http://fims)  (note: FIMS is my server name)
PS C:\ > $spSite.CompatibilityLevel  15
PS C:\ > $spSite.CompatibilityLevel = 14 'CompatibilityLevel' is a ReadOnly property.

At line:1 char:1
+ $spSite.CompatibilityLevel = 14
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

The TechNet article indicates to use the full domain name in their example.
Seems only the server name is actually required.

Now I am stuck as it appears the property is read only.

If you are still willing to guide me, please do advise.

Many thanks

Andy,

Will all due respect, you have been all over the place and presented contradicting statements.

On your original post you wrote "When I attempt to install FIMs, and point it to the sharepoint instance, it complains that SQL Server Full-Text Search component is not installed."  And then you said that after trying on a fresh server you had the same issue, "Now I have returned to the FIM Prerequisites and Verifications Steps and am hitting a wall again.
Perhaps you can lend some advice on the first of the four steps.This is the same error I had on the prior server, where I abandoned the install. "

And lastly you said this, "I indicated I had installed SQL 2012 with full text search, and SharePoint 2013 on a Windows 2012 server. I also indicated I was trying to perform the SharePoint pre-requisites before installing FIMS. " In this statement you say you have installed SharePoint and yet you are having issues with installing Pre-Requisites for FIM (By the way it is called FIM (Forefront Identity Manager 2010), not FIMS).

It is your responsibility to make it as clear as possible and not accept the community to read between the lines or try to guess your issue.

So, please try to make this clear.  Perhaps create a new thread, since most people will be ignoring this one now, so you can get some attention.  Take the time to make the case clear and see how we can help.

Hi Nosh, thank you for your feedback and yes I will start a new thread, as my original question was answered.

I really saw no problem with calling my server FIMS instead of FIM. It just rolls off the tongue better.