Hi,

I've set up at user profile synchronization service which works - users get from AD to CA->Manage Profile Serive->User Profiles, and new changes in AD are updated correctly.

Then i have some sharepointgroups, where i've added some users. The name and mailaddresses are correctly transferred. But then comes the problem; when i change userproperties in AD (etc. a user got a new emailaddress), the changes get synced to User Profiles correctly, but not to the user in the group. A solution is to remove the user from the sharepointgroup and then add the user again, but i would like to get this update happening automatic.

How can i make it Work?

Regards Allan

(be aware that this is my first post in this community)

I would like to know certain things regarding Distributed cache.
If I have sharepoint 2013 server (no other SP servers in the farm)

Less than 10.000 users (in both questions)
16GB memory on the server. How much memory should I configure for the DC?
What if I have 3 servers: 2 WFE (16GB) and 1 APP server (20GB)?

thanks,
Olafur

Greetings,

This question is regarding a SharePoint 2013 WFE server's SharePoint Tracing service consuming high CPU. Below is a screenshot.

Currently we have two Windows 2012 WFE virtual servers with 8 GIG memory. The local C drive is where the OS is installed only and it has been allocated 40GB, the E drive is where SharePoint is installed and it has 50 GB (currently we have 48 GB free), a P drive for the page file.

One of the WFE servers is facing the high CPU usage as shown above. The other isn't.
None of these WFE have been configured for the search service. 

Has anyone experienced this before? 

Daniel Christian (MCTS)

Hi All,

   Just recently new to Sharepoint in our company we have went with the foundation 2013 product.

Had a bit of bother Setting the server up initially as our servers do not have direct access to the internet, so did the offline installation through Prerequsite.exe and i think this is what might have caused this issue as i messed about quite a lot learning how to get everything installed.

So here lies the issue,

In the Central Admin page, under health analyzer i am getting the error - Title "One of the cache host in the cluster is down" Failing Servers - [My servers Hostname] - SPDistibutedCacheService (AppFabricCachingService)

The AppFabric service is started with the NT Auth Network Account automatically so i dont think its a problem with the service itself but i could be wrong.

There hasn't been any problems reported thus far with the site but i want to make sure that I have this server configured to its optimum.

Anyone any ideas for this sharepoint novice?

Thanks

Andy

Greetings,

One fire put out and another to work on.  We recently lost a server out of our test farm because of a VM Host failure.  They were unable to get it to remount into the VM so we were left with rebuilding it.

We rebuilt the server and added it back into the farm.  Everything looked to have joined backup fine.  It shows up in Get-SPServer), it shows up in 'Manage Servers' CA seems to be functioning properly (it was the main of one of two CA servers). So from a high level view it appears to be a functioning member of the Farm.

However when I go and try to create a web application from this server it will not propagate to the remaining WFEs in the Farm.  The site and application pool only get created on itself and no where else.

When I create the web application from the secondary CA server that never had an issue the site gets propagated everywhere like normal, even to the newly rebuilt CA server.

Not sure where to start on this one as everything I've looked at seems to show that the rebuilt server is a proper member of the farm.

Any help is appreciated.

Hi,

We have Laptops in a Domain using Kerberos Authentication when connected to the LAN. SharePoint Website opens fine.

While travelling this users logon using cached credentials.

 -  no Kerberos Credential assigned in this session.

 - SharePoint site will not open. (site is in Intranet Zone)

In this case users open the site with Firefox (using NTLM).

Is IE11 configurable in a way to use NTLM if the user logged with cached credentials onto Windows and the KDC is not connectible?

thanks

Markus

I am currently setting up a SharePoint 2013 instance. At my company we have an existing SQL Server 2008 R2 (SP1) installation with SSAS, which users are currently accessing with Excel 2010 & 2013 PowerPivot.

