Cannot Create ShrePoint Search Service Application for SP2013

Hi All,
Thanks in advance for any help you may provide.
While Creating a new search service application i have received the following error:
Errors were encountered during the configuration of the Search Service Application.
System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated. Parameter name: sddlForm at System.Security.AccessControl.RawSecurityDescriptor.BinaryFormFromSddlForm(String sddlForm) at System.Security.AccessControl.RawSecurityDescriptor..ctor(String
sddlForm) at Microsoft.SharePoint.Win32.SPNetApi32.CreateShareSecurityDescriptor(String[] readNames, String[] changeNames, String[] fullControlNames, String& sddl) at Microsoft.SharePoint.Win32.SPNetApi32.CreateFileShare(String name, String description,
String path) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.CreateAnalyticsUNCShare(String dirParentLocation, String shareName) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionAnalyticsShare(SearchServiceApplication
serviceApplication) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.CreateDefaultStoreLocation(SearchServiceApplication serviceApplication) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionRawEventStore(SearchServiceApplication
serviceApplication) at
The Fix with Sharing the Analitics_GUID Folder doesn't work, because it creates every Time a new one.
I really appreciate if you could give me a help.
Regards!
Martin

Hi all,
Thank you very much for your Response.
I have resolve this Issue yesterday, but didn't have time to answer.
I have tried everything (Create over Powershell and GUI) and as I say the fix with Analitics_GUID dont work. I have give everyone Full Controll on the hole Office Folder and Sub-folders.
I have look with the Reflector in the Code that causes the Exception and find that the SDDL string need some format in
that has an Domain Account and not Local Account. I mean some SID Domain ids.
So there is no way to create an "Complete" Installation ( not Standalone) without having a Domain. It is possible but you cannot create Search Service App and some
other Components didn't work as expected.
My Software was:
Windows Server 2012 Datacenter
SQL Server 2012 Enterprise with SP1
SharePoint 2013 Enterprise
So I created a "local" domain an it works.
Thank you very much
Regards
Martin

Similar Messages

One Search service application for multiple web applications in a single server

We are planning to host 17 Web applications in a single Server. Do I need to create search service application for each web application or I need to create one Search service application , create a Content source for each web
application and create a Result source for filtering. Which is the best approach. And which approach takes more RAM memory.
In my application I am using Search web part, "Recently Changed Items", "Popular Items" web parts. when I created only one one Search Service application for all web applications and using Result sources ,
I am not getting the results. What could be the problem.

Hi,
One SSA is ok, but you should think about access rights. If the access is clear cut between all the web apps you should be ok with one SSA. Multiple result sources limiting on content source also works, but could easily be bypassed.
Multiple SSA's will eat up RAM/CPU like a mother :)
As for popular etc.. it could be due to how those sources are set up, but haven't investigated or tested this much.
Thanks,
Mikael
Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
http://techmikael.blogspot.com/
Author of Working with FAST Search Server 2010 for SharePoint

Create SharePoint 2010 Search Service Application Using Powershell

Hi Team,
Could you please assist me in completing the search service application for
two server using powershell. Both the servers will be running all the component
Version SharePoint 2010
# 1.Setting up some initial variables.
write-host 1.Setting up some initial variables.
$SSAName = "Search Service Application"
$SVCAcct = "Domain\ServiceAccount"
$SearchAppPoolName ="DefaultAppPool"
$SSI = get-spenterprisesearchserviceinstance -local
$err = $null
$SSADBName="Search_AdminDB"
$SSADBServer="DBServer"
$host1="Server1"
$host2="Server2"
# Start Services search services for SSI
write-host Start Services search services for SSI
Start-SPEnterpriseSearchServiceInstance -Identity $SSI
# 2.Create an Application Pool.
write-host 2.Create an Application Pool.
#$AppPool = new-SPServiceApplicationPool -name $SSAName"-AppPool" -account $SVCAcct
$AppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
# 3.Create the SearchApplication and set it to a variable
write-host 3.Create the SearchApplication and set it to a variable
$SearchApp = New-SPEnterpriseSearchServiceApplication -DatabaseServer $SSADBServer -Name $SSAName -applicationpool $AppPool -databasename $SSADBName
#4 Create search service application proxy
write-host 4 Create search service application proxy
$SSAProxy = new-spenterprisesearchserviceapplicationproxy -name $SSAName"ApplicationProxy" -Uri $SearchApp.Uri.AbsoluteURI
# 5.Provision Search Admin Component.
write-host 5.Provision Search Admin Component.
set-SPenterprisesearchadministrationcomponent -searchapplication $SearchApp -searchserviceinstance $SSI
# 6.Create a new Crawl Topology.
write-host 6.Create a new Crawl Topology.
$CrawlTopo = $SearchApp | New-SPEnterpriseSearchCrawlTopology
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
Source:blog.MSDN Author- Russ Maxwell
Thanks Basva

