Showing posts with label configure. Show all posts
Showing posts with label configure. Show all posts

Monday, March 12, 2012

Report Services: The server commited a protocol violation

Can anyone help with this problem?

I have a green light on my Report Services Confuration, and can configure the server within sharepoint integrated mode. I have also assign the appropriate permission for aspnet etc..etc.

From within Business Intelligent studio when I tried to publish my reports I get the below error:

The server commited a protocol violation

Here is a copy of the report server services log file.

<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.3042.00</Product>
<Locale>en-US</Locale>
<TimeZone>GMT Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServerService__main_06_21_2007_10_47_38.log</Path>
<SystemName>DMTXDW01VM2</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
<OSVersion>5.2.3790.65536</OSVersion>
</Header>
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!21/06/2007-10:47:39:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!servicecontroller!9!21/06/2007-10:47:46:: i INFO: Total Physical memory: 1073094656
ReportingServicesService!servicecontroller!4!21/06/2007-10:47:47:: i INFO: RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'

Urgent help required!


Have you tried adding this to the web.config file?

<system.net>

<settings>

<httpWebRequest useUnsafeHeaderParsing="true" />

...

|||

Hi Tau Liang,

Many thanks for the help, but unfortunatly it did not help! Is the above to go into the Report Manager or Report Services web configuration file or other?

Randine

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:


ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)


The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:


ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)


The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Friday, March 9, 2012

Report Server Windows Service

Hi everyone,

I am not able to access my report server. Here is the message i get when i try to configure it.

System.InvalidOperationException: Cannot start service ReportServer on computer 'Machine-9JP5R91'. > System.ComponentModel.Win32Exception: The service did not start due to a logon failure
End of inner exception stack trace
at System.ServiceProcess.ServiceController.Start(String[] args)
at System.ServiceProcess.ServiceController.Start()
at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)

It says log on failure but i dont know how to change the settings...

Please let me know....

Thanks!!

SqlNew

The Report Server Service requires an account to run. You can set this account through the MMC Service control panel applet or by using the RS Configuration tool. The account password may have expired and all you will need to do is set a new password.

One issue to understand is that if you change the user account that starts the service, the encrypted content of your report server will not work. You will need to restore a backup of the encrypted content if you have it or delete the content. If you delete the content, all stored user and password information will be removed. You should back up your database if you need to change the account.

Report server SQL 2005

For some reason I can't configure that Report server on a SQL 2005
(workgroup) that is part of the Windows 2003 SBS R2 software.
In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
is greyed out.
I tried uninstalling it and reinstalling and applied the patches. Not I
can't even open the CONFIGURE REPORT SERVER program. I get "NO report
servers were found on the machince" Detail, "Invaild namespace"
All I am tring to do get perpare SQL so I can install CRM 3.0.
Did you apply SP2 to your Reporting Services service? This SP solves most
problem.
Ekrem ?nsoy
"support at Marin" <supportatMarin@.discussions.microsoft.com> wrote in
message news:7A0756F0-F3AF-469A-A61C-B9C1C37603E8@.microsoft.com...
> For some reason I can't configure that Report server on a SQL 2005
> (workgroup) that is part of the Windows 2003 SBS R2 software.
> In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
> is greyed out.
> I tried uninstalling it and reinstalling and applied the patches. Not I
> can't even open the CONFIGURE REPORT SERVER program. I get "NO report
> servers were found on the machince" Detail, "Invaild namespace"
> All I am tring to do get perpare SQL so I can install CRM 3.0.

Report server SQL 2005

