SharePoint 2013 - SQL Server BCS Model Incremental Crawl content doesnt show up in Search results

SharePoint 2013 - SQL Server BCS Model Incremental Crawl content doesn't show up in Search results, Incremental crawl is working fine, i.e., its picking up newly added records in table to the Search, but the newly added content is not available in search
results page.
But when i do a Full Crawl, search results are showing up with appropriate content.
What could be the issue here?
Suresh Kumar Udatha.

This time on the Full crawl I got only 62 warnings and 12 errors and ~537.000 success. Warnings were about truncating the crawl documents because their content length exceed the configured for crawl. The 12 errors were "Processing this item failed because
of a timeout when parsing its contents." and "The content processing pipeline failed to process the item.". I think 12 errors is not much to re-execute full crawl. Site collection has one SP Site Group (with Read Permission Level). In this site group I have
only one AD Group added, so permission change is not a possible reason for re-crawl, plus nobody changed anything in this ad group. All documents are stored in 2 document libraries and there are no sub-sites. I want to access these documents trough search
(custom managed property restriction kql) but this way I have no mechanism to fast re-crawl only error documents from the first full-crawl (those 12). This is very strange and put SP 2013 Search almost unusable for my scenario.
Thanks,
Darko
Darko Milevski http://mkdot.net/blogs/darko/

Similar Messages

SharePoint 2013 SQL Server Edition for BI Features - must be on SharePoint SQL Server?

I need to install SQL Server 2012 for a new SharePoint 2013 installation.
Let's say I want to use the BI features of SharePoint 2013 like PowerView.
I already have a separate SQL Server running SQL Server 2012 BI Edition that is used as the database server for our data warehouse and some apps. But this SQL Server will not be used to house the SharePoint 2013 databases.
Do I need to install SQL Server 2013 BI Edition on the SharePoint 2013 SQL Server (where the SharePoint 2013 databases will be housed) or can I used SQL Server 2013 Standard Edition on that server and utilize the BI Edition on the data warehouse server to
use the BI features of SharePoint?

