none
Upgrading to SharePoint 2010 Foundation on SBS Server 2008

    Question

  • Hi all,

    I've just tried to install SharePoint Foundation on 2010 on Windows Small Business Server 2008 and whilst the literature I've found suggests that this is supported, I receive the following error:

    SharePoint 2010 Products cannot be installed in Stand-alone mode on a Domain Controller.  For more information on upgrading, see http://support.microsoft.com/?kbid=975805.

    What's funny about the KB ID, is that it doesn't exist. 

    The pre-requisites for SharePoint 2010 Foundation installed OK and the SharePoint installer has detected that it will perform an in-place upgrade.  the STSADM -o preupgradecheck output is below.

    Any idea's?  It would be really great if we could start using the shared workspace and ribbon features that are inherent with SPF2010.

    Jason.

     

    Tuesday, May 11, 2010 7:06 AM

All replies

  • Sorry forgot to attach the output

     

    Processing configuration file: WssPreUpgradeCheck.xml

            ServerInfo... Information Only

            FarmInfo... Information Only

            UpgradeTypes... Information Only

            SiteDefinitionInfo... Information Only

            LanguagePackInfo... Information Only

            FeatureInfo... Information Only

            AamUrls... Information Only

            LargeList... Passed

            CustomListViewInfo... Passed

            CustomFieldTypeInfo... Passed

            CustomWorkflowActionsFileInfo... Passed

            ModifiedWebConfigWorkflowAuthorizedTypesInfo... Passed

            ModifiedWorkflowActionsFileInfo... Passed

            DisabledWorkFlowsInfo... Passed

            OSPrerequisite... Passed

            WindowsInternalDatabaseMigration... Passed

            WindowsInternalDatabaseSite... Passed

            MissingWebConfig... Passed

            ReadOnlyDatabase... Passed

            InvalidDatabaseSchema... Passed

            ContentOrphan... Passed

            SiteOrphan... Passed

            PendingUpgrade... Passed

            InvalidServiceAccount... Passed

            InvalidHostName... Passed

            SPSearchInfo... Information Only


    Tuesday, May 11, 2010 7:08 AM
  • Same problem here. Does anybody know a way to fix it?
    Thursday, May 13, 2010 8:36 AM
  • Hi Jason!

    Actually I can not present you a solution for that problem but here are some points that could come to consideration.

    A SharePoint 2010 installation / migration on a W2K8 R2 server (Enterprise; + AD) does prohibit that (at least not for my server). I've a customer who is running a Small Business Server 2008 installation and this server has numerous limitations compared to other W2K8 server. To break this down it's a set of policies and rules which controls the behaviour and tells you what it allows and what not regarding to an action. When you do an installation on a W7 Development machine you have to tune the config.xml installation file (-> http://msdn.microsoft.com/de-de/library/ee554869(v=office.14).aspx). Maybe that can be an option but please don't try this on a production server (when it's a production server, clone it and try this on a virtual machine).
    The second point is the in-place upgrade. In the moment I'm preparing a migration from a middle-sized SharePoint 2007 Farm. I was running a first test on two virtual testserver and in the beginning everthing ran well - did not show any errors. After a reboot the new monitoring feature (+ event log) show me a quite number of errors which are not to solved. To understand this failures I've tried to do this on a new Out-of-the-Box MOSS2007 (W2K8; Stand-alone;) installation. I ran the in-place upgrade and everthing works fine. OK or better not - the discussed MOSS2007 installation has any errors (event log, SP Log). I'm looking now for an alternative (a partial upgrade of the databases).

    I hope that helps a bit
    guy        

     

    Thursday, May 13, 2010 9:57 AM
  • I ran into this problem today. The real rub for me is I'm upgrading from the SPF2010 beta which did install and run fine on SBS2008.

     

    I'm going to pray that at some point there is an SBS installer similar to the Exchange 2007 SP2 wrapper.

    Thursday, May 13, 2010 9:53 PM
  • I've seen nothing to indicate it's officially supported on SBS 2008.
    Friday, May 14, 2010 5:37 AM
  • I've seen nothing to indicate it's officially supported on SBS 2008.

    Me either, take it from a SBS Specialist, WAIT! till the official upgrade from the SBS team, you will break many features of SBS by messing with the intergrated Sharepoint functions.
    Friday, May 14, 2010 4:30 PM
  • Jason, I am running SBS 2008 on a Dell Poweredge T610 as virtualized system. The installation is rather fresh and I did not get into using the orginal SharePoint Services 3.0 installation. What I had to do on my system was remove the orignal SharePoint installation and reinstall it but NOT run the SharePoint Technologies Configuration wizard. Then I installed SharePoint Foundation and ran the Configuration Wizard for it.

    The down side to this is if you have SharePoint configured with data you will probably lose it unless you restore the data through SQL.

    I also configured my system to run in a server farm by setting up a dedicated SQL Server with SQL 2008 R2 and a application server as the main server in the SharePoint Foundation farm. These servers were setup first before installing and adding my SBS 2008 server to the farm.

    With my setup I am able to access my SharePoint Foundation site through the Remote Web workplace. To prevent the error message about services not running in the SBS Console, I removed the SharePoint Services 3.0 installation from the SBS.

    Daryl Gilbert


    Daryl Gilbert II
    Monday, May 17, 2010 1:05 AM
  • Yes it is on the list, and yes you can set it up,(It meets the min reguirements technically) But, and this is a big BUT! you will break many of the features that is SBS. RWW being one of the major features keep an eye on the Offical SBS Team Clog ( http://blogs.technet.com/sbs/ ) for a SBS Specific upgrade, we went through this with SBS 2003 when WSS 3 came out and broke many of desired features.
    Monday, May 17, 2010 3:22 AM
  • Computer Information Agency:
    http://supportweb.ciaops.net.au/blog/archive/2010/04/26/sharepoint-foundation-2010-on-sbs-2008.aspx

    And the installer says it can't be installed on a domain controller.

    Until somethng definitive comes from the SBS blog, I'm not going with what the SharePoint blog says.

    Monday, May 17, 2010 5:19 AM
  • Hi all, thanks for your responses.  Now I have to figure out why after two weeks, I didn't get notified of anyone's responses to this thread via email :).

    Anyhoo thanks again for the feedback.  Given that our SBS environment is production, I guess I'm a little too weary to proceed based on the responses from this thread, for now. 

    One of our main reasons for foundation 2010 was the sharepoint workspace feature and the benefits this will have for our customers that use sharepoint technologies, as well as increasing uptake for those smaller businesses that don't understand the benefits sharepoint can bring to the table.

    ...And because we have data in there running live, I guess I'd rather not tinker with it for now.  We will just have to sit and wait.

    One of the most annoying situations here is the fact that all the pre-requisites have now been installed and are consuming resources on our server that are essentially wasted for now.  Not only that but the conflicting information on the web suggests that you can do it but in actual fact, you can't.

     

    I guess time will tell... hopefully it will be a short time :)

     

    Thanks again for everyone's responses.

     

    Jason

     

    Monday, May 24, 2010 1:15 AM
  • Just be patient a bit longer.  There will be a whitepaper on this.
    Monday, May 24, 2010 5:00 AM
  • That is great news Susan -- I hope to see this soon as I really want to leverage some of the Office 2010 / SPF features at a new office.

     

    E: And hopefully I'll actually get the alerts now on this thread like I politely asked for.

    Thursday, June 24, 2010 4:17 PM
  • The main difference between WSS and SPF is that WSS is branded in "Windows", and it leverages Windows Internal Database(WID). However, due to some of the legal and planning reason SPF has to be run on a seperate SQL instance instead of WID. So with standalone mode it will try to install SQL Server 2008 Express on to your machine. Currently SQL Server 2008 Express is not supported on a DC, and this behavior triggered the issue that SharePoint Foundation cannot be installed on a DC in standalone mode. I'm not a SBS expert, not sure if you can install a seperate SQL Server or not - but then you maybe able to use complete farm install on the server to get around.
    Thursday, June 24, 2010 6:17 PM
  • Just be patient a bit longer.  There will be a whitepaper on this.


    Hi folks,

    any update on this?

    Wednesday, July 07, 2010 1:09 PM
  • Just be patient a bit longer.  There will be a whitepaper on this.


    Hi folks,

    any update on this?


    Seems like we are patient, is there an ETA on the white paper?

    Would save a lot of people some headaches.
    Cheers

    Monday, July 26, 2010 10:22 AM
  • It's in beta testing, I don't know the ETA.  I'll post back here when it's released.
    Monday, July 26, 2010 5:07 PM
  • Hi folks.

    I have the same issue/error reported but I'm running Windows Server 2008 R2 Enterprise not Small Business Server 2008.  I'm also awaiting the white paper / fix for this since I'm excited to utilize VS 2010 with the new templates and SharePoint Foundation 2010.

    Rich

    Tuesday, July 27, 2010 11:10 AM
  • Hello All
    I just get an HP ML 350 G6 with SBS 2008 installation, but my server with an update of the components of the tools of SharePoint 2010 when I start the installation I get the following error message: Unable to continue the installation because of errors acc: Windows SharePoint Service 3.0 Service Pack 2 or later is required for the upgrade. But even though I uninstall the 2007 version installed on my server.
    Please can someone given a helping hand?

     

    Monday, August 09, 2010 2:02 PM
  • Hello All
    I just get an HP ML 350 G6 with SBS 2008 installation, but my server with an update of the components of the tools of SharePoint 2010 when I start the installation I get the following error message: Unable to continue the installation because of errors acc: Windows SharePoint Service 3.0 Service Pack 2 or later is required for the upgrade. But even though I uninstall the 2007 version installed on my server.
    Please can someone given a helping hand?
    Monday, August 09, 2010 2:03 PM
  • Please, be patient a little longer.  I can't help you until the white paper is released as that will give you the official supported path to upgrade.
    Tuesday, August 10, 2010 5:25 AM
  • Ok susan
    Tuesday, August 10, 2010 11:53 AM
  • Ok susan
    After restarting my server was installed successfully pass, but my concern is every time I run the central administration is asking me to configure my SQL server, and yet my SQL Server 2005 that is installed is accessible I try to configure the 2008 version which is pre-installed on my SBS 2008, but he asked me to find the file required and I do not find the file, can you help me?
    Tuesday, August 10, 2010 12:16 PM
  • Hi Susun and other MVP's,

    Still no news about upgrading SharePoint Services 3.0 to SharePoint Foundation 2010 on Small Business Server 2008?

     

     

    Pieter

    Tuesday, August 17, 2010 7:26 AM
  • I know but it's not released yet :-( I'm sorry and will post as soon as it is.
    Tuesday, August 17, 2010 4:17 PM
  • Ok. Thanks.

    I'm feeling this is going to be something for SBS2010 :-)

    Wednesday, August 18, 2010 7:40 AM
  • Nope it won't be. Keep the faith. Just got it confirmed again today that it's almost done.
    Wednesday, August 18, 2010 7:42 AM
  • Hi, Do you have an ETA yet on the whitepaper? Thomas
    Wednesday, August 18, 2010 2:51 PM
  • I haven't been authorized to release that info, but I will be posting back here to this thread as soon as it is released.
    Wednesday, August 18, 2010 5:15 PM
  • I haven't been authorized to release that info, but I will be posting back here to this thread as soon as it is released.


    Hi Susan,

    Thanks for the updates on this but I think Microsoft owe it to us to at least give us an ETA on the resolution.  We are trying to run businesses here and wanting to use SharePoint 2010 to do our job... Microsoft give all this hype about a product then make a ____-up like this and cannot giv a resolution ETA...

    Is there any more information we can have to al least allow us to plan when we will be able to use SharePoint 2010 on a stand-alone machine with a domain controller installed on it? - Can you not even indicate if it is very close or a way off?

    Being secrative about resolutions will only put people off the product... especually when all people want is a resolution.

    I hope we can get some more news on this soon?????

    Thursday, August 19, 2010 3:10 PM
  • By the end of the month is what I've been told, but I'm not Microsoft, stuff happens and things can slip. Ergo why I say "soon". Keep in mind that fax integration does not work post install so be prepared to review if it will fit your needs.
    Thursday, August 19, 2010 4:03 PM
  • Any news on this item?

    I heard Susan saying something about the end of August.. :)

    Christian

     

    Thursday, September 02, 2010 2:35 PM
  • I also said ... this is Microsoft and you know how they slip.

    Lemme to run a question up the flagpole again.

    Thursday, September 02, 2010 7:13 PM
  • Step-by-Step Guide to Migrating from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 on a server running Windows Small Business Server 2008:
    http://technet.microsoft.com/en-us/library/ff959273(WS.10).aspx

    Download details: Guide to Migrating from WSS 3.0 to SharePoint Foundation 2010 on Windows SBS 2008:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=2dc66a0f-f840-4b29-93d3-13db70c85cba&displayLang=en&utm_source=feedburner&utm_medium=twitter&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29#tm

     

    Feedback from Robert Crane --

    I see a few issues. The main is at step 10 which is supposed to be - Connect the ShareWebDb database to SQL Server 2008 but is in fact a duplication of step 12. Basically it is missing the step of attaching the content DB to SQL 2008 Express.

    Just what I see.

    Thanks

    Robert

    Computer Information Agency:
    http://supportweb.ciaops.net.au/blog/archive/2010/09/03/sharepoint-2010-migration-on-sbs-2008-released-from-microsoft.aspx

    Friday, September 03, 2010 3:35 AM
  • I have posted what I believe to be the correct steps for Step 10 here:

    http://supportweb.ciaops.net.au/blog/archive/2010/09/08/sharepoint-foundation-2010-on-sbs-2008-%E2%80%93-step-10.aspx

    that should at least allow the process to complete. There are a few other issues that I mention in my original blog post that I'll update soon but the above link should allow you to complete the process until Microsoft has a chance to edit the original document.

    Thanks

    Robert Crane

     

    Wednesday, September 08, 2010 1:21 PM
  • From what i can see at the requirements for SharePoint Foundation 2010 (http://technet.microsoft.com/en-us/library/cc288751.aspx), i understand that SQL 2005 is only supported when used in a farm. Is that correct? So when SBS 2008 is installed with SQL Server 2005 and SQL 2005 is not used in a farm, an upgrade to SQL 2008 is needed first? Or is SQL Server 2005 also supported?

    Roland

    Monday, September 13, 2010 7:58 AM
  • Basically on a single server you need 64 bit SQL 2008 or better. The version of SQL 2005 on SBS 2008 is not supported by SharePoint Foundation 2010 to my knowledge.


    To be supported on SBS 2008 my understanding is that yes SharePoint Foundation must use 64 bit SQL Server 2008 or better since it is a single server instance. You don't have to upgrade the SQL 2005 instance, SQL 2008 will happily site side by side SQL 2005 (apart from the SQL Management tools which have to be SQL 2008).

    The advice is to use SQL 2008 or better to remain supported.

    Thanks

    Robert

    Monday, September 13, 2010 8:13 AM
  • Hello Robert,

    Thank you for the quick and clear answer. Then maybe i'm going to use SQL 2008 Express side by side with SQL 2005.

    Thanks again,
    Roland

    Monday, September 13, 2010 8:51 AM
  • This works like a charm. But when i install Web Apps 2010 after the installation (they work), the server is getting VERY (!) slow. And when I check the active processes there are several host services running out the system memory. Is it possible there is compatibility issue between Web Apps 2010 and Small Business Server 2008? When i install the Web Apps 2010 on Windows Server 2008 R2 i dont experience any speed problems.

    Or am I doing something wrong?

     

    Grts.

    Monday, September 13, 2010 9:44 AM
  • Hello,

    SharePoint Services 3.0 SP2 is installed on my SBS 2008 but it has never been used. I would like to install v2010 Foundation and look into giving this a try. I can't manage to uninstall SharePoint Services 3.0 as described in the above notes: "Microsoft Windows SharePoint Services 3.0 Setup has stopped working". There isn't much to go on in the Event Viewer at all. I tried to reinstall the WSS Installation (in line with the SBS 2008 repair guide), but this doesn't get me anywhere either.

    I was wondering if I could continue with the v2010 installation (without first removing wss 3.0) - as there isn't anything within the existing WSS that I wish to keep.

    Many thanks,
    Stephen

    Monday, September 13, 2010 10:00 AM
  • If you attempt to install SharePoint Foundation 2010 with WSS v3.0 still installed you wil most likely be taken into upgrade mode which won't work on SBS 2008. You need to totally remove WSS v3.0 from SBS 2008 before you attempt a SharePoint Foundatin 2010 installation I have found.

    The supported process totally removes WSS v3.0 so if there is nothing in that you have used then migrating shouldn't be an issue. However, always ensure you backup the existing content databases and store them somewhere secure jut in case you need to roll back.

    I would however also recommend that you totally remove WSS v3.0 before you commence if at all possible because if you get issues it becomes harder to troubleshoot given you don't have a 'standard' environmen t you are moving from.

     

    Thanks

    Robert

    • Proposed as answer by Studio Two Monday, September 13, 2010 12:31 PM
    Monday, September 13, 2010 11:21 AM
  • I've installed SharePoint Foundation 2010 according the official Step-by-Step-Guide. After having some trouble during the Installation with the UAC switched on on the SBS 2008 now it seems to work. But there are two points witch are not working. I can't see the status of the internal web side in the Windows SBS Console and I even can't access the settings from there.

    The other problem is the access via the companyweb link. DNS is working and I added an Alternate Access Mapping for http://companyweb as Intranet. The binding on the IIS Adminstration for this side have been changed too. When I want to access the companyweb page I only have the chance to give my login credentials three times and afterwards I only see a white page. If I clear the bindings on the IIS Administration for this page and leave them blank I do have the chance to log in the Sharepoint Foundation 2010 via the url of the server. But this only works on the server itself. If I try to connect from a client pc, the only chance to have a succsessful login is by using the IP of the server.

    What might be the problem with the installation. I'm seeking for about 2 days but without any luck.

     

    Thanks

    Volker

    Wednesday, September 15, 2010 1:56 PM
  • I can't see the status of the internal web side in the Windows SBS Console and I even can't access the settings from there.

    That is expected, just use the native SharePoint tool.

     

    When I want to access the companyweb page I only have the chance to give my login credentials three times and afterwards I only see a white page.

    Ensure you installed SBS update rollup 4 as per the instructions.

    Also post over in www.sbsforum.info for SBS specific info.

    Wednesday, September 15, 2010 4:40 PM
  • Provided you follow the document EXACTLY (including using upper and lower case when creating the SharePoint site) you should see the status of Companyweb in your console. This however is as far as it goes with integration. You are unable to manage the site or use the wizards and there is also no longer any integration with fax or email archiving.

    SharePoint Foundation 2010 is still subject to the common lookback connector issue that was evident with WSS v3. HAve a look at this blog post:

     

    http://blogs.technet.com/b/sbs/archive/2009/05/07/event-2436-for-sharepoint-services-3-search.aspx

    for guidance.

    My guess is that (as Susan notes) rollup package 4 resolves this but I don't know that for sure.

    Thanks

    Robert Crane

    Wednesday, September 15, 2010 11:45 PM
  • Roland,

    I'd suggest you go with SQL 2008 R2 because it has a DB limit of 10GB instead of 4GB which is teh case with SQL Express 2008 (no R2). You can however do an inplace upgrade I believe from SQL Express 2008 to SQL Express 2008 R2 without too much hassle I believe.

    Thanks

    Robert Crane

    Thursday, September 16, 2010 1:09 AM
  • Pieter,

    My guess is that the SQL version you have installed to support Sharepoint 2010 has not had its memory trimmed. Go in to the SQL management management console and select the instance of SQL. Right mouse click at the top of the tree and select properties. Then adjust the memory to something more reasonable than the huge number that is there by default. This will limit the amount of RAM that SQL will consume. If you don't do that it takes as much as it can grab (i.e. everything spare).

    If that doesn't help need to know:

    - RAM in server

    - SQL Server in use with SharePoint 2010

    - free disk space

    - AV in use

    - SharePoint content database size

    Thanks

    Robert Crane

    Thursday, September 16, 2010 1:14 AM
  • Hey Roland -- I followed this advice and went with SQL Server 2008 Express R2 in order to get the larger DB limit -- however, this was not without its problems.   Being that I'm an Access 2007 guy, I may have bitten off more than I could handle!  

    I went with the SQL Server 2008 R2 Express with Tools (64-bit) version and ran into problems from the get-go as this was just way over my head . . . 

    I finally got it resolved through several postings at Experts Exchange:

    http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL_Server_2008/Q_26484547.html

     . . . but I would caution users that installing SBS Server 2008 Express R2 is no easy task -- it would be very nice if some very knowledgeable SQL Server DB tech would post a DETAILED step-by-step on how to do this properly under SBS-2008 in conjunction with this article on installing SharePoint Foundation Server (step 6). 

    Although I've got SharePoint Foundation 2010 running under SBS-2008 now, it was not easy! 

     

     

    Tuesday, October 05, 2010 3:33 AM
  • I followed the whitepaper with the only exception being I used SQL Express 2008 R2 (for the larger database limit) and my search doesn't work, and neither does sharepoint designer 2010.  When it tries to crawl the site, I get an error from the gatherer with event id 14.  Sharepoint designer, when I try to connect to https://remote.servername.com:987 connects, asks for my credentials and then says that the server cannot complete the request, and if I click details it's blank.  pressing ok nets me the following error: "An error occurred while trying to fetch data from your SharePoint site.  Unexpected response from the server.  The content type of the response is "".  The Status Code is "OK""

     

    This is really quite frustrating, as I haven't managed to find a solution for either of these problems anywhere.  without the search feature working, it's really quite useless.

    Thursday, October 14, 2010 2:23 PM
  • Brian, 

    if you have time - please write down the steps you did to install / upgrade the SQL Server (whole step 6). Maybe I can follow you until an expert updates the guide.

    Thank you!

    Wednesday, October 20, 2010 6:49 PM
  • If the issue is merely the installation of a SQL Express instance on the SBS DC, why not allow the Express to install, then create a full instance elsewhere with the Standard install that comes with SBS, migrate the databases, tweak the pointers to the database, and then remove the SQL Express? I make this sound easier than it is, but in principle, it should be no different than migrating any other database at the SQL level. The difficulty, I'm guessing, is at the IIS level where TFS 2010 keeps its pointers. But truly, how much difference can there be between an RWW installation and one that displays TFS?
    Sunday, October 24, 2010 3:02 PM