Hello
I am implementing a new SharePoint 2013 server. I have created a new site collection with 2 site administrators (the farm administrator account and the default content access account). If I tried to access any site of this site collection with one of these 2 site collection administrators, the documents included in the libraries are not visible. Is it normal? What am I suppose to do for them to have access to the content?
Best regards
Yann
Hi,
Something strange is happening with my community site. For a few day i was able to do operations but now everytime when I go to community site my IE 10/Crome crash with error Microsoft Office 2013 has crashed.
It will not crash if I dont use community site. Did someone has the same issue? Please help
I've added AD FS as a trusted provider for my SP2013 default site.
I've primarily used http://technet.microsoft.com/en-us/library/hh305235.aspx
I can still login using IWA, but when I try to login through ADFS, I have "Sorry, this site hasn't been shared with you" message. If I delete cookies, go back again but select Windows Integrated, I can log-in.
ADFS is working for two other applications, one IWA and one CBA. As far as I can tell, Claims are being presented to SP.
Are there any 'gotchas' that I should know aside what's published? What are the common issues with this configuration?
I just installed the March 2013 update 15.0.4481.1005 (KB2767999) on all of my farm servers according to this article and rebooted. Aside from forgetting to start the timer service on my application server before rebooting (required me to manually start the IIS application pools and central admin website) it all went fine.
However, central admin and the configuration wizard is reporting that my WFE's do not have the update applied. I tried to run the installer again and of course it says that the update is already installed.
In Central Admin the Servers in Farm page shows that the Application sever upgrade is blocked, and the WFE's say installation required.
Patch Status page for one of my WFE's:
SharePoint version on WFE showing it is the correct version:
I've tried iisreset's and complete server restarts. Any help would be appreciated.
I was following the directions below to try to fix an issue where my document library would not give me the option to create a document of type "Report Data Source"
http://technet.microsoft.com/en-us/library/bb326289(v=sql.110).aspx
After doing this step
To enable the content types and content management in all document libraries in an existing Business Intelligence Center site, you can toggle the Reporting Services integration feature.
Go to Site settings.
In SharePoint 2013, click the Settings icon. 
In SharePoint 2010, click Site Actions, then click Site Settings.
Click Site collection features.
Find the Report Server Integration Feature and click Deactivate.
Refresh the browser then click Activate for the Report Server Integration Feature.
Clicking Activate not gives me this error:
The content type with Id 0x010100C3676CDFA2F24E1D949A8BF2B06F6B8B defined in feature {e8389ec7-70fd-4179-a1c4-6fcb4342d7a0} was found in the current site collection or in a subsite
Any pointers on fixing this. I already deleted my power pivot gallery thinking that might be where the content type was defined but I still can't activate the feature.
I need a forum to support my SharePoint related services, and I'd like to host it in the new Office 365.
My requirements are similar to this forum:
- read access for anybody (anonymous or authenticated)
- ability to register at no cost to post questions and answers
Is this possible? I am stuck as the public website doesn't seem to offer anything like forums or discussion boards, while the collaboration sites don't allow anonymous access.
Christophe Humbert Path to SharePoint http://blog.PathToSharePoint.com User Managed Solutions http://UserManagedSolutions.com
I am trying to follow the below MSDN article to install reporting services in sharepoint mode on an application server where sharepoint enterprise edition is already installed.
http://msdn.microsoft.com/en-us/library//jj219068.aspx
I hit a roadblock in step1 (at step 10) where I am not seeing the shared features called "Reporting Services - SharePoint" and "Reporting Services add-in for SharePoint Products".
I am unable to understand why those features are missing from feature selection page.
Any thoughts/ideas?
Thanks!
Hello,
I have been doing some SharePoint 2013 upgrade tests and everything has worked out so far in the test environment, so I decided to start setting up production and stumbled into an issue when starting up the User Profile Synchronization Service.
I have tried every single thing out there (so please don't tell me to make sure my farm account belongs to the admin group because it does), trust me, nothing has worked, although I believed I have made some progress.
Initially I realized there was a problem with the Forefront Identity Manager and FIMsynchronization Service, which I couldn't start. Look to the errors and found this :
Forefront Identity Manager - Required attribute 'externalHostName' not found.
FIMSynchronization Service - The computer_id in the database does not match this computer
So I researched this two issues and fixed them, then tried to start the FIMSynchrinization service and worked (at this point I though i'd nailed it :S) however, when starting the Synchronizaion Service, it stopped, it also sets both services (Forefront Identity Manager & FIMSynchronization Service) as disabled.
Not idea whats happening now but it I feel really tired/frustrated and could use some help.
Pilsen
hii.. i am new to sharepoint 2010. the issue i have is
when i opened central admin
i got this error page
HTTP Error 502 (Bad Gateway): The gateway or proxy server received an invalid response from an upstream server.
please help me
j.rajashekar
please any help
$site=Get-SPSite http://fim1Result:
$site.AllowSelfServiceUpgrade=$false
Exception to establish "AllowSelServiceUpgrade": "Invalid operation given the current state of the object."
In line: 1 Character: 1
+ $site.AllowSelfServiceUpgrade = $false
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], SetValueIncovationException
+ FullyQualifiedErrorId : ExceptionWhenSetting
$sitio = Get-SPSite http://fim1
try { $sitio.AllowSelfServiceUpgrade = $false }
catch [Exception] { Write-Host "`n" $_.Exception "`n" -ForegroundColor Red }
Result:System.InvalidOperationException: Invalid operation given the current state of the object. in Microsoft.SharePoint.SPSite.CheckPermssionForUpdatingUpgradeFlags(Boolean upgradeCheck) in Microsoft.SharePoint.SPSite.SaveLifeCyclePropertiesWithPermissionCheck(LifeCycleFlagField lifeCycleFlags, LifeCycleFlagField mask, Boolean upgradeCheck) in CallSite.Target(Closure , CallSite , Object , Boolean )
I'm trying to install the 180-day trial for SharePoint Server 2013 but when it asks me for the product key, the key provided on the below page does not work for me - NQTMW-K63MQ-39G6H-B2CH9-FRDWJ
Does anybody know why..?
Hello,
I recently upgraded from SharePoint 2010 to 2013. On 2010 we had Office Web Apps but we are not going to use this feature on 2013.
Now, when I click on an Office document in a Document Library, the browser says:
The webpage cannot be displayed
This is the url where the page gets redirected.
ms-excel:ofv|u|https://portal/sites/Business/Document1.xls
I tried turning on & off the 'Default open behavior for browser-enabled documents' option in the Document Library Settings. By the way, this is the behavior for all libraries on the entire farm.
Thanks!
Hi
Do i need to include both https and http for a webapp i put inn the content source for crawling? I am using both urls. While https is the default one.
example:
http://mywebapp
https://mywebapp
br
Bjorn
Hi. I cannot get the personal site collections (mysites/personal) to work, only the profile pages of mysites work (mysites). For instance clicking on the "SkyDrive" or "Sites" link doesn't work - it just redirects back to the profile ("about") page. Also, "Follow"-links on documents don't work.
I've added managed paths:
New-SPManagedPath "mysites" -HostHeader -Explicit #mysite host
New-SPManagedPath "mysites/personal" -HostHeader #mysites
And I've also successfully created the mysite host:
New-SPSite -url "https://$customerName.sphosting.company.no/mysites" -SiteSubscription $sub -HostHeaderWebApplication $webApp -owneralias $customerTenantAdmin -owneremail $customerTenantAdminEmail -template SPSMSITEHOST#0
$upaProxy = Get-SPServiceApplicationProxy | where-object {$_.DisplayName -eq $upaProxyName}
Add-SPSiteSubscriptionProfileConfig -id $sub -SynchronizationOU $customerName -MySiteHostLocation "https://$customerName.sphosting.company.no/mysites" -MySiteManagedPath "/mysites/personal" -SiteNamingConflictResolution "None" -ProfileServiceApplicationProxy $upaProxy
No error on these scripts. I've also turned on Self-Service Site creation. However, still personal sites are not created when users access mysite. Any idea what is wrong?
Pål A
Hi, I've a SharePoint 2013 farm whose SP Health Analyzer is showing 3 accounts running as SPfarm.
One was the distributed cache service which I've sorted.
One is the User profile Syn service which I know needs to run as the Farm account.
The other is SPSearchHostController(Windows Service) - SharePoint Search Host Controller
I can't find any technical information on the method of changing this service to run under a different account.
Does anyone know if this service can be changed to a managed SP account through CA without giving any specific permissions beforehand?
Thanks
Hi all.
I seem to be having an issue with exporting sharepoint properties to AD. Importing works fine the issue only starts to happen if I try and export more than 1 property.
I've replaced the user profile service a number of times as part of my testing and I'm still trolling through all the SQL commands that take place when I create the export link so it's still a WIP.
Process: Standard sharepoint to AD mappings with all set to Import. Tested and works fine - no issues.
Edit an attribute (eg workphone), remove the import map and create a new export map. Tested and works fine.
Edit another attribute (eg department), remove the import map and create a new export map. Click OK to get back to property listings and I now have 2 sharepoint attributes mapped to the same AD property. Work Phone->telephonenumber and Department->Telephonenumber.
Editing either one of these properties and I can see both export maps listed in the properties....and I can also create another mapping if I want (this should not be possible with a mapping already done).
Doing a third property change - I end up with 3 sharepoint properties going to the same AD attribute....
I've tried a number of options for the mapping process (eg reboot / full sync inbetween each step of the property change) but there's no difference.
Our old SP2010 server worked fine (and still does if I re-enable the sync) using this process and I also tried a setting comparison between the 2 systems just to make sure.
Has anyone seen this before? and if so - where's the best starting point to tracking down the issue? (aside from the usual ULS logs and trying to decode the sql tables...)
Thanks.
JohnB.