Pirobase and sharepoint server in ep

Hi,
Can anyone tell me if we can use Pirobase as the content management with EP and Sharepoint server for collaboration with EP.If yes, where to find the documents related to the same.
rgds,
Rohit

for first approach.
1- go to central admin and add all roles you need for the server that will stay
2- log into the server you will remove then run configuration wizard and choose disconnect from farm
you will have now one server, you can clean it up and keep it or later remove it when u have the new one
3- to add new server
https://technet.microsoft.com/en-us/library/cc261752.aspx
Kind Regards,
John Naguib
Senior Consultant
John Naguib Blog
John Naguib Twitter
Please remember to mark this as answered if it helped you

Similar Messages

How to integrate AD CS and SharePoint Server

Dear Expert,
I will set up the lab for digital signature, I have AD CS and SharePoint Server in separate machine.
How do I integrate? and it's possible to use SharePoint for digital signature solution.
Can you share How to?

Hi,
For the documents which are stored on SharePoint server, user can easily find out who had edited the documen by the ModifiedBy column, and the version history, so there is no need to sign them.
If you want to provide furthur protect after the document has been downloaded from SharePoint, you can consider AD RMS integration with SharePoint, i.e., the information right management.
For more information, you can have a look at the blogs:
http://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-active-directory-certificate-service-in-your-windows-server-2008-r2.aspx
http://technet.microsoft.com/en-us/library/cc545900.aspx
http://download.microsoft.com/download/3/6/B/36B2F4F5-55AD-4D64-BC5B-62B536E35A62/SharePoint-2013-Configuration-Guidance-for-21-CFR-Part-11%20v2.pdf
Best Regards,
Eric
Eric Tao
TechNet Community Support

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Scale out sharepoint server search to index server and Microsoft SharePoint Foundation Web Application to new server

Hi
in my single server these below service are running:
SharePoint Server Search
User Profile Service
Microsoft SharePoint Foundation Web Application
here how i scale out Microsoft SharePoint Foundation Web Application to another server
and SharePoint Server Search to new index server.
adil

Check here to see how to add servers to the farm:
http://technet.microsoft.com/en-us/library/cc261752(v=office.15).aspx
What Inderjeet meant was that if you chose to install SharePoint as a single server instead of a complete farm, you won't be able to add servers to the farm at a later time. You can check if this is the case by checking the registry key he mentioned. If
that is indeed the case, there's nothing to it but reinstall the farm.
So that is why you never should choose the single server option, it locks you in and limits future options, while choosing to install sharepoint as a complete farm it's still perfectly acceptable to host it on a single server.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Clarification on SharePoint Online and SQL Server

I have several subsites on a SharePoint 2013 server that uses external content types and the Business Data Connectivity Service to access tables in a SQL Server database. I used the Sharepoint 2013 Designer to configure most of this, but at times, I also
used Visual Studio 2013. Everything works fine. It successfully uses a secure store Application ID to authenticate connections to a remote SQL Server (i.e. the SQL Server and SharePoint server are 2 completely different machines that are not even within the
same domain). The external lists on the SharePoint site are capable of reading data in the SQL tables, updating data, adding new data, and deleting old data. I have specified permissions to users/groups that help me control who can access the external lists
on the SharePoint sites. Everything has been working well for a while now.
But now I have to start thinking about using SharePoint Online, instead of an on-premises SharePoint server. And everything I am reading indicates that what I do above is not going to work with SharePoint Online. It sounds like I will have to either move
our database to a SQL Azure service, or if I want to continue using our existing SQL Server, then I am going to have to develop a WCF service that will allow SharePoint Online to communicate with our own SQL Server. Am I understanding this correctly? Or is
there a way to take what I did above and make it work with SharePoint Online?
Thank you,
Steven

Hi,
We can use Hybrid Connections to connect SharePoint Online to an on-premises SQL Server.
Here is a blog from MSDN for your reference:
http://blogs.msdn.com/b/alimaz/archive/2014/07/31/connect-sharepoint-online-to-an-on-premises-sql-server-from-an-azure-provider-hosted-app-using-hybrid-connections.aspx
We can also customize a WCF service and publish it to public web site to achieve it.
Best Regards
Dennis Guo
TechNet Community Support

