Sharepoint Foundation 2013 - Databases running in compatibility range, upgrade recommended

I have an issue with Search within my SharePoint Foundation 2013 Farm. This is a new Farm, so I can remove the search service application and re-create if this is a way that can clear the 2 issues I am experiencing.
Issue:
My search service application seems to be working fine as I am able to crawl content and retrieve results, however the DB's associted with this search service application are reported with the following warning within the SharePoint Health Analyzer. I have
been unable to run the Upgrade-SPContentDatabase command against these databases as I get a message saying that the content database could not be found:
Title
Databases running in compatibility range, upgrade recommended.
Severity
2 - Warning
Category
Configuration
Explanation
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
Search_Service_Application_AnalyticsReportingStoreDB_a3c64b2f3b9b4a5d83383ec0b1ecfcf4,
Search_Service_Application_CrawlStoreDB_ffb8d716450242cc849a7f44f521bfc9,
Search_Service_Application_DB_0fe433c02db6435db85285e9fd83863e,
Search_Service_Application_LinksStoreDB_75efb2f689cf49f19c98a5a8155e47b7.
Remedy
To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
Kevin Evans

http://social.technet.microsoft.com/Forums/sharepoint/en-US/d6b8a59c-e432-43a2-9581-d281c8cb7fb4/databases-running-in-compatibility-range-upgrade-recommended
ran these hotfixes on my frontends:
417831_intl_x64_zip.exe
429437_intl_x64_zip.exe
429440_intl_x64_zip.exe
Restarted and followed by 1,2,3
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
If you recently applied any hotfix check
http://blog.entos.at/Lists/Posts/Post.aspx?ID=14
If this helped you resolve your issue, please mark it Answered

Similar Messages

Databases running in compatibility range, upgrade recommended. Sharepoint 2010 SP2 after installing December 2013 CU

I just installed December 2013 CU for Sharepoint 2010 with SP2. I runned the Product Configuration Wizards a couple of time and exexute "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures".
But still I'm left with one database that is out of date.
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
Search_Services_Application_DB_0256be25a85b4c3081387181e4a8c6c7.
Do you know what can I try next to fix this?
Thanks!

Hi Steve,
In the Upgrade log what is the error when PSconfig attempts the Upgrade, I am assuming it completes with a warning?
Cheers,
-Ivan

Duplicate Search Databases in SharePoint Foundation 2013 Farm

I seem to have 2 seperate issues with Search within my SharePoint Foundation 2013 Farm. This is a new Farm, so I can remove the search service application and re-create if this is a way that can clear the 2 issues I am experiencing.
Issue 1:
For some reason I have 2 instances of the following search related DB's:
SearchAdminDatabase
SearchAnalyticsReportingDatabase
SearchGathererDatabase
SearchLinksDatabase
1 instance of each of the databases all report database status of "No Action Required" and the other instance of all the DB's report a database status of "Not Responding".
Issue 2:
My search service application seems to be working fine as I am able to crawl content and retrieve results, however the DB's associted with this search service application are reported with the following warning within the SharePoint Health Analyzer. I have
been unable to run the Upgrade-SPContentDatabase command against these databases as I get a message saying that the content database could not be found:
Title
Databases running in compatibility range, upgrade recommended.
Severity
2 - Warning
Category
Configuration
Explanation
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
Search_Service_Application_AnalyticsReportingStoreDB_a3c64b2f3b9b4a5d83383ec0b1ecfcf4,
Search_Service_Application_CrawlStoreDB_ffb8d716450242cc849a7f44f521bfc9,
Search_Service_Application_DB_0fe433c02db6435db85285e9fd83863e,
Search_Service_Application_LinksStoreDB_75efb2f689cf49f19c98a5a8155e47b7.
Remedy
To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
Kevin Evans

