Re: sql 2008 install problem re: visual studio 2008
ronco...@gmail.com
<ten....@dnartreb.noraa> wrote:
> This happened to a lot of people who installedVisualStudio2008, then got
> wind of a pre-release CTP version of SP1 for VS2008. They installed that,
> but unfortunatelySQL2008is not compatible with that. You may need to
> uninstall the SP you have and get the *real* SP1. Or maybe as drastic as
> removingVisualStudioand not installing it until AFTER installingSQLServer2008. It is a pain, I know. These things should work together like
> peanut butter and jam instead of oil & water, but it is what we're stuck
> with right now unfortunately.
Thanks Aaron--I am also experiencing install problems installing SQL
Server 2008 Express with Microsoft Visual Studio 2008 Professional
Edition, when SQL Server 2005 was working fine before. I have had to
nuke/remove VS08 entirely, and SQL Server 2005 entirely (Professional
edition) and now I'm going to first load SQL Server 08 and then, as
you recommend, try Visual Studio 2008 Express editions (C#, Web
development editions) and hope that works.
But I've lost my paid for versions--and no amount of patching or SP
work (they all fail at the end). Various hints of workarounds on the
net but it's too complicated. Installation failed for component
Runtime Pre-requisites. MSI returned error code 1603 is one such
error...what it amounts to is that if you are missing a certain hotfix
patch, you will run into a dead end that will necessitate you fiddle
with your registry and/or uninstall Office 2007/ 2003, from what I've
seen. The problem arose when I installed VS08 on top of VS05, after a
separate installation of VS08 by itself failed.
I have Vista OS on a 32 bit Core 2 Duo.
RC
ronco...@gmail.com
wrote:
Here is the protocol I am following:
1) Remove all versions of Visual Studio
2) remove all versions of SQL Server
3) remove Office 2007 (according to some reports on the net, this is
the reason the installation fails...luckily I don't use Office 2007
much and this was no big loss)
4) Install Dot Net 3.5 framework and SP1 for it.
5) Install SQL Server 2008 Express. This program has a checklist of
other programs you must also install before you can install this
(three or four, names escape me, like "Powershell 1.0 for Vista", but
you'll be prompted during setup to install these and you cannot
proceed in SS08 unless you install these). During installation of SQL
Server 2008 you would do well to follow some blogger's screenshots (I
followed one guy, but cannot find his link now, but did find this
site, note the caveat*). For example, setting up SQL Server for
passwords via Windows Authentication vs. Mixed Mode--you have to make
a choice and not leave the spaces blank. I chose Windows
Authentication since it's simpler and you can always change into Mixed
Mode later.
6) Install Vista SP 1 (released in 2009)
7) install the various flavors of Visual Studio Express (C#, ASP.NET
in my instance).
So far I'm at step #6, but if I have any problems I'll post here.
Throughout each of these steps you should reboot, since there are
registry changes made. The entire process, unless you are very
diligent and are stuck next to your computer, takes about a day (even
with DSL downloads). I don't think you can automate the install, but
I could be wrong.
RC
* http://www.packtpub.com/article/microsoft-sql-server-2008-installation-made-easy
SQL 2008 server is the latest in the line of Microsoft database
servers and this article by Dr. Jayaram Krishnaswamy discusses the
challenges one may face in installing the Developer version of this
product which was released in November 2007. On a virgin machine the
software probably installs without a hitch but with a history of
installs, especially of the earlier versions it is anything but a joy
ride.
"It is almost always true for most of the software I have installed,
not necessarily limited to Microsoft. However, most of Microsoft
products need entry in the Window's registry and it is almost certain
that one has to follow a certain protocol if one wishes to have a
successful install. In fact the unsuccessful install flags out what
went wrong while the initial steps do verify the requirements during
installation. Despite this help and warnings one may face problems
simply because it is not possible to foresee all possible combinations
of hardware, software, user created error issues at launch time of the
product. Again this article does not guarantee a successful install if
one were to follow the steps delineated but gives you some guidance
based on the author's experience."
On problems with Visual Studio 2008 SP1 install see here:
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/315c7885-e680-4a83-b6a5-8a2795f596ea/#page:2
ronco...@gmail.com
wrote:
As promised, I did complete the installation, and everything kind of
works, but with caveats.
First, ADO.NET programs work with Visual Studio C# but only when
connecting using SQL Server Compact Edition databases, not regular SQL
Server Express databases, as it should.
Below are some error messages. I did fix the last error by giving
permission to the file in question, but the others fail.
I think this is a global permissions problem for SQL Server (not
limited to a file), but I'm not sure. I'll post in another thread.
RC
---------------------------
Microsoft Visual C# 2008 Express Edition
---------------------------
Failed to generate a user instance of SQL Server due to a failure in
starting the process for the user instance. The connection will be
closed.
---------------------------
OK
---------------------------
///////////////////////////////////////////////////////////////////////
---------------------------
Microsoft Visual C# 2008 Express Edition
---------------------------
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
---------------------------
OK
---------------------------
///////////////////////////////
---------------------------
Microsoft Visual C# 2008 Express Edition
---------------------------
Access to the database file is not allowed. [ File name = C:\Program
Files\Microsoft SQL Server Compact Edition\v3.5\Samples
\Northwind.sdf ]
---------------------------
OK //I FIXED THIS BY CHANGING THE SECURITY PERMISSION ON THE DATABSE
FILE Northwind.sdf
---------------------------
////////////