Upgrading both SharePoint 2010 server and DB server with latest available patch

We have 2 servers in the farm ( SharePoint server and Database server)
We are planning to patch the database server and SharePoint server as well at the same time.
For this activity I have found some ways :
Way 1:
First I will do the patching in SP server and run the configuration wizard.
Once it's finished , I will shutdown the SP server.
Start patching in SQL server
After done in Sql server , I will restart the SP server.
Way 2:
First I will do the patching in SP server and run the configuration wizard.
Once it's finished , I will disconnect the SP server from SQL server by using the configuration wizard.
Start patching in SQL server
After done in Sql server , I will reconnect both the server's.
Way 3:
I don't follow any one of the above ways. Simply patch both the server's one by one (Here might be, when we do the DB server patch upgrade database connection failed entries will be track into event viewer because of DB server unavailability )
Here my questions are :
If disconnect the server's from each other , can I reestablish the connection again ?? Is there that option ???
Is it compulsory to disconnect / shutdown the SP server while patching in DB server ???????
Suppose I don't follow any of the above way , cause any issues ?????
If any DB connection related entries will track into Event Viewer, is this cause any issues ?????
Any suggestions would be appreciated.
RameshNK

Patching order will not matter. You also do not necessarily have to shutdown SharePoint while patching SQL. Yes, SharePoint will throw errors in the Event Log and ULS log.
I might suggest patching SQL Server first, simply because it is quick and in my experience, "safe". That is, the patching process works and works well. It is unlikely you'll come out with an unserviceable SQL Server instance.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
Thanks a lot.

Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks.

SharePoint server 2013 Search Service App on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Microsoft SharePoint Server 2013 encountered an error during setup

(the html editor over here is a pain you know where - not even bold text is working...)
Every time I try to install SP 2013 SP1 on my WS 2012 R2 Update virtual machine the installer dies.
NOTE: I can reproduce this any time. Both the SharePoint 2013 (including SP1) .iso as well as the WS 2012 R2 (including Update) .iso are fresh copies out of the MSDN library.
The installation fails where the installer tries to install the binaries. No configuration wizard yet. I made sure all the prerequisites are there. The PreRequisitesInstaller.exe reboots the virtual machine several times (twice) and then it is all set.
PS C:\Users\bsom> add-windowsfeature net-wcf-http-activation45, net-wcf-tcp-activation45,net-wcf-pipe-activation45
Success Restart Needed Exit Code Feature Result
True No NoChangeNeeded {}
PS C:\Users\rsom> Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,
Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-
Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-A
uth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Conso
le,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation
,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Sc
ripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer
Success Restart Needed Exit Code Feature Result
True No NoChangeNeeded {}
PS C:\Users\bsom>
UPDATE: I had a quick look at %Temp%\SharePoint Server Setup(20140513...).log
2014/05/13 20:30:40:858::[2344] Log level changed from: Verbose to: Standard
2014/05/13 20:30:40:858::[2344] Error: Failed to install product: D:\global\oserver.MSI ErrorCode: 1603(0x643).
2014/05/13 20:30:40:858::[2344] Log level changed from: Standard to: Verbose
2014/05/13 20:30:40:858::[2344] Rolling back chain
Any ideas?
UPDATE: Installing office prior to the sharepoint installation had no effect (solution was suggested here).
UPDATE: Installing all windows updates (for Windows Server and Office client applications) didn't help either... same error.
UPDATE: I made sure my windows server and sharepoint server images are exactly those you can currently find on MSDN. SHA1 hashes match.

I just did a Server 2012 R2 and SP 2013 w/ SP1 install the other night on Hyper-V running on 8.1 Pro without issues. ISO was from MSDN.
Have you run a crc (or md5, forget what is used) to validate the ISO matches what MSDN says it should be?
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint Server Publishing infrastructure - Sorry, you don't have access to this page

