I need some serious help here

I had the evaluation version running, generated beautiful reports.
I upgraded my computer from Windows 2000 to 2003 and after a day or two
realized RS would not run, but it could have expired.
I upgraded my RS from the evaluation version to the release version,
choosing "upgrade". After the upgrade at first it wouldn't allow access to
the virtual dirs (eventually I hard-coded the Admin name/password in the
impersonation line in web.config which fixed it) and after that it
complained about unable to connect to the database. I tried the rsconfig
utility, then it complained about unable to decrypt a key pair and it
suggested restoring the default, which of course I did not have (it really
surprised me there).
I un-installed RS and started a fresh install. Now it says "The edition of
the Report Server Database is not supported on the edition of SQL Server
2000 you have chosen".
Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
using my SQL Server version (my machine was still Win 2000 though).
I have been fighting this install for about 7 hours now (on a Sunday),
googled, newsgroups, used bad language, etc, etc.
I am (or was) going to demo some (beautiful) reports to a client tomorrow.Do you have SP3a installed on your SQL2K enterprise?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
>I had the evaluation version running, generated beautiful reports.
> I upgraded my computer from Windows 2000 to 2003 and after a day or two
> realized RS would not run, but it could have expired.
> I upgraded my RS from the evaluation version to the release version,
> choosing "upgrade". After the upgrade at first it wouldn't allow access to
> the virtual dirs (eventually I hard-coded the Admin name/password in the
> impersonation line in web.config which fixed it) and after that it
> complained about unable to connect to the database. I tried the rsconfig
> utility, then it complained about unable to decrypt a key pair and it
> suggested restoring the default, which of course I did not have (it really
> surprised me there).
> I un-installed RS and started a fresh install. Now it says "The edition of
> the Report Server Database is not supported on the edition of SQL Server
> 2000 you have chosen".
> Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
> using my SQL Server version (my machine was still Win 2000 though).
> I have been fighting this install for about 7 hours now (on a Sunday),
> googled, newsgroups, used bad language, etc, etc.
> I am (or was) going to demo some (beautiful) reports to a client tomorrow.
>|||Hi Brian,
I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at when
it decides that this is the wrong version?
I guess I can backup all databases and re-install SQL Server if you think
that should do it. I gave that a thought already, but then it came to mind
what if it is something else and I went through that exercise for nothing.
Thanks for your ideas,
Chris.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Do you have SP3a installed on your SQL2K enterprise?
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> >I had the evaluation version running, generated beautiful reports.
> > I upgraded my computer from Windows 2000 to 2003 and after a day or two
> > realized RS would not run, but it could have expired.
> > I upgraded my RS from the evaluation version to the release version,
> > choosing "upgrade". After the upgrade at first it wouldn't allow access
to
> > the virtual dirs (eventually I hard-coded the Admin name/password in the
> > impersonation line in web.config which fixed it) and after that it
> > complained about unable to connect to the database. I tried the rsconfig
> > utility, then it complained about unable to decrypt a key pair and it
> > suggested restoring the default, which of course I did not have (it
really
> > surprised me there).
> > I un-installed RS and started a fresh install. Now it says "The edition
of
> > the Report Server Database is not supported on the edition of SQL Server
> > 2000 you have chosen".
> > Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
> > using my SQL Server version (my machine was still Win 2000 though).
> > I have been fighting this install for about 7 hours now (on a Sunday),
> > googled, newsgroups, used bad language, etc, etc.
> > I am (or was) going to demo some (beautiful) reports to a client
tomorrow.
> >
> >
>|||I just looked at my notes from my install on Windows 2003. For Windows 2003
only, you need a hotfix for SQL Server. Seems strange that SQL Server needs
it but only on 2003 but there you are. It is in the installation notes for
the install. Besides SP3a you need hotfix 859.
Your situation is a bit different. Only RS is on 2003 and your SQL Server is
still on 2000 so it seems like you wouldn't need the hotfix but you are
accessing it from Windows 2003 so maybe that is the key point. In my case
SQL Server and RS are both on Windows 2003.
In any case, it won't hurt anything and it might fix your problem so I
suggest installing the hotfix and see if that helps.
Hope that helps.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi Brian,
> I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at
when
> it decides that this is the wrong version?
> I guess I can backup all databases and re-install SQL Server if you think
> that should do it. I gave that a thought already, but then it came to mind
> what if it is something else and I went through that exercise for nothing.
> Thanks for your ideas,
> Chris.
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > Do you have SP3a installed on your SQL2K enterprise?
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > >I had the evaluation version running, generated beautiful reports.
> > > I upgraded my computer from Windows 2000 to 2003 and after a day or
two
> > > realized RS would not run, but it could have expired.
> > > I upgraded my RS from the evaluation version to the release version,
> > > choosing "upgrade". After the upgrade at first it wouldn't allow
access
> to
> > > the virtual dirs (eventually I hard-coded the Admin name/password in
the
> > > impersonation line in web.config which fixed it) and after that it
> > > complained about unable to connect to the database. I tried the
rsconfig
> > > utility, then it complained about unable to decrypt a key pair and it
> > > suggested restoring the default, which of course I did not have (it
> really
> > > surprised me there).
> > > I un-installed RS and started a fresh install. Now it says "The
edition
> of
> > > the Report Server Database is not supported on the edition of SQL
Server
> > > 2000 you have chosen".
> > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
happy
> > > using my SQL Server version (my machine was still Win 2000 though).
> > > I have been fighting this install for about 7 hours now (on a Sunday),
> > > googled, newsgroups, used bad language, etc, etc.
> > > I am (or was) going to demo some (beautiful) reports to a client
> tomorrow.
> > >
> > >
> >
> >
>|||Hi Bruce,
I have both SQL Server and RS running on the same 2003 machine, upgraded
from Win 2000 to 2003.
I am now attempting to locate hotfix 859, if you know the URL drop it here.
Thanks.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> I just looked at my notes from my install on Windows 2003. For Windows
2003
> only, you need a hotfix for SQL Server. Seems strange that SQL Server
needs
> it but only on 2003 but there you are. It is in the installation notes for
> the install. Besides SP3a you need hotfix 859.
> Your situation is a bit different. Only RS is on 2003 and your SQL Server
is
> still on 2000 so it seems like you wouldn't need the hotfix but you are
> accessing it from Windows 2003 so maybe that is the key point. In my case
> SQL Server and RS are both on Windows 2003.
> In any case, it won't hurt anything and it might fix your problem so I
> suggest installing the hotfix and see if that helps.
> Hope that helps.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Hi Brian,
> >
> > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at
> when
> > it decides that this is the wrong version?
> > I guess I can backup all databases and re-install SQL Server if you
think
> > that should do it. I gave that a thought already, but then it came to
mind
> > what if it is something else and I went through that exercise for
nothing.
> >
> > Thanks for your ideas,
> >
> > Chris.
> >
> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > Do you have SP3a installed on your SQL2K enterprise?
> > >
> > > --
> > > Brian Welcker
> > > Group Program Manager
> > > SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > >I had the evaluation version running, generated beautiful reports.
> > > > I upgraded my computer from Windows 2000 to 2003 and after a day or
> two
> > > > realized RS would not run, but it could have expired.
> > > > I upgraded my RS from the evaluation version to the release version,
> > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> access
> > to
> > > > the virtual dirs (eventually I hard-coded the Admin name/password in
> the
> > > > impersonation line in web.config which fixed it) and after that it
> > > > complained about unable to connect to the database. I tried the
> rsconfig
> > > > utility, then it complained about unable to decrypt a key pair and
it
> > > > suggested restoring the default, which of course I did not have (it
> > really
> > > > surprised me there).
> > > > I un-installed RS and started a fresh install. Now it says "The
> edition
> > of
> > > > the Report Server Database is not supported on the edition of SQL
> Server
> > > > 2000 you have chosen".
> > > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
> happy
> > > > using my SQL Server version (my machine was still Win 2000 though).
> > > > I have been fighting this install for about 7 hours now (on a
Sunday),
> > > > googled, newsgroups, used bad language, etc, etc.
> > > > I am (or was) going to demo some (beautiful) reports to a client
> > tomorrow.
> > > >
> > > >
> > >
> > >
> >
> >
>|||Nope, did not help if this was the correct hotfix, downloaded from
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
Thanks in any case.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Hi Bruce,
> I have both SQL Server and RS running on the same 2003 machine, upgraded
> from Win 2000 to 2003.
> I am now attempting to locate hotfix 859, if you know the URL drop it
here.
> Thanks.
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > I just looked at my notes from my install on Windows 2003. For Windows
> 2003
> > only, you need a hotfix for SQL Server. Seems strange that SQL Server
> needs
> > it but only on 2003 but there you are. It is in the installation notes
for
> > the install. Besides SP3a you need hotfix 859.
> >
> > Your situation is a bit different. Only RS is on 2003 and your SQL
Server
> is
> > still on 2000 so it seems like you wouldn't need the hotfix but you are
> > accessing it from Windows 2003 so maybe that is the key point. In my
case
> > SQL Server and RS are both on Windows 2003.
> >
> > In any case, it won't hurt anything and it might fix your problem so I
> > suggest installing the hotfix and see if that helps.
> >
> > Hope that helps.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi Brian,
> > >
> > > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking
at
> > when
> > > it decides that this is the wrong version?
> > > I guess I can backup all databases and re-install SQL Server if you
> think
> > > that should do it. I gave that a thought already, but then it came to
> mind
> > > what if it is something else and I went through that exercise for
> nothing.
> > >
> > > Thanks for your ideas,
> > >
> > > Chris.
> > >
> > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
message
> > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > Do you have SP3a installed on your SQL2K enterprise?
> > > >
> > > > --
> > > > Brian Welcker
> > > > Group Program Manager
> > > > SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > >I had the evaluation version running, generated beautiful reports.
> > > > > I upgraded my computer from Windows 2000 to 2003 and after a day
or
> > two
> > > > > realized RS would not run, but it could have expired.
> > > > > I upgraded my RS from the evaluation version to the release
version,
> > > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> > access
> > > to
> > > > > the virtual dirs (eventually I hard-coded the Admin name/password
in
> > the
> > > > > impersonation line in web.config which fixed it) and after that it
> > > > > complained about unable to connect to the database. I tried the
> > rsconfig
> > > > > utility, then it complained about unable to decrypt a key pair and
> it
> > > > > suggested restoring the default, which of course I did not have
(it
> > > really
> > > > > surprised me there).
> > > > > I un-installed RS and started a fresh install. Now it says "The
> > edition
> > > of
> > > > > the Report Server Database is not supported on the edition of SQL
> > Server
> > > > > 2000 you have chosen".
> > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
> > happy
> > > > > using my SQL Server version (my machine was still Win 2000
though).
> > > > > I have been fighting this install for about 7 hours now (on a
> Sunday),
> > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > I am (or was) going to demo some (beautiful) reports to a client
> > > tomorrow.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||OK, just in case any of the following might help you. There were several
things I had to do different under 2003 Server.
1. Hotfix 859
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
2. Configure server with application server, asp.net (two distinct
activities). Seems if this was an issue you would get a different error
message
3. I selected built-in account. Two choices: network and system. It defaults
to network. I wanted system (which is how my previous configurations were
configured).
Other than these my installation went smoothly but then I had a clean
install of Windows 2003 Advanced Server and SQL Server Enterprise.
What do you get when you do a select @.@.version? I get this:
Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: )
Bruce L-C
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> Nope, did not help if this was the correct hotfix, downloaded from
> http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> Thanks in any case.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > Hi Bruce,
> >
> > I have both SQL Server and RS running on the same 2003 machine, upgraded
> > from Win 2000 to 2003.
> > I am now attempting to locate hotfix 859, if you know the URL drop it
> here.
> >
> > Thanks.
> >
> > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > I just looked at my notes from my install on Windows 2003. For Windows
> > 2003
> > > only, you need a hotfix for SQL Server. Seems strange that SQL Server
> > needs
> > > it but only on 2003 but there you are. It is in the installation notes
> for
> > > the install. Besides SP3a you need hotfix 859.
> > >
> > > Your situation is a bit different. Only RS is on 2003 and your SQL
> Server
> > is
> > > still on 2000 so it seems like you wouldn't need the hotfix but you
are
> > > accessing it from Windows 2003 so maybe that is the key point. In my
> case
> > > SQL Server and RS are both on Windows 2003.
> > >
> > > In any case, it won't hurt anything and it might fix your problem so I
> > > suggest installing the hotfix and see if that helps.
> > >
> > > Hope that helps.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > Hi Brian,
> > > >
> > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking
> at
> > > when
> > > > it decides that this is the wrong version?
> > > > I guess I can backup all databases and re-install SQL Server if you
> > think
> > > > that should do it. I gave that a thought already, but then it came
to
> > mind
> > > > what if it is something else and I went through that exercise for
> > nothing.
> > > >
> > > > Thanks for your ideas,
> > > >
> > > > Chris.
> > > >
> > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> message
> > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > >
> > > > > --
> > > > > Brian Welcker
> > > > > Group Program Manager
> > > > > SQL Server Reporting Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > >I had the evaluation version running, generated beautiful
reports.
> > > > > > I upgraded my computer from Windows 2000 to 2003 and after a day
> or
> > > two
> > > > > > realized RS would not run, but it could have expired.
> > > > > > I upgraded my RS from the evaluation version to the release
> version,
> > > > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> > > access
> > > > to
> > > > > > the virtual dirs (eventually I hard-coded the Admin
name/password
> in
> > > the
> > > > > > impersonation line in web.config which fixed it) and after that
it
> > > > > > complained about unable to connect to the database. I tried the
> > > rsconfig
> > > > > > utility, then it complained about unable to decrypt a key pair
and
> > it
> > > > > > suggested restoring the default, which of course I did not have
> (it
> > > > really
> > > > > > surprised me there).
> > > > > > I un-installed RS and started a fresh install. Now it says "The
> > > edition
> > > > of
> > > > > > the Report Server Database is not supported on the edition of
SQL
> > > Server
> > > > > > 2000 you have chosen".
> > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
quite
> > > happy
> > > > > > using my SQL Server version (my machine was still Win 2000
> though).
> > > > > > I have been fighting this install for about 7 hours now (on a
> > Sunday),
> > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > I am (or was) going to demo some (beautiful) reports to a client
> > > > tomorrow.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||DAMN, my @.@.version is exactly the same, word for word, except for one word,
where yours says "Enterprise" mine says "Developer". It was installed close
to 3 years ago and I could swear by it that it was the Enterprise. The
evaluation version was happy, what a shame the release is not happy.
Bruce, thanks for your help.
Now I am sitting here with the Enterprise Edition CD in my hand, wondering
what will happen if I install it over the Developers.
I am going to post this question in the SQL Server newsgroup as well, if you
know the answer though, drop it here. Thanks again.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:##mhJXTXEHA.2520@.TK2MSFTNGP12.phx.gbl...
> OK, just in case any of the following might help you. There were several
> things I had to do different under 2003 Server.
> 1. Hotfix 859
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
> 2. Configure server with application server, asp.net (two distinct
> activities). Seems if this was an issue you would get a different error
> message
> 3. I selected built-in account. Two choices: network and system. It
defaults
> to network. I wanted system (which is how my previous configurations were
> configured).
> Other than these my installation went smoothly but then I had a clean
> install of Windows 2003 Advanced Server and SQL Server Enterprise.
> What do you get when you do a select @.@.version? I get this:
> Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
Windows
> NT 5.2 (Build 3790: )
> Bruce L-C
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> > Nope, did not help if this was the correct hotfix, downloaded from
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> >
> > Thanks in any case.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > Hi Bruce,
> > >
> > > I have both SQL Server and RS running on the same 2003 machine,
upgraded
> > > from Win 2000 to 2003.
> > > I am now attempting to locate hotfix 859, if you know the URL drop it
> > here.
> > >
> > > Thanks.
> > >
> > > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > I just looked at my notes from my install on Windows 2003. For
Windows
> > > 2003
> > > > only, you need a hotfix for SQL Server. Seems strange that SQL
Server
> > > needs
> > > > it but only on 2003 but there you are. It is in the installation
notes
> > for
> > > > the install. Besides SP3a you need hotfix 859.
> > > >
> > > > Your situation is a bit different. Only RS is on 2003 and your SQL
> > Server
> > > is
> > > > still on 2000 so it seems like you wouldn't need the hotfix but you
> are
> > > > accessing it from Windows 2003 so maybe that is the key point. In my
> > case
> > > > SQL Server and RS are both on Windows 2003.
> > > >
> > > > In any case, it won't hurt anything and it might fix your problem so
I
> > > > suggest installing the hotfix and see if that helps.
> > > >
> > > > Hope that helps.
> > > >
> > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > > Hi Brian,
> > > > >
> > > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS
looking
> > at
> > > > when
> > > > > it decides that this is the wrong version?
> > > > > I guess I can backup all databases and re-install SQL Server if
you
> > > think
> > > > > that should do it. I gave that a thought already, but then it came
> to
> > > mind
> > > > > what if it is something else and I went through that exercise for
> > > nothing.
> > > > >
> > > > > Thanks for your ideas,
> > > > >
> > > > > Chris.
> > > > >
> > > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> > message
> > > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > > >
> > > > > > --
> > > > > > Brian Welcker
> > > > > > Group Program Manager
> > > > > > SQL Server Reporting Services
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > > rights.
> > > > > >
> > > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> message
> > > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > > >I had the evaluation version running, generated beautiful
> reports.
> > > > > > > I upgraded my computer from Windows 2000 to 2003 and after a
day
> > or
> > > > two
> > > > > > > realized RS would not run, but it could have expired.
> > > > > > > I upgraded my RS from the evaluation version to the release
> > version,
> > > > > > > choosing "upgrade". After the upgrade at first it wouldn't
allow
> > > > access
> > > > > to
> > > > > > > the virtual dirs (eventually I hard-coded the Admin
> name/password
> > in
> > > > the
> > > > > > > impersonation line in web.config which fixed it) and after
that
> it
> > > > > > > complained about unable to connect to the database. I tried
the
> > > > rsconfig
> > > > > > > utility, then it complained about unable to decrypt a key pair
> and
> > > it
> > > > > > > suggested restoring the default, which of course I did not
have
> > (it
> > > > > really
> > > > > > > surprised me there).
> > > > > > > I un-installed RS and started a fresh install. Now it says
"The
> > > > edition
> > > > > of
> > > > > > > the Report Server Database is not supported on the edition of
> SQL
> > > > Server
> > > > > > > 2000 you have chosen".
> > > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
> quite
> > > > happy
> > > > > > > using my SQL Server version (my machine was still Win 2000
> > though).
> > > > > > > I have been fighting this install for about 7 hours now (on a
> > > Sunday),
> > > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > > I am (or was) going to demo some (beautiful) reports to a
client
> > > > > tomorrow.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Ah ha. I was wondering about that but you seemed real certain it was
enterprise. Developer has the same features as enterprise so it is easy to
not know, that is why I had you check. I had developer and went to
enterprise but darn if I can remember if I had to unistall/reinstall or if I
could upgrade. Good news is that the problem is solved. Simple once you know
the solution <g>.
Bruce L-C
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uFvSAFUXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> DAMN, my @.@.version is exactly the same, word for word, except for one
word,
> where yours says "Enterprise" mine says "Developer". It was installed
close
> to 3 years ago and I could swear by it that it was the Enterprise. The
> evaluation version was happy, what a shame the release is not happy.
> Bruce, thanks for your help.
> Now I am sitting here with the Enterprise Edition CD in my hand, wondering
> what will happen if I install it over the Developers.
> I am going to post this question in the SQL Server newsgroup as well, if
you
> know the answer though, drop it here. Thanks again.
>
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:##mhJXTXEHA.2520@.TK2MSFTNGP12.phx.gbl...
> > OK, just in case any of the following might help you. There were several
> > things I had to do different under 2003 Server.
> > 1. Hotfix 859
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
> > 2. Configure server with application server, asp.net (two distinct
> > activities). Seems if this was an issue you would get a different error
> > message
> > 3. I selected built-in account. Two choices: network and system. It
> defaults
> > to network. I wanted system (which is how my previous configurations
were
> > configured).
> >
> > Other than these my installation went smoothly but then I had a clean
> > install of Windows 2003 Advanced Server and SQL Server Enterprise.
> >
> > What do you get when you do a select @.@.version? I get this:
> > Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
> > Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
> Windows
> > NT 5.2 (Build 3790: )
> >
> > Bruce L-C
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> > > Nope, did not help if this was the correct hotfix, downloaded from
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> > >
> > > Thanks in any case.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > Hi Bruce,
> > > >
> > > > I have both SQL Server and RS running on the same 2003 machine,
> upgraded
> > > > from Win 2000 to 2003.
> > > > I am now attempting to locate hotfix 859, if you know the URL drop
it
> > > here.
> > > >
> > > > Thanks.
> > > >
> > > > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > > I just looked at my notes from my install on Windows 2003. For
> Windows
> > > > 2003
> > > > > only, you need a hotfix for SQL Server. Seems strange that SQL
> Server
> > > > needs
> > > > > it but only on 2003 but there you are. It is in the installation
> notes
> > > for
> > > > > the install. Besides SP3a you need hotfix 859.
> > > > >
> > > > > Your situation is a bit different. Only RS is on 2003 and your SQL
> > > Server
> > > > is
> > > > > still on 2000 so it seems like you wouldn't need the hotfix but
you
> > are
> > > > > accessing it from Windows 2003 so maybe that is the key point. In
my
> > > case
> > > > > SQL Server and RS are both on Windows 2003.
> > > > >
> > > > > In any case, it won't hurt anything and it might fix your problem
so
> I
> > > > > suggest installing the hotfix and see if that helps.
> > > > >
> > > > > Hope that helps.
> > > > >
> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > > > Hi Brian,
> > > > > >
> > > > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS
> looking
> > > at
> > > > > when
> > > > > > it decides that this is the wrong version?
> > > > > > I guess I can backup all databases and re-install SQL Server if
> you
> > > > think
> > > > > > that should do it. I gave that a thought already, but then it
came
> > to
> > > > mind
> > > > > > what if it is something else and I went through that exercise
for
> > > > nothing.
> > > > > >
> > > > > > Thanks for your ideas,
> > > > > >
> > > > > > Chris.
> > > > > >
> > > > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> > > message
> > > > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > > > >
> > > > > > > --
> > > > > > > Brian Welcker
> > > > > > > Group Program Manager
> > > > > > > SQL Server Reporting Services
> > > > > > >
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > >
> > > > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > message
> > > > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > > > >I had the evaluation version running, generated beautiful
> > reports.
> > > > > > > > I upgraded my computer from Windows 2000 to 2003 and after a
> day
> > > or
> > > > > two
> > > > > > > > realized RS would not run, but it could have expired.
> > > > > > > > I upgraded my RS from the evaluation version to the release
> > > version,
> > > > > > > > choosing "upgrade". After the upgrade at first it wouldn't
> allow
> > > > > access
> > > > > > to
> > > > > > > > the virtual dirs (eventually I hard-coded the Admin
> > name/password
> > > in
> > > > > the
> > > > > > > > impersonation line in web.config which fixed it) and after
> that
> > it
> > > > > > > > complained about unable to connect to the database. I tried
> the
> > > > > rsconfig
> > > > > > > > utility, then it complained about unable to decrypt a key
pair
> > and
> > > > it
> > > > > > > > suggested restoring the default, which of course I did not
> have
> > > (it
> > > > > > really
> > > > > > > > surprised me there).
> > > > > > > > I un-installed RS and started a fresh install. Now it says
> "The
> > > > > edition
> > > > > > of
> > > > > > > > the Report Server Database is not supported on the edition
of
> > SQL
> > > > > Server
> > > > > > > > 2000 you have chosen".
> > > > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
> > quite
> > > > > happy
> > > > > > > > using my SQL Server version (my machine was still Win 2000
> > > though).
> > > > > > > > I have been fighting this install for about 7 hours now (on
a
> > > > Sunday),
> > > > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > > > I am (or was) going to demo some (beautiful) reports to a
> client
> > > > > > tomorrow.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>