Value of upgrading WSS 3.0 To SharePoint Foundation?

We have a WSS 3.0 site which the primary purpose is for storing documents that are shared with external business partners who have AD accounts in our domain without them needing to have VPN and access to our file servers. It is especially useful for
documents that are over mail size limits or are too sensitive to be sent over email. Few other features of WSS are in use.
They simply open a browser and browse to the URL, and log in using account credentials on our domain which we have assigned to them. From there they can download and upload documents.
Also, we use Office 2010, so we will not be able to use any of the features of SharePoint Foundation 2013 that are not compatible with Office versions below 2013.
Since WSS 3.0 has support until late 2017, is there any real value to upgrading to SharePount Foundation 2010 for this use case other than getting a modernized look and feel?
We could just wait until 2016 and upgrade to whatever version of SharePoint Foundation that comes out after 2013.

I believe in the "if it ain't broke, don't fix it" atttude. If what you have is working for your needs and your users are happy, upgrading may not make sense in your specific case.
My only concern is the upgrade path. As it stands today, to upgrade from WSS 3.0 to SharePoint Foundation 2013 using out of the box methods, you need to first upgrade to SharePoint Foundation 2010 (in-place or database attach) and then again upgrade to SharePoint
2013 (database attach only).
Let's say a new version of SharePoint Foundation comes out sometime between now and before support for WSS 3.0 ends. I would expect the upgrade path to be the same as I just outlined above, along with another step to upgrade from 2013 to vNext.
Whether you upgrade now or upgrade later you'll still need to go through the same process. I suppose what really matters is when you want to upgrade.
As always the third-party community will likely have solutions to migrate directly when vNext launches. :)
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Similar Messages

Third Party Tools To Upgrade WSS 3.0 to SharePoint Foundation 2013?

Since you cannot upgrade WSS 3.0 directly to SharePoint Foundation 2013 using just the SharePoint software, I wanted to look at 3rd party tools that automate the migration directly to 2013 without requiring an intermediate upgrade to 2010.
We have a simple WSS 3.0 farm with 2 SharePoint Servers and 2 SQL servers that are are load balanced so that the site stays up if any one of the servers goes down. It may be just round robin load balancing.
I'd like to see if I can determine if any of these migration tools would save enough time and effort for this type of environment to be worth the cost. It would be nice if we could do the upgrade all in once day instead of having 2 outages.

HI,There are third party tools to upgrade sharepoint but not from wss 3.0 to directly sharepoint 2013.Its not at all possible as I know.Please find the below link that clearly explains the Upgrade process.
http://expertsharepoint.blogspot.de/2014/03/sharepoint-up-gradationmoss2007.html
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/
It looks like there are such products.
This one says it can be used to migrate directly from even WSS 2.0 to SharePoint 2013.
http://www.fpweb.net/sharepoint-2013/migrate-sharepoint-2003-to-sharepoint-2013/
I don't like that it doesn't indicate anything about pricing on the page so you have to call a sales rep and give away all your contact information before you can get a quote. I probably will not call them.
We would "like" to speed up the migration process and have only a single outage, but since the SharePoint environment is small, we will not be spending thousands of dollars just to save having to do two upgrades. We would probably end up just
going to 2010 and canceling the 2013 upgrade if needed.

Upgrading the Features framework in SharePoint foundation 2013

Hi all,
I have a question, how can I upgrade the features of Sharepoint foundation 2013. In Sharepoint Health Analyzer, there is an error "missing server side dependencies" and description of this error it has been said that I need to upgrade the feature
to latest version.
Can you please tell me how can I upgrade the feature so that above error does not appear in Health Analyzer.
Thanks for help.

Try below:
http://itfreesupport.com/2014/09/missing-server-side-dependencies-on-sharepoint-2010-and-sharepoint-2013/
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

No Page title after migration from WSS 3.0 to SharePoint Foundation 2013

Dear community,
I have migrated serval sitecollections from WSS 3.0 (SharePoint 2007) to SharePoint 2010 Foundation and then to SharePoint Foundation 2013.
Now in SharePoint 2013 no page titles appears, but under the title "Homepage" appears. I'dont know where "Homepage" is come from. The title of the page is "Test". Changing the title has no effect. In SharePoint 2010 Foundation
the page titles appears correctly.
Does anyone have a solution for this problem?
Thank you very much and best regards,
Lucian

I compared the html code of the two sites.
Migrated site:
<h1 id="pageTitle" class="ms-core-pageTitle">
<span id="DeltaPlaceHolderPageTitleInTitleArea">
<label class="ms-hidden">Test Title</label>
</span>
<div id="DeltaPlaceHolderPageDescription" class="ms-displayInlineBlock ms-normalWrap">
<a href="javascript:;" id="ms-pageDescriptionDiv" style="display:none;">
<span id="ms-pageDescriptionImage"> </span>
</a>
<span class="ms-accessible" id="ms-pageDescription">
</span>
<script type="text/javascript">// <![CDATA[
_spBodyOnLoadFunctionNames.push("setupPageDescriptionCallout");
// ]]>
</script>
</div>
</h1>
Standard site:
<h1 id="pageTitle" class="ms-core-pageTitle">
<span id="DeltaPlaceHolderPageTitleInTitleArea">
Test Title
</span>
<div id="DeltaPlaceHolderPageDescription" class="ms-displayInlineBlock ms-normalWrap">
<a href="javascript:;" id="ms-pageDescriptionDiv" style="display:none;">
<span id="ms-pageDescriptionImage"> </span>
</a>
<span class="ms-accessible" id="ms-pageDescription">
</span>
<script type="text/javascript">// <![CDATA[
_spBodyOnLoadFunctionNames.push("setupPageDescriptionCallout");
// ]]>
</script>
</div>
</h1>
There is a .NET Code in the HTML Code of the migrated site:
<label class="ms-hidden">Test Title</label>

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 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

