(Default) instance already exists (not really!)

Ok,

I haven't had this much trouble installing MS software in many moons. My end goal is to install Team Foundation Server, but to do that I need SQL Server 2005 first, then SharePoint, then TFS. At each of these steps it is appearing to be a mine field, and it is apparent that the MS Installer is doing a terrible job at uninstalling everything.

End of whine. So my situation is this, I had installed MS SQL Server Developer 2005 and found out that the Reporting Server wasn't working. Basically, because at one time or another I had FP extentions installed, and permissions were hopelessly munged. The fix on the forums was to back everything out... SQL Server, IIS, Sharepoint, and do a scorch and burn, effectively erradicating any trace that any of these existed on the disk.

This accomplished, but... now when I try to reinstall SQL Server, it claims the default instance "already exists." So... I've tried various registry hacks, tracking down any trance of instances. Here are some of things I've tried to no avail...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=148487&SiteID=1
http://support.microsoft.com/default.aspx?scid=kb;en-us;290991&sd=tech
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

So... short of going beyond scorch and burn, and nuke the entire machine, what are my options? Erasing the OS and starting from scratch does not seem like an option because, it seems, that seems I'll never get anything installed if I have to keep doing this.

Ideas anyone? Your help is greatly appreciated.

-Eric

FYI -- When running RegSeeker I find nearly 300 bogus registry entries left over from the MS uninstall--someone's got to fix that.Ok, I found a possible solution. But... it is very very risky. So don't blame me if you torpedo your server using my advice. But it worked for me.

But I'm posting this in case someone else find themselves in the same bind as me.

Following the suggestion of one of the other forum posts I saw, I looked for all entries for SQL Server. I saw a zillion entries for version 9.0.242.0.

Using RegSeeker, I wacked those. So they were gone.

Next, I saw another bazillion entries for "SQL Server." I surmized that SQL Server was completely uninstalled, these should be gone as well. So I delete those as well.

Another search for "SQLServer" also turned up a bazillion entries. Most of these were classes. Taking a deep breath, I deleted all of these as well.

In all, there were many thousands of registry entries that probably should have been deleted by the uninstall, but weren't.

So far, I've managed to reinstall SQL Server 2005 Developer and all is A-OK. So problem solved (I'd knock on wood if I have any real wood in my cube).

-Ericsql

(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
I forgot to mention that both machine are with 32 bits processors
Thanks again
AA
"AA" <aa@.personal.net.py> wrote in message
news:%23K0V94MIEHA.2376@.TK2MSFTNGP12.phx.gbl...
> Hello, I am purchasing a HP DL-380 (Cluster)
> I am planing to install Windows 2003 and SQL 2000
> Both machines has two processors and 4 GB o Physical Memory (RAM), but I
> want to put 6 GB in the
> Active Machine and 2 GB in the Passive Machine.
> So, That is possible?
> 1) Is possible to have differentes memory configuration in a cluster?
> 2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
>
> Thanks a lot!!
>
> AA
>