At time people create search service application and delete it. SA is deleted but database were not deleted for some reason. so these might be those stale database. You can delete them if you want
http://blogs.technet.com/b/tothesharepoint/archive/2011/12/19/find-active-databases-used-by-sharepoint-server-2010.aspx
If you want a report of all of your SharePoint databases that includes the GUIDs and related property values, use the SharePoint 2010 Management Shell.
There are several Windows PowerShell cmdlets you can use to find all of the SharePoint databases and then print this report to a text file. The quickest and perhaps easiest cmdlet is “Get-SPDatabase”. Run this cmdlet in the SharePoint
2010 Management Shell to list all of the SharePoint Server databases with properties for each one. From this potentially large list you can then obtain specific information such as the database ID by using additional syntax in your cmdlet. Similarly, also
in the SharePoint 2010 Management Shell, run “Get-SPDatabase | Sort-Object
disksizerequired -desc | Format-Table Name” and you will get a simple list of the names for each database. You can then print this list to a text file by adding, “| out-file c:\db.txt” to the end of the command.
For detailed information, see
Windows PowerShell for SharePoint Server 2010,
Database cmdlets,
Get-SPDatabase, and
Get-SPContentDatabase.
If this helped you resolve your issue, please mark it Answered

Do I have to install SharePoint Foundation 2013 via a script in order to name my content databases without the GUID references?

Hi,
I want to install SharePoint Foundation 2013 on a standalone server with SQL Express but I want to be able to name the content databases without their GUID references. Will I have to use an install script (AutoSPInstaller perhaps?) to achieve this?
Thanks.

You can't do a standalone install if you want the alias (also if you plan to move the databases in the future)
You'll need to create the alias before you create the farm with the Configuration wizard or PowerShell so you can specify the alias. Whether you create the alias before or after installing SQL Express doesn't matter as long as it points to the instance.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

SharePoint Foundation 2013 Optimization For Large File Transfer?

We are considering upgrading from WSS 3.0 to SharePoint Foundation 2013.
One of the improvements we want to see after the upgrade is a better user experience when downloading large files. It can be done now, but it is not reliable.
Our document library consists of mostly average sized Office documents, but it also includes some audio and video files and software installer package zip files ranging from 100MB to 2GB in size.
I know we can change the settings to "allow" larger than default file downloads but how do we optimize the server setup to make these large file transfers work as seamlessly as possible? More RAM on the SharePoint Foundation server? Other Windows,
SharePoint or IIS optimizations? The files will often be downloaded from the Internet, so we will not have control over the download speed.

SharePoint is capable of sending large files, it is an HTTP stateless system like any other website in that regard. Given your server is sized appropriately for the amount of concurrent traffic you expect, I don't see any special optimizations required.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
I see information like this posted warning against doing it as if large files are going to cause your SharePoint server and SQL to crash.
http://blogs.technet.com/b/praveenh/archive/2012/11/16/issues-with-uploading-large-documents-on-document-library-wss-3-0-amp-moss-2007.aspx
"Though SharePoint is meant to handle files that are up to 2 gigs in size, it is not practically feasible and not recommended as well."
"Not practically feasible" sounds like a pretty dire warning to stay away from large files.
I had seen some other links warning that large file in the SharePoint database causes problems with fragmentation and large amounts of wasted space that doesn't go away when files are removed or that the server may run out of memory because downloaded
files are held in RAM.

Sharepoint Foundation 2013 On a SBS 2011 Domain??

I have an SBS 2011 domain with 2 servers(SBS2011 Premium) The SBS box acts as domain controller and the second server runs Server 2008R2 and has SQL 2008R2 on it for Dynamics GP and Dynamics CRM 2011 and hosts the Sharepoint Foundation 2010 Databases. Is
there a way that I can setup a Sharepoint Foundation 2013 farm. Currently both boxes are farm members in the 2010 farm. I would like to keep the setup similar but if I have to can I just run the farm on the 2nd server. Will it live side by side with the Sharepoint
2010 on the SBS box. What about Companyweb? Thanks in advance
Joe Powers

I guess SBS guys will be the right people to answer your query, please post you question on the below forum:
http://social.technet.microsoft.com/Forums/en-US/home?category=sbsserver
Please ensure that you mark a question as Answered once you receive a satisfactory response.

SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

Hi
I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
into WSS 3.0 Farm A before the migration to SP 2010.
My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?
Thanks.

The answer is Yes, and you are correct about the best practice of a limit of 100GB,
although, document and record centers (e.g. non collaborative) can go much higher.
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#ContentDB
That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each. You can use Move-SPSite to accomplish that feat.
You'll want a separate instance for 2010 and a separate instance for 2013
and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
please check the below link that explains more about the migration from share point 2007->2013.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15)
Stacy www.sharepointpapa.com

SharePoint Foundation 2013 Web Analytics

Problem:
I am using SharePoint Foundations 2013 (no patches) and trying to get Web Analytics working but running into difficulty. The error I am getting is the dreaded, "A web analytics report
is not available for this site. Usage processing may be disabled on this server or the usage data for this site has not been processed yet.", when I click on Site Settings -> Site Web analytics reports
Items completed:
Enabled Site Usage and data collection in Central Admin.
Logs are full of data in the hive
I can see the data in dbo.requestusage in the WSS logging database.
Possible problem is that Web Analytics has been deprecated in SharePoint 2013 however why would Microsoft have Web analytics link if it was deprecated.
Question:
How can I get Web Analytics to show data or has it been completely removed from SharePoint Foundations 2013 and the link is just there for frustration?
Jay

We’re having the same Problem.
According to the following links, “Usage Analytics” and “Usage Reporting and Logging” are
available in SharePoint Foundation 2013:
http://www.khamis.net/blog/Lists/Posts/Post.aspx?ID=96
http://blog.blksthl.com/2013/01/14/sharepoint-2013-feature-comparison-chart-all-editions/
Are they wrong?
I don’t mean the search related Reports (Most Popular Items), I mean the very simple Reports like
Number of Page Views, Number of Unique Visitors, Number of Referrers, Top Pages/Visitors/Referrers/Browsers (URL: /_layouts/15/usageDetails.aspx)
Sharepoint Hosting und Beratung www.sharepoint-foundation-hosting.ch

Provision Search in SharePoint Foundation 2013 without Domain Controller / Active Directory - Domain accounts

Hi,
I have successfully setup SharePoint Foundation 2013 as single server farm with SQL Server Standard database in a DMZ environment using local accounts since DMZ doesn't have an Active Directory and hence Domain accounts using powershell as described
in https://theblobfarm.wordpress.com/2012/12/03/installing-sharepoint-2013-without-a-domain-controller
When I run Farm configuration wizard to provision search service application, I get an error:
ERROR: "The service application(s) for the service "Search Service Application" could not be provisioned because of the following error: I/O error occurred."
The log file logged the details of this error as:
ERROR: "Failed to create file share Analytics_e441aa1c-1a8d-4f0a-a079-58b499eb4c50 at D:\SharePoint Search\Office Server\Analytics_e441aa1c-1a8d-4f0a-a079-58b499eb4c50 (System.ArgumentException: The SDDL string contains an invalid sid or a sid
that cannot be translated."
After investigation, I found that potentially the error could be because the timer service is trying to setup a network share for analytics component (as part of provisioning search). It is trying to setup that share with a domain account that happens to
be a local user instead in this case and fails with error “System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated”.
I got some pointer from the below thread
https://social.technet.microsoft.com/Forums/en-US/c8e93984-f4e5-46da-8e8a-c5c79ea1ff62/error-creating-search-service-application-on-sharepoint-foundation-with-local-account?forum=sharepointadmin
However, the above thread doesn't state that the solution worked.
I have tried creating share manually for Analytics_<Guid> folder but it doesn't work since every time farm configuration wizards is run it creates a new Analytics_<Guid> folder.
Since, I have setup SharePoint Foundation 2013 on a production environment I cannot test and trial various solutions.
Can some please guide me on how to successfully provision search for SharePoint Foundation 2013 setup as a single server farm with SQL Server Standard database in a DMZ environment using local accounts (without Active Directory - domain accounts).
Thanks in advance.
Himanshu