Upgrade WSS content DB WSS 3.0 using database attached method‏

i m trying to upgrade WSS content DB WSS 3.0 using database attached method. when i use stsadm command to addcontentdb getting following error. i have also run db repair command but still getting error.
[SPUtility] [DEBUG] [3/23/2015 11:41:39 PM]: File C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\sql\storeup.sql, Time out = 24595 sec
[SPManager] [ERROR] [3/23/2015 11:54:36 PM]: Upgrade [SPContentDatabase Name=WSS_Content_DB Parent=SPDatabaseServiceInstance] failed.
[SPManager] [ERROR] [3/23/2015 11:54:36 PM]: The transaction log for database 'WSS_Content_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The transaction log for database 'WSS_Content_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The statement has been terminated.
pls guide how to fix.
iffi

sounds like the database ran out of log space. did you fill the drive? does the database's log file have a hard limit?
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

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

After upgrade SP-Crawl Error: The SharePoint item being crawled returned an error when attempting to download the item.

Hi All - After the upgrade, I am getting SP-Crawl Error for certain links. I check the Crawl component has proper permission.
Google is showing some article like
http://blog.karstein-consulting.com/2012/04/20/error-in-crawl-log-the-sharepoint-item-being-crawled-returned-an-error-when-attempting-to-download-the-item/
not sure if this resolution is referring to 2010 and/or 2013.
I checked the registery editor. I couldn't find 14.0 under the Office Server.
Any clue?
Regards,
Khushi
Khushi

I checked the web application policy the search crawl account has full read permission.
Crawl
Fiddler
Log Error referring the Correlation ID
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Monitoring                    nasq Medium Entering monitored scope (Request (GET:/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Parent No
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Logging Correlation Data      xmnv Medium Name=Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD) e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af71 Medium HTTP Request method: GET e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af75 Medium Overridden HTTP request method: GET e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af74 Medium HTTP request URL: /sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
Files                         aise3 Medium Failure when fetching document. 0x80070090 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    b4ly Medium Leaving Monitored Scope (Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Execution Time=20.5461867360237 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    b4ly Medium Leaving Monitored Scope (Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Execution Time=29.917489513332 e8b1679c-0476-70d4-9fcd-2549ba3ee9d4
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    nasq Medium Entering monitored scope (Request (GET:<SiteURL>nsurance%20Benefits%2fLife%20Insurance%2fBasic%20Life%20and%20ADD&FolderCTID=0x01200039DA632EEACF264685CF39D68A18F7C8)).
Parent No
Any clue?
Regards,
Khushi
Khushi

Using ADFS with SharePoint Foundation 2013?

We have a WSS 3.0 web site used primarily for sharing documents with business partners who do not work for our company. We plan on doing the 2 step upgrade to SharePoint Foundation 2013
Our internal users also use it but normally just use internal network file shares if they aren't planning to share the documents with external users.
Each business partner's company has a sub site within our main WSS site and documents are uploaded to that section of the site if we want to share documents with employees of that company.
Since we use AD for authentication, to make this work, we create AD user accounts for each external user and add them to a security group that gives them access to only their company's subsite on the main site.
We have to maintain their passwords, reset them and delete/disable them when that person no longer needs access. Each business partner has a limit on the number of users who can get one of our AD accounts due to limits on the number of CALs available
to them. It is messy because these users often forget their passwords since they aren't using these accounts every day.
Is there a better way to do this so that we no longer have create and maintain user accounts for external users other than having to do a domain trust with all these other domains?
I have heard of ADFS, but will it allow us to still control which sites and documents the external company users can access if we are not creating and managing the accounts and adding them to the correct security groups ourselves?
We don't want every user from the partner's domains to be able to access the site. If we use ADFS, how do we keep control of which external users have access to the site?

Yes, you would add permissions just the same way you do with users from your local Active Directory. And yes, if you chose the email address to be the user's identifier, you would simply ask for the email addresses that you wanted and input those to the
appropriate permissions on your SharePoint sites.
You'll want to take a look at this:
http://blogs.msdn.com/b/russmax/archive/2013/10/31/guide-to-sharepoint-2013-host-name-site-collections.aspx
Also another thing to keep in mind is that you'll need to have those 3rd parties set up ADFS themselves, and you'll create an ADFS Trust between you and the 3rd party.
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.

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

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 People field wont save data

Guys, having an issue with a list column. We have some columns that are Person or Group. when we enter in a user, it finds it just fine saves it just fine. but if i come back into that list and edit some other field the Person or Group field is totaly
cleared out. I don't know what is going on. we are using SharePoint foundation 2013.

If you're using SharePoint 2013 April 2013 CU or higher, this is a known issue where the People data is missing in Edit view. There is a separate issue that is resolved in the September 2014 CU:
http://support.microsoft.com/kb/2995905
Consider the following scenario:
You create a SharePoint 2013 list that contains a Person or Group (people picker) column.
You create or edit an item, and then you select a person whose name contains a comma in the Person or Group field.
In this scenario, the value of the Person or Group field is lost when you save the item.
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.

Value of upgrading WSS 3.0 To SharePoint Foundation?

Similar Messages

Maybe you are looking for