For some reason I can't configure that Report server on a SQL 2005
(workgroup) that is part of the Windows 2003 SBS R2 software.
In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
is greyed out.
I tried uninstalling it and reinstalling and applied the patches. Not I
can't even open the CONFIGURE REPORT SERVER program. I get "NO report
servers were found on the machince" Detail, "Invaild namespace"
All I am tring to do get perpare SQL so I can install CRM 3.0.Did you apply SP2 to your Reporting Services service? This SP solves most
problem.
Ekrem ?nsoy
"support at Marin" <supportatMarin@.discussions.microsoft.com> wrote in
message news:7A0756F0-F3AF-469A-A61C-B9C1C37603E8@.microsoft.com...
> For some reason I can't configure that Report server on a SQL 2005
> (workgroup) that is part of the Windows 2003 SBS R2 software.
> In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
> is greyed out.
> I tried uninstalling it and reinstalling and applied the patches. Not I
> can't even open the CONFIGURE REPORT SERVER program. I get "NO report
> servers were found on the machince" Detail, "Invaild namespace"
> All I am tring to do get perpare SQL so I can install CRM 3.0.

Report server SQL 2005

For some reason I can't configure that Report server on a SQL 2005
(workgroup) that is part of the Windows 2003 SBS R2 software.
In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
is greyed out.
I tried uninstalling it and reinstalling and applied the patches. Not I
can't even open the CONFIGURE REPORT SERVER program. I get "NO report
servers were found on the machince" Detail, "Invaild namespace"
All I am tring to do get perpare SQL so I can install CRM 3.0.Did you apply SP2 to your Reporting Services service? This SP solves most
problem.
--
Ekrem Ã?nsoy
"support at Marin" <supportatMarin@.discussions.microsoft.com> wrote in
message news:7A0756F0-F3AF-469A-A61C-B9C1C37603E8@.microsoft.com...
> For some reason I can't configure that Report server on a SQL 2005
> (workgroup) that is part of the Windows 2003 SBS R2 software.
> In the REPORTING SERVICE CONFIGURTOR the "REPORT MANAGER VITUAL DIRECTORY
> is greyed out.
> I tried uninstalling it and reinstalling and applied the patches. Not I
> can't even open the CONFIGURE REPORT SERVER program. I get "NO report
> servers were found on the machince" Detail, "Invaild namespace"
> All I am tring to do get perpare SQL so I can install CRM 3.0.

Saturday, February 25, 2012

Report Server Email Delivery setup

I have Report Server setup and I want to add email delivery functionality.
According to Books Online, to configure a Report Server for email delivery
only the following is necessary in RSReportServer.config:
1) SMTPServer - Note I entered just the mail/smtp server host name, not
fully qualified, not a UNC name...just the servername (i.e: Server1). The
values section of the help info says the entry can be "an ip address, a DNS
resolvable name or the name of the computer hosting the SMTP service. I chose
the latter.
2) SMTPAccountName
I added both the above settings, but under "New Subscription" only "Report
Server file share" shows up under "Delivered By". I restarted the Report mgr
service and iisreset.
What's missing?Under C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config
<Extension Name="Report Server Email" ... >
<Configuration>
<RSEmailDPConfiguration>
<From>Type and Email ID Here</From>
Once you add some email id over here which is from email then you will be
able to see the Email Delivery option
"pdx" wrote:
> I have Report Server setup and I want to add email delivery functionality.
> According to Books Online, to configure a Report Server for email delivery
> only the following is necessary in RSReportServer.config:
> 1) SMTPServer - Note I entered just the mail/smtp server host name, not
> fully qualified, not a UNC name...just the servername (i.e: Server1). The
> values section of the help info says the entry can be "an ip address, a DNS
> resolvable name or the name of the computer hosting the SMTP service. I chose
> the latter.
> 2) SMTPAccountName
> I added both the above settings, but under "New Subscription" only "Report
> Server file share" shows up under "Delivered By". I restarted the Report mgr
> service and iisreset.
> What's missing?

Report Server Configuration Issues!

I am attemping to configure Reporting Services on my fresh SQL Server 2005 install. I am literally setting all the defaults for the virtual dirs, identities etc. But when I get to Database Setup, I again pick the defaults, and click New.

It creates the DBs fine, but then asks me whether I want to upgrade the DB, which I find amazing seeing as this is a fresh install.