Is it possible to access the Analysis Services from this existing SQL 2008 R2 server from SP 2013? If so, is there anything that needs to be installed on this box? (Or is it the case that I really can't use SQL Server 2008 with SP 2013 Excel Services?)

Hi

i habe one big Problem i want to set configure site mailboxes in SharePoint 2013

i follow this site http://technet.microsoft.com/en-us/library/jj552524

when i want to set site and then to check i get this. (sorry i habe only german sharepoint2013)

I can set spappprincipalpermission.

I hope someone can help me.

tanxs

Greetings,

I'm going through a standard process of setting up a Search Topology for a SharePoint 2013 farm. However, this time I have run into an issue. Below, I have provided the powershell I use to setup the Topology and also the error I get. 

I get the error after I have attempted to activate the Topology. I have a hunch that the solution is simple but I cannot seem to place a finger on it. Any help is appreciated.

#Prepare the topology variables

$hostApp1 = Get-SPEnterpriseSearchServiceInstance -Identity "AppServer" 

$hostWF1 = Get-SPEnterpriseSearchServiceInstance -Identity "WFEServer"

$hostWF2 = Get-SPEnterpriseSearchServiceInstance -Identity "WFEServer"

Start-SPEnterpriseSearchServiceInstance -Identity $hostApp1

Start-SPEnterpriseSearchServiceInstance -Identity $hostWF1

Start-SPEnterpriseSearchServiceInstance -Identity $hostWF2

#Get Search Service Instance status (started or stopped) after running the above commands

Get-SPEnterpriseSearchServiceInstance -Identity $hostApp1

Get-SPEnterpriseSearchServiceInstance -Identity $hostWF1

Get-SPEnterpriseSearchServiceInstance -Identity $hostWF2

#Setting up the topology

$ssa = Get-SPEnterpriseSearchServiceApplication

$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa

#Activate the search

$ssa = Get-SPEnterpriseSearchServiceApplication

$activeTopology = Get-SPEnterpriseSearchTopology –Active –SearchApplication $ssa

$activeTopology

#SPAPP-SRV1

New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp1

New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp1

New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp1

New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp1 -IndexPartition 0

#SPWF-SRV1 , SPWF-SRV2 , SPWF-SRV3

New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostWF1

New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostWF2

#View each of the components

$file = “c:\componentinfo.txt”

$ssa = Get-SPEnterpriseSearchServiceApplication

$activeTopology = Get-SPEnterpriseSearchTopology –SearchApplication $ssa –Active

Get-SPEnterpriseSearchComponent –SearchTopology $activeTopology | Out-File $file

#Activate the Topology

 Set-SPEnterpriseSearchTopology -Identity $newTopology

Below is the error I get

Below is the error.

Set-EnterpriseSearchToplogy: Toplogy must contain at least one component of type: Microsoft.Office.Server.Search.Administration.Toplogy.CrawlComponent at Line:1 Char:1

Thanks in advance.

Daniel Christian (MCTS)

This is a spin off from a previous issue I had but now I think this is a bug and it appears to only be in the Post.aspx view. To summarize, when the exact same web part is added to the POST.aspx page as well as the /Forms/AllItems.aspx page, it crashes on the first and works on the latter.

To try and keep this short I'll be simple

Initial setup.....

1) Create a Team Site with a contacts app

2) Create a Blog SUB site with a contacts app and a document app

3) In the team site, create a new Site Column that is a Lookup to it's Contact app (based on Last Name Linked Field)

4) In the sub BLOG site, create a new Site Column that is a Lookup to it's Contact app (based on Last Name Linked Field)

5) In the sub BLOG site, add both the Parent Team Site Lookup and the Blog Site Lookup as an "Existing Column" to both the POST and the Document Apps.

so at this point, you should have a blog sub site with a Post app and a Document app that have 2 new columns added: One is the Contact lookup column from the Parent site, the other is the Contact Lookup column from the local Blog site.

Let the fun begin...

6) On the Blog post details page (the page that comes up when you click on the title of an individual BLOG post), add 2 new web parts.... one is the existing "Post" library, which means you would have the same info just in a different view) and the other web part is the existing "Document" library. For each newly added Web part.... edit the current view and make sure to include the newly added Lookup columns.

7) On the Blog's Document library page (the page that comes up when you view everything in this app), add 2 new web parts.... one is the existing "Post" library, and the other web part is the existing "Document" library (which is a duplicate of the already existing web part). For each newly added Web part.... edit the current view and make sure to include the newly added Lookup columns.