Microsoft documentation doesn't always specifically call out all products (Project Server isn't there, either). But it does apply. You'll need to stand up at least one Domain Controller, or allow port access back to a DC.
Preferably, set up SharePoint on the internal network and use a reverse proxy (which will terminate client connections at the reverse proxy) present in the DMZ.
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.

Users in new OU in Active Directory have to enter credentials when accessing SharePoint Foundation 2013

Hi,
We have a SharePoint farm consisting of one web front end server and one database server, running SharePoint Foundation 2013. This farm has been up and running for over a year and uses AD for authentication, and SharePoint groups for authorization.
The problem we are seeing is when we create a new Organizational Unit in AD, and add users under this new OU they are prompted for their credentials when trying to access SharePoint. We've done the below tests to narrow the issue down:
1) New user (xxx) in new OU (111) logs into Windows PC and tries to access SharePoint via IE 10 -- they are prompted for their credentials. They are required to enter their username as 'domain\username' to be able to log in successfully to SharePoint.
2) Existing user (yyy), in existing OU (222) logs into same Windows PC and tries to access SharePoint via IE 10 -- they are NOT prompted for their credentials and get into SharePoint successfully.
3) Existing user (yyy) is moved into new OU (111), logs into same Windows PC and tries to access SharePoint via IE 10 -- they are prompted for credentials and need to use 'domain\username' to log in to SharePoint
4) Existing user (yyy) is moved out of new OU (111) and back into their old OU (222), logs into same Windows PC and tries to access SharePoint via IE 10 -- they are prompted for credentials and need to use 'domain\username' to log in to SharePoint
Note: both the new OU (111) and old OU (222) are within the same parent OU.
1 & 2 combined tell me that it's not a PC or IE issue. We've also tried 1 & 2 on multiple PCs so that would eliminate a profile issue as well.
To me it seems that SharePoint doesn't know that the new OU is in our domain, so it doesn't think the users within the new OU are in our domain, which is why they have to supply the domain with their username when logging in...but I'm not exactly an expert
when it comes to AD so this is just a guess on my part.
As a long shot, what I thought may fix it would be by syncing AD with SharePoint by using User Profile Synchronization, but it's not offered as part of SharePoint Foundation, so I used this nice solution at CodePlex (https://foundationsync.codeplex.com/),
but that did not fix it.
Does anyone have any ideas on how to fix this? Or what the issue may be?
Thanks,
Shaun

Hi Christopher,
Thanks for the reply.
I feel very stupid right now -- I did look at this before posting this question to the forum, but it seems I didn't look far enough.
We have a GPO that enters our domain into the 'Local intranet' of IE. Our SharePoint site's URL is "http://sharepoint.ourdomain.com" and we've got "*.ourdomain.com" under Local intranet sites. But, I also found the FQDN "sharepoint.ourdomain.com"
under 'Trusted sites' and that seems to confuse SharePoint because once I moved the FQDN to Local intranet, and removed it from Trusted Sites, the user is now not prompted for their credentials when going into SharePoint.
Thanks for your reply in making me take a second look.
EDIT: We've just removed the FQDN from Local intranet, so all we have is "*.ourdomain.com" under Local intranet and it works as well.
Regards,
Shaun

When connecting to a server farm in sharepoint foundation 2013 cannot create new farm error: One or more types failed to load