(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
Do not do this. Just remember that some day resources from node one with 6GB of memory failover to node 2 with 2GB of memory. What will you do then
rgds
Sinisa Perovic
|||What you will do then is exactly what everyone has to do who is running a
configuration with dissimilar processing capacity. You plan for the case
where both are running on the node with the least power. You estimate the
degradation in performance for the applications based on various load and
time scenarios. You then make a business decision as to whether that
degradation in performance during that specific downtime scenario is
acceptable or not. If it is acceptable, you configure it and off you go.
If it isn't acceptable, you come up with alternatives. Saying to not ever
do this is a very simplistic answer that simply is not correct.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

"SQL Server Management Studio Express" install location

I just installed the "SQL Server Management Studio Express" but it didn't tell me where it was installed. How do I get the application started ?A short-cut should have been add to ALL Programs | Microsoft SQL Server 2005 | SQL Server Management Studio Express CTP.

Peter|||found it here

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"

"Setup has detected one or more instances of SQL Server 2000..."

Tried to install the CTP and got a message stating that 2008 won't coexist with 2000. I had an instance of 2000 Developer Edition on here that I was testing some stuff with. I removed that, rebooted, and I still get the same message. Am I to assume that you can't even install 2008 if you've got the 2000 client tools installed, or am I missing something else?
Have a look at section 2.1.1 of the readme file, it states "To work around this issue, manually remove the registry key at HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80, and then re-run SQL Server "Katmai" June CTP Setup." Note that this will likely break the 2000 tools so uninstall them first or better yet use VPC/VMWare to create an isolated environment. CTP's often don't play well with other versions and can be difficult to uninstall cleanly.|||Ah ha, the actual CTP ISO has an outdated readme that doesn't mention that part. I bet that'll do the trick. Thanks.
|||

Hi,

I also got the same warning message about side by side running of SQL2k and Katmai June CTP. But I could not find any note about SQL 2000 in the readme documents of the installation.

|||Yeah, the readme file that's included with the installation is slightly out of date. I think this is the one you need: http://connect.microsoft.com/SQLServer/Downloads/DownloadDetails.aspx?DownloadID=6834

|||

Hi David,

Thanks for the link. Great help!

"Setup has detected one or more instances of SQL Server 2000..."

Tried to install the CTP and got a message stating that 2008 won't coexist with 2000. I had an instance of 2000 Developer Edition on here that I was testing some stuff with. I removed that, rebooted, and I still get the same message. Am I to assume that you can't even install 2008 if you've got the 2000 client tools installed, or am I missing something else?
Have a look at section 2.1.1 of the readme file, it states "To work around this issue, manually remove the registry key at HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80, and then re-run SQL Server "Katmai" June CTP Setup." Note that this will likely break the 2000 tools so uninstall them first or better yet use VPC/VMWare to create an isolated environment. CTP's often don't play well with other versions and can be difficult to uninstall cleanly.|||Ah ha, the actual CTP ISO has an outdated readme that doesn't mention that part. I bet that'll do the trick. Thanks.
|||

Hi,

I also got the same warning message about side by side running of SQL2k and Katmai June CTP. But I could not find any note about SQL 2000 in the readme documents of the installation.

|||Yeah, the readme file that's included with the installation is slightly out of date. I think this is the one you need: http://connect.microsoft.com/SQLServer/Downloads/DownloadDetails.aspx?DownloadID=6834

|||

Hi David,

Thanks for the link. Great help!

"Enable user SQL instances"

Hi I have Visual Studio 2005 with SP1 installed, and I want to install the Management Studio. I tried many times installing that and I always got the same problem, which is when I try to create a database in VS I just don’t get trough as I used to. A message appears saying that I’ve to enable some estance. So to resolve the problem I saw if is everything ok with the SQL Server, which seemed to be fine, but I couldn’t start the Report service.

Now I just formatted the computer and I’m afraid to happen all over again. May be the version with only the Management would be fine, I don’t know if it adds something beside of that.

Thank you very much.

After installing Express, you need to explicitly enable remote connections. Is this the issue you are seeing? If not, please supply an exact error message or a log snippet showing the problem.

Thanks,
Sam Lester (MSFT)

|||

Was about "Enable user SQL instances" and the Report Service didn’t started too.

How do I enable this remote connections?

And in the instalation, Should I Add a user to the SQL Server Administration Role?

And also in the step "ready to install" of the SQL Server SP2 shows the following:

The following components will be installed:

· SQL Server Database Services (Upgrade)

(Database Services, Replication, Full-Text Search)

· Reporting Services

(Reporting Services, Report Manager)

· Client Components (Upgrade)

(Connectivity Components, Management Studio Express)

Warning: Setup found that the following components that already exist are at a different service pack level than the components being installed.

Components: Microsoft SQL Server 2005 Tools Express Edition, Microsoft SQL Server 2005 Express Edition (SQLEXPRESS)

After completing setup, you must download and apply the latest SQL Server 2005 service pack to all the components.

$#@$#%! SQL 2005 Cluster Install!

I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.

SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.

For a premier product, this installation SUCKS.

Whooo. Okay. I feel better.

Here's my situation:
4-node Cluster (Windows 2003 Enterprise Edition), SP1
SQL 2005 Enterprise Edition

Process:
Install OS
Patch OS to SP1
Cluster OS on SAN
Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks
Configure MSDTC (network access, configure cluster resources)

Start SQL Installation
Install RTM Binaries on Node 1 for Default Instance
Install Workstation and non-cluster components on remaining nodes
Install RTM Binaries on Node 2 for Named Instance

Reboot all nodes

Install SP1 for all instances from node 1

Install SP1 for all local services/applications for all other nodes

While attempting to install the 2153 SQL patch/hotfix, the process will either:
Hang while waiting for the first passive node for the default instance; or
Crash immediately with no error messages in the logs.

This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.

Regards,

hmscottI had a very similar problem recently involving a Windows 2003 cluster and an active / active install. I had to give the userid I was using explicit full permissions on the WINDOWS/temp folder on the secondary machine before the install would complete successfully, even though the account I was using was a domain admin.

It's certainly a stab in the dark, but may be worth a try|||I was able to complete the 2153 patch process by deselecting one of the nodes (ie, but only choosing to do one node at a time.

The other #$!#@.! I hate about using the 2153 patch is that it must be run on all the nodes for the non-clustered services (notification services, SQL Tools, integration services).

I love SQL 2005. I expect to earn a substantial part of my income for the next 5 years from SQL 2005. But I sure do not like the installation of SQL 2005. I hope that they get these issues resolved by SQL 2008.

Regards,

hmscott