Solved

Error installing SQL Server 2008 R2 on Windows 7 32-bit: failed to find LandingPage.exe--continue?

Posted on 2013-05-28
4
662 Views
Last Modified: 2013-06-08
A coworker of mine got the attached error installing SQL Server 2008 R2 on Windows 7 32-bit:
Installation error for SQL Server 2008 R2: LandingPage.exe"An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.  The system cannot find the file specified.  (C:\Users\<user>\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_<many alphanumeric characters>\10.0.0.0\user.config"
with options of Continue and Quit.
Now, I have looked on Google and ExpertsExchange and have found several instances of this error; however, in all cases,  people are asking about how to fix the problem.  It seems to boil down to A) uninstalling/reinstalling SQL Server; B) reinstalling .NET 3.5 and/or 4.0 or C) having corrupt installation media.  The thing is, my coworker just continued.  Now, SQL Server and the applications using it seem to be working fine after just ignoring the error.

Does anyone know what happens if you just ignore the error?  Does SQL Server have subtle problems down the line because of it?  Or is the simple fact that SQL appears to be working normally sufficient evidence that the installation managed to work around the problem?

One more note: The system previously had SQL Server Developer Edition; my coworker uninstalled this and all other SQL Server items he could find in Programs and Features before installing SQL Server 2008 R2.

Thanks,
Midnight42
0
Comment
Question by:midnight42
  • 2
  • 2
4 Comments
 
LVL 11

Expert Comment

by:SThaya
Comment Utility
0
 
LVL 11

Expert Comment

by:SThaya
Comment Utility
0
 

Accepted Solution

by:
midnight42 earned 0 total points
Comment Utility
Thanks to all who posted, but the posts did not quite answer my question.  The threads involved show how to fix this problem while reinstalling SQL Server; for complicated reasons, a reinstall is unacceptable except as a last resort.  My question was, what are the consequences if we leave SQL Server installed after the error?  (The installation appeared to go normally after getting this error.)

In any case, another coworker found the answer to this question: The assembly involved can give trouble when installing on systems without U.S. English as the language; certain symbols (e.g. British pound symbols) may not display correctly.  This is unlikely to be a problem in our case, so we can simply leave SQL Server installed as is.

I am marking this question solved.
0
 

Author Closing Comment

by:midnight42
Comment Utility
As stated above, I (or rather a coworker) found the answer.  My question: What are the consequences of ignoring this error and proceeding with the installation of SQL Server?  The answer: The assembly in question can cause errors displaying symbols that are not used in U.S. English, e.g. British pound symbols, etc.  This will not be an issue with this particular installation, so ignoring the error and finishing the installation was fine with us.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

This is basically a blog post I wrote recently. I've found that SARGability is poorly understood, and since many people don't read blogs, I figured I'd post it here as an article. SARGable is an adjective in SQL that means that an item can be fou…
In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now