Could you please assist me in completing the search service application for
two server using powershell. Both the servers will be running all the component
Hi Basva,
Do you want to provision two search service applications in single farm?
Commonly, only one search service application is needed in a farm for Search function.
Here are articles for detail information about how to provision search service application using powershell:
http://blogs.msdn.com/b/jjameson/archive/2011/02/28/powershell-script-to-configure-search-in-sharepoint-server-2010.aspx
http://blogs.msdn.com/b/russmax/archive/2009/10/20/sharepoint-2010-configuring-search-service-application-using-powershell.aspx
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

How to create Search Service Application in SharePoint 2013

When I am Creating Search Service Application through SharePoint Central Administration I am getting the error:
Path of how I created It:
Central Administration->Application Management->Manage Service Applications
Here Click on New and Select Search Service Application
How Should I create new search service application?
As I want to create crawled Property and manage property for Search Center in SharePoint On Premises.

Hi darsh,
For creating a new search service application, you can refer to the blog:
http://technet.microsoft.com/en-us/library/gg502597.aspx
http://blogs.technet.com/b/praveenh/archive/2013/02/07/create-a-new-search-service-application-in-sharepoint-2013-using-powershell.aspx
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378
For your issue , please refer to the article:
http://praveensharepointknowledgebase.wordpress.com/2012/05/29/error-while-creating-search-service-application/
Best Regards,
Eric
Eric Tao
TechNet Community Support

Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Technical Support Details:
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
as well as:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
Search Administration page, the "System Status" shows the following message:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
try again
Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
running.
Does anyone know how I can resolve this problem?
Thanks!

Hi Joaquin,
According to your description, the error occurred when you re-created the Search Service Application.
Based on the error message, I recommend to verify the things below:
   1. Check if the association between the Search Service Application proxy and the web application is configured.
Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
   2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
    3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Unable to create Search Service Application

Hi All,
When I tried to create Search Service Application in Central Admin, I'm getting Error on creation. The below is the detail error.
Errors were encountered during the configuration of the Search Service Application.
Microsoft.SharePoint.SPException: The timer job completed, but failed on one or more machines in the farm. at Microsoft.SharePoint.Administration.SPTimerJobAsyncResult.End()
at Microsoft.SharePoint.Administration.SPServiceApplication.ProvisionInstances() at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Provision() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision() at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.b__22()
at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.UpdateIgnoreSPUpdatedConcurrencyException(String description, SearchAdminUtilsUpdateDelegate updateDelegate, SearchAdminUtilsRefreshObjectDelegate refreshObjectDelegate) at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.CreateSearchApp()
at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication() at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
5/2/2011 11:49:08 AM
Could any body guide, where I'm missing?.
Thanks
When I looked in EventViewer for more error details, the below is the error message.
Access to 'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied
any ideas?.

