Tag Info

New answers tagged

-1

Got to Start --> Run --> Services.msc --> Windows Management Instrumentation --> Restart the service.. Thanks, Ankit


0

looks like their is missing updates or missing PSconfig wizard.from the versions numbers, one farm is on Service Pack 1 and one is on May 2015 CU. I think one farm get the updates and other is still behind. You have to apply same update on 2nd farm. Check more about version numbers here: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346


0

Thanks a lot Jesus for your quick answer, yes I will definitely asked specific question. I will also go through all the the links you sent. Yes I am an advanced developer with HTML, CSS and kind of Intermediate with JAVASCRIPT, How I am going to use them without designer and no access to the server? can I use a third party editor. Please more detail on ...


0

You are tackling a lot of stuff for your first time out with SharePoint. The answer is YES you can do this. "How" you do it depends on the way your administrators deployed SharePoint and what services they made available to you. First - with Search. Some things do have to be configured in Central Admin, but not everything. More than likely for your ...


1

As Waqas Sarwar mentioned, I had to start SharePoint Foundation Web Application on the Search Server to get rid of that message. When I stop it again and re-run the missing server side dependencies the error appears again. I now disabled the check, because I must not run two Web frontends because of some 3rd party licenses.


2

please look at this link, it shows how to achieve what you're trying to do. using System; using Microsoft.SharePoint.Administration; namespace Test { class Program { static void Main(string[] args) { SPDiagnosticsService diagSvc = SPDiagnosticsService.Local; string ulsLogLocation = diagSvc.LogLocation; ...


0

I ran into this exact issue today with KB2889937 which I resolved by completing the following: Download the executable for KB2889937 from https://support.microsoft.com/en-us/kb/2889937 Ensure you have a full backup of the farm including server snapshots just in case! Run the EXE for KB2889937 on each server in the farm. For those where it is already ...


1

I encountered the same error a few days ago. Reported it to MS Support and they told me there might be a bug in SharepointOnline which causes the Managed Properties page to default to the incorrect level of site instead of sitecol So avoid using this URL _layouts/15/managedproperty.aspx?property=RefinableString00&level=site And simply use this URL ...


0

There are two rights that control whether users can create a top-level Web site, subsites, or workspaces: Use Self-Service Site Creation and Create Subsites. See this Technet article for details. Also permissions are defined at the site collection level. For your case you will have to create a new permission level at the site collection where you don't ...



Top 50 recent answers are included