locked
Microsoft Windows SharePoint Services 3.0 1033 Lang Pack -- Error 1706? RRS feed

  • Question

  • when I install windows sharepoint service 3.0 it give me the following error, please advise me how to solve this problem?

    Thanks you in advance.

     

    Event Type:    Error
    Event Source:    MsiInstaller
    Event Category:    None
    Event ID:    11706
    Date:        7/24/2008
    Time:        10:05:13 AM
    User:        TFSRTM08\Darren
    Computer:    TFSRTM08
    Description:
    Product: Microsoft Windows SharePoint Services 3.0 1033 Lang Pack -- Error 1706. An installation package for the product Microsoft Windows SharePoint Services 3.0 1033 Lang Pack cannot be found. Try the installation again using a valid copy of the installation package 'wssmui.msi'.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 7b 39 30 31 32 30 30 30   {9012000
    0008: 30 2d 31 30 31 35 2d 30   0-1015-0
    0010: 34 30 39 2d 30 30 30 30   409-0000
    0018: 2d 30 30 30 30 30 30 30   -0000000
    0020: 46 46 31 43 45 7d         FF1CE} 

    Saturday, August 2, 2008 3:24 PM

Answers

  • There's no reason that I can see (or have read about) why a normal installation of WSS 3.0 should produce an error message that points to a Language Pack.

    So I suggest you give us full (and I mean full) information of your server; your operating system; your setting of pre-requisites for the WSS 3.0 installation and the WSS 3.0 installation itself (and which version of the download did you use).

    I'm assuming this was a new installation of WSS 3.0 and not an upgrade from WSS 2.0 as you didn't mention that ....

     

    I'm also assuming there is nothing else on the server (apart from the pre-requisites) when you installed WSS 3.0.

     

     

    • Marked as answer by Jake Wardley Monday, August 4, 2008 1:56 PM
    Sunday, August 3, 2008 8:11 AM
  • Hello Mark,

     

    I agree with Mike’s response that this issue is rare and it’s very important to know the environment where you tried to install WSS 3.0.

     

    Please also check the installation package in case it’s damaged or not properly downloaded. The official downloading links to Windows SharePoint Service 3.0 are:

     

    Windows SharePoint Service 3.0

    http://www.microsoft.com/downloads/details.aspx?FamilyId=D51730B5-48FC-4CA2-B454-8DC2CAF93951&displaylang=en

     

    Windows SharePoint Service 3.0 with SP1

    http://www.microsoft.com/downloads/details.aspx?FamilyID=ef93e453-75f1-45df-8c6f-4565e8549c2a&displaylang=en

     

    Thanks!

     

    Regards,

    Lionel

    • Marked as answer by Jake Wardley Monday, August 4, 2008 1:56 PM
    Monday, August 4, 2008 8:29 AM