It doesnt work.
I Stopped the search service and then try to receate the Search sercie application with the gui. In the log I get the same error.
SearchConfigWizardFinish page failed with exception. System.InvalidCastException: Unable to cast COM object of type 'Microsoft.Office.Server.Search.Administration.MSSITLB.CGatheringManagerClass' to interface type 'Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherManagerAdmin3'.
This operation failed because the QueryInterface call on the COM component for the interface with IID '{0FF1CE14-013A-0000-0000-000000000000}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
Server stack trace:      at Microsoft.Office.Server.Search.Administration.Gatherer.get_AdminObject()     at Microsoft.Office.Server.Search.Administration.Gatherer.ProvisionGlobalProperties()
at Microsoft.Office.Server.Search.Administration.Gatherer.Provision()     at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision()     at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.DeployLocalServiceInstance[T](T
localSearchServiceInstance)     at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.Create(AbstractSearchConfigWizard wizardOM)     at Microsoft.Office.Server.Search.Internal.UI.SearchConfigWizardFinish.ExecuteConfigurationTimerJob(SPLongOperationState
longOperationState, String& strRedirectPage)     at Microsoft.SharePoint.SPStatefulLongOperation.SetThreadCultureAndRun(RunStatefulOperation runOperation, SPLongOperationState state, CultureInfo culture, CultureInfo uICulture)
at Microsoft.SharePoint.SPStatefulLongOperation.<>c__DisplayClass6.<Run>b__0(Object state)     at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state)     at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)     at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Exception
rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)     at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData&
msgData)     at System.Threading.WaitCallback.EndInvoke(IAsyncResult result)     at Microsoft.SharePoint.Utilities.SPThreadPool.RunAsyncWorkItem(ImpersonatedCallbackParam param, TimerCallback timerCallback, Object timerState,
Int32 timerPeriod)     at Microsoft.SharePoint.Utilities.SPThreadPool.RunAsyncWorkItemWithImpersonation(WaitCallback workItemCallback, Object workItemState, TimerCallback timerCallback, Object timerState, Int32 timerPeriod)
at Microsoft.SharePoint.SPStatefulLongOperation.Run(RunStatefulOperation runOperation)     at Microsoft.Office.Server.Search.Internal.UI.SearchConfigWizardFinish.<>c__DisplayClass2.<Commit>b__0(SPStatefulLongOperation longOperation)

Error "Unable to load word breaker for locale 0. Error code 8007007e." with search service application.

I recreate the Search service application and the default Content source stayning in the 'Recovering' status.
The log give multiple error 'Unable to load word breaker for locale 0. Error code 8007007e.'
The default language is English and the reference in registry for word breaker dll is naturallanguage1.dll but I found only the naturallanguage6.dll.

Hi,
For your issue, check your current language settings and ensure that search supports the current language.
On the SharePoint Server open Registry Editor (Start -> type “Regedit” and hit enter).
Point to : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeServer\14.0\Search\Setup\ContentIndexCommon\LanguageResources\Default\English
Under the registry key for each of the languages there is a value called StemmerDLLPath and WBDLLPathOverride
Updated the registry entry with NATURA~1.dll to NATURA~2.dll
Point to Start -> Administrative Tools -> Services, right click on SharePoint Server Search 14 and click on Restart.
Performed a Full Crawl and wait for the Full Crawl to complete and try searching again.
For more detailed information, refer to the following blogs:
http://blog.ithinksharepoint.com/2008/04/20/a-word-breaker-was-not-found-for-the-given-language-error-when-crawling-content/
http://www.sharepoint2013.me/Blog/Post/175/Word-breakers-in-SharePoint-2013
Best Regards,
Lisa Chen
Lisa Chen
TechNet Community Support

Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
Thanks a lot.

Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks.

The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'GUID′ in search application 'Search Service Application' is in a good state and try again.