Results....

What you should see is that the actual "POST" page (/List/Posts/Post.aspx?ID=n) will not even display the original untouched web part. The added Document web part (with the new columns showing) will show and the Contact Linking works. The second occurrence of the Post Web part (which includes the new lookup columns) crashes and displays an error on the screen.

If you open up the Document Library, you will see the original untouched web part working, and BOTH of the newly added web parts which includes the exact same "Post" + new Lookup columns as above.

... so long story short... the same web part for the same object library with the same display columns works in the _layouts/15/start.aspx#/myDocs/Forms/AllItems.aspx however does not work in the the /_layouts/15/start.aspx#/Lists/Posts/Post.aspx

...

I have the default Content Source 'Local SharePoint sites' configured to crawl everything under the hostname for each start address. The only start address is the root URL I have configured to access SharePoint, the same URL that is working perfectly for browsing all the sites, http://sharepoint.XXX.com.

The full crawl finishes in about two minutes. The Crawl Log reports 1 success, 0 warnings, and 0 errors.

Using the Search Center site to search for ContentSource:"Local SharePoint Sites"returns a single result, the home page of the site collection. It doesn't seem to be crawling into the sub-sites or document libraries. I have links on the Home.aspx to every sub-site and in those sites there are links to every library.

I made the search service account a site collection administrator.

I tried to add sub-sites to the Content Source, such as http://sharepoint.XXX.com/Management, but it gives me an error saying it can't add it when crawling the entire web application. This makes sense.

I just can't figure out why my default crawl is not getting any errors, and actually finding the Home.aspx, but not anything deeper. Any ideas on what to check next?

Thanks in advance for any help you can provide.

EDIT:

It might be worth noting that I have two other Content Sources that are working.

One starting at sps3://sharepoint.XXX.com that has 33 Successes, 0 Warnings, and 0 Errors. It is showing everyone that has logged into the SharePoint site in People in the Search Center.

The other on is a File Shares type with two shares listed to start from. This has 112,000 Successes and is showing the files in the search results in the Search Center.

Hello,

We have created a Content Deployment job for our upgraded SP13 site. Following is the error:

Exception of type 'Cobalt.ErrorException' was thrown. *** Inner exception: Exception of type 'Cobalt.ErrorException' was thrown.

The object for which this error is being thrown is '/FormServerTemplates/Forms/template.dotx'.

Any help on this would be appreciated.

Thanks and Regards,

Neha

I have some of these in the event log at the same time I am getting user complaints

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/28/2014 3:58:02 AM
Event ID:      8062
Task Category: Http Throttling
Level:         Critical
Keywords:     
User:          xxxxxxxxxxx
Computer:      xxxxxxxxxxxxxxxx
Description:
Http throttling on xxxxx.xxx stops because there is no heavy load detected now. 30 requests have been throttled during the throttling period.

Is this related to Req Managment Service and is there a way to just disable it?

Or is that a bad idea?

themush

When a user tries to follow some document or site, the same error occurs. When I look at the personal site of the user, the "Social" list is missing.

When I have another user do the same thing, it works! The Social list for that user is there.

The difference between the 2 users:

The user where the issue occurs => mysite has been upgraded from SharePoint 2010

The user where the issue doesn't occur => mysite has been created after the upgrade to SharePoint 2013.

So, I tried to delete the mysite of the user who had the issue and let him recreate it by visiting the MySite host and now it works!

The thing is... I have 10k+ users having the same issue and a lot of them are actually using their mysite, so deleting those mysites is not really an option.

I have 2 questions:

1. why is that "Social" list not created when mysites are upgraded from SharePoint 2010? Steps followed as MSFT provided

2. Can I trigger some script/setting which fixes this for existing sites? 

Thanks,

Thanks and Regards, Parth

Hi,

I do have one SharePoint farm with single SharePoint 2013 enterprise server on Windows Server 2012.

One web application site, which is deployed to: https://sp.mycompany.com , as team site. This is only AAM (default zone)