If I click No and move onto Initialization, then the app tells me there was an error switching panels, and says:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the report server database and verify access rights. (rsInvalidReportServerDatabase).

If I click Yes, it attempts to update the database (that it just created!), and bombs out with the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.


at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

Does anybody have any ideas on this one? It seems like a authentication issue, but surely if it created the database, it should then have given itself some rights to use it!

This has been driving me up the wall, so all help is very much appreciated :)

I get the same behaviour!? (Upgrade from SQLServer 2000 -> 2005, then installed ReportServer)

Any fixes/solutions yet?

Report Server Configuration

I'm attempting to install and configure Report Server for the first time.

In the "Configure Report Server" dialog box the first 5 tasks are successfully configured with green circles and check marks. ( Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity)

Database Setup has a red circle with an X.

The following is returned in Task Status:

Verifying Database Edition. The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

The following error is returned in the Report Server error log:

ReportingServicesService!library!e!4/5/2007-16:52:27:: i INFO: Catalog SQL Server Edition = Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: restricted SKUs: Workgroup Express Developer Evaluation - actual SKU Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

ReportingServicesService!library!e!4/5/2007-16:52:27:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

at Microsoft.ReportingServices.Diagnostics.Sku.EnsureCorrectEdition(SqlConnection sqlConn, String connectionString, Boolean checkRestrictedSkus)

We are running SQL Server 2005 Workgroup Edition

9.00.3054.00 SP2 Workgroup Edition

It sounds like the error is saying that Report Server is not compatible with SQL Server 2005 Workgroup Edition?

Any suggestions?

Thank you.

Are you trying to install the Express version on Workgroup? I don't think that's supported. Workgroup does include Reporting Services, but you should install it from the Workgroup installation.|||I'm getting the same error message, have you found a resolution.|||My problem was operator error. I had used the wrong disc when installing SQL Server 2005 on a Small Business Server. I used the SQL Server Standard Edition disc rather than the SQL Server 2005 disc that came with Small Business Server. I uninstalled SQL Server and installed it from the Small Business Server SQL Server disc and everything was fine.

Report Server Configuration

I'm attempting to install and configure Report Server for the first time.

In the "Configure Report Server" dialog box the first 5 tasks are successfully configured with green circles and check marks. ( Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity)

Database Setup has a red circle with an X.

The following is returned in Task Status:

Verifying Database Edition. The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

The following error is returned in the Report Server error log:

ReportingServicesService!library!e!4/5/2007-16:52:27:: i INFO: Catalog SQL Server Edition = Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: restricted SKUs: Workgroup Express Developer Evaluation - actual SKU Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

ReportingServicesService!library!e!4/5/2007-16:52:27:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

at Microsoft.ReportingServices.Diagnostics.Sku.EnsureCorrectEdition(SqlConnection sqlConn, String connectionString, Boolean checkRestrictedSkus)

We are running SQL Server 2005 Workgroup Edition

9.00.3054.00 SP2 Workgroup Edition

It sounds like the error is saying that Report Server is not compatible with SQL Server 2005 Workgroup Edition?

Any suggestions?

Thank you.

Are you trying to install the Express version on Workgroup? I don't think that's supported. Workgroup does include Reporting Services, but you should install it from the Workgroup installation.|||I'm getting the same error message, have you found a resolution.|||My problem was operator error. I had used the wrong disc when installing SQL Server 2005 on a Small Business Server. I used the SQL Server Standard Edition disc rather than the SQL Server 2005 disc that came with Small Business Server. I uninstalled SQL Server and installed it from the Small Business Server SQL Server disc and everything was fine.

Report Server and Report Manager on different machines