All replies

  • There's no reason that I can see (or have read about) why a normal installation of WSS 3.0 should produce an error message that points to a Language Pack.

    So I suggest you give us full (and I mean full) information of your server; your operating system; your setting of pre-requisites for the WSS 3.0 installation and the WSS 3.0 installation itself (and which version of the download did you use).

    I'm assuming this was a new installation of WSS 3.0 and not an upgrade from WSS 2.0 as you didn't mention that ....

     

    I'm also assuming there is nothing else on the server (apart from the pre-requisites) when you installed WSS 3.0.

     

     

    • Marked as answer by Jake Wardley Monday, August 4, 2008 1:56 PM
    Sunday, August 3, 2008 8:11 AM
  • Hello Mark,

     

    I agree with Mike’s response that this issue is rare and it’s very important to know the environment where you tried to install WSS 3.0.

     

    Please also check the installation package in case it’s damaged or not properly downloaded. The official downloading links to Windows SharePoint Service 3.0 are:

     

    Windows SharePoint Service 3.0

    http://www.microsoft.com/downloads/details.aspx?FamilyId=D51730B5-48FC-4CA2-B454-8DC2CAF93951&displaylang=en

     

    Windows SharePoint Service 3.0 with SP1

    http://www.microsoft.com/downloads/details.aspx?FamilyID=ef93e453-75f1-45df-8c6f-4565e8549c2a&displaylang=en

     

    Thanks!

     

    Regards,

    Lionel

    • Marked as answer by Jake Wardley Monday, August 4, 2008 1:56 PM
    Monday, August 4, 2008 8:29 AM
  • I also have this problem. I have version of SharePoint installed with TFS 2007. In this version of WSS I cannot create new Web Applications or search sites, lists etc, so I need to upgrade to newer version WSS 3.0.

    I use only English language, regional settings are on USA, and I have same message as above.

    Thans for tips.
    Wednesday, October 8, 2008 7:28 AM
  • Please give me a link ,from where you get that tfs2007?

    Thanks.
    Wednesday, October 8, 2008 1:24 PM
  • I recently ran into the same problem in a lab server and think I have additional information but not an answer.  My server was a stable TFS 2008 (I'm sure the 2007 statement in another post was a typo) with WSS 3.0 SP1.  I installed the latest Team System Web Access service pack release and frankly botched the install.  I'm relatively sure that my broken TSWA install is what killed my WSS.  I state that both because of timing (it broken immediately after the TSWA uninstall) and because I know there was significant MUI support added to TSWA.  I don't have an answer but will try to fix this lab system as I have time and will post an update when I find it.
    Sunday, November 2, 2008 1:23 PM
  • I am facing this same problem so this must be more prominent than most people think. I have tried for hours trying to fix this problem and it has been a nightmare and I hope to never see it again. I inherited this horrible server and am going to retire it but I wanted more people to know that this is a problem with SharePoint and Microsoft needs to be more aware. Also this problem happened after the December 2008 cummulative update.
    Monday, January 12, 2009 9:57 PM
  • The problem is still out there, I got the same error message when during a install of WSS SP 2.

    What is the scoop.
    Thursday, July 2, 2009 6:53 AM
  • Also seeing this with TFS 2008.  Got this after installing WSS3 SP2 and doing a repair operation.

    Tuesday, February 9, 2010 9:03 PM
  • Had some time to come back and look at this.  Found 3 things that seemed to help.  With lots of runs of psconfigui in between.

    This happened after a data tier move, which went smoothly on the version control and work item side.  It was a little bumpier in the SSRS area and very bumpy when it came to SharePoint.

    error:

    [SPWssWebApplicationSequence] [ERROR] [3/1/2010 4:25:28 PM]: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=Default Web Site Parent=SPWebService is being updated by <domain>\<username>, in the STSADM process, on machine <app tier hostname>.  View the tracing log for more information about the conflict.

    solution:

    clear the SharePoint file system cache.  See http://support.microsoft.com/kb/939308

    error:

    An exception of type System.Data.SqlClient.SqlException was thrown.

    solution:

    Find and replace any occurrences of the old database name in WSS_Config.  The following bit of PowerShell helped:

    $sc=new-object data.sqlclient.sqlconnection 'Data Source=<data tier host>;Initial Catalog=WSS_Config;Integrated Security=true'
    $sa=new-object data.sqlclient.sqldataadapter @"
    declare @s varchar(max)
    set @s = 'select' + (select ' ISNULL((select * from wss_config..'
        + name + ' for xml path(''' + name + ''')),'''') + ' from wss_config.sys.objects
        where type = 'u' for xml path('')) + ''''''
    execute(@s)
    "@,$sc
    $ds=new-object data.dataset
    $sa.fill($ds)
    [xml]$wc='<root>'+$ds.tables[0].rows[0].column1+'</root>'
    # note: this search is case-sensitive
    $wc.selectnodes("/*/*[contains(.,'<old data tier host name>')]")|select outerxml
    

    The output of the script is one row for each row where the old data tier host name appears.  The top level element of the row is the table name and the next level down are the column names.

    error:

    The B2B upgrader timer job failed

    solution:

    See http://blog.mediawhole.com/2009/05/sharepoint-sp2-upgrade-fails-b2b.html (comments 3 and 4)


    After these three actions, TFS' captive SharePoint installation seemed to be back in business.  YMMV
    • Edited by unbob Tuesday, March 2, 2010 6:51 PM whitespace
    Tuesday, March 2, 2010 6:50 PM
  • I ran into this today.  I found no helpful info anywhere, so I'm posting my findings here.  I searched the registry for wssmui.msi and found the path to be a temp directory that no longer existed.  It was apparently where the WSS 3 installer (.exe) put the extracted files.  I had run the installer on another computer that still had the extracted files.  I copied them into existence on the server with this problem and all was well.

    Dear Microsoft,

    Please do not assume that your extracted temp files will live forever in a Windows user's temp directory!

    Sincerely,

    Lee C.

    Tuesday, May 18, 2010 7:09 PM
  • Lee - Thanks for your post.  I also ran into a problem installing WSS 3.0 with SP1, getting this error: "An installation package for the product Microsoft Windows SharePoint Services 3.0 1033 Lang Pack cannot be found.  Try the installation again using a valid copy of the installation package 'wssmui.msi'."

    Thanks to your post I searched the registry for wssmui.msi and found it under HKEY_Local_Machine\Software\Classes\Installer\Products\somefolder.  I uninstalled the broken unfinished install of WSS (by downloading and running the install again and chosing Remove), then  removed the registry folder containing the found wssmui.msi as well as another WS 3.0 entry just above it.  

    Then I  installed WSS again, this time with no error.

     

    Thursday, June 10, 2010 1:19 PM
  • Agreed - Lee thanks for your post. I was getting the language pack error when I tried a repair install. Searching through the registry, I also found the location it wanted the language pack to be in and I was able to match that up and finsih the install.
    Thursday, August 12, 2010 1:14 PM
  • Hi!

    I had the same problem. I installed WSS 3.09 directly from TFS 2010, and got this error. The solution was to un/install the WSS 3.0. Why it never works straight forward?

    Wednesday, November 10, 2010 4:01 PM