April 8, 2009 at 6:18 pm
I've investigated a lot on the web but still cannot correct my problem with SQL Server 2008 Express.
I already have an SQL Server 2005 Standard Edition default database set up on my Vista machine. I also have loaded Visual Web Developer 2008 and all works fine.
Now i have downloaded SQL Server 2008 express an given it a named instance XXXXXX.
However, i get errors when trying to connect via SSMS 2008. I have attached my LOG file which indicates the model and tempdb physical file locations are a weird directory location on e: drive which doesn't even exist.
I have read a number of forums about running the cmd and sqlcmd commands in order to ALTER the locations for these database files. However my tempdb is not even created yet for the new instance since i have yet to start the service for the first time.
Does anyone know exactly what to do to get the services running?
April 8, 2009 at 7:16 pm
Hi,
Have you configured it properly while installing the SQL 2008 and also does the SQL server start up account has right permissions? It seems to me that it is an operating system error. Investigate the file path issues, if the problem still persists I would advise you to re install the 2008.
And also please do not cross post as this leads other members to confusion.
April 9, 2009 at 6:05 am
Hi,
I am agree with above post. I have Win XP on my laptop and have installed both SS2k5 and SS2k8; and both are working fine.
It will be helpful if you provide your installation steps and the version which u hv installed!
"Don't limit your challenges, challenge your limits"
April 13, 2009 at 4:53 pm
I've now done several uninstall/reinstalls and still the same problem exists. I've read a number of posts and a lot of them say the Visual Studio 2008 components cause issues or conflicts with SQL Server 2008 express installation.
I then decided to install the VWD/SQL Server 2008 Express package onto a different machine that has no other instances or visual studio installations and the package installed 100% successfully.
My only course of action now appears to completely uninstall all SQL Instances, Visual Studio instances (particularly 2008), Visual Web developer, etc... so that my system is entirely clean.
However, as i need to keep my system set up for SQL Server 2005 Standard along with BIDS 2005 in order to match my production system, i will be forced to buy a new hard drive, install the Vista O/S from scratch, effectively setting up a new development machine with VWD/SQL server 2008 express.
Sooooooo sad how microsoft cannot get their versioning right between Standard licensed editions and free express editions!!!
April 13, 2009 at 10:35 pm
Actually the installation order effects a lot. You need to install
1) IIS 7
2) .NET framework 3.5
3) SQL Server 2008
4) Visual Studio 2008
Please check your installation order (also check your version compatibility too).
Also, are you going to setup new server? If yes, then why Vista? You can go for any server OS. I would prefer server OS then Vista for any of my server.
"Don't limit your challenges, challenge your limits"
April 13, 2009 at 10:58 pm
I agree the order of package installation does matter a lot as well as versioninig.
Hence why i want to go back to the beginning and not clash with any of my pre-existing 2005 software. I've already managed to wreck my 2005 BIDS which i now cannot even re-install from disk. It says all my components are already installed, even though i cannot start the app. So now i'm gonna have to remove and re-install everything anyway.
As for the O/S I'm using Vista on my Client machine to develop in ASP.NET hence why i want to install SQL Server, VWD, etc...
This is just to learn ASP.NET better for the time being until i purchase the proper Visual Studio package from MS for production use later. Then i will synchronise my dev. and prod. machines and O/S's.
At present our production server runs WIN2K3 with SQL Server 2005 Standard, hence why i'm having trouble with upgrading only my client machine to 2008 software and .NET.
Now that i've wrecked my client machine already, i plan to buy a new hard drive and install all 2008 components from scratch including my OS.
Then i can run:
1) Hard Drive #1 with Vista, SQL Server 2005, BIDS, etc...
2) New Hard Drive #2 with Vista, SQL Server 2008 Express, VWD 2008, etc...
Complete separation is the only way to be sure all installs are successful, unless you know the proper order from the beginning.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply