Month: January 2014
There is a compatibility range mismatch between the Web server and database
Today, I had this error when I was trying to deploy a simple Hello World App for first time.
I tried everything on this blog and still didnt work.
http://blog.mannualag.com/2013/03/07/nuisances-of-starting-developing-apps-for-sharepoint-2013/#
Guys, let me tell you what my problem was.
When I first started I was developing with the farm account, suddently when I was trying to deploy VS says that you can not use the system account to deploy apps. Read the link above.
So, I logged in with my account, and the mistake was this: I created the app management service application and the new web application with my username, yes its farm admin, yes its local administrator.
The problem is the farm account has a server role of db creation and security admin, this means that when this account tries to create databases, it will also make the security adjustments needed on the databases for the configuration to be correct.
Because I tried to do this with a normal user account which has no Sql Server roles, then the Content DB was created, and the app management service application was created too.
However, it didnt set up the security on the databases the right way
After following the post above, and checking the logs with the dba we saw this error :
There is a compatibility range mismatch between the Web server and database
We double checked permissions and they were all set correctly.
Solution:
1. Delete the app management service application.
2. Delete the new web application content database.
Fortunately it was a development environment, after recreating these 2 things, the app was succesfully deployed using F5 on Vs 2012.
How to change the site column group name
This question comes from Twitter from: Kyle Redddock, @WinPhanKyle
He wanted to know how to change the group name of the site columns through central admin.
This is not possible through central admin but its pretty easy through powershell.
The first thing you have to know is that you can not create a group of columns, the group name is actually a property of the site column itself, and once you change all the group names of your site columns, then you will all the columns grouped under a different group (if that makes sense)
$site = new-object Microsoft.SharePoint.SPSite(“http://xxxx:4000”);
$site.rootweb.Fields[“TheColumnName”].Group = “TheNewGroupTitle”;
$site.rootweb.Fields[“TheColumnName”].Update();
Property doesn’t exist or is used in a manner inconsistent with schema settings.
Today, I had this on my enterprise environment which was not easy to figure out.
All our environments should be the same, but apparently it was not the case for the test environment.
Because we are trying to align together all our environments, we backed up one content database from prod and restore it into the test environment, and one of the pages didnt work showing the error: Property doesn’t exist or is used in a manner inconsistent with schema settings.
This page has a content search webpart with a very easy query:
contentclass:”STS_ListItem” {SearchBoxQuery} ParentLink:”*opportunityinfo*”
As you can see the query is using OOTB managed properties, then I thought, wtf, I am screwed up, I checked the ULS logs and I saw:
SearchServiceApplicationProxy::Execute–Error occured: System.ServiceModel.FaultException`1[Microsoft.Office.Server.Search.Administration.SearchServiceApplicationFault]: SortList (Fault Detail is equal to Microsoft.Office.Server.Search.Administration.SearchServiceApplicationFault).
Getting results failed: SortList
Failed to get document content data. System.ComponentModel.Win32Exception (0x80004005): Cannot complete this function at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(Int32 rowOrd, Object ospFileStmMgr, SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)Could not get DocumentContent row: 0x80004005.
SearchServiceApplicationProxy::GetUpdatedQueryParameterSpecifications–Proxy Name:Search Service Application Proxy EndPoint: http://be-xxxxx:32843/69cb3b7380164049ba43d8679204fb85/SearchService.svc
From the ULS Logs, all entries were high except Getting results failed: SortList, so I immediately checked the SORTING tab. And there it was. The sort field was empty, why? because the managed property did not exist on the test environment.
I created the managed property and voila!!!, I fixed the problem!
I am a genius!
My Tasks Aggregation in SharePoint Server and Exchange Task Integration
This whitepaper explains how to make the My Tasks work and set it up.
Luis Valencia - Sharepoint Architect 