Showing posts with label ssrs. Show all posts
Showing posts with label ssrs. Show all posts

Monday, March 26, 2012

Installing and Configuring SSRS on Vista

This config stuff is getting a little bit ridiculous. I already had a
default instance of SQL Server 2005 SP2 down on the machine. I got all of
the IIS components installed on Vista in order to get an installation of
SSRS to go through. There was no installation option for configuration.
After installing, I applied SP2. Then I opened up IIS Manager and set the
app pool to Classic ASP.NET. When I launch RS Configuration, I select my
default instance, click connect, it it promptly blows up with the following
error:
YES, the SQL Server instance is started. If I click continue, it constantly
throws WMI errors. I managed to get to the database configuration and
create the reportserver and reportservertemp databases. Doing anything to
the virtual directories causes RS Configuration to simply abort and shut
down. I obviously can't get to either the reports or reportserver website,
because the config tool crashes and won't setup the virtual directories in
the config. (If I look in IIS admin, neither of the sites has a virtual
directory configured and the connection string is set to SQLEXPRESS and NOT
the default instance that I have on the machine.) This is getting
ridiculous. Does anyone have a manual config checklist which does NOT
require this Config tool, because the RS Config simply does NOT work.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
ReportServicesConfigUI.WMIProvider.WMIProviderException: A WMI error has
occurred and no additional error information is available. -->
System.Runtime.InteropServices.COMException (0x8000000A)
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.InvokeMethod(String methodName,
ManagementBaseObject inParameters, InvokeMethodOptions options)
at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
-- End of inner exception stack trace --
at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
at
ReportServicesConfigUI.WMIProvider.RSInstance.get_DelayLoadConfiguration()
at
ReportServicesConfigUI.WMIProvider.RSInstance.get_Item(ConfigurationItemNames
itemName)
at ReportServicesConfigUI.ConfigurationManager.ResetStepStatus()
at ReportServicesConfigUI.ConfigurationManager.ChangeMachine()
at ReportServicesConfigUI.ConfigurationManager.LaunchDialog()
at ReportServicesConfigUI.ConfigurationManager.OnActivated(EventArgs e)
at System.Windows.Forms.Form.set_Active(Boolean value)
at System.Windows.Forms.Form.WmActivate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
---
RSConfigTool
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/RSConfigTool.exe
---
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
---
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
---
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
---
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
---
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
---
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
--
Mike - mhotek@.mssqlserver.com
President FilAm Software Technology, Inc
Vice-President MHS Enterprises, Inc
MCITP - SQL Server DBA, MCT
http://www.mssqlserver.com
http://www.mhse.netI hacked my way around and manually added the virtual directory within IIS
Admin for the Reports website. I then hacked and manually input the
<ReportServerVirtualDirectory> within the RSWebApplication.config file. It
at least finds the website now when I go to http://<machine>/reports.
However, it fails on the connection attempt with the VERY unhelpful error
message of:
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version.
So, since I know that it is all compatible, I'm assuming that I missed
something when I manually created the connection string in IIS Admin. Does
anyone have a sample connection string from a working SSRS configuration?
--
Mike - mhotek@.mssqlserver.com
President FilAm Software Technology, Inc
Vice-President MHS Enterprises, Inc
MCITP - SQL Server DBA, MCT
http://www.mssqlserver.com
http://www.mhse.net
"Michael Hotek" <mike.hotek@.mhse.net> wrote in message
news:2D164AE8-B582-4478-8D92-96C284E996DA@.microsoft.com...
> This config stuff is getting a little bit ridiculous. I already had a
> default instance of SQL Server 2005 SP2 down on the machine. I got all of
> the IIS components installed on Vista in order to get an installation of
> SSRS to go through. There was no installation option for configuration.
> After installing, I applied SP2. Then I opened up IIS Manager and set the
> app pool to Classic ASP.NET. When I launch RS Configuration, I select my
> default instance, click connect, it it promptly blows up with the
> following error:
> YES, the SQL Server instance is started. If I click continue, it
> constantly throws WMI errors. I managed to get to the database
> configuration and create the reportserver and reportservertemp databases.
> Doing anything to the virtual directories causes RS Configuration to
> simply abort and shut down. I obviously can't get to either the reports
> or reportserver website, because the config tool crashes and won't setup
> the virtual directories in the config. (If I look in IIS admin, neither
> of the sites has a virtual directory configured and the connection string
> is set to SQLEXPRESS and NOT the default instance that I have on the
> machine.) This is getting ridiculous. Does anyone have a manual config
> checklist which does NOT require this Config tool, because the RS Config
> simply does NOT work.
> See the end of this message for details on invoking
> just-in-time (JIT) debugging instead of this dialog box.
> ************** Exception Text **************
> ReportServicesConfigUI.WMIProvider.WMIProviderException: A WMI error has
> occurred and no additional error information is available. -->
> System.Runtime.InteropServices.COMException (0x8000000A)
> at
> System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
> errorCode, IntPtr errorInfo)
> at System.Management.ManagementObject.InvokeMethod(String methodName,
> ManagementBaseObject inParameters, InvokeMethodOptions options)
> at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
> -- End of inner exception stack trace --
> at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
> at
> ReportServicesConfigUI.WMIProvider.RSInstance.get_DelayLoadConfiguration()
> at
> ReportServicesConfigUI.WMIProvider.RSInstance.get_Item(ConfigurationItemNames
> itemName)
> at ReportServicesConfigUI.ConfigurationManager.ResetStepStatus()
> at ReportServicesConfigUI.ConfigurationManager.ChangeMachine()
> at ReportServicesConfigUI.ConfigurationManager.LaunchDialog()
> at ReportServicesConfigUI.ConfigurationManager.OnActivated(EventArgs e)
> at System.Windows.Forms.Form.set_Active(Boolean value)
> at System.Windows.Forms.Form.WmActivate(Message& m)
> at System.Windows.Forms.Form.WndProc(Message& m)
> at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&
> m)
> at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
> ************** Loaded Assemblies **************
> mscorlib
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
> ---
> RSConfigTool
> Assembly Version: 9.0.242.0
> Win32 Version: 9.00.3042.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/RSConfigTool.exe
> ---
> System.Windows.Forms
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
> ---
> System
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
> ---
> System.Drawing
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
> ---
> System.Xml
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
> ---
> System.Management
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
> ---
> System.ServiceProcess
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
> ---
> ************** JIT Debugging **************
> To enable just-in-time (JIT) debugging, the .config file for this
> application or computer (machine.config) must have the
> jitDebugging value set in the system.windows.forms section.
> The application must also be compiled with debugging
> enabled.
> For example:
> <configuration>
> <system.windows.forms jitDebugging="true" />
> </configuration>
> When JIT debugging is enabled, any unhandled exception
> will be sent to the JIT debugger registered on the computer
> rather than be handled by this dialog box.
> --
> Mike - mhotek@.mssqlserver.com
> President FilAm Software Technology, Inc
> Vice-President MHS Enterprises, Inc
> MCITP - SQL Server DBA, MCT
> http://www.mssqlserver.com
> http://www.mhse.net|||Turn off user account control (UAC) in Vista.
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Michael Hotek" <mike.hotek@.mhse.net> wrote in message
news:91E85C23-8B52-49A4-B1A4-2F0F5CF7B362@.microsoft.com...
>I hacked my way around and manually added the virtual directory within IIS
>Admin for the Reports website. I then hacked and manually input the
><ReportServerVirtualDirectory> within the RSWebApplication.config file. It
>at least finds the website now when I go to http://<machine>/reports.
>However, it fails on the connection attempt with the VERY unhelpful error
>message of:
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version.
> So, since I know that it is all compatible, I'm assuming that I missed
> something when I manually created the connection string in IIS Admin.
> Does anyone have a sample connection string from a working SSRS
> configuration?
> --
> Mike - mhotek@.mssqlserver.com
> President FilAm Software Technology, Inc
> Vice-President MHS Enterprises, Inc
> MCITP - SQL Server DBA, MCT
> http://www.mssqlserver.com
> http://www.mhse.net
> "Michael Hotek" <mike.hotek@.mhse.net> wrote in message
> news:2D164AE8-B582-4478-8D92-96C284E996DA@.microsoft.com...
>> This config stuff is getting a little bit ridiculous. I already had a
>> default instance of SQL Server 2005 SP2 down on the machine. I got all
>> of the IIS components installed on Vista in order to get an installation
>> of SSRS to go through. There was no installation option for
>> configuration. After installing, I applied SP2. Then I opened up IIS
>> Manager and set the app pool to Classic ASP.NET. When I launch RS
>> Configuration, I select my default instance, click connect, it it
>> promptly blows up with the following error:
>> YES, the SQL Server instance is started. If I click continue, it
>> constantly throws WMI errors. I managed to get to the database
>> configuration and create the reportserver and reportservertemp databases.
>> Doing anything to the virtual directories causes RS Configuration to
>> simply abort and shut down. I obviously can't get to either the reports
>> or reportserver website, because the config tool crashes and won't setup
>> the virtual directories in the config. (If I look in IIS admin, neither
>> of the sites has a virtual directory configured and the connection string
>> is set to SQLEXPRESS and NOT the default instance that I have on the
>> machine.) This is getting ridiculous. Does anyone have a manual config
>> checklist which does NOT require this Config tool, because the RS Config
>> simply does NOT work.
>> See the end of this message for details on invoking
>> just-in-time (JIT) debugging instead of this dialog box.
>> ************** Exception Text **************
>> ReportServicesConfigUI.WMIProvider.WMIProviderException: A WMI error has
>> occurred and no additional error information is available. -->
>> System.Runtime.InteropServices.COMException (0x8000000A)
>> at
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
>> errorCode, IntPtr errorInfo)
>> at System.Management.ManagementObject.InvokeMethod(String methodName,
>> ManagementBaseObject inParameters, InvokeMethodOptions options)
>> at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
>> -- End of inner exception stack trace --
>> at ReportServicesConfigUI.WMIProvider.RSInstance.RefreshServerStatus()
>> at
>> ReportServicesConfigUI.WMIProvider.RSInstance.get_DelayLoadConfiguration()
>> at
>> ReportServicesConfigUI.WMIProvider.RSInstance.get_Item(ConfigurationItemNames
>> itemName)
>> at ReportServicesConfigUI.ConfigurationManager.ResetStepStatus()
>> at ReportServicesConfigUI.ConfigurationManager.ChangeMachine()
>> at ReportServicesConfigUI.ConfigurationManager.LaunchDialog()
>> at ReportServicesConfigUI.ConfigurationManager.OnActivated(EventArgs e)
>> at System.Windows.Forms.Form.set_Active(Boolean value)
>> at System.Windows.Forms.Form.WmActivate(Message& m)
>> at System.Windows.Forms.Form.WndProc(Message& m)
>> at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&
>> m)
>> at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
>> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
>> IntPtr wparam, IntPtr lparam)
>>
>> ************** Loaded Assemblies **************
>> mscorlib
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
>> ---
>> RSConfigTool
>> Assembly Version: 9.0.242.0
>> Win32 Version: 9.00.3042.00
>> CodeBase:
>> file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/RSConfigTool.exe
>> ---
>> System.Windows.Forms
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
>> ---
>> System
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
>> ---
>> System.Drawing
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
>> ---
>> System.Xml
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
>> ---
>> System.Management
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
>> ---
>> System.ServiceProcess
>> Assembly Version: 2.0.0.0
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
>> ---
>> ************** JIT Debugging **************
>> To enable just-in-time (JIT) debugging, the .config file for this
>> application or computer (machine.config) must have the
>> jitDebugging value set in the system.windows.forms section.
>> The application must also be compiled with debugging
>> enabled.
>> For example:
>> <configuration>
>> <system.windows.forms jitDebugging="true" />
>> </configuration>
>> When JIT debugging is enabled, any unhandled exception
>> will be sent to the JIT debugger registered on the computer
>> rather than be handled by this dialog box.
>> --
>> Mike - mhotek@.mssqlserver.com
>> President FilAm Software Technology, Inc
>> Vice-President MHS Enterprises, Inc
>> MCITP - SQL Server DBA, MCT
>> http://www.mssqlserver.com
>> http://www.mhse.net
>
Posted by visiblefghv at 5:10 AM 0 comments
Labels: , , , , , , , , , , , , , , , , ,