If I enable site feature on Any site in any site collection on Sharepoint farm,
every one get lock out (include Farm admin, ect) with error Sorry, you don't have access to this page.
I have to go to Web application -> User Policies Add: NT Authority\Authenticated Users, so that I can
log in to site, disable feature and everything start to work.
On : Site Collection Administration -> Site Collection Features
-> SharePoint Server Publishing Infrastructure : is activated
Infrastructure : I use Host name site collection, all effected sites are located in the same web application.
I think problem is with “SharePoint Server Publishing Infrastructure”. Because if I enable
that feature on site collection, then o have problem choosing together
SharePoint Server Standard Site Collection features and SharePoint Server Enterprise Site Collection features
If SharePoint Server Publishing Infrastructure is enabled, if a activate Standard Site Collection features , then choosing Server Enterprise Site Collection features, produce error : Sorry, something went wrong.
But I can enabled both features “Standard Site & Server Enterprise” before enabling SharePoint Server Publishing Infrastructure.
ULS logs, when I enable SharePoint Server Publishing Infrastructure :
From bottom up : Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|DOMAIN\user1, ClaimsCount=55
DelegateControl: Exception thrown while adding control 'Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource':
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid&
pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002), StackTrace:
at Microsoft.SharePoint.SPWeb.GetObjectForUrl(String strUrl, Guid& listId)
at Microsoft.SharePoint.Utilities.SPUtility.<>c__DisplayClass9.<FindObjectAccessed>b__8()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Utilities.SPUtility.FindObjectAccessed(SPWeb web, SPSite site, SPObjectType&
objType, String& strObject, String& strListItemId)
at Microsoft.SharePoint.Utilities.SPUtility.RedirectToAccessDeniedPage(HttpContext context)
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(HttpContext context)
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid&
pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControlsInternal()
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at Microsoft.SharePoint.WebControls.DelegateControl.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
SPRequest.GetMetadataForUrl: UserPrincipalName=, AppPrincipalName= ,bstrUrl=/_layouts/15/ManageFeatures.aspx ,METADATAFLAGS=59
Unknown SPRequest error occurred. More information: 0x80070002
Access Denied. Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)), StackTrace:
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS,
Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32&
plItemId, Int32& plType, Object& pvarFileOrFolder).
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)), StackTrace:
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControlsInternal()
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at Microsoft.SharePoint.WebControls.DelegateControl.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
SPRequest.GetMetadataForUrl: UserPrincipalName=i:0).w|s-1-5-21-1794000256-2036170096-312552118-17692, AppPrincipalName= ,bstrUrl=/Cache Profiles ,METADATAFLAGS=59
Feature Activation: Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') was activated at URL
https://intranet.domain.com.
Calling 'FeatureActivated' method of SPFeatureReceiver for Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa').
Feature Activation: Activating Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') at URL
https://intranet.domain.com.

Hi Mali,
According to your description, my understanding is that users cannot access the SharePoint site if SharePoint Server Publishing Infrastructure is enabled.
If I misunderstood please feel free to correct me.
I recommend use PowerShell to activate the feature in SharePoint 2013 to see if the issue still occurs.
http://technet.microsoft.com/en-us/library/ff607803(v=office.15).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

After installing Project Server 2013 (without updating SharePoint Server 2013 SP1))

I am facing the problem while opening project web app. I configured the SharePoint 2013 and project server 2013. Here is the detail what I performed the steps:
OS Server 2012 R2, SQL Server 2012, SharePoint server 2013 version
15.0.4420.1017, Project Server 2013 version
15.0.4454.1000. SharePoint configured and running successfully. After project web app site provisioning successfully completed. I got the below error.
Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly 'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' cannot reduce access.
I run this psconfig -cmd upgrade -inplace b2b -wait -force. But still getting same error.
Previous steps:
Earlier I had also tried to install SharePoint Server 2013 SP1 "3823428". After the installation SP1 some of sharePoint site features suddenly stopped e.g: Cannot browse "Service Applications -->
Manage service applications" option even after re-start the server. This was previous error after upgrading SP1
"Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation"
Anyone can help me!!! Thanks...
Faisal Numan

hello,
For SP2013 and PS2013 to work properly on Windows Server 2012 R2 you need to use the SP1 install media for both, download SharePoint 2013 with SP1 and Project Server 2013 with SP1
http://support.microsoft.com/kb/2891274
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

SharePoint Server 2010 can't connect to the Configuration Database