My sharepoint server has now two different IPs in same subnet.

By default, in IIS , web app is allocated to all available IPs. I want to make sure that sharepoint opens only on one ip (for other reasons). But if I modify, IIS binding, and put fixed IP. , then sharepoint does not work, it opens blank page without any errors on site, in ULS or inside.

I have made sure that my DNS configuration is correct. If i revert back to all IPs it works.

How can I make that sharepoint web application works only on one particular IP.

Or troubleshoot this problem ?

-- Hrvoje Kusulja

I am getting mixed content type errors on a host header site collection I have set up on a SharePoint 2013 farm. Consequently some SharePoint funcitonality is not working. For example modifying views fails with generic error message "Cannot complete this action" and IE mixed content type warnings.

Our setup is as follows:

Web Application on port 80
The AAM default public URL for Web Application is using https

A Host header site collection has been created with a http URL

Note that March 2013 Public Update has not yet been installed so I cannot created alternate AAM zone URLs for host header site collection.

F5 has been configured as per F5 recomendations for SSL termination as far as I can see. We have also followed the Microsoft advice here:

http://technet.microsoft.com/en-us/library/cc424952.aspx#section2g

In IE debugger I get errors like:

Using Flddler Web Debugger it would appear some js and css files GET requests are being made using https and are returning 404 File Not Found responses.

Has anyone else had such problems? I am sure it is F5 configuration type problem.

Dear all,

I am working on a standalone install Sharepoint 2013.  We would like to test out newsfeed feature but it always showing "we're still collecting the latest news. you may see more if you try again a little later".

I checked the Distributed Cache service is started. AppFarbic windows service is running. The "User Profile Service Application - Activity Feed Job" is started and running every 10 minute (and checked last run time is ok).  The "User Profile Synchronization Application" is configured and I am able to propagate my AD content and select some AD group to sync.

The only point I am suspecting is "user profile synchronization service" is stopped.  I cannot start it because it require my "Network Service" password but I don't have. Searching in this forum and found in SP2010, "user profile synchronization service" is not supported for Standalone install.  Is it also true for SP2013?  I only have a 8GB notebook which it is nearly impossible for me build up a farm just to test out Newsfeed feature.  Is there any workaround? 

Thank you for any input!

Mark

Hello,

I have SharePoint 2013 running with SQL 2012 SP1, tried configuring Access Services following the steps given here  but when i try creating a Customer Web App using Access 2013 but i still get the error below. Please advise, you can also assist with another link that has a working solution for the same.

Meshack

Please help if you can.

Central Admin reports an issue, in that the farm account should not be used for other services.

Failing service is SPTimerService (SPTimerV4).

Details indicate:
BOWLESRICE\sp_farm, the account used for the SharePoint timer service and
the central administration site, is highly privileged and should not be used for
any other services on any machines in the server farm.  The following services
were found to use this account: Distributed Cache Service(Windows
Service)

I tried this Management Shell script:
$farm = Get-SPFarm
$cacheService = $farm.Services | where {$_.Name -eq "AppFabricCachingService"}
$accnt = Get-SPManagedAccount -Identity bowlesrice\SP_Services
$cacheService.ProcessIdentity.CurrentIdentityType = "SpecificUser"
$cacheService.ProcessIdentity.ManagedAccount = $accnt
$cacheService.ProcessIdentity.Update()
$cacheService.ProcessIdentity.Deploy()

But it errors with :
Exception calling "Deploy" with "0" argument(s): "cacheHostInfo is null"
at line:1 char:1
$cacheService.ProcessIdentity.Deploy()
* CategoryInfo: NotSpecifiedd: (:) [], MethodInvocationException
* FullyQualifiedErrorID : InvalidOperationException

I have tried logged in with local admin, SP_Farm, SP_Admin and SP_Services, and same error.

I checked and the windows service "AppFabricCachingService" was set to Disabled, and I tried setting to Automatic, and it denies access starting it using SP_Services, so I set the service to logon as "Local System Account" and it starts, but the script still faisl with same error.

I've tried about everything I can find.

Please help, and Thank You SO MUCH!