Another post with a well-known title. Believe me, I know. Here's my setup;
- 1 Server 2012 WFE, SharePoint Server 2013, totally up-to-date, including the september 2014 hotfix
- 1 Server 2012 DB, SQL Server 2012
Installed SP 2013 using PowerShell, with the AutoSPinstaller. Worked like a charm. Got everything up and running, with some tweaking here and there to customize it to fit my situation. Now, I can't get the Search Service Application to work. Must have created,
deleted and recreated it at least 30 times. Used both PowerShell scripts, PowerShell line-by-line, Central Admin, heck, I even went so far as to use the configuration wizzard... No luck. I keep on getting the message that search cannot connect to the machine
that hosts the 'administration component'.
In order to avoid answers that suggest all the things I've already tried, here's a summary of the various scenarios I followed:
Tried both a dedicated application pool as well as the SharePoint Web Services Default
Timer job job-application-server-admin-service is running and not showing errors
IIS 8.0 is installed, so is .NET 4.5 (not the known perp of IIS 7.5 and .NET 4.0)
the get-SPEnterpriseSearchServiceInstance -local returns a healthy, online state
the SPEnterpriseSearchQueryAndSiteSettingsServiceInstance is also running
FireWall is disabled; registry has the BackConnectionHostNames modified with the necessary FQDNs
Accounts used to install and / or run the serviceapp all have sufficient rights - tried a dedicated managed account, SP_2013_SearchSvc, the SP admin account, and even the original Farm account; all to no avail, I keep on getting the error message.
Even tried stsadm to start the server search running - NOTHING WORKS!!!
As you might understand, this is driving me nuts. About to miss my second deadline, and no amount of IISresetting is making this go away. Been stuck on this issue for far too long, now (my searching is measured in days and weeks instead of hours, by now).
Whoever helps me solve this - you will have my eternal gratitude, and a nice bottle of Prosecco. Or whatever's your poison. You need to come get it, though. I´m situated in the Netherlands. Hey, you always meant to visit Amsterdam and see for yourself, right?
Thanks, community, for coming to my rescue!

Thanks again - Alas, I've been there. Deleted Search a dozen times, at least, and tried installing it, initially using a PowerShell script (tried several scripts actually, from full-blown total Search Applications with extensive topologies to the most basic
of basics 'please just start without showing me errors'), PowerShell line-by-line to see where things went South, next tried installing through Central Admin (hoping that it was my own stupidity in overlooking things and hoping The System would get it right
for me), and eventually even tried using the config wizzard as a total and utter last resort - Nothing worked.
At first, I found out that removing a Service App needs a *little* bit more work than simply removing it through Central Admin, but by now I can truthfully state that if there's one thing I've become supergood at, it's removing Search Service Applications.Totally.
I will check out the article, though - I realized early on in my SharePoint experience that regardless of what you think you know, there's so much more to find out. I know, that's almost philosophical. That is, my friends, indeed the point I've reached...

SharePoint Search Service Application Restore Is Failing