Monday, March 12, 2012

Installation problem

I have installed SSRS 2005 in one system.There is only configuration tools.

But there is no SQL server Business intelligent development studio,SQL Server Mangement Studio and Performence tools.

While I am installing I am not getting this problem in all machines.

Please help me

Do you have SQL Server Express installed ? If yes, you will have to download the tools that don′t come with the default package or download the Advanced Services ediotion:

http://msdn.microsoft.com/vstudio/express/sql/download/

HTH, Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Thanks Jens
Posted by visiblefghv at 4:12 AM 0 comments
Labels: , , , , , , , , , , , , , ,

Friday, March 9, 2012

Installation Of SSRS

I have two machines on a network (Machine A and Machine B). Machine A has SQL
Server and IIS installed on it and Machine B is the web server. Machine B
does not have Sql Server.
Is there any way by which I can upload my .rdl files on Machine B ie; create
the virtual folders (Reports and ReportsServer) on Machine B?
TIAafraid not as far as I know. When you deploy the reports the rdl files
are actually stored in the reporting services database, which is on
machine A. They aren't stored as physical files on your web server /
Machine B.
A further problem - if you're using RS 200 - is that the web server
will have to have an instance of SQL server installed on it, as the
reporting services database has to be on the same machine as the web
project. Sounds crazy I know but that's the way it is.|||This is so wrong. You DO NOT have to have SQL Server installed where RS is
installed. A quick primer.
RS is an asp.net application. It uses SQL Server as its metadata/object
store. SQL Server can be either on the same machine or on another machine
(this is true for both RS 2000 and RS 2005). If you have Enterprise you can
support a web farm. Several RS servers all sharing the same database (this
means reports, subscriptions, security, etc is setup once for the whole web
farm deployment).
Licensing is a different matter. Any box that has RS installed needs a SQL
Server license, just the same as if you do have SQL Server on the box.
My preference is to have SQL Server on the same box even if my data is
somewhere else. It doesn't cost any more and then my metadata/object storage
is on the same machine as RS. However, again, you do not have to do this.
Note, if the intention is to integrate RS with your own web app you should
really really consider RS 2005. RS 2005 does not require a SQL Server 2005
database, it can use SQL Server 2000 database BUT you do have to buy a SQL
Server 2005 license for the box running RS. VS 2005 has two new controls
that work only with RS 2005: a web form and a winform control. The webform
control makes integration much easier and it is easier to get fuller
functionality quicker than anything you could do with RS 2000.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gearóid" <ghealy@.gmail.com> wrote in message
news:1146818234.435496.208080@.i39g2000cwa.googlegroups.com...
> afraid not as far as I know. When you deploy the reports the rdl files
> are actually stored in the reporting services database, which is on
> machine A. They aren't stored as physical files on your web server /
> Machine B.
> A further problem - if you're using RS 200 - is that the web server
> will have to have an instance of SQL server installed on it, as the
> reporting services database has to be on the same machine as the web
> project. Sounds crazy I know but that's the way it is.
>|||I tried to change the name of the instance of SQL server while installing
SSRS, but it is givinng me error "Login Failed for Guest". I can login to the
Query Analyzer from this remote machine but SSRS is not allowing to connect.
What is the proper way of assiging user name and pwd while installing SSRS.
Do I have to make changes to logins and users on the sql machine.
"Bruce L-C [MVP]" wrote:
> This is so wrong. You DO NOT have to have SQL Server installed where RS is
> installed. A quick primer.
> RS is an asp.net application. It uses SQL Server as its metadata/object
> store. SQL Server can be either on the same machine or on another machine
> (this is true for both RS 2000 and RS 2005). If you have Enterprise you can
> support a web farm. Several RS servers all sharing the same database (this
> means reports, subscriptions, security, etc is setup once for the whole web
> farm deployment).
> Licensing is a different matter. Any box that has RS installed needs a SQL
> Server license, just the same as if you do have SQL Server on the box.
> My preference is to have SQL Server on the same box even if my data is
> somewhere else. It doesn't cost any more and then my metadata/object storage
> is on the same machine as RS. However, again, you do not have to do this.
> Note, if the intention is to integrate RS with your own web app you should
> really really consider RS 2005. RS 2005 does not require a SQL Server 2005
> database, it can use SQL Server 2000 database BUT you do have to buy a SQL
> Server 2005 license for the box running RS. VS 2005 has two new controls
> that work only with RS 2005: a web form and a winform control. The webform
> control makes integration much easier and it is easier to get fuller
> functionality quicker than anything you could do with RS 2000.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Gearóid" <ghealy@.gmail.com> wrote in message
> news:1146818234.435496.208080@.i39g2000cwa.googlegroups.com...
> > afraid not as far as I know. When you deploy the reports the rdl files
> > are actually stored in the reporting services database, which is on
> > machine A. They aren't stored as physical files on your web server /
> > Machine B.
> >
> > A further problem - if you're using RS 200 - is that the web server
> > will have to have an instance of SQL server installed on it, as the
> > reporting services database has to be on the same machine as the web
> > project. Sounds crazy I know but that's the way it is.
> >
>
>
Posted by visiblefghv at 6:05 AM 0 comments
Labels: , , , , , , , , , , , , ,

