May 2010 - Posts

SharePoint 2010 – SQL Server has an unsupported version 10.0.2531.0

I am trying to perform a database attach upgrade to SharePoint Foundation 2010.

At this point I am trying to attach the content database to a Web application by using Windows Powershell:

Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]

I am following the directions from this TechNet article: Attach databases and upgrade to SharePoint Foundation 2010.  When I go to mount the content database I am receiving this error:

Mount-SPContentDatabase : Could not connect to [DATABASE_SERVER] using integrated security: SQL server at [DATABASE_SERVER] has an unsupported version 10.0.2531.0. Please refer to “http://go.microsoft.com/fwlink/?LinkId=165761” for information on the minimum required SQL Server versions and how to download them.

At first this did not make sense because the default SharePoint Foundation 2010 website was running just fine.  But then I realized that the default SharePoint Foundation site runs off of SQL Server Express and that I had just installed SQL Server Web Edition (since the database is greater than 4GB) and restored the database to this version of SQL Server.

Checking the documentation link above I see that SharePoint Server 2010 requires a 64-bit edition of SQL Server with the minimum required SQL Server versions as follows:

  • SQL Server 2008 Express Edition Service Pack 1, version number 10.0.2531
  • SQL Server 2005 Service Pack 3 cumulative update package 3, version number 9.00.4220.00
  • SQL Server 2008 Service Pack 1 cumulative update package 2, version number 10.00.2714.00

    The version of SQL Server 2008 Web Edition with Service Pack 1 (the version I installed on this machine) is 10.0.2531.0.

    SELECT @@VERSION:
    Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Web Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)

    But I had to read the article several times since the minimum version number for SQL Server Express is 10.0.2531.0.  At first I thought I was good with the version of SQL Server 2008 Web that I had installed, also 10.0.2531.0.  But then I read further to see that there is a cumulative update (hotfix) for SQL Server 2008 SP1 (NOT the Express edition) that is required for SharePoint 2010 and will bump the version number to 10.0.2714.00.

    So the solution was to install the Cumulative update package 2 for SQL Server 2008 Service Pack 1 on my SQL Server 2008 Web Edition to allow SharePoint 2010 to work with SQL Server 2008 (other than the SQL Server 2008 Express version).

    SELECT @@VERSION (After installing Cumulative update package 2):
    Microsoft SQL Server 2008 (SP1) - 10.0.2714.0 (X64)   May 14 2009 16:08:52   Copyright (c) 1988-2008 Microsoft Corporation  Web Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)

  • SQL Server 2008 Service Pack 1 and the Invoke or BeginInvoke cannot be called error message

    When trying to install SQL Server 2008 Service Pack 1 to a SQL Server 2008 instance that is running on a virtual machine, the installer will start:

    image 

    But then after about 20 seconds I receive the following error message:

    image

    TITLE: SQL Server Setup failure.
    -----------------------------
    SQL Server Setup has encountered the following error:
    Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
    ------------------------------
    BUTTONS:
    OK
    ------------------------------

    Searching for this issue I found that several people have the same problem and there is no clear solution.  Some had success with closing windows or Internet Explorer but that didn’t work for me; what did work is to make sure the SQL Server 2008 “Please wait while SQL Server 2008 Setup processes the current operation.” dialog is selected and has the focus when it first shows up.  Selected (with the current focus) it looks like this:

    image 

    Without focus the dialog looks like this:

    image

    Add a comment if you find out any information about how to consistently get around this issue or why it is happening in the first place.

    Visual Studio confused when there are multiple system.web sections in your web.config

    I am trying to start debugging in Visual Studio for the website I am currently working on but Visual Studio is telling me that I have to enable debugging in the web.config to continue:

    image

    But I clearly have debugging enabled:

    image

    At first I chose the option to Modify the Web.config file to enable debugging but then I started receiving the following exception on my site:

    HTTP Error 500.19 - Internal Server Error

    The requested page cannot be accessed because the related configuration data for the page is invalid.

    Config section 'system.web/compilation' already defined. Sections must only appear once per config file. See the help topic <location> for exceptions

     

    So what is going on here?  I already have debug=”true”, Visual Studio tells me I do not, and then when I give Visual Studio permission to fix the problem, I get a configuration error.

    Eventually I tracked it down to having two <system.web> sections.

    I had defined customErrors higher in the web.config:

    image

    And then had a second system.web section with compilation debug=”true” further down in the web.config.  This is valid in the web.config and my site was not complaining but I guess Visual Studio does not know how to handle it and sees the first system.web, does not see the debug=”true” and thinks your site is not set up for debugging.

    To fix this so that Visual Studio was not going to complain, I removed the duplicate system.web declaration and moved the customErrors statement down.

    Configuring SharePoint Foundation 2010 for SharePoint Workspace 2010

    SharePoint Workspace 2010 is the new version of Groove that will give you an offline copy of a SharePoint website and also allow you to work with a SharePoint site outside of a browser.  SharePoint Workspace 2010 is especially nice for editing documents in a SharePoint Document library.  SharePoint Workspace makes the SharePoint Document Library work just like a folder on your computer and will handle the synchronization of the documents back to the SharePoint server for you.

    If you try connecting SharePoint Workspace 2010 to a default SharePoint Foundation 2010 installation you may get an error like this one:

    ---------------------------
    Sync to SharePoint Workspace
    ---------------------------
    SharePoint Workspace was unable to interpret the SharePoint location. Please check and ensure the location contains no typing errors.
    ---------------------------
    OK Help
    ---------------------------

    This is because the default configuration of SharePoint Foundation 2010 requires two configuration changes to allow SharePoint Workspace 2010 to work.

    The first is to enable the Remote Differential Compression feature on the server that is hosting SharePoint.  This is used by SharePoint Workspace 2010 to send and receive the files for synchronization.

    To enable Remote Differential Compression go to the Server Manager > Features and choose Add Features.

    image

    Check the box for the Remote Differential Compression feature and then click Install to enable this feature.

    image

     

    The second configuration change to allow SharePoint Workspace 2010 to work with your SharePoint Foundation 2010 server is to add an Alternate Access Mapping of the public facing DNS name (or IP address) to SharePoint using the SharePoint Central Admin.  If you are connecting to your SharePoint site using the machine name then this is not necessary, but if you are connecting over the Internet through either an IP address or DNS name then you will need to add this alternate access mapping.

    The reason is that when SharePoint is first installed, the only way it thinks users are connecting to the server is through the machine name: http://machine_name (as if on a local intranet).  Since most likely SharePoint Workspace 2010 users will be connecting through a public facing DNS name (or IP address), you will need to add this DNS name (or IP address) as an alternate access mapping (indicating that this DNS name is the same as the machine_name and should map to the SharePoint site).

    To add an Alternate Access Mapping to SharePoint Foundation 2010, visit the SharePoint Central Administration on the SharePoint Foundation 2010 server:

    image

    Once in the SharePoint Central Administration website, click on the Application Management link

    image

    Then under the Web Applications heading choose Configure alternate access mappings

    image

    Choose Edit Public URLs

    image

    And then select the public facing SharePoint website that you want to add an access mapping to.  You do this by changing the Alternate Access Mapping Collection (clicking on the “No selection” drop down button) to the website that is running on Port 80.

    image

    The  default name of the public facing SharePoint site is “SharePoint – 80” but you may have changed that when you configured your SharePoint site.

    image

    Once you have switched the Alternate Access Mapping Collection to the public SharePoint website (SharePoint – 80) then you can specify the Public URL by adding the publically accessible IP Address or DNS name to the Internet field:

    image

    image

    Click Save to apply the alternate access mapping and now you should be able to connect to your SharePoint Foundation 2010 site with SharePoint Workspace 2010:

    image

    clip_image001

     

    SharePoint Foundation 2010 is the free version of SharePoint that installs on top of Windows Server 2008.  With SharePoint Workspace 2010 you can get an offline copy of your SharePoint team site allowing you to add/edit your documents in any SharePoint document library easily and allow SharePoint Workspace 2010 to handle the file synchronization for you. 

    You can take a look at SharePoint Foundation 2010 quickly and easily by starting a preconfigured SharePoint Foundation 2010 Virtual Machine at Vaasnet.com.  Vaasnet.com is a new Internet startup that provides preconfigured virtual machines (such as a virtual machine with SharePoint Foundation 2010 already installed) that are ready for you to start and begin using right away.  Vaasnet.com takes the hassle out of downloading and installing the Windows Server 2008 operating system and SharePoint Foundation 2010 so that you can quickly log in and begin trying out the new features of SharePoint Foundation 2010.

    How to view Outlook 2010 Internet headers for an email

    In Outlook 2010 getting to the Internet headers for an email has been moved to the File Menu for a particular email message. 

    In Outlook 2007 (and previous versions) you used to be able to view the internet headers of an email message by right-clicking on any email message and choosing the “Options” menu option from the context menu that appeared.  In Outlook 2010 this has moved to the File menu.

    To get to the Internet Headers of an email in Outlook 2010:

    Open the email message in its own window (by double clicking on the message).

    Then go to File > Info for that message:

    image

    And then in the right-hand pane click on the Properties button

    image

    This will bring up the Properties dialog with the Internet headers located at the bottom:

    image

    More Posts

    Search

    Go

    This Blog

    News

    Syndication