When trying to create a new server farm in the sharepoint foundation 2013 we get a following error :
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.
PS C:\Users\Administrator> New-SPConfigurationDatabase
cmdlet New-SPConfigurationDatabase at command pipeline position 1
Supply values for the following parameters:
DatabaseName: SharePoint_Config
DatabaseServer: PC78\SQLEXPRESS,25111
FarmCredentials
Passphrase: *********
New-SPConfigurationDatabase : One or more types failed to load. Please refer
to the upgrade log for more details.
At line:1 char:1
+ New-SPConfigurationDatabase
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:
SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], SPUpgra
deException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon
figurationDatabase
And the error log is shown below :
Microsoft.SharePoint.Upgrade.SPUpgradeException: One or more types failed to load.
Please refer to the upgrade log for more details.
at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_ActionsInternal()
at Microsoft.SharePoint.Upgrade.SPUtility.GetLatestTargetSchemaVersionByMajorVersion(Type typeActionSequence, Int32 majorVer)
at Microsoft.SharePoint.Upgrade.SPUtility.get_CurrentSPSiteWssTargetSchemaVersion()
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPContentDatabase database, SPSiteSubscription siteSubscription, String siteUrl, String title, String description, UInt32 nLCID, Int32 compatibilityLevel, String webTemplate, String ownerLogin, String ownerName, String ownerEmail, Strin... b712a522-fa85-49eb-b59c-dedf55295504
...g secondaryContactLogin, String secondaryContactName, String secondaryContactEmail, String quotaTemplate, String sscRootWebUrl, Boolean useHostHeaderAsSiteName, Boolean overrideCompatibilityRestriction)
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPSiteSubscription siteSubscription, String siteUrl, String title, String description, UInt32 nLCID, Int32 compatibilityLevel, String webTemplate, String ownerLogin, String ownerName, String ownerEmail, String secondaryContactLogin, String secondaryContactName, String secondaryContactEmail, Boolean useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance(SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, ... b712a522-fa85-49eb-b59c-dedf55295504
...String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuil... b712a522-fa85-49eb-b59c-dedf55295504
...der configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase.InternalProcessRecord()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord() b712a522-fa85-49eb-b59c-dedf55295504
Error Category: InvalidData Target Object Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase Details NULL RecommendedAction NULL b712a522-fa85-49eb-b59c-dedf55295504
Leaving ProcessRecord Method of New-SPConfigurationDatabase. e9ae5ba6-c499-0000-d35c-aee999c4cf01
we are using server 2012 R2 and we don't have office 2010 installed

Yes,SQL server is on the same server as SharePoint
SQL has both the permissions Securityadmin
and DBcreator roles on SQL Server.
When we run those sharepoint management shell commands the database will be created with the error
msg (shown in attachment)

SharePoint Foundation 2013 - March 2014 Update Issue - Need help

We've just applied the SharePoint Foundation 2013 March 2014 Update, it always requires that we run the SharePoint Products Configuration Wizard at the end of install, but this time it's getting stuck at step 9 of 10 (the profile sync service cannot be
started even as admin). Is anyone else having any issues with this update? Has anyone else applied it yet? Is anyone else planning to apply it?
If anyone can help with advice on this I'd appreciate it.

Hi,
We can still access CA but sync will not start. Tried rebooting after the failed configuration and tried to run it again but it didn't work.
4/2014 10:45:16 5 ERR            Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc
that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 5 ERR            An exception of type System.ServiceModel.EndpointNotFoundException was thrown. Additional exception information: There was no endpoint listening at
http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at //localhost:32843/SecurityTokenServiceApplication/securitytoken. that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException,
if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 1 ERR          One or more configuration tasks has failed or some tasks were not run
4/2014 10:45:16 1 INF          Leaving function TaskDriver.OnTaskDriverStopping
04/14/2014 10:45:16 1 INF        Leaving function TaskDriver.ExecuteTasks
04/14/2014 10:45:16 1 ERR        One or more configuration tasks has failed to execute
4/2014 10:45:16 1 ERR          Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review
the extended error information located at D:\Logs\PSCDiagnostics_4_14_2014_10_44_8_154_1605984328.log, fix the problem, and run this configuration wizard again.
04/14/2014 10:45:16 1 INF          Entering function StringResourceManager.GetResourceString
4/2014 10:45:16 1 INF      Leaving function TaskDriver.Run
04/14/2014 10:45:16 1 ERR      Post setup configuration was not run successfully when using the command line task driver module
04/14/2014 10:45:16 1 INF    Leaving function PsconfigCommandLineMain.Main
This is the meaty part of the errors we are getting. Right now our entire site is down. If you know of anything to remedy these errors let me know.

SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

Hi,
We have a SharePoint Foundation 2013 with SP1 Environment.
In that, we have 2 Front-End Servers and 2 App Servers. In the Front-End Servers, the Search Service is stopped and is in Disabled state and in the 2 App Servers in One App Server, Search is Online and in another Search is Starting but goes to Stopped sooon
after.
Originally, we had only 1 App Server and we were running our Search Service and Search Service Application in that. Now since the index location became full and we were unable to increase the drive there, we added one more App Server and now the issue is
Search is not properly getting configured in either of these App servers. What we want to do is run Search only in the new App Server, because we have a lot of storage space for Index locations here, but in the older App Server, not run Search at all. We
tried keeping the Search Service disabled and ran the below PowerShell Scripts, but none of the ones are working. These scripts are creating the Search Service Application, but the error of "Admin Component is not Online", "Could not connect
to the machine hosting SharePoint 2013 admin component" is coming up.
http://www.funwithsharepoint.com/provision-search-for-sharepoint-foundation-2013-using-powershell-with-clean-db-names/
http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Can I get some help please?
Karthick S

Hi Karthick,
For your issue, could you provide the
detail error message of ULS log to determine the exact cause of the error?
For SharePoint 2013, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
For troubleshooting your issue, you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint
Foundation:
[string]$farmAcct = "DOMAIN\service_Account"
[string]$serviceAppName = "Search Service Application"
Function WriteLine
Write-Host -ForegroundColor White "--------------------------------------------------------------"
Function ActivateAndConfigureSearchService
Try
# Based on this script : http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
Start-SPEnterpriseSearchServiceInstance $env:computername
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
$appPool = Get-SPManagedAccount -Identity $farmAcct
New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
$saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
$svcPool = $saAppPool
$adminPool = $saAppPool
$searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
$searchService = $searchServiceInstance.Service
$bindings = @("InvokeMethod", "NonPublic", "Instance")
$types = @([string],
[Type],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool])
$values = @($serviceAppName,
[Microsoft.Office.Server.Search.Administration.SearchServiceApplication],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$svcPool,
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$adminPool)
$methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
$searchServiceApp = $methodInfo.Invoke($searchService, $values)
$searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
$searchServiceApp.Provision()
catch [system.exception]
Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
finally
WriteLine
ActivateAndConfigureSearchService
Reference:
https://sharepointpsscripts.codeplex.com/releases/view/112556
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected].
Eric Tao
TechNet Community Support