Issue:
When performing a Search Service restore with the CA UI, the restore is failing. The backup was generated from a Full level backup that is run nightly from the cmdlet Backup-SPFarm. The Farm is running SharePoint 2013 SP1, Windows Server 2012 And SQL
Server 11.0.3128. Both Production and the test environment have the same topology.
The sprestore.log file shows the following error message:
[12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint id for this application is 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928'.
[12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928' to this application.
[12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint has been found and set. NOTE: The id of the default endpoint will be different than specified in the logs if
the restore mode is not 'overwrite'.
[12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'bb456994-47ac-4bad-9197-9a4d5b39bf5c' to this application.
[12/17/2014 12:37:55 PM] FatalError: Object Search Service Application failed in event OnPostRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
        SqlException: The database principal owns a database role and cannot be dropped.
User does not have permission to perform this action.
[12/17/2014 12:37:55 PM] Debug:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj,
Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean
asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout,
Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.Office.Server.Data.SqlDatabaseManager.GrantAccess(String user)
   at Microsoft.Office.Server.Search.Administration.SearchDatabase.GrantAccess(String username, String role)
   at Microsoft.Office.Server.Search.Administration.SearchDatabase.SynchronizeAccessRules(SearchServiceApplication searchApp)
   at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.SynchronizeDatabases()
   at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision()
   at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPostRestore(Object sender, SPRestoreInformation info)
A SQL Profile was run beginning at 12/18/2014 11:11.
A SQL exception can be found at 11:20:03 with the error:
               The database principal owns a database role and cannot be dropped.
The issue has to do with the SQL statement just prior to the exception:
declare @p4 int
set @p4=NULL
declare @p5 int
set @p5=NULL
exec sp_executesql N'declare @db_user_name sysname
select @db_user_name = name from dbo.sysusers where sid = SUSER_SID(@user_name) and hasdbaccess = 1
if (@db_user_name is null)
begin
if exists(select * from dbo.sysusers where name = @user_name)
exec @revoke_result = sp_revokedbaccess @user_name
exec @grant_result = sp_grantdbaccess @user_name, @db_user_name output
end',N'@user_name nvarchar(128),@revoke_result int output,@grant_result int output',@user_name=N'----\sp2013uatfarmacct',@revoke_result=@p4 output,@grant_result=@p5 output
select @p4, @p5
I highlighted the row in red causing the issue. For some reason SharePoint during the Search Restore process try’s to delete the user “------\sp2013uatfarmacct” from the database Search_Service_Application_DB_60bb9889222841aa94f59aed71349a6b
And re-add them again. But the reason for the failure is because the user “------\sp2013uatfarmacct” is the owner of the database role “SPSearchDBAdmin”, so it cant.
I checked all other Service databases that contain the role SPSearchDBAdmin and they all correctly have the owner as dbo
NOT ------\sp2013uatfarmacct.
Further checking the SQL trace log a SQL batch is executed at 12/18/2014 11:19:59.790 that states the following:
-- Drop existing role members
IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
Begin
    DECLARE @RoleMemberName sysname
    DECLARE Member_Cursor CURSOR FOR
    SELECT [name]
    FROM sys.database_principals
    WHERE
        principal_id IN
            SELECT member_principal_id
            from sys.database_role_members
            where role_principal_id in (
            select principal_id
            FROM sys.database_principals where [name] = N'SPSearchDBAdmin' AND type = 'R' ))
    OPEN Member_Cursor;
    FETCH NEXT FROM Member_Cursor
    into @RoleMemberName
    WHILE @@FETCH_STATUS = 0
    BEGIN
        exec sp_droprolemember @rolename=N'SPSearchDBAdmin', @membername= @RoleMemberName
        FETCH NEXT FROM Member_Cursor
        into @RoleMemberName
    END;
    CLOSE Member_Cursor;
    DEALLOCATE Member_Cursor;
End
-- Drop/Create role
IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
DROP ROLE [SPSearchDBAdmin]
CREATE ROLE [SPSearchDBAdmin]
I highlighted the statement in red that is eventually causing the SP restore to fail. For some unknown reason to me when this statement is executed the new ROLE SPSearchDBAdmin owner is -----\sp2013uatfarmacct
instead of dbo.
As a test I executed via SQL Management Studio “CREATE ROLE [SPSearchDBAdmin]” and it correctly created the owner as dbo.
So the problem and my question is why when the SP Search Service is restored is the ROLE SPSearchDBAdmin owner being set to “-----\ sp2013uatfarmacct”, which in turn seems to be causing the restore failure?

Hi!
I believe it is trying to delete a user who owns the schema of the database. You can try changing the schema owner to some other user like "dbo", and then drop the first user.
Below are a few links that can help you with much more details.
http://blogs.technet.com/b/mdegre/archive/2010/12/19/the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped.aspx
http://littletalk.wordpress.com/2009/11/09/fix-for-the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped-error-in-sql-server-2005/
http://dotnetgun.blogspot.com/2011/02/database-principal-owns-schema-in.html
Thanks,
Owens
Owens G. Jesse

Error: Create new Self-Service application with FPM

Hi,
I'm creating a new self-service application using FPM. I ran into this error when launching the application:
[email protected]385c385c
Any help would be much appreciated. Thanks.
- julius

Hi,
According to your error message, it can be caused by the search service application cannot set up a network share for every query component where the crawlers can dump their data.
For troubleshooting your issue, please make sure the Server service in Services.msc is started, and your account is a member of WSS_WPG group and WSS_WPG group has full control permission on C:\Program Files\Microsoft Office Servers\15.0\Data\Office
Server\Applications(if using default locations).
For more information, you can refer to the blog:
https://social.technet.microsoft.com/Forums/sharepoint/en-US/0762de1a-f9df-4a9a-bc7c-5cb26009435f/sharepoint-2010-search-service-application-stuck-in-initializing-status?forum=sharepointadminprevious
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Getting error while editing content source of search service application

Hi,
when i edit the content source of SharePoint Search Service Application and click on OK Button then i get the following error.
Error it gives : An item with the same key has already been added.
and when i check it in ULS log it gives this.
Application error when access /_admin/search/editcontentsource.aspx, Error=An
item with the same key has already been added. Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version,
FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs,
TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
at [0]:
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]:
An item with the same key has already been added.   Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version,
FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs,
TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
at [0]:
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Getting Error Message for Exception System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: An
item with the same key has already been added. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.ArgumentException: An
item with the same key has already been added.
at Microsoft.Office.Server.Search.Administration.SearchApi.WriteAndReturnVersion(CodeToRun`1 remoteCode, VoidCodeToRun localCode, Int32 versionIn)
at SyncInvokeEditContentSource(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&
rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
Can anyone please help me, how can i resolved this issue.i am stuck :(
Thanks in advance
Muhammad Luqman

Also tried with this code, but no succeed.
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
$searchapp = Get-SPEnterpriseSearchServiceApplication "Search Service Application"
$StartAddresses = "http://insite"
$cs = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -identity "Local SharePoint sites"
$cs | Set-SPEnterpriseSearchCrawlContentSource –StartAddresses $StartAddresses
I have now only single content source and all others are removed now but still getting same error.
Muhammad Luqman

Sharepoint foundation 2013 Search Service Application.

Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks in advance for help.

Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Cannot create JDBC driver of class '' for connect URL 'null'

HI,
Can any one help why i am getting the below error:
Cannot create JDBC driver of class '' for connect URL 'null'
The Error Stack Trace is:
Cannot create JDBC driver of class '' for connect URL 'null'
java.lang.NullPointerException
    at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcDriver.knownURL(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcDriver.acceptsURL(Unknown Source)
    at java.sql.DriverManager.getDriver(Unknown Source)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1437)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1371)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
    at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCConnection.Open(Unknown Source)
    at com.crystaldecisions.reports.queryengine.JDBConnectionWrapper.Open(SourceFile:123)
    at com.crystaldecisions.reports.queryengine.Connection.br(SourceFile:1786)
    at com.crystaldecisions.reports.queryengine.Connection.bs(SourceFile:505)
    at com.crystaldecisions.reports.queryengine.Connection.t4(SourceFile:3020)
    at com.crystaldecisions.reports.dataengine.dfadapter.DFAdapter.a(SourceFile:697)
    at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.a(SourceFile:309)
    at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.long(SourceFile:264)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1150)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:660)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:166)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:528)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:526)
    at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:524)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:423)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:351)
    at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
    at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
    at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
    at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
    at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
    at com.crystaldecisions.sdk.occa.report.application.ds.a(SourceFile:186)
    at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(SourceFile:878)
    at com.crystaldecisions.sdk.occa.report.application.ReportSource.getPromptDatabaseLogOnInfos(SourceFile:815)
    at com.crystaldecisions.sdk.occa.report.application.AdvancedReportSource.getPromptDatabaseLogOnInfos(SourceFile:338)
    at com.businessobjects.report.web.a.e.a(SourceFile:174)
    at com.businessobjects.report.web.a.e.a(SourceFile:97)
    at com.businessobjects.report.web.a.e.a(SourceFile:343)
    at com.businessobjects.report.web.a.t.a(SourceFile:1726)
    at com.businessobjects.report.web.event.bw.broadcast(SourceFile:97)
    at com.businessobjects.report.web.event.am.a(SourceFile:53)
    at com.businessobjects.report.web.a.t.if(SourceFile:2104)
    at com.businessobjects.report.web.e.a(SourceFile:300)
    at com.businessobjects.report.web.e.a(SourceFile:202)
    at com.businessobjects.report.web.e.a(SourceFile:135)
    at com.crystaldecisions.report.web.ServerControl.a(SourceFile:607)
    at com.crystaldecisions.report.web.ServerControl.processHttpRequest(SourceFile:342)
    at org.apache.jsp.CrystalReport_jsp._jspService(CrystalReport_jsp.java:205)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1023)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Cannot create JDBC driver of class '' for connect URL 'null'
java.lang.NullPointerException
    at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcDriver.knownURL(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcDriver.acceptsURL(Unknown Source)
    at java.sql.DriverManager.getDriver(Unknown Source)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1437)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1371)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
    at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCConnection.Open(Unknown Source)
    at com.crystaldecisions.reports.queryengine.JDBConnectionWrapper.Open(SourceFile:123)
    at com.crystaldecisions.reports.queryengine.Connection.br(SourceFile:1786)
    at com.crystaldecisions.reports.queryengine.Connection.
Thanks
Penchal

HI Shailendra,
I think your expecting code. The Code is as follows. and also for few reports i am getting Unexpected Database Error help me in this also
if(reportName != null && !"".equals(reportName) && reportSource==null){
        //Initializing report
        ReportClientDocument boReportClientDocument = new ReportClientDocument();
        boReportClientDocument.open(reportName, 0);
          Fields<IParameterField> parameterFields = boReportClientDocument.getDataDefController().getDataDefinition().getParameterFields();
          System.out.println("Param Fields Size:"+parameterFields.size());
     if (parameterFields.size() > 0) {
        ParameterFieldController paramController = boReportClientDocument.getDataDefController().getParameterFieldController();
        for (int i = 0; i < parameterFields.size(); i++) {
            String paramName = parameterFields.getField(i).getName().trim();
            System.out.println("                    -          "+paramName);
            if(request.getParameter(paramName) != null) {
                paramController.setCurrentValue("", paramName, request.getParameter(paramName));
                System.out.println(paramName+":"+request.getParameter(paramName));
            }else {
                System.out.println("Param is Null:"+paramName+":"+request.getParameter(paramName));
                paramController.setCurrentValue("", paramName, "");
    reportSource = boReportClientDocument.getReportSource();
    //session.setAttribute("ReportSource", reportSource);
    boReportClientDocument.close();
    CrystalReportViewer crystalReportViewer = new CrystalReportViewer();
    crystalReportViewer.setName(reportName);
    crystalReportViewer.setOwnPage(true);
    crystalReportViewer.setBestFitPage(true);
    crystalReportViewer.setToolPanelWidth(0);
    crystalReportViewer.setHasToggleParameterPanelButton(false);
    crystalReportViewer.setHasToggleGroupTreeButton(false);
    crystalReportViewer.setReportSource(reportSource);
    crystalReportViewer.setEnableDrillDown(false);
            crystalReportViewer.processHttpRequest(request, response,getServletConfig().getServletContext(),null);
Thanks
Penchal

Upgrade Search Service Applications

Is there any reason why we want to upgrade the service applications (using database attach) like secure store, user profile, search service.. rather than re-creating them manually? We are trying to upgrade from SP 2010 to SP 2013 and was stuck
figuring out how to go with service applications.
Thanks in advance.

Hi AparnaT,
There are six service applications that we can be upgraded: business data connectivity, performance point service, search service, user profile service, managed meta data web service and secure store service.
All of them have databases which contains many important data. Such as the Business Data Connectivity service uses a database to store information about external data, the Managed Metadata service uses a database to store metadata information, the Search
service application Administration database contains settings for the Search service application such as content sources, crawl rules, start addresses, server name mapping, and federated locations, the
User Profile service uses databases to store profile, social, and sync information. So we need to upgrade the service applications rather than re-creating them manually.
Reference:
http://technet.microsoft.com/en-us/library/ee731990(v=office.15).aspx
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Cannot Create ShrePoint Search Service Application for SP2013

Similar Messages

Maybe you are looking for