Sunday, February 19, 2012

Installation doesn't install server components

When I try to install SSRS, it doesn't seem to install the server component.
The feature selection shows client components only.
I have a Microsoft SQL Server 2000 Standard Edition (Reporting Services) CD.
Am I missing something or do simply have the wrong CD?
Thanks
RonYou must have IIS installed and running on the machine to have the SSRS
Server component installed.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:120A0BD0-84BF-45F7-B1F2-2356BFCF042C@.microsoft.com...
> When I try to install SSRS, it doesn't seem to install the server
component.
> The feature selection shows client components only.
> I have a Microsoft SQL Server 2000 Standard Edition (Reporting Services)
CD.
> Am I missing something or do simply have the wrong CD?
> Thanks
> Ron|||Actually IIS was installed - it was ASP.NET that needed to be installed.
Thanks
Ron
"David Frommer" wrote:
> You must have IIS installed and running on the machine to have the SSRS
> Server component installed.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:120A0BD0-84BF-45F7-B1F2-2356BFCF042C@.microsoft.com...
> > When I try to install SSRS, it doesn't seem to install the server
> component.
> > The feature selection shows client components only.
> >
> > I have a Microsoft SQL Server 2000 Standard Edition (Reporting Services)
> CD.
> > Am I missing something or do simply have the wrong CD?
> >
> > Thanks
> >
> > Ron
>
>
Posted by visiblefghv at 11:54 PM 0 comments
Labels: , , , , , , , , , , , , ,
Subscribe to: Posts (Atom)