Sharepoint Foundation 2013 is not Installing on Window 7

When I click on 'Install Sharepoint Foundation" 2013 nothing happen. Same is issue with "Install Sharepoint Foundation Pr-Requisite"

SharePoint 2013 does not support being installed on Windows client (Windows 7 or 8). Instead, try using a Virtual Machine running a supported Server OS. You can use VMware Player (free) on Windows 7, or if you have Windows 8 Pro or Enterprise, Hyper-V.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Not able to install SharePoint Foundation 2013 SP1 on a Windows Server 2012 R2

I am very new working with SharePoint and Server 2012. I had and am having a lot of problems installing SharePoint Foundation 2013. I get over the typical errors as download all prerequisites from the Internet, installing the Farms, etc.
After I completed all the installations steps, and the installation has finished I tried to open SharePoint 2013 Central Administration but I can't access to it.
Does anyone has a suggestion?

HI Sofia,Did you run the PSCONFIG wizard after the succesful completion of installation.If not,please run.Find the below link that gives more details on the installations.
http://expertsharepoint.blogspot.de/2013/11/detailed-sharepoint2013-installation-i.html
http://expertsharepoint.blogspot.de/2013/10/installation-of-sharepoint-2013-on.html
Anil Avula[Microsoft Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Sharepoint Foundation 2013 - Databases running in compatibility range, upgrade recommended

Similar Messages

Maybe you are looking for