30 aprilie 2012 22:34
I have 2 warnings which won't go away...
one says my database is outdated... I have run the upgrade -inplace force 5 times already.. each time it says success, I then click on re analyse but the warning stays put!! I'm tearing my hair out..
The other warning says that I have fragmented indecis.. I clicked on that warning and click FIX IT... nothing... still there...
What am I supposed to do? It's driving me nuts.
or should I just get my coat, put my hat on and walk away..?
1 mai 2012 06:46
check the above link if it did not give an answer please take a screen shot for the error so that we can help you
If the reply was helpful or informative, please remember to mark it as answer or vote as helpful. MCITP SHAREPOINT
1 mai 2012 07:41Ok I did that, and checked auto fix
warnings are still there..
1 mai 2012 15:25
I've just run
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
and then gone into the warnings, opened and re-analyzed the warning... Surely... that should do it????
2 mai 2012 08:56
STILL THE WARNING WONT GO AWAY... I HAVE INSTALLED THIS 5 !##" times.. AND IT TELLS ME SUCCESS , YET THE WARNING IS STILL THERE!
personally I really think microsoft should have thought out the whole error process in SharePoint a little bit better...
It would have made so much sense to describe how exactly to fix the problem but no... that would be too sensible. Instead they just tell you to go to a webpage that has no useful information whatsoever.
IF this has any use, the databases that are outdated are:
- Editat de dubsdj - MCITP 2 mai 2012 08:59
2 mai 2012 14:53
Here is some information on the errors you provided in your screenshot.
Databases running in compatibility range, upgrade recommended.
Search - One or more property databases have fragmented indices.
2 mai 2012 15:51To supplement the post above, if you database server is upgraded you still need to check your database compatibility mode itself on the database in sql. Right click your database, go to options and there you will see what mode it's in. SharePoint is pretty much compatible with all of them so you will want to use the highest level. Unless you have an old sql server this should fix it.
3 mai 2012 08:05But how do I upgrade it? I have all the latest and optional updates installed on the SharePoint Server... surely SQL R2 was one of those updates..
3 mai 2012 08:11
I'm in the SQL Management Studio, but I don't see the options that you describe? Or am I doing the wrong thing?
I have looked in my start menu, it says SQL Server 2008.... but I then went to windows updates ALL, I couldn't find an update for SQL
3 mai 2012 21:14
Your on the server options, not the database itself. You need to find your content database and see what the compatibility level is set at.
8 mai 2012 00:10
I found one of the instances... checked its options.
it appears to be set to correct compatibility level?
even though central admin says it isn't..
8 mai 2012 00:12DO you have screenshots? You don't connect to a database, you connect to an instance. Then there should be a databases drop down section which you shoudl see your content database there usually WSS_Content or something along those lines. You right click that and properties.
8 mai 2012 00:50
isn't that what i have done in the post above?
8 mai 2012 01:18yeah, i was responding to your post before you edited it ;P.
8 mai 2012 07:37hehhehe
21 mai 2012 08:24
Still not resolved by the way.
I have done everything mentioned here, and checked each database in SQL Server. All of them are set to the latest version.
I'm a bit worried about this warning now, if it falls out of the compatibility range will share point completely stop working?
23 mai 2012 20:49Try upgrading to SQL Server Express 2008 R2
24 mai 2012 08:32
do you have a download link for this?
This is what I have got:
24 mai 2012 20:13I missread the error, this isn't going to have anything to do with sql. it's something with your SharePoint not sql. Have you run the SharePoint configuration wizard on all your front end servers after upgrading? If so I would run them again anyway to see what happens. Then worse case maybe it's a stuck alert. Remove it then see if it comes back in later on.
24 mai 2012 20:26I'll give that a go
24 mai 2012 20:30
Have you recently applied any SharePoint updates?
What is the configuration database version listed in Servers in Farm (Central Administrator -> System Settings -> Manage servers in this farm)?
What are the versions listed in Mange Patch Status (Central Administrator -> Upgrade and Migration -> Check product and patch installation status)
In the affected databases, what are the versions listed in the dbo.Versions table (In SQL Management Studio: Expand the database -> expand Tables -> right click dbo.Versions -> Select Top 1000 Rows)?
25 mai 2012 08:11
To answer the reply saying run the configuration wizard. Well the error has reappeared so that hasn't worked.
25 mai 2012 08:26
I haven't applied any SharePoint updates. I don't know where I can do such a thing...
although I have run the database update over a million times.. (well not quite but..)
Database version is: 14.0.6114.5001
Manage Patch Status: 14.0.6029.1000
affected table 1:
affected table 2:
affected table 3:
30 mai 2012 08:11
I'm really concerned now, if that compatibility range slips out of focus.. will my sharepoint just cease to work? That would be disasterous..
especially when it seems there is no apparent way to fix this :(
30 mai 2012 19:01
So 6114 is the December 2011 CU and 6106 is the June 2011 CU, it looks like they didn't upgrade when the December CU was applied. You could try updating each database individually ($db = Get-SPContentDatabase [GUID]; $db.Update()), which may work.
30 mai 2012 19:20You did install the full SharePoint CU when you did updates right? and not just SharePoint Foundation? If you did just Foundation (if it lets you I don't know for sure) then this could be the cause since it wouldn't upgrade SharePoint Server databases. You might want to make sure you applied the full SharePoint Server CU then run the Configuration again and it should upgrde them automatically. Just a thought? Should be able to see by going to add/remove programs and checking the show updates box or whatever link they have now. Then look under sharepoint for your latest update installed and match up the KB article.
31 mai 2012 07:52
That shell command that you gave me Jason has confused me. Where would I attempt this? In the Powershell or something? Do you have a clearer description by any chance?
Turismon - I'm still a bit unsure when you say about installing the CU... what CU? I haven't done any windows updates with sharepoint included? Unless it does it itself without me knowing?
If somebody could point me in the right direction to get all these updates, would be great! I'm at a bit of a loss here.
I'm still learning this system.
Thanks very much!
31 mai 2012 08:03
Here are the updates that I have got applied? How can I get newer ones? or is it just automatic?
31 mai 2012 09:27
Well somone had to install SP1 :P. But it does look like you have an update of some sort to SharePoint Foundation. Your best bet would be to just update to the lasted CU (Cummlative Update). This gives you the latest build of SharePoint for all SharePoint Products and Foundation. You may want to read into doing the update but it's pretty easy.
You just download the package. Install it on your web front end servers, then once installed you run the SharePoint Product and configuration wizard and leave in the existing settings, this will run through and update your farm and databases. If you get an error installing it usually means because of some incompatable features on your site, I just run through it twice and it updates fine the 2nd time around running the configuration wizard. Processes takes about 10-20 minutes so be ready for a little bit of planned downtime.
31 mai 2012 11:45
ok, but I have sharepoint standard...At least I thought I did?!?
in my convert licence type, it says that I have:
I'm impressed with myself that I have managed to get as far as I have with Sharepoint, but now I think I'm a bit out of my depth with it LOL..
still, I won't give up.
31 mai 2012 12:55
Sorry, I was thinking out loud. The full directions are:
- Open an elevated SharePoint Management Console (right click -> Run as Administrator)
- At the prompt run the Get-SPContentDatabase cmdlet:
Get-SPContentDatabase -WebApplication http://yourwebappurl
- Get-SPContent database will return a list of content databases in the web application and their GUIDs. Select and copy the GUID from one of the databases with the issue.
- Run Get-SPContentDatabase again, this time telling it which DB to use (by pasting the GUID) and assigning the result to a variable:
$db = Get-SPContentDatabase -Identity [GUID]
- Run the Update() method on the content database:
31 mai 2012 13:34
I ran that shell command, all I get is this:
Which I assume is my whole Sharepoint database! I can't see the individual faulty tables... do I just update the whole thing?
- Editat de dubsdj - MCITP 31 mai 2012 13:44
31 mai 2012 13:39
So I ran it anyway... did the db.update... it seemed to accept it but appeared to do nothing, just sat on the prompt?
do I need to do something else?
31 mai 2012 14:29
31 mai 2012 14:38
Here's the post I was thinking about. Similar issue -- after an upgrade the Search database was not upgraded. The OP had found a resolution online but could not validate that their database was affected. I was able to determine that the database needed upgrading, though I have no idea about the details of the resolution they were going to perform.
My suggestion to recreate the search database may apply if you're comfortable with noting the configuration and recreating the service. By creating the service from scratch, the databases would be created with the current version so the issue can be resolved.
The high-level process would be to:
- Create a new search service application in parallel to the existing search service application
- Transfer over the configuration from the old service to the new. Configuration to include would be content sources, scopes, properties, exclusions, etc.
- Set up crawls in the new service to validate the same number of items for all scopes (compared to the old service)
- Re-associate the web application to this new search application (Mange Web Applications -> Service Connections) to validate it is working before deleting the old service application.
- Delete the old service
31 mai 2012 15:08
Based on SQL Management screenshoot and warning info, the key is here : http://technet.microsoft.com/en-gb/library/hh564106.aspx.
You need to upgrade your SQL server to SQL Server 2008 R2.
SharePoint Architect, Singapore
Microsoft MVP | SharePoint Server | Singapore
Blog : http://blog.libinuko.com
31 mai 2012 15:16
the problem is, SQL server R2 does not appear in my windows update? So I don't know how I can get the upgrade for it.
Jason - That's a real pain, I have spent hours setting up my Search Service and Crawls :(
I really hope that I don't have to redo all that again.
31 mai 2012 15:25
You won't see updates for R2 because it's a separate product with new features. In other words, upgrading involves a purchase (software + licenses).
As for reconfiguring search, the SharePoint Enterprise Search Migration Tool for SharePoint Server 2010 (download site) can handle migrating your configuration to a new search instance. Personally I have never used the tool but it sounds promising.
31 mai 2012 15:28
I have just ran a query in Management Studio and it says I have:
Express Edition (64 bit) 10.0.5500.0 SP3
31 mai 2012 15:29
hmm ok wish me luck!
I'll let you know how I get on
31 mai 2012 15:51You need to update to the latest CU first before anything else. You don't even have the CU right after SP1 which is pretty much a requirement with the SP1 install due to some major bugs, can't remember what but it was in the install instructions to do it. So I would start with the update I linked above to make sure you are running the newest build and that could solve you problem too. After that then you need to look at rebuilding your Search or whatever DB's.
31 mai 2012 16:06ok Turismon, I will try that first.
5 iunie 2012 23:12hotfix for office? a bit confusing..
6 iunie 2012 00:30
hotfix applied, config wizard run
warning still present :(
I found this article, can anybody guide me through this?
I think I have to run the shell or something.
6 iunie 2012 12:04
I have deleted the warning.
I did that yesterday and it hasn't returned yet....
11 iunie 2012 07:59
OK now it's back again! Monday morning, great :(
I suppose I'm going to have to delete all my search settings :(
12 iunie 2012 05:30Honestly, at this point, just leave it, if everything is working and there are no issues, wait till the next CU comes out and see if the issue goes away after the updates are applied. It's just a service application, not like it messes with your main content databases or anything like that.
12 iunie 2012 07:35
Ok Turismon, thanks for the advice.
I'lll leave it for now, hopefully the CU will fix it next time.
I really appreciate your time and help on this.
24 septembrie 2012 22:18
Just to say this still isn't fixed.... update run... still the same.
1 aprilie 2013 23:26
The same problem just befell us. Warning (shown below) in the Health Analyzer Reports that just won't go away. According to Technet the solution is to let the health rule run. Yeah... not so much, Microsoft. Not so much.
Search - One or more property databases have fragmented indices.
2 - Warning
ExplanationHeavily fragmented indexes can degrade query and crawl performance.
RemedyIndex fragmentation can be remedied by either reorganizing an index or by rebuilding an index. Refer to SQL Server documentation for details on how to manually detect and repair fragmented indices. This job should be run outside your normal SQL Server maintenance window, during off-peak hours, as query and crawl performance will be adversely affected. Do not run this job during farm backup/restore/upgrade. Disable this job if your SQL database mirroring latency is excessive. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=167143".
Failing ServicesSPTimerService (SPTimerV4)
9 aprilie 2013 19:47
Okay this was a strange fix for us, but it worked.
Looking through the ULS logs we saw the following errors:
SearchServiceApplication 'Search Service Application' is in restore/backup state. Skipping the rule. 0657476f-33d2-4707-905d-896091178675
04/01/2013 16:33:01.63 OWSTIMER.EXE (0x0DD8) 0x06AC SharePoint Foundation Health 8fs4 Medium Automatic repair is being attempted. 0657476f-33d2-4707-905d-896091178675
04/01/2013 16:33:01.79 OWSTIMER.EXE (0x0DD8) 0x06AC SharePoint Server Search HealthRule dls7 High SearchServiceApplication 'Search Service Application' is in restore/backup state. Skipping the rule. 0657476f-33d2-4707-905d-896091178675
04/01/2013 16:33:01.85 OWSTIMER.EXE (0x0DD8) 0x06AC SharePoint Foundation Health 8fs5 Medium The automatic repair Failed. 0657476f-33d2-4707-905d-896091178675
Went to Central Admin > Manage Service Applications > Search Service Application and saw that indeed the crawl status was stuck in a restore/backup state.
Try as I could, I could not get the Search Service Application out of that state. In the end I deleted the service application, re-ran the Health Analyzer Rule for "Search - One or more property databases have fragmented indices" and the warning message went away.
Luckily we didn't need our Search Service Application because we are using FAST for SharePoint 2010. For others, you will likely need to re-create the service application after you delete it (which sucks for you).