Yes, BI or Enterprise must be installed on the SharePoint server in order to integrate SSRS. PowerPivot can be on a separate server with just a download (http://www.microsoft.com/en-us/download/details.aspx?id=35577) for certain components residing on
the SharePoint server. This will give you PowerView, as well.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 + SQL Server 2008 vs 2012

I am trying to determine the best course of action when building a new SharePoint 2013 Enterprise Farm. Should we use SQL Server 2008 R2 or SQL Server 2012? I have found some information online, but I wanted to know if there were more pros and cons to SQL
2012 over 2008. Can anyone tell me if my short list is adequate enough? Also, are there any integration concerns with other applications that I may need to look out for by using SQL 2012 that don't exist in SQL 2008?
The list of benefits of SQL 2012 over SQL 2008 I know of include:
AlwaysOn
Read-Only Secondary
Contained Database
ColumnStore Indexes
Shredded Storage
PowerPivot BI
Reporting Services BI
Are there any negatives to using SQL 2012?
Thanks,
Alex

Alex,
The only negatives I have seen are
1. You must be careful that the AOAG configuration is supported. For many cases like the config DB, Async mode is not supported for DR.
2. Microsoft has not published their support stance for Many DBs yet.
So for example for "App Management Service Application" DB or "Secure Store" DB Microsoft says
To be determined. Currently not supported because testing is not finished.
For a complete list look here
http://technet.microsoft.com/en-us/library/jj841106.aspx
So although AOAG is a great option technically (and perhaps in the long run the strategic option) I would like Microsoft to complete their testing. (unless one is ready to take risk and go where MS itself hasn't gone)
val it: unit=()

SharePoint 2013 - SQL Server 2012 PPIV - using a PPIV workbook as a data source - getting PPIV web service error

I created a PowerPivot (SQL Server 2012 SP1) workbook and uploaded it to SharePoint 2010 Portal and started using it as a data source in an excel file. This worked fine and we saw no issues with it until we moved to SharePoint 2013 environment.
I uploaded the same PowerPivot workbook (source workbook) to SharePoint 2013 Portal and now trying to use it as a data source. I tried to change connection properties so that I could use the new portal address for the workbook. When
I try to save my changes, I see that OLAP queries are getting fired "Refreshing OLAP cube" shows up in the status bar, but eventually after running these OLAP queries (I would say after a minute), I get the following error -
Couldn't find anything specific in SharePoint logs or maybe I wasn't looking for the right thing.
Has anyone seen this issue? Why would PPIV service throw an error after running for a while? Is it a timeout issue of some kind? How can we take care of this?
Thanks,
Sonal

ULS log showed the following exception: The maximum number of allowed sessions per user has been exceeded.
Under Excel Services global settings, max limit is set. Default is 25, increasing it resolved this issue.
Thanks,
Sonal

Benefit of SharePoint 2013 sql server membership provider

Hi All, Please share your thoughts for this..
We are working with SharePoint 2013 public facing website with Form based authentication. Anyone can register and start using our site. We are storing
all the user related data in Active directory. As of now we are having around 25000 users in our portal . We are planning to move all external user information from AD to SQL membership table. Could you please suggest me to benefit of using SQL membership
instead AD

performance-wise, they're pretty similar either way (given a single dedicated role server).
security-wise, compared to SQL, AD makes some data easier to access (since LDAP queries can expose data to any user), but harder to hack (obtain copy of hashed passwords)
As far as management, there is NO management interface for the SQL membership provider... including USERS (reset password, lock/unlock account, etc), not just groups.
As far as SSO technology, SqlMembershipProvider is absolutely NOT an SSO technology. Not to say that it can't be used for logins, but authentication and single sign-on are two very different goals.
I would also argue that since you can't decrypt the AD passwords, the move to SQL is going to be a little difficult for users.
And, have you considered adding another AD server instead? With a little bit of fiddling around, you can add a dedicated AD server and prioritize SP authentication requests where you want.
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

SharePoint 2013 & SQL Server Reporting Services

Hi there,
We are developing a web application in sharepoint 2013 in which we are using authentication mode="Windows”. We have used a custom web part containing report viewer control for showing charts and reports, that we have
developed using SSRS ( *.rdl files) and have all the .rdl files within Sharepoint Document Library.
To start with, we were getting the error “Report Server has encountered a SharePoint error. (rsSharePointError) The user does not exist or is not unique.” To fix this, we changed <identity impersonate="false"
/> from <identity impersonate="true" /> at web.config level which did the trick.
However, we are now facing another issue wherein tabular reports are renedered ok in SharePoint through report viewer custom web part but chart based reports are not rendered. The chart image is not displayed.
Can somebody please help with a resolution?
The code snippet for rendering the report is given below for reference purposes
Thanks in advance
Monica
private
void BindReport()
            string reportFullPath
= "http://c4968397007/ReportLibrary/Reports/"
+ ReportPath;
            litReportHeading.Text = ReportPath;
            reportViewerControl.ServerReport.ReportPath = reportFullPath;
            reportViewerControl.ServerReport.ReportServerUrl =
new
Uri("http://c4968397007/_vti_bin/ReportServer");
            reportViewerControl.ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Remote;
            Microsoft.Reporting.WebForms.ServerReport
serverreport = reportViewerControl.ServerReport;
IReportServerCredentials irsc =
new
ReportViewerCredentials("username",
"password",
"domainName");
            rvControl.ServerReport.ReportServerCredentials = irsc;
            rvControl.ServerReport.Refresh();

Hi Monica Bhatt,
For this issue, please first check the following similar thread, whether the steps provided are working in your scenario:
http://social.msdn.microsoft.com/Forums/en-US/2bc30c80-290b-4346-a024-2f9f65db756f/chart-not-displaying-in-drillthrough-report-using-reportviewer?forum=sqlreportingservices
Thanks,
Qiao
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]
Qiao Wei
TechNet Community Support

SharePoint 2013, SQL Server 2012 SP1 Enable RBS for Additional Content Databases

We Enabled RBS in our SharePoint 2013 Environment recently. The time when we Configuring we had only one Content Database and we successfully configured. now we created more web applications and we need to enable RBS for newly created Content Databases.
we searched and tried lots of approaches, but we cudn't manage to achieve this. can anyone help us to enable RBS on additional Content Databases. (No offense but direct instructions would be great rather than providing links).
Thank you!

Here is step by step instruction with screenshot
http://thesharepointfarm.com/2011/03/enabling-rbs-on-multiple-content-databases/
Try to run
run this command on the SharePoint server: msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=”WSS_Second” FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=”DBServer”
Thank you so much for the reply Indrajeet. we followed the instruction to the letter but when we try the command, it failed. while doing some search, we came across an interesting Article.
http://rudolphoravec.blogspot.com/2012/10/remote-blob-storage-rbs-and-sharepoint.html
And surprisingly it is Working.

SharePoint 2013 SQL Server Reporting Services Report Viewer (Web Part) - IE Tab Title

Hi,
We are using a wiki Library to create page with SQL Server Reporting Services Report Viewer Web Part.
Everything is working great except for the Internet Explorer tab, instead of giving me the name of the Report it is showing the name of the web application. All the other wiki pages is working fine.
Regards,
Social Technet Microsoft.

Hi Brysk,
Is there any difference between the problemaitc page containing the webpart and other working wiki pages for showing the title name in IE tab?
The IE tab should show the information in tag<title> of the page, please check if it is correct for that page (using F12).
Also check if it is related to IE browser compatibility issue.
Thanks
Daniel Yang
TechNet Community Support

Migrate biztalk 2006R2/SQL server 2005 projects to Biztalk 2013/SQL server 2012

We have Biztalk application projects deployed on Biztalk 2006R2/SQL server 2005 environment on a single server
Now we have installed and configured Biztalk 2013/SQL server 2012 in a multicomputer environment where Biztalk server is on one computer while SQL server is on the other.
Now it's time to migrate the projects 2006R2 to 2013.. Is it a smooth process? I found a lot of posts about migration from 2006R2 to Biztalk 2010... Just wondering if it is similar or more complex?? Appreciate any help/suggestions.. thanks!!

Hi Annee,
Following article should answer your question:
BizTalk Application Migration Guide
Also have a look at following forum post:
http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral
Maheshkumar S. Tiwari|http://tech-findings.blogspot.in/

Network Load Balancing between SharePoint 2013 App server and WFE

Hi,
Can we do NLB between SharePoint 2013 App server and WFE Server ?
Below is our Architecture,
1. WFE Server (1)
2. APP Server (1)
3. Database Server
4. Domain Controller
We have configured NLB but, when we stop IIS on APP server, SharePoint 2013 web app link is not working.
is it possible ?
Please help us

You can do NLB between WFE and APP server however make sure that web application service is started from central admin which host sharepoint sites.
Why do you stop IIS on APP server, definitely it will not be able to host web app sites. rather you can just disable APP node on NLB to test it.

Folder name showing in the search result in SharePoint 2013

Hello,
In SharePoint 2013, when user search for a document within a folder, Search content along with Folder name and icon getting displayed in the search result. I am trying to hide Folder name from search result. Please suggest some way to achieve this.
Thank you
Jyotiraaditya

Hi,
As I understand, you want to search without folders in SharePoint 2013.
You can do the steps to achieve your request:
In search center in results page, click Edit page.
In search results web part, click dropdown in the upper right corner -> click Edit Web Part.
Click Change query -> in Property filter field -> choose contenttype, not contains, folder -> click Add property filter -> ok.
Thanks,
Dean Wang

Split TempDb in SharePoint 2010 Sql Server DB

Hi ,
We have envirenment of sharepoint farm,one Database server.We have plan to split tempDb acording microsoft best practices.
By the time of we have the largest content database is 260 in size and SQL Server has a 2-core processor.
So the tempdb would be split in two files with 40 GB per .mdf file.
Kinldy suiggest hopw to split TempDb.
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Hi Shanky,
We are not facing any issue,But we had take Micorosft RaaS services,Microsoft Consutlatan suggest thet we should break oure TempDb
RaaS ISSUE/RISK
Initial Size of Temp DB is too small
TempDB database Size may be too small.
SQL Server instance has only one tempdb data file while there are more than one scheduler in use
One or more user database files are placed on same disk volume along with TempDB database files
REMEDIATION COMMENTS
The size and physical placement of the tempdb database can affect the performance of a SharePoint farm. For example, if the size that is defined for tempdb
is too small, part of the system-processing load may be taken up with autogrowing tempdb to the size required to support the workload every time you restart the instance of SQL Server. You can avoid this overhead by increasing the
sizes of the tempdb data and log files.
Currently .mdf and .ldf files are in the D volume along with all other SharePoint databases and there is just one tempdb .mdf file.
More information:
http://technet.microsoft.com/en-us/library/ms175527(v=SQL.105).aspx
ACTION PLAN
Set the recovery model of tempdb to SIMPLE recovery model.
Create as many files as needed to maximize disk bandwidth. Using multiple files reduces tempdb storage contention and yields significantly better scalability. However,
do not create too many files because this can reduce performance and increase management overhead. As a general guideline, use
# of TempDB Files = # of Processors Cores / 4 and then adjust the number of files up or down as necessary.
Preallocate space for all tempdb files by setting the file size to a value large enough to accommodate the typical workload in the environment. You can go by a rule
of thumb that the size should be 25% of the largest SharePoint content database.
Important: Make each TEMPDB data file the same size.
Allow your TEMPDB files to grow automatically and monitor the disk free space, set the file growth in fix size and not in percentage. We recommend the following
general guidelines for setting the FILEGROWTH increment for tempdb files:
tempdb file size from 0 to 100 MB - FILEGROWTH increment in 10 MB
tempdb file size from 100 to 200 MB - FILEGROWTH increment in 20 MB
tempdb file size from 200 MB or more - FILEGROWTH increment in 10%*
* The FILEGROWTH increment should be set to a maximum of 6 GB, regardless of the tempdb file size.
Put the tempdb database on a fast I/O subsystem. Use disk striping if there are many directly attached disks.
Put the tempdb database on disks that differ from those that are used by SharePoint.
Important: This action plan requires a downtime of your SharePoint
farm as you will have to stop SQL Server services to move data and transaction log files to different disks.
By the time of this remediation the largest content database is 300 in size and SQL Server has a 2-core processor. So the tempdb would be
split in two files with 40 GB per .mdf file.
STATUS
SharePoint administrators will work on the action plan.
Downtime required for to apply this action plan? YES
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Sharepoint 2013 Web server role placement

We are in the process of deploying sharepoint 2013, and I have a question on deploying the web server roles. Where should they be ideally placed, on the internal network or on the DMZ.
If they are placed on the DMZ, can the web server roles be on workgroups or do they have to be always on the domain. Can you join a work group computer to sharepoint farm, I assumed it always had to be on the domain.
Majority of our sharepoint users will be internal, but we have external partners who we want to access the sites as well, thats why we are thinking DMZ.
Any advise on the above questions

Yes, that is correct. You need those ports.
The WFEs communicate with every other server in the farm, as well as your Active Directory, DNS, and SMTP servers. This includes all supporting infrastructure services such as LDAP, Kerberos (if you're using it), etc. I believe SMB is only if you are indexing
fileshares.
It does seem like quite a lot for a web server, however a SharePoint WFE is not just a web server.
Here is the list of ports:
TCP 80, TCP 443 (SSL)
Custom ports for search crawling, if configured (such as for crawling a file share or a website on a non-default port)
Ports used by the search index component — TCP 16500-16519 (intra-farm only)
Ports required for the AppFabric Caching Service — TCP 22233-22236
Ports required for Windows Communication Foundation communication — TCP 808
Ports required for communication between Web servers and service applications (the default is HTTP):
HTTP binding: TCP 32843
HTTPS binding: TCP 32844
net.tcp binding: TCP 32845 (only if a third party has implemented this option for a service application)
Ports required for synchronizing profiles between SharePoint 2013 and Active Directory Domain Services (AD DS) on the server that runs the Forefront Identity Management agent:
TCP 5725
TCP&UDP 389 (LDAP service)
TCP&UDP 88 (Kerberos)
TCP&UDP 53 (DNS)
UDP 464 (Kerberos Change Password)
For information about how to synchronize profiles with other directory stores, see User
Profile service hardening requirements, later in this article.
Default ports for SQL Server communication — TCP 1433, UDP 1434. If these ports are blocked on the SQL Server computer (recommended) and databases are installed on a named instance, configure a SQL Server client
alias for connecting to the named instance.
Microsoft SharePoint Foundation User Code Service (for sandbox solutions) — TCP 32846. This port must be open for outbound connections on all Web servers. This port must be open for inbound connections on Web servers
or application servers where this service is turned on.
Ensure that ports remain open for Web applications that are accessible to users.
Block external access to the port that is used for the Central Administration site.
SMTP for e-mail integration — TCP 25
Jason Warren
Infrastructure Architect
Habanero Consulting Group
habaneroconsulting.com/blog

Error rsItemNotFound when using ReportingService2010 endpoint in SharePoint Mode (SQL Server 2012 & SP2013)

Hi all,
I installed SQL Server 2012 in SharePoint Mode, with SharePoint 2013 on a Windows Server 2012 virtual machine. The issue occurs when I try to use the ListChildren operation of the ReportService2010 endpoint.
It manages to connect to the server, but it refuses to list any children. Here's the code I'm using:
using System;
using System.Net;
internal class Test
public static void Main()
var rs = new ReportingService2010
Credentials = new NetworkCredential("username", "password", "machine")
CatalogItem[] items = null;
// Retrieve a list of all items from the report server database.
try
items = rs.ListChildren("/", true);
catch (Exception e)
Console.WriteLine(e.Message);
When executed, this code throws an exception (which is caught and displayed) : "The item '/' cannot be found. (rsItemNotFound)"
The same code works (i.e. does not throw any exception and the items variable contains some CatalogItem) when used against a SQL Server 2012 configured in native mode.
I'm not sure what I'm doing wrong here, maybe the first parameter shouldn't be "/" but something else?
Thanks for your help
Aotio

+1
I'm getting this error as well. My test software is connecting to two different servers; one is running on SharePoint 2010 and I have no problems using the ReportingService2010 functions on that, but I am getting this same error when trying to connect
to a service on SharePoint 2013.

SharePoint 2013 - SQL Reporting Services Add-In

Hi,
In our old SharePoint 2010 environment the "SQL 2008 R2 Reporting Services ShrerPoint 2010 Add-in" has been installed which in turns provides the "SQL Server Reporting Services Report Viewer" web part.
I have upgraded the Farm to SharePoint 2013 and SQL 2012. Where I can get the the add-in above that is compatible with
SQL 2012 and SharePoint 2013?
I have found an add-in here for SQL 2012 and SharePoint 2010, but not sure this is compatible with SharePoint 2013...
Many Thanks,

Hi
I am also getting the below Error while testing the Content Db with SharePoint 2013 Web application.
1. Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [WSS_Content_8080], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
One or more assemblies are referenced in the database
[WSS_Content_8080], but are not installed on the current
farm. Please install any feature or solution which contains
these assemblies.
2. Database [WSS_Content_8080] has reference(s) to a missing
feature: Id = [c769801e-2387-47ef-a810-2d292d4cb05d], Name =
[Report Server File Sync], Description = [Synchronizes
Report Server files (.rdl, .rsds, .smdl, .rsd, .rsc) from a
SharePoint document library to the report server when files
are added or updated in the document library.], Install
Location = [ReportServerItemSync].
The feature with Id c769801e-2387-47ef-a810-2d292d4cb05d is
referenced in the database [WSS_Content_8080], but is not
installed on the current farm. The missing feature may cause
upgrade to fail. Please install any solution which contains
the feature and restart upgrade if necessary.
I have SQL 2008 reporting Services SharePoint 2010 Add-in.
for SharePoint 2013 we are using the SQL server 2008 Sp1. I think it is not possible to use SQL server 2012 SP1 for the report Services in SharePoint 2013.
Please suggest me to use the report services in SharePoint 2013 with Sql server 2008 SP1.
Thanks And Regards
Dileep Kumar

SharePoint 2013 - SQL Server BCS Model Incremental Crawl content doesnt show up in Search results

Similar Messages

Maybe you are looking for