Hi Techys,
I have a SharePoint Server 2010 Farm, and I have Installed SharePoint SP1 package,
Then I,m trying to run the SharePoint configuration wizard, That time i have the below error.
"Can't connect to the Configuration Database"
I have checked all the services belongs to the sql server and SharePoint server.
here i found, SharePoint Timer service is automatically Stopped while browsing the Central admin url.
Please help me to resolve the above issue.
Many Thanks,
Madhu

What you mean error in Config wizard, could you please share the complete error log?
For Timer Services, check under which account it is running and check event log why its stoped?
for CA error there are couple of possible reason for this:
Make sure SQL related instances / services are running fine.
Make sure your farm admin account have permission on config DB.
Make sure Config Database Exist.
Make sure you can connect to SQL server from your APP /WFE.
If everything is running fine, then you may need to reconfigure the sharepiont products and technologies configuration wizard. The issues might be because of the update that might have installed some additional components for installation.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Deploy Exchange 2013 , Lync server 2013 and shrepoint server 2013

Hi dears ,
I have a deployment requirement in which I have to plan for deploy Exchange 2013 , Lync server 2013 and SharePoint server 2013 on premise for 500 user and for one organization , now I have been asked to provide the software and hardware requirement
for this deployment .
so I wonder , is there any guide or link to find the hardware and software requirements for this deployment ?

Hi,
You can refer to the link below about the hardware/system requirements for Lync Server 2013:
https://technet.microsoft.com/en-us/library/gg398438.aspx
Note: it is not supported to install Lync Server in the same computer with DC, Exchange Server and SharePoint Server.
If you want to deploy Lync Server, you’d better read the guide firstly before deploy it:
https://technet.microsoft.com/en-us/library/gg398616.aspx
For the deployment of Exchange 2013 and SharePoint 2013, you can also post case on Exchange and SharePoint forum, and there are more experts will help you:
Exchange 2013:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
SharePoint 2013:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=sharepoint
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Sync CROD with Sharepoint Server 2007

Is it possible to somehow sync automatically contacts between CROD and Sharepoint Server 2007? What I would like to do is that contacts are exported and sync auytomatically each time there is a new contact from CROD to SS2007.

I would recommend posting this question on the CRM On Demand Integration Development forum.

Office 2013 and SharePoint 2013 server properties - The required term set is not available.

Hi,
After creating new document from ribbon with the new document function on any template the managed metadata based server properties cannot be selected and properties boxes are grayed out. Mouse over displays "The Required term set is not available".
Works fine when using it form resource (SharePoint) domain both with user domain and resource domain accounts.
There is a two-way trust btw domains.
SPNs are done for AppPools.
AppPool accounts have delegations and are set to impersonate with GPO.
SharePoint Web Application is on kerberos authentication.
There is no difference when sites are using user or resource domain AppPool accounts.
The WFE and SQL Server have computer delegations.
Server env: Windows Server 2008 R2 with all updates, SQL Server 2008 R2 with all updates, on-prem SharePoint Server 2013 with no CU.
User env: Windows 7 ENT, IE10 and Office 2013 with all updates.
There is no internet connection and internet connection is not possible. The internet connection is cheated with two DNS A record setting for
www.msftncsi.com and dns.msftncsi.com. Also registry changes "ActiveDnsProbeContent" ip- address for Win7 is done via GPO to private IP. This is done because otherwise check-in/check-out does not work.
Last things on IIS log are:
2014-01-24 10:38:36 192.168.n.n PROPFIND /TestDoc - 5445 0#.w|userdomain\test3-user 192.168.51.51 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 207 0 0 639
2014-01-24 10:38:37 192.168.n.m OPTIONS / - 5445 0#.w|userdomain\test3-user 192.168.51.51 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 842
2014-01-24 10:38:54 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
2014-01-24 10:39:25 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 0
2014-01-24 10:39:56 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
2014-01-24 10:40:27 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
What I missed.
Br,
-timo-

Same problem here!. Giving the computer network access allows the control to be populated. Then I disabled and restarted and it seems to be ok....

Pirobase and sharepoint server in ep

Similar Messages

Maybe you are looking for