Hi,everyone
I am a newbie to the SQL server.
In my project,I need a SQL server in minimal size to meet the XPE
environment.
How can I get the goal mentioned above?
Where can I find the technical articles or files needed for building minimal
SQL?
Any hints are appreciated!
Best regards!
MerryMerry.Win wrote:
> Hi,everyone
> I am a newbie to the SQL server.
> In my project,I need a SQL server in minimal size to meet the XPE
> environment.
> How can I get the goal mentioned above?
> Where can I find the technical articles or files needed for building minimal
> SQL?
> Any hints are appreciated!
> Best regards!
> Merry`
A good place to start is the SQL Server Home Page:
http://www.microsoft.com/sql/default.mspx
Check out SQL Server Mobile:
http://www.microsoft.com/sql/editions/sqlmobile/default.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts
Wednesday, March 28, 2012
Monday, March 19, 2012
Help : I Can't Re-installed RS !
I uninstalled Reporting Services SP1 from the development environment.
My Database is on a distant Server.
I want to re-install Reporting Service and I have this message when I select
my Report Server Database (the same as before the uninstal) : "The Report
Server Database is a different version and cannot be used for this
installation."
Can you help me ?First you need to install RS and point to an new DB. After the install
upgrade RS to SP1. Once this is done you will need to run RSConfig to point
to the old DB. If you saved off your Symmetric key you will want to reapply
it using rskeymgmt.exe. If you did not you will need to run
rskeymgmt.exe -d. Doing this will delete all the encrypted content, meaning
you will have to reenter all of your report credentials.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karine" <Karine@.discussions.microsoft.com> wrote in message
news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> I uninstalled Reporting Services SP1 from the development environment.
> My Database is on a distant Server.
> I want to re-install Reporting Service and I have this message when I
select
> my Report Server Database (the same as before the uninstal) : "The Report
> Server Database is a different version and cannot be used for this
> installation."
> Can you help me ?
>
>|||Karine,
I have a step-by-step document that you may find useful:
http://prologika.com/blog/archive/2004/08/20/161.aspx
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com : http://tinyurl.com/3l49j
Home page and blog: http://www.prologika.com/
----
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:%23ymuy74iEHA.1040@.TK2MSFTNGP09.phx.gbl...
> First you need to install RS and point to an new DB. After the install
> upgrade RS to SP1. Once this is done you will need to run RSConfig to
point
> to the old DB. If you saved off your Symmetric key you will want to
reapply
> it using rskeymgmt.exe. If you did not you will need to run
> rskeymgmt.exe -d. Doing this will delete all the encrypted content,
meaning
> you will have to reenter all of your report credentials.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Karine" <Karine@.discussions.microsoft.com> wrote in message
> news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> > I uninstalled Reporting Services SP1 from the development environment.
> > My Database is on a distant Server.
> > I want to re-install Reporting Service and I have this message when I
> select
> > my Report Server Database (the same as before the uninstal) : "The
Report
> > Server Database is a different version and cannot be used for this
> > installation."
> >
> > Can you help me ?
> >
> >
> >
>|||Thanks.
I don't use your method because RS has allready uninstalled and so I can't
save my key.
I delete from my SQL Server the DataBase Report and the database
ReportserverTempDB. I run RS install, I select my SQL Server and I can
continu running the install.
I can deploy my reports so now ... all is good ...
"Teo Lachev" wrote:
> Karine,
> I have a step-by-step document that you may find useful:
> http://prologika.com/blog/archive/2004/08/20/161.aspx
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com : http://tinyurl.com/3l49j
> Home page and blog: http://www.prologika.com/
> ----
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:%23ymuy74iEHA.1040@.TK2MSFTNGP09.phx.gbl...
> > First you need to install RS and point to an new DB. After the install
> > upgrade RS to SP1. Once this is done you will need to run RSConfig to
> point
> > to the old DB. If you saved off your Symmetric key you will want to
> reapply
> > it using rskeymgmt.exe. If you did not you will need to run
> > rskeymgmt.exe -d. Doing this will delete all the encrypted content,
> meaning
> > you will have to reenter all of your report credentials.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Karine" <Karine@.discussions.microsoft.com> wrote in message
> > news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> > > I uninstalled Reporting Services SP1 from the development environment.
> > > My Database is on a distant Server.
> > > I want to re-install Reporting Service and I have this message when I
> > select
> > > my Report Server Database (the same as before the uninstal) : "The
> Report
> > > Server Database is a different version and cannot be used for this
> > > installation."
> > >
> > > Can you help me ?
> > >
> > >
> > >
> >
> >
>
>
My Database is on a distant Server.
I want to re-install Reporting Service and I have this message when I select
my Report Server Database (the same as before the uninstal) : "The Report
Server Database is a different version and cannot be used for this
installation."
Can you help me ?First you need to install RS and point to an new DB. After the install
upgrade RS to SP1. Once this is done you will need to run RSConfig to point
to the old DB. If you saved off your Symmetric key you will want to reapply
it using rskeymgmt.exe. If you did not you will need to run
rskeymgmt.exe -d. Doing this will delete all the encrypted content, meaning
you will have to reenter all of your report credentials.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karine" <Karine@.discussions.microsoft.com> wrote in message
news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> I uninstalled Reporting Services SP1 from the development environment.
> My Database is on a distant Server.
> I want to re-install Reporting Service and I have this message when I
select
> my Report Server Database (the same as before the uninstal) : "The Report
> Server Database is a different version and cannot be used for this
> installation."
> Can you help me ?
>
>|||Karine,
I have a step-by-step document that you may find useful:
http://prologika.com/blog/archive/2004/08/20/161.aspx
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com : http://tinyurl.com/3l49j
Home page and blog: http://www.prologika.com/
----
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:%23ymuy74iEHA.1040@.TK2MSFTNGP09.phx.gbl...
> First you need to install RS and point to an new DB. After the install
> upgrade RS to SP1. Once this is done you will need to run RSConfig to
point
> to the old DB. If you saved off your Symmetric key you will want to
reapply
> it using rskeymgmt.exe. If you did not you will need to run
> rskeymgmt.exe -d. Doing this will delete all the encrypted content,
meaning
> you will have to reenter all of your report credentials.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Karine" <Karine@.discussions.microsoft.com> wrote in message
> news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> > I uninstalled Reporting Services SP1 from the development environment.
> > My Database is on a distant Server.
> > I want to re-install Reporting Service and I have this message when I
> select
> > my Report Server Database (the same as before the uninstal) : "The
Report
> > Server Database is a different version and cannot be used for this
> > installation."
> >
> > Can you help me ?
> >
> >
> >
>|||Thanks.
I don't use your method because RS has allready uninstalled and so I can't
save my key.
I delete from my SQL Server the DataBase Report and the database
ReportserverTempDB. I run RS install, I select my SQL Server and I can
continu running the install.
I can deploy my reports so now ... all is good ...
"Teo Lachev" wrote:
> Karine,
> I have a step-by-step document that you may find useful:
> http://prologika.com/blog/archive/2004/08/20/161.aspx
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com : http://tinyurl.com/3l49j
> Home page and blog: http://www.prologika.com/
> ----
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:%23ymuy74iEHA.1040@.TK2MSFTNGP09.phx.gbl...
> > First you need to install RS and point to an new DB. After the install
> > upgrade RS to SP1. Once this is done you will need to run RSConfig to
> point
> > to the old DB. If you saved off your Symmetric key you will want to
> reapply
> > it using rskeymgmt.exe. If you did not you will need to run
> > rskeymgmt.exe -d. Doing this will delete all the encrypted content,
> meaning
> > you will have to reenter all of your report credentials.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Karine" <Karine@.discussions.microsoft.com> wrote in message
> > news:074B3037-396E-45D3-B245-1E6798FA1ED1@.microsoft.com...
> > > I uninstalled Reporting Services SP1 from the development environment.
> > > My Database is on a distant Server.
> > > I want to re-install Reporting Service and I have this message when I
> > select
> > > my Report Server Database (the same as before the uninstal) : "The
> Report
> > > Server Database is a different version and cannot be used for this
> > > installation."
> > >
> > > Can you help me ?
> > >
> > >
> > >
> >
> >
>
>
Help , Several Connections , Port : 1433
Environment:
SQL Server Standard Edition
Microsoft Windows NT - 5.2 (3790)
8.00.760 (SP3)
DOS Command : netstat -n . Results as follows
Find several connections about port 1433
Who can help me ? How to resolve the problem ?
Please , thank you .
.
.
.
.
TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
.
.
.Hi
You may want to do a netstat -n -o to find what process is trying to connect
to the servers. It sounds like some process is browsing the network for
servers and port 1433 is open on the remote servers.
John
"test" wrote:
>
> Environment:
> SQL Server Standard Edition
> Microsoft Windows NT - 5.2 (3790)
> 8.00.760 (SP3)
>
> DOS Command : netstat -n . Results as follows
> Find several connections about port 1433
>
> Who can help me ? How to resolve the problem ?
> Please , thank you .
>
> ..
> ..
> ..
> ..
> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
> ..
> ..
> ..
>
>
>|||netstat -ano , find : SID = 5664
tasklist , find : 5664 = syswinxp.exe
"syswinxp.exe" maybe a trojan .
Thanks for your help .
"John Bell" <jbellnewsposts@.hotmail.com> ¼¶¼g©ó¶l¥ó·s»D:46CCFA26-F813-4A39-8EF9-EF517084BB6E@.microsoft.com...
> Hi
> You may want to do a netstat -n -o to find what process is trying to
> connect
> to the servers. It sounds like some process is browsing the network for
> servers and port 1433 is open on the remote servers.
> John
> "test" wrote:
>>
>> Environment:
>> SQL Server Standard Edition
>> Microsoft Windows NT - 5.2 (3790)
>> 8.00.760 (SP3)
>>
>> DOS Command : netstat -n . Results as follows
>> Find several connections about port 1433
>>
>> Who can help me ? How to resolve the problem ?
>> Please , thank you .
>>
>> ..
>> ..
>> ..
>> ..
>> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
>> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
>> ..
>> ..
>> ..
>>
>>
>>
SQL Server Standard Edition
Microsoft Windows NT - 5.2 (3790)
8.00.760 (SP3)
DOS Command : netstat -n . Results as follows
Find several connections about port 1433
Who can help me ? How to resolve the problem ?
Please , thank you .
.
.
.
.
TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
.
.
.Hi
You may want to do a netstat -n -o to find what process is trying to connect
to the servers. It sounds like some process is browsing the network for
servers and port 1433 is open on the remote servers.
John
"test" wrote:
>
> Environment:
> SQL Server Standard Edition
> Microsoft Windows NT - 5.2 (3790)
> 8.00.760 (SP3)
>
> DOS Command : netstat -n . Results as follows
> Find several connections about port 1433
>
> Who can help me ? How to resolve the problem ?
> Please , thank you .
>
> ..
> ..
> ..
> ..
> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
> ..
> ..
> ..
>
>
>|||netstat -ano , find : SID = 5664
tasklist , find : 5664 = syswinxp.exe
"syswinxp.exe" maybe a trojan .
Thanks for your help .
"John Bell" <jbellnewsposts@.hotmail.com> ¼¶¼g©ó¶l¥ó·s»D:46CCFA26-F813-4A39-8EF9-EF517084BB6E@.microsoft.com...
> Hi
> You may want to do a netstat -n -o to find what process is trying to
> connect
> to the servers. It sounds like some process is browsing the network for
> servers and port 1433 is open on the remote servers.
> John
> "test" wrote:
>>
>> Environment:
>> SQL Server Standard Edition
>> Microsoft Windows NT - 5.2 (3790)
>> 8.00.760 (SP3)
>>
>> DOS Command : netstat -n . Results as follows
>> Find several connections about port 1433
>>
>> Who can help me ? How to resolve the problem ?
>> Please , thank you .
>>
>> ..
>> ..
>> ..
>> ..
>> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
>> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
>> ..
>> ..
>> ..
>>
>>
>>
Friday, March 9, 2012
HELP - SRS for Developer Ed installed instead of for Standard Ed.
I have been getting ready to finally put into my company's Production
Environment all the reports I have been developing in our Test Environment.
The Test Environment is SQL 2000 Developer Edition, and SRS was installed via
the CD that came in the box - I read that it said "For SQL Server 2000
Developer Edition only."
The decision was made that we did not need Enterprise Edition features, so a
Standard Edition SQL Server 2000 license was purchased and installed, be my
supervisor. He then used the SAME CD for SRS to install that I did. His
logic was "These Microsoft disks can detect what version of SQL Server is
running, and only install the components for the version detected."
I was unaware of this and have been loading the new server with reports and
running the Report Snapshots for the LONG RUNNING REPORTS, and setting up the
Shared Schedules and Permissions for the 125+ reports. I was about to start
creating the Manual Subscriptions for the various reports when I noticed the
'New Data-driven Subscription' button, and then realized what happened.
I would like to avoid redoing work, if possible. Is there a way to
over-install the Standard Edition Version of SQL Reporting Services on top of
the Developer Edition, so I don't have to re-setup everything? Is there a
way to downgrade/upgrade Editions without having to re-build the site?It is possible to do this. Before starting anything, of course, backup your
databases and the report server encryption key (see help topics on backing
up report server).
1. Uninstall the developer edition (this will not remove the report server
databases)
2. Install the standard edition. When asked for a database, use a new one.
Do NOT use the one from the developer install
3. After installation is complete, run rsconfig to point the new
installation at the old database
4. Delete the temporary database that you created as part of step 2.
If you created any data driven subscriptions, they will no longer run with
standard installed.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> I have been getting ready to finally put into my company's Production
> Environment all the reports I have been developing in our Test
Environment.
> The Test Environment is SQL 2000 Developer Edition, and SRS was installed
via
> the CD that came in the box - I read that it said "For SQL Server 2000
> Developer Edition only."
> The decision was made that we did not need Enterprise Edition features, so
a
> Standard Edition SQL Server 2000 license was purchased and installed, be
my
> supervisor. He then used the SAME CD for SRS to install that I did. His
> logic was "These Microsoft disks can detect what version of SQL Server is
> running, and only install the components for the version detected."
> I was unaware of this and have been loading the new server with reports
and
> running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
the
> Shared Schedules and Permissions for the 125+ reports. I was about to
start
> creating the Manual Subscriptions for the various reports when I noticed
the
> 'New Data-driven Subscription' button, and then realized what happened.
> I would like to avoid redoing work, if possible. Is there a way to
> over-install the Standard Edition Version of SQL Reporting Services on top
of
> the Developer Edition, so I don't have to re-setup everything? Is there a
> way to downgrade/upgrade Editions without having to re-build the site?|||I followed your instructions, except I hadn't yet deleted the 'temp' database
yet - didn't want to get rid of it until I knew things are working. They
aren't. I get the following error now:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Online help says the following:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
I am not using a Web Farm. I have one server that houses the source
databases for my company, and this SRS server that hosts the IIS website and
the SRS databases, both with standard edition. The RDS file points to the
source database server. Is this what SRS consideres a Web Farm? According
to your schemeatics on Reporting Services I have a proper license for both
servers.
"Brian Hartman [MSFT]" wrote:
> It is possible to do this. Before starting anything, of course, backup your
> databases and the report server encryption key (see help topics on backing
> up report server).
> 1. Uninstall the developer edition (this will not remove the report server
> databases)
> 2. Install the standard edition. When asked for a database, use a new one.
> Do NOT use the one from the developer install
> 3. After installation is complete, run rsconfig to point the new
> installation at the old database
> 4. Delete the temporary database that you created as part of step 2.
> If you created any data driven subscriptions, they will no longer run with
> standard installed.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > I have been getting ready to finally put into my company's Production
> > Environment all the reports I have been developing in our Test
> Environment.
> > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> via
> > the CD that came in the box - I read that it said "For SQL Server 2000
> > Developer Edition only."
> >
> > The decision was made that we did not need Enterprise Edition features, so
> a
> > Standard Edition SQL Server 2000 license was purchased and installed, be
> my
> > supervisor. He then used the SAME CD for SRS to install that I did. His
> > logic was "These Microsoft disks can detect what version of SQL Server is
> > running, and only install the components for the version detected."
> >
> > I was unaware of this and have been loading the new server with reports
> and
> > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> the
> > Shared Schedules and Permissions for the 125+ reports. I was about to
> start
> > creating the Manual Subscriptions for the various reports when I noticed
> the
> > 'New Data-driven Subscription' button, and then realized what happened.
> >
> > I would like to avoid redoing work, if possible. Is there a way to
> > over-install the Standard Edition Version of SQL Reporting Services on top
> of
> > the Developer Edition, so I don't have to re-setup everything? Is there a
> > way to downgrade/upgrade Editions without having to re-build the site?
>
>|||I went ahead and deleted the new 'temp' databases after running rsconfig
again. I still get the same errors listed below.
"Rob 'Spike' Stevens" wrote:
> I followed your instructions, except I hadn't yet deleted the 'temp' database
> yet - didn't want to get rid of it until I knew things are working. They
> aren't. I get the following error now:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Online help says the following:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
> I am not using a Web Farm. I have one server that houses the source
> databases for my company, and this SRS server that hosts the IIS website and
> the SRS databases, both with standard edition. The RDS file points to the
> source database server. Is this what SRS consideres a Web Farm? According
> to your schemeatics on Reporting Services I have a proper license for both
> servers.
> "Brian Hartman [MSFT]" wrote:
> > It is possible to do this. Before starting anything, of course, backup your
> > databases and the report server encryption key (see help topics on backing
> > up report server).
> >
> > 1. Uninstall the developer edition (this will not remove the report server
> > databases)
> > 2. Install the standard edition. When asked for a database, use a new one.
> > Do NOT use the one from the developer install
> > 3. After installation is complete, run rsconfig to point the new
> > installation at the old database
> > 4. Delete the temporary database that you created as part of step 2.
> >
> > If you created any data driven subscriptions, they will no longer run with
> > standard installed.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > I have been getting ready to finally put into my company's Production
> > > Environment all the reports I have been developing in our Test
> > Environment.
> > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > via
> > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > Developer Edition only."
> > >
> > > The decision was made that we did not need Enterprise Edition features, so
> > a
> > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > my
> > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > running, and only install the components for the version detected."
> > >
> > > I was unaware of this and have been loading the new server with reports
> > and
> > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > the
> > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > start
> > > creating the Manual Subscriptions for the various reports when I noticed
> > the
> > > 'New Data-driven Subscription' button, and then realized what happened.
> > >
> > > I would like to avoid redoing work, if possible. Is there a way to
> > > over-install the Standard Edition Version of SQL Reporting Services on top
> > of
> > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > way to downgrade/upgrade Editions without having to re-build the site?
> >
> >
> >|||Also, Iâ'm finding this error message in the application log:
Reporting Services components from different editions cannot be used together.
"Rob 'Spike' Stevens" wrote:
> I went ahead and deleted the new 'temp' databases after running rsconfig
> again. I still get the same errors listed below.
> "Rob 'Spike' Stevens" wrote:
> > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > yet - didn't want to get rid of it until I knew things are working. They
> > aren't. I get the following error now:
> >
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Online help says the following:
> > You cannot use the Standard edition of Reporting Services to deploy multiple
> > report servers in a Web farms.
> >
> > I am not using a Web Farm. I have one server that houses the source
> > databases for my company, and this SRS server that hosts the IIS website and
> > the SRS databases, both with standard edition. The RDS file points to the
> > source database server. Is this what SRS consideres a Web Farm? According
> > to your schemeatics on Reporting Services I have a proper license for both
> > servers.
> >
> > "Brian Hartman [MSFT]" wrote:
> >
> > > It is possible to do this. Before starting anything, of course, backup your
> > > databases and the report server encryption key (see help topics on backing
> > > up report server).
> > >
> > > 1. Uninstall the developer edition (this will not remove the report server
> > > databases)
> > > 2. Install the standard edition. When asked for a database, use a new one.
> > > Do NOT use the one from the developer install
> > > 3. After installation is complete, run rsconfig to point the new
> > > installation at the old database
> > > 4. Delete the temporary database that you created as part of step 2.
> > >
> > > If you created any data driven subscriptions, they will no longer run with
> > > standard installed.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights
> > >
> > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > I have been getting ready to finally put into my company's Production
> > > > Environment all the reports I have been developing in our Test
> > > Environment.
> > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > via
> > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > Developer Edition only."
> > > >
> > > > The decision was made that we did not need Enterprise Edition features, so
> > > a
> > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > my
> > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > running, and only install the components for the version detected."
> > > >
> > > > I was unaware of this and have been loading the new server with reports
> > > and
> > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > the
> > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > start
> > > > creating the Manual Subscriptions for the various reports when I noticed
> > > the
> > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > >
> > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > of
> > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > way to downgrade/upgrade Editions without having to re-build the site?
> > >
> > >
> > >|||I was able to find a solution. Thanks for the help you did provide.
"Rob 'Spike' Stevens" wrote:
> Also, Iâ'm finding this error message in the application log:
> Reporting Services components from different editions cannot be used together.
>
> "Rob 'Spike' Stevens" wrote:
> > I went ahead and deleted the new 'temp' databases after running rsconfig
> > again. I still get the same errors listed below.
> >
> > "Rob 'Spike' Stevens" wrote:
> >
> > > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > > yet - didn't want to get rid of it until I knew things are working. They
> > > aren't. I get the following error now:
> > >
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Online help says the following:
> > > You cannot use the Standard edition of Reporting Services to deploy multiple
> > > report servers in a Web farms.
> > >
> > > I am not using a Web Farm. I have one server that houses the source
> > > databases for my company, and this SRS server that hosts the IIS website and
> > > the SRS databases, both with standard edition. The RDS file points to the
> > > source database server. Is this what SRS consideres a Web Farm? According
> > > to your schemeatics on Reporting Services I have a proper license for both
> > > servers.
> > >
> > > "Brian Hartman [MSFT]" wrote:
> > >
> > > > It is possible to do this. Before starting anything, of course, backup your
> > > > databases and the report server encryption key (see help topics on backing
> > > > up report server).
> > > >
> > > > 1. Uninstall the developer edition (this will not remove the report server
> > > > databases)
> > > > 2. Install the standard edition. When asked for a database, use a new one.
> > > > Do NOT use the one from the developer install
> > > > 3. After installation is complete, run rsconfig to point the new
> > > > installation at the old database
> > > > 4. Delete the temporary database that you created as part of step 2.
> > > >
> > > > If you created any data driven subscriptions, they will no longer run with
> > > > standard installed.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no rights
> > > >
> > > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > > I have been getting ready to finally put into my company's Production
> > > > > Environment all the reports I have been developing in our Test
> > > > Environment.
> > > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > > via
> > > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > > Developer Edition only."
> > > > >
> > > > > The decision was made that we did not need Enterprise Edition features, so
> > > > a
> > > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > > my
> > > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > > running, and only install the components for the version detected."
> > > > >
> > > > > I was unaware of this and have been loading the new server with reports
> > > > and
> > > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > > the
> > > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > > start
> > > > > creating the Manual Subscriptions for the various reports when I noticed
> > > > the
> > > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > > >
> > > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > > of
> > > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > > way to downgrade/upgrade Editions without having to re-build the site?
> > > >
> > > >
> > > >
Environment all the reports I have been developing in our Test Environment.
The Test Environment is SQL 2000 Developer Edition, and SRS was installed via
the CD that came in the box - I read that it said "For SQL Server 2000
Developer Edition only."
The decision was made that we did not need Enterprise Edition features, so a
Standard Edition SQL Server 2000 license was purchased and installed, be my
supervisor. He then used the SAME CD for SRS to install that I did. His
logic was "These Microsoft disks can detect what version of SQL Server is
running, and only install the components for the version detected."
I was unaware of this and have been loading the new server with reports and
running the Report Snapshots for the LONG RUNNING REPORTS, and setting up the
Shared Schedules and Permissions for the 125+ reports. I was about to start
creating the Manual Subscriptions for the various reports when I noticed the
'New Data-driven Subscription' button, and then realized what happened.
I would like to avoid redoing work, if possible. Is there a way to
over-install the Standard Edition Version of SQL Reporting Services on top of
the Developer Edition, so I don't have to re-setup everything? Is there a
way to downgrade/upgrade Editions without having to re-build the site?It is possible to do this. Before starting anything, of course, backup your
databases and the report server encryption key (see help topics on backing
up report server).
1. Uninstall the developer edition (this will not remove the report server
databases)
2. Install the standard edition. When asked for a database, use a new one.
Do NOT use the one from the developer install
3. After installation is complete, run rsconfig to point the new
installation at the old database
4. Delete the temporary database that you created as part of step 2.
If you created any data driven subscriptions, they will no longer run with
standard installed.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> I have been getting ready to finally put into my company's Production
> Environment all the reports I have been developing in our Test
Environment.
> The Test Environment is SQL 2000 Developer Edition, and SRS was installed
via
> the CD that came in the box - I read that it said "For SQL Server 2000
> Developer Edition only."
> The decision was made that we did not need Enterprise Edition features, so
a
> Standard Edition SQL Server 2000 license was purchased and installed, be
my
> supervisor. He then used the SAME CD for SRS to install that I did. His
> logic was "These Microsoft disks can detect what version of SQL Server is
> running, and only install the components for the version detected."
> I was unaware of this and have been loading the new server with reports
and
> running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
the
> Shared Schedules and Permissions for the 125+ reports. I was about to
start
> creating the Manual Subscriptions for the various reports when I noticed
the
> 'New Data-driven Subscription' button, and then realized what happened.
> I would like to avoid redoing work, if possible. Is there a way to
> over-install the Standard Edition Version of SQL Reporting Services on top
of
> the Developer Edition, so I don't have to re-setup everything? Is there a
> way to downgrade/upgrade Editions without having to re-build the site?|||I followed your instructions, except I hadn't yet deleted the 'temp' database
yet - didn't want to get rid of it until I knew things are working. They
aren't. I get the following error now:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Online help says the following:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
I am not using a Web Farm. I have one server that houses the source
databases for my company, and this SRS server that hosts the IIS website and
the SRS databases, both with standard edition. The RDS file points to the
source database server. Is this what SRS consideres a Web Farm? According
to your schemeatics on Reporting Services I have a proper license for both
servers.
"Brian Hartman [MSFT]" wrote:
> It is possible to do this. Before starting anything, of course, backup your
> databases and the report server encryption key (see help topics on backing
> up report server).
> 1. Uninstall the developer edition (this will not remove the report server
> databases)
> 2. Install the standard edition. When asked for a database, use a new one.
> Do NOT use the one from the developer install
> 3. After installation is complete, run rsconfig to point the new
> installation at the old database
> 4. Delete the temporary database that you created as part of step 2.
> If you created any data driven subscriptions, they will no longer run with
> standard installed.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > I have been getting ready to finally put into my company's Production
> > Environment all the reports I have been developing in our Test
> Environment.
> > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> via
> > the CD that came in the box - I read that it said "For SQL Server 2000
> > Developer Edition only."
> >
> > The decision was made that we did not need Enterprise Edition features, so
> a
> > Standard Edition SQL Server 2000 license was purchased and installed, be
> my
> > supervisor. He then used the SAME CD for SRS to install that I did. His
> > logic was "These Microsoft disks can detect what version of SQL Server is
> > running, and only install the components for the version detected."
> >
> > I was unaware of this and have been loading the new server with reports
> and
> > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> the
> > Shared Schedules and Permissions for the 125+ reports. I was about to
> start
> > creating the Manual Subscriptions for the various reports when I noticed
> the
> > 'New Data-driven Subscription' button, and then realized what happened.
> >
> > I would like to avoid redoing work, if possible. Is there a way to
> > over-install the Standard Edition Version of SQL Reporting Services on top
> of
> > the Developer Edition, so I don't have to re-setup everything? Is there a
> > way to downgrade/upgrade Editions without having to re-build the site?
>
>|||I went ahead and deleted the new 'temp' databases after running rsconfig
again. I still get the same errors listed below.
"Rob 'Spike' Stevens" wrote:
> I followed your instructions, except I hadn't yet deleted the 'temp' database
> yet - didn't want to get rid of it until I knew things are working. They
> aren't. I get the following error now:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Online help says the following:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
> I am not using a Web Farm. I have one server that houses the source
> databases for my company, and this SRS server that hosts the IIS website and
> the SRS databases, both with standard edition. The RDS file points to the
> source database server. Is this what SRS consideres a Web Farm? According
> to your schemeatics on Reporting Services I have a proper license for both
> servers.
> "Brian Hartman [MSFT]" wrote:
> > It is possible to do this. Before starting anything, of course, backup your
> > databases and the report server encryption key (see help topics on backing
> > up report server).
> >
> > 1. Uninstall the developer edition (this will not remove the report server
> > databases)
> > 2. Install the standard edition. When asked for a database, use a new one.
> > Do NOT use the one from the developer install
> > 3. After installation is complete, run rsconfig to point the new
> > installation at the old database
> > 4. Delete the temporary database that you created as part of step 2.
> >
> > If you created any data driven subscriptions, they will no longer run with
> > standard installed.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > I have been getting ready to finally put into my company's Production
> > > Environment all the reports I have been developing in our Test
> > Environment.
> > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > via
> > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > Developer Edition only."
> > >
> > > The decision was made that we did not need Enterprise Edition features, so
> > a
> > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > my
> > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > running, and only install the components for the version detected."
> > >
> > > I was unaware of this and have been loading the new server with reports
> > and
> > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > the
> > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > start
> > > creating the Manual Subscriptions for the various reports when I noticed
> > the
> > > 'New Data-driven Subscription' button, and then realized what happened.
> > >
> > > I would like to avoid redoing work, if possible. Is there a way to
> > > over-install the Standard Edition Version of SQL Reporting Services on top
> > of
> > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > way to downgrade/upgrade Editions without having to re-build the site?
> >
> >
> >|||Also, Iâ'm finding this error message in the application log:
Reporting Services components from different editions cannot be used together.
"Rob 'Spike' Stevens" wrote:
> I went ahead and deleted the new 'temp' databases after running rsconfig
> again. I still get the same errors listed below.
> "Rob 'Spike' Stevens" wrote:
> > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > yet - didn't want to get rid of it until I knew things are working. They
> > aren't. I get the following error now:
> >
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Online help says the following:
> > You cannot use the Standard edition of Reporting Services to deploy multiple
> > report servers in a Web farms.
> >
> > I am not using a Web Farm. I have one server that houses the source
> > databases for my company, and this SRS server that hosts the IIS website and
> > the SRS databases, both with standard edition. The RDS file points to the
> > source database server. Is this what SRS consideres a Web Farm? According
> > to your schemeatics on Reporting Services I have a proper license for both
> > servers.
> >
> > "Brian Hartman [MSFT]" wrote:
> >
> > > It is possible to do this. Before starting anything, of course, backup your
> > > databases and the report server encryption key (see help topics on backing
> > > up report server).
> > >
> > > 1. Uninstall the developer edition (this will not remove the report server
> > > databases)
> > > 2. Install the standard edition. When asked for a database, use a new one.
> > > Do NOT use the one from the developer install
> > > 3. After installation is complete, run rsconfig to point the new
> > > installation at the old database
> > > 4. Delete the temporary database that you created as part of step 2.
> > >
> > > If you created any data driven subscriptions, they will no longer run with
> > > standard installed.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights
> > >
> > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > I have been getting ready to finally put into my company's Production
> > > > Environment all the reports I have been developing in our Test
> > > Environment.
> > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > via
> > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > Developer Edition only."
> > > >
> > > > The decision was made that we did not need Enterprise Edition features, so
> > > a
> > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > my
> > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > running, and only install the components for the version detected."
> > > >
> > > > I was unaware of this and have been loading the new server with reports
> > > and
> > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > the
> > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > start
> > > > creating the Manual Subscriptions for the various reports when I noticed
> > > the
> > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > >
> > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > of
> > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > way to downgrade/upgrade Editions without having to re-build the site?
> > >
> > >
> > >|||I was able to find a solution. Thanks for the help you did provide.
"Rob 'Spike' Stevens" wrote:
> Also, Iâ'm finding this error message in the application log:
> Reporting Services components from different editions cannot be used together.
>
> "Rob 'Spike' Stevens" wrote:
> > I went ahead and deleted the new 'temp' databases after running rsconfig
> > again. I still get the same errors listed below.
> >
> > "Rob 'Spike' Stevens" wrote:
> >
> > > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > > yet - didn't want to get rid of it until I knew things are working. They
> > > aren't. I get the following error now:
> > >
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Online help says the following:
> > > You cannot use the Standard edition of Reporting Services to deploy multiple
> > > report servers in a Web farms.
> > >
> > > I am not using a Web Farm. I have one server that houses the source
> > > databases for my company, and this SRS server that hosts the IIS website and
> > > the SRS databases, both with standard edition. The RDS file points to the
> > > source database server. Is this what SRS consideres a Web Farm? According
> > > to your schemeatics on Reporting Services I have a proper license for both
> > > servers.
> > >
> > > "Brian Hartman [MSFT]" wrote:
> > >
> > > > It is possible to do this. Before starting anything, of course, backup your
> > > > databases and the report server encryption key (see help topics on backing
> > > > up report server).
> > > >
> > > > 1. Uninstall the developer edition (this will not remove the report server
> > > > databases)
> > > > 2. Install the standard edition. When asked for a database, use a new one.
> > > > Do NOT use the one from the developer install
> > > > 3. After installation is complete, run rsconfig to point the new
> > > > installation at the old database
> > > > 4. Delete the temporary database that you created as part of step 2.
> > > >
> > > > If you created any data driven subscriptions, they will no longer run with
> > > > standard installed.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no rights
> > > >
> > > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > > I have been getting ready to finally put into my company's Production
> > > > > Environment all the reports I have been developing in our Test
> > > > Environment.
> > > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > > via
> > > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > > Developer Edition only."
> > > > >
> > > > > The decision was made that we did not need Enterprise Edition features, so
> > > > a
> > > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > > my
> > > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > > running, and only install the components for the version detected."
> > > > >
> > > > > I was unaware of this and have been loading the new server with reports
> > > > and
> > > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > > the
> > > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > > start
> > > > > creating the Manual Subscriptions for the various reports when I noticed
> > > > the
> > > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > > >
> > > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > > of
> > > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > > way to downgrade/upgrade Editions without having to re-build the site?
> > > >
> > > >
> > > >
Subscribe to:
Posts (Atom)