It is possible to configure a system of servers such that
the Report Manager can be running on a separate machine
than the Report Server?
We are concerned about the security issues of exposing a
server with the Front Page Server Extensions installed on
it, because it will reside outside of our corporate
firewall. As an alternative, we are hoping we can host
the Web Server/IIS box outside the firewall, and have
this machine run the Report Manager, while another box
inside the firewall runs the Report Server (which,
incidentally, will also be a separate box than the data
server).
Whether the security concerns of FPSE are real or
perceived, our clients might not like them. So, is the
type of configuration described above at all possible?
If not, please explain why. If it is possible, please
explain how.
Thanks in advance!Front Page Server extensions are not necessary for Report Manager. Just to
make sure I checked one of my servers (Windows 2003) and the default website
which has Report Manager does not have FP server extension.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Justin" <anonymous@.discussions.microsoft.com> wrote in message
news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> It is possible to configure a system of servers such that
> the Report Manager can be running on a separate machine
> than the Report Server?
> We are concerned about the security issues of exposing a
> server with the Front Page Server Extensions installed on
> it, because it will reside outside of our corporate
> firewall. As an alternative, we are hoping we can host
> the Web Server/IIS box outside the firewall, and have
> this machine run the Report Manager, while another box
> inside the firewall runs the Report Server (which,
> incidentally, will also be a separate box than the data
> server).
> Whether the security concerns of FPSE are real or
> perceived, our clients might not like them. So, is the
> type of configuration described above at all possible?
> If not, please explain why. If it is possible, please
> explain how.
> Thanks in advance!
>|||So, FPSE are only required on a Report Designer
installtion -- is that correct?
FPSE are a requirement for VisualStudio.NET installation,
which are required for Report Designer, right?
>--Original Message--
>Front Page Server extensions are not necessary for
Report Manager. Just to
>make sure I checked one of my servers (Windows 2003) and
the default website
>which has Report Manager does not have FP server
extension.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
>"Justin" <anonymous@.discussions.microsoft.com> wrote in
message
>news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> It is possible to configure a system of servers such
that
>> the Report Manager can be running on a separate machine
>> than the Report Server?
>> We are concerned about the security issues of exposing
a
>> server with the Front Page Server Extensions installed
on
>> it, because it will reside outside of our corporate
>> firewall. As an alternative, we are hoping we can host
>> the Web Server/IIS box outside the firewall, and have
>> this machine run the Report Manager, while another box
>> inside the firewall runs the Report Server (which,
>> incidentally, will also be a separate box than the data
>> server).
>> Whether the security concerns of FPSE are real or
>> perceived, our clients might not like them. So, is the
>> type of configuration described above at all possible?
>> If not, please explain why. If it is possible, please
>> explain how.
>> Thanks in advance!
>
>.
>|||No. FPSE are not required for anything. The report designer does not even
have to have IIS.
You've gotten a misconception from somewhere that this is required.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<anonymous@.discussions.microsoft.com> wrote in message
news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
> So, FPSE are only required on a Report Designer
> installtion -- is that correct?
> FPSE are a requirement for VisualStudio.NET installation,
> which are required for Report Designer, right?
>
> >--Original Message--
> >Front Page Server extensions are not necessary for
> Report Manager. Just to
> >make sure I checked one of my servers (Windows 2003) and
> the default website
> >which has Report Manager does not have FP server
> extension.
> >
> >--
> >Bruce Loehle-Conger
> >MVP SQL Server Reporting Services
> >
> >"Justin" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> >> It is possible to configure a system of servers such
> that
> >> the Report Manager can be running on a separate machine
> >> than the Report Server?
> >>
> >> We are concerned about the security issues of exposing
> a
> >> server with the Front Page Server Extensions installed
> on
> >> it, because it will reside outside of our corporate
> >> firewall. As an alternative, we are hoping we can host
> >> the Web Server/IIS box outside the firewall, and have
> >> this machine run the Report Manager, while another box
> >> inside the firewall runs the Report Server (which,
> >> incidentally, will also be a separate box than the data
> >> server).
> >>
> >> Whether the security concerns of FPSE are real or
> >> perceived, our clients might not like them. So, is the
> >> type of configuration described above at all possible?
> >> If not, please explain why. If it is possible, please
> >> explain how.
> >>
> >> Thanks in advance!
> >>
> >
> >
> >.
> >|||Yes, I guess I do have that misconception. I thought
that in order to deploy a report from the report designer
to the report server, FPSE were required.
I'm glad to hear that this is not the case. I'll check
out our servers again and try to verify this.
Thanks.
>--Original Message--
>No. FPSE are not required for anything. The report
designer does not even
>have to have IIS.
>You've gotten a misconception from somewhere that this
is required.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
><anonymous@.discussions.microsoft.com> wrote in message
>news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
>> So, FPSE are only required on a Report Designer
>> installtion -- is that correct?
>> FPSE are a requirement for VisualStudio.NET
installation,
>> which are required for Report Designer, right?
>>
>> >--Original Message--
>> >Front Page Server extensions are not necessary for
>> Report Manager. Just to
>> >make sure I checked one of my servers (Windows 2003)
and
>> the default website
>> >which has Report Manager does not have FP server
>> extension.
>> >
>> >--
>> >Bruce Loehle-Conger
>> >MVP SQL Server Reporting Services
>> >
>> >"Justin" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> >> It is possible to configure a system of servers such
>> that
>> >> the Report Manager can be running on a separate
machine
>> >> than the Report Server?
>> >>
>> >> We are concerned about the security issues of
exposing
>> a
>> >> server with the Front Page Server Extensions
installed
>> on
>> >> it, because it will reside outside of our corporate
>> >> firewall. As an alternative, we are hoping we can
host
>> >> the Web Server/IIS box outside the firewall, and
have
>> >> this machine run the Report Manager, while another
box
>> >> inside the firewall runs the Report Server (which,
>> >> incidentally, will also be a separate box than the
data
>> >> server).
>> >>
>> >> Whether the security concerns of FPSE are real or
>> >> perceived, our clients might not like them. So, is
the
>> >> type of configuration described above at all
possible?
>> >> If not, please explain why. If it is possible,
please
>> >> explain how.
>> >>
>> >> Thanks in advance!
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||What you might be confused about is thinking about using Visual Studio for
regular ASP.Net development. It is common to have FPSE for that. However,
with RS you are not deploying webpages. What you are doing is using
webservices to deploy the RDL. If you look on the server you will see that
no files are even showing up there when you deploy. That is because the RDL
is being stored in the database, not in the file system.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Justin" <anonymous@.discussions.microsoft.com> wrote in message
news:176001c4ccc2$b3afef70$a501280a@.phx.gbl...
> Yes, I guess I do have that misconception. I thought
> that in order to deploy a report from the report designer
> to the report server, FPSE were required.
> I'm glad to hear that this is not the case. I'll check
> out our servers again and try to verify this.
> Thanks.
> >--Original Message--
> >No. FPSE are not required for anything. The report
> designer does not even
> >have to have IIS.
> >
> >You've gotten a misconception from somewhere that this
> is required.
> >
> >--
> >Bruce Loehle-Conger
> >MVP SQL Server Reporting Services
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
> >> So, FPSE are only required on a Report Designer
> >> installtion -- is that correct?
> >>
> >> FPSE are a requirement for VisualStudio.NET
> installation,
> >> which are required for Report Designer, right?
> >>
> >>
> >> >--Original Message--
> >> >Front Page Server extensions are not necessary for
> >> Report Manager. Just to
> >> >make sure I checked one of my servers (Windows 2003)
> and
> >> the default website
> >> >which has Report Manager does not have FP server
> >> extension.
> >> >
> >> >--
> >> >Bruce Loehle-Conger
> >> >MVP SQL Server Reporting Services
> >> >
> >> >"Justin" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> >> >> It is possible to configure a system of servers such
> >> that
> >> >> the Report Manager can be running on a separate
> machine
> >> >> than the Report Server?
> >> >>
> >> >> We are concerned about the security issues of
> exposing
> >> a
> >> >> server with the Front Page Server Extensions
> installed
> >> on
> >> >> it, because it will reside outside of our corporate
> >> >> firewall. As an alternative, we are hoping we can
> host
> >> >> the Web Server/IIS box outside the firewall, and
> have
> >> >> this machine run the Report Manager, while another
> box
> >> >> inside the firewall runs the Report Server (which,
> >> >> incidentally, will also be a separate box than the
> data
> >> >> server).
> >> >>
> >> >> Whether the security concerns of FPSE are real or
> >> >> perceived, our clients might not like them. So, is
> the
> >> >> type of configuration described above at all
> possible?
> >> >> If not, please explain why. If it is possible,
> please
> >> >> explain how.
> >> >>
> >> >> Thanks in advance!
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||Yes, that makes sense. I think that is exactly where I
was going wrong.
Thanks again!
>--Original Message--
>What you might be confused about is thinking about using
Visual Studio for
>regular ASP.Net development. It is common to have FPSE
for that. However,
>with RS you are not deploying webpages. What you are
doing is using
>webservices to deploy the RDL. If you look on the server
you will see that
>no files are even showing up there when you deploy. That
is because the RDL
>is being stored in the database, not in the file system.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
>"Justin" <anonymous@.discussions.microsoft.com> wrote in
message
>news:176001c4ccc2$b3afef70$a501280a@.phx.gbl...
>> Yes, I guess I do have that misconception. I thought
>> that in order to deploy a report from the report
designer
>> to the report server, FPSE were required.
>> I'm glad to hear that this is not the case. I'll check
>> out our servers again and try to verify this.
>> Thanks.
>> >--Original Message--
>> >No. FPSE are not required for anything. The report
>> designer does not even
>> >have to have IIS.
>> >
>> >You've gotten a misconception from somewhere that this
>> is required.
>> >
>> >--
>> >Bruce Loehle-Conger
>> >MVP SQL Server Reporting Services
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
>> >> So, FPSE are only required on a Report Designer
>> >> installtion -- is that correct?
>> >>
>> >> FPSE are a requirement for VisualStudio.NET
>> installation,
>> >> which are required for Report Designer, right?
>> >>
>> >>
>> >> >--Original Message--
>> >> >Front Page Server extensions are not necessary for
>> >> Report Manager. Just to
>> >> >make sure I checked one of my servers (Windows
2003)
>> and
>> >> the default website
>> >> >which has Report Manager does not have FP server
>> >> extension.
>> >> >
>> >> >--
>> >> >Bruce Loehle-Conger
>> >> >MVP SQL Server Reporting Services
>> >> >
>> >> >"Justin" <anonymous@.discussions.microsoft.com>
wrote
>> in
>> >> message
>> >> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> >> >> It is possible to configure a system of servers
such
>> >> that
>> >> >> the Report Manager can be running on a separate
>> machine
>> >> >> than the Report Server?
>> >> >>
>> >> >> We are concerned about the security issues of
>> exposing
>> >> a
>> >> >> server with the Front Page Server Extensions
>> installed
>> >> on
>> >> >> it, because it will reside outside of our
corporate
>> >> >> firewall. As an alternative, we are hoping we
can
>> host
>> >> >> the Web Server/IIS box outside the firewall, and
>> have
>> >> >> this machine run the Report Manager, while
another
>> box
>> >> >> inside the firewall runs the Report Server
(which,
>> >> >> incidentally, will also be a separate box than
the
>> data
>> >> >> server).
>> >> >>
>> >> >> Whether the security concerns of FPSE are real or
>> >> >> perceived, our clients might not like them. So,
is
>> the
>> >> >> type of configuration described above at all
>> possible?
>> >> >> If not, please explain why. If it is possible,
>> please
>> >> >> explain how.
>> >> >>
>> >> >> Thanks in advance!
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>