(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

<?xml version="1.0" encoding="utf-8"?>

Hey we've been building some reports.. occassionally the build / change
team complains when we use 'special characters' in our reports..
I opened up our RDLs; and I noted that we have this as the first line
<?xml version=3D"1.0" encoding=3D"utf-8"?>
I was thinking that we might need to change to 16 in order to allow
'special characters'
<?xml version=3D"1.0" encoding=3D"utf-16"?>
In other words; we are using SSRS 2005 in order to 'print letters' for
mass-mailing.. and we have some letters that people are printing out.
We just want to be able to use a simple character for a box-- as in a
simple checkbox-- that they can print off; fill out.. and snailmail
back in
I just have this gut feeling that I'm going to break our build process
if I send in a special character.. because 70% of our breaks have been
the result of special characters so far.
So am I limited to the ASCII set? Can I use Unicode characters?
So I need to set the UTF8 flag at the top of our reports to UTF16?
Thanks
-Aaron
=E2=80=ABanyone?
does anyone else have reports that have this at top?
<?xml version=3D"1.0" encoding=3D"utf-16"?>
or does everyone else have
<?xml version=3D"1.0" encoding=3D"utf-8"?>
you see this is the piece that's a buch of crap; microsoft is blocking
my posts.. just because I speak the truth.
Piece of shit ass company supports CENSORSHIP-- not in China-- but here
in their own backyard
-Aaron
aaron.kempf@.gmail.com wrote:
> Hey we've been building some reports.. occassionally the build / change
> team complains when we use 'special characters' in our reports..
> I opened up our RDLs; and I noted that we have this as the first line
> <?xml version=3D"1.0" encoding=3D"utf-8"?>
>
> I was thinking that we might need to change to 16 in order to allow
> 'special characters'
> <?xml version=3D"1.0" encoding=3D"utf-16"?>
> In other words; we are using SSRS 2005 in order to 'print letters' for
> mass-mailing.. and we have some letters that people are printing out.
> We just want to be able to use a simple character for a box-- as in a
> simple checkbox-- that they can print off; fill out.. and snailmail
> back in
>
> I just have this gut feeling that I'm going to break our build process
> if I send in a special character.. because 70% of our breaks have been
> the result of special characters so far.
> So am I limited to the ASCII set? Can I use Unicode characters?
> So I need to set the UTF8 flag at the top of our reports to UTF16?
> > Thanks
> > > -Aaron
> > =E2=80=AB|||my friend Hari told me that Reporting Services only supports the Ascii
character set.. is this true?
-Tom
aaron.kempf@.gmail.com wrote:
> anyone?
> does anyone else have reports that have this at top?
> <?xml version=3D"1.0" encoding=3D"utf-16"?>
> or does everyone else have
> <?xml version=3D"1.0" encoding=3D"utf-8"?>
> you see this is the piece that's a buch of crap; microsoft is blocking
> my posts.. just because I speak the truth.
> Piece of shit ass company supports CENSORSHIP-- not in China-- but here
> in their own backyard
> -Aaron
>
>
> aaron.kempf@.gmail.com wrote:
> > Hey we've been building some reports.. occassionally the build / change
> > team complains when we use 'special characters' in our reports..
> >
> > I opened up our RDLs; and I noted that we have this as the first line
> > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> >
> >
> > I was thinking that we might need to change to 16 in order to allow
> > 'special characters'
> >
> > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> >
> > In other words; we are using SSRS 2005 in order to 'print letters' for
> > mass-mailing.. and we have some letters that people are printing out.
> >
> > We just want to be able to use a simple character for a box-- as in a
> > simple checkbox-- that they can print off; fill out.. and snailmail
> > back in
> >
> >
> > I just have this gut feeling that I'm going to break our build process
> > if I send in a special character.. because 70% of our breaks have been
> > the result of special characters so far.
> >
> > So am I limited to the ASCII set? Can I use Unicode characters?
> > So I need to set the UTF8 flag at the top of our reports to UTF16?
> > > > Thanks
> > > > > > -Aaron
> > > > =E2=80=AB|||yeah.. it looks like reporting services only supports the ASCII / ANSI
character set..
I wonder how the people in China do it?
-Aaron
punjab_tom@.hotmail.com wrote:
> my friend Hari told me that Reporting Services only supports the Ascii
> character set.. is this true?
> -Tom
>
>
> aaron.kempf@.gmail.com wrote:
> > anyone?
> >
> > does anyone else have reports that have this at top?
> > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > or does everyone else have
> > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> >
> > you see this is the piece that's a buch of crap; microsoft is blocking
> > my posts.. just because I speak the truth.
> >
> > Piece of shit ass company supports CENSORSHIP-- not in China-- but here
> > in their own backyard
> >
> > -Aaron
> >
> >
> >
> >
> > aaron.kempf@.gmail.com wrote:
> > > Hey we've been building some reports.. occassionally the build / chan=ge
> > > team complains when we use 'special characters' in our reports..
> > >
> > > I opened up our RDLs; and I noted that we have this as the first line
> > > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> > >
> > >
> > > I was thinking that we might need to change to 16 in order to allow
> > > 'special characters'
> > >
> > > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > >
> > > In other words; we are using SSRS 2005 in order to 'print letters' for
> > > mass-mailing.. and we have some letters that people are printing out.
> > >
> > > We just want to be able to use a simple character for a box-- as in a
> > > simple checkbox-- that they can print off; fill out.. and snailmail
> > > back in
> > >
> > >
> > > I just have this gut feeling that I'm going to break our build process
> > > if I send in a special character.. because 70% of our breaks have been
> > > the result of special characters so far.
> > >
> > > So am I limited to the ASCII set? Can I use Unicode characters?
> > > So I need to set the UTF8 flag at the top of our reports to UTF16?
> > > > > > Thanks
> > > > > > > > > -Aaron
> > > > > > =E2=80=AB|||In India; we need to use a larger character set than ASCII / ANSI
can someone help?
-Tom
aaron.kempf@.gmail.com wrote:
> yeah.. it looks like reporting services only supports the ASCII / ANSI
> character set..
> I wonder how the people in China do it?
> -Aaron
>
> punjab_tom@.hotmail.com wrote:
> > my friend Hari told me that Reporting Services only supports the Ascii
> > character set.. is this true?
> >
> > -Tom
> >
> >
> >
> >
> > aaron.kempf@.gmail.com wrote:
> > > anyone?
> > >
> > > does anyone else have reports that have this at top?
> > > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > > or does everyone else have
> > > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> > >
> > > you see this is the piece that's a buch of crap; microsoft is blocking
> > > my posts.. just because I speak the truth.
> > >
> > > Piece of shit ass company supports CENSORSHIP-- not in China-- but he=re
> > > in their own backyard
> > >
> > > -Aaron
> > >
> > >
> > >
> > >
> > > aaron.kempf@.gmail.com wrote:
> > > > Hey we've been building some reports.. occassionally the build / ch=ange
> > > > team complains when we use 'special characters' in our reports..
> > > >
> > > > I opened up our RDLs; and I noted that we have this as the first li=ne
> > > > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> > > >
> > > >
> > > > I was thinking that we might need to change to 16 in order to allow
> > > > 'special characters'
> > > >
> > > > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > > >
> > > > In other words; we are using SSRS 2005 in order to 'print letters' =for
> > > > mass-mailing.. and we have some letters that people are printing ou=t=2E
> > > >
> > > > We just want to be able to use a simple character for a box-- as in= a
> > > > simple checkbox-- that they can print off; fill out.. and snailmail
> > > > back in
> > > >
> > > >
> > > > I just have this gut feeling that I'm going to break our build proc=ess
> > > > if I send in a special character.. because 70% of our breaks have b=een
> > > > the result of special characters so far.
> > > >
> > > > So am I limited to the ASCII set? Can I use Unicode characters?
> > > > So I need to set the UTF8 flag at the top of our reports to UTF16?
> > > >
> > > > Thanks
> > > > > > > > > > > > -Aaron
> > > > > > > > =E2=80=AB