Hi,
I had trouble getting reporting services going. I would
get the configuration error. If I restart the IIS Admin
the reporting services works fine but my other aspx pages
get the same configuration error. Something about
Microsoft.Office.Interop.Owc. If I restart IIS Admin
again the other aspx pages work but reporting services
does not.
What is going on here?
Can't Reporting Services and other .NET pages co-exist?
Please help.
-Marciaapplications can co-exist, but not in the same virtual folder.
maybe you can try to create a new application pool dedicated to reporting
services. (this is required when installing reporting services and
sharepoint on the same server)
I've already installed RS on some computer and I never get any error.
What is the content of your web.config files? (under the RS folders and un
der parent folder)
"Marcia Gorby" <anonymous@.discussions.microsoft.com> a écrit dans le message
de news:5ffc01c48174$eb0e7840$a401280a@.phx.gbl...
> Hi,
> I had trouble getting reporting services going. I would
> get the configuration error. If I restart the IIS Admin
> the reporting services works fine but my other aspx pages
> get the same configuration error. Something about
> Microsoft.Office.Interop.Owc. If I restart IIS Admin
> again the other aspx pages work but reporting services
> does not.
> What is going on here?
> Can't Reporting Services and other .NET pages co-exist?
> Please help.
> -Marcia
Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts
Friday, March 30, 2012
Monday, March 12, 2012
Reporting Service will not start
SQL Server 2005 SP1 (Express) will not start
Reporting Services Configuration Manager reports:
System.ServiceProcess.TimeoutException: Time out has expired and the
operation has not been completed.
at
System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
desiredStatus, TimeSpan timeout)
at
ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
Windows Event Application log contains:
Service cannot be started. System.TypeInitializationException: The type
initializer for 'Microsoft.ReportingServices.Library.Global' threw an
exception. --> System.Configuration.ConfigurationErrorsException: An error
occurred creating the configuration section handler for RStrace: That
assembly does not allow partially trusted callers. (c:\Program
Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
System.Security.SecurityException: That assembly does not allow partially
trusted callers.
at
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
SecurityAction action, Object demand, IPermission permThatFailed)
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
fillCache)
...
Thanks for the helpI have the exact same problem on my machine - did you ever find a solution to
this?
"Automate" wrote:
> SQL Server 2005 SP1 (Express) will not start
> Reporting Services Configuration Manager reports:
> System.ServiceProcess.TimeoutException: Time out has expired and the
> operation has not been completed.
> at
> System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> desiredStatus, TimeSpan timeout)
> at
> ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
>
> Windows Event Application log contains:
> Service cannot be started. System.TypeInitializationException: The type
> initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> exception. --> System.Configuration.ConfigurationErrorsException: An error
> occurred creating the configuration section handler for RStrace: That
> assembly does not allow partially trusted callers. (c:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> System.Security.SecurityException: That assembly does not allow partially
> trusted callers.
> at
> System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> SecurityAction action, Object demand, IPermission permThatFailed)
> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> Boolean& bNeedSecurityCheck)
> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> fillCache)
> ...
>
> Thanks for the help|||The problem was occuring on a large companies computers that used their own
standardized secure Windows install images. They told me they had to open up
the security of DCOM but I don't know exactly what they changed.
"Flayto" wrote:
> I have the exact same problem on my machine - did you ever find a solution to
> this?
> "Automate" wrote:
> > SQL Server 2005 SP1 (Express) will not start
> >
> > Reporting Services Configuration Manager reports:
> >
> > System.ServiceProcess.TimeoutException: Time out has expired and the
> > operation has not been completed.
> > at
> > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > desiredStatus, TimeSpan timeout)
> > at
> > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> >
> >
> > Windows Event Application log contains:
> >
> > Service cannot be started. System.TypeInitializationException: The type
> > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > occurred creating the configuration section handler for RStrace: That
> > assembly does not allow partially trusted callers. (c:\Program
> > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > System.Security.SecurityException: That assembly does not allow partially
> > trusted callers.
> > at
> > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > SecurityAction action, Object demand, IPermission permThatFailed)
> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > Boolean& bNeedSecurityCheck)
> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > fillCache)
> > ...
> >
> >
> > Thanks for the help|||Well, I managed to fix the problem after a bit of research. In the end, all I
needed to do was re-install .Net 2.0 framework. I'm not sure if it got
damaged because of the order I installed applications on my computer, but
repairing Framework 2.0 seems to have done the trick.
"Automate" wrote:
> The problem was occuring on a large companies computers that used their own
> standardized secure Windows install images. They told me they had to open up
> the security of DCOM but I don't know exactly what they changed.
> "Flayto" wrote:
> > I have the exact same problem on my machine - did you ever find a solution to
> > this?
> >
> > "Automate" wrote:
> >
> > > SQL Server 2005 SP1 (Express) will not start
> > >
> > > Reporting Services Configuration Manager reports:
> > >
> > > System.ServiceProcess.TimeoutException: Time out has expired and the
> > > operation has not been completed.
> > > at
> > > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > > desiredStatus, TimeSpan timeout)
> > > at
> > > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> > >
> > >
> > > Windows Event Application log contains:
> > >
> > > Service cannot be started. System.TypeInitializationException: The type
> > > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > > occurred creating the configuration section handler for RStrace: That
> > > assembly does not allow partially trusted callers. (c:\Program
> > > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > > System.Security.SecurityException: That assembly does not allow partially
> > > trusted callers.
> > > at
> > > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > > SecurityAction action, Object demand, IPermission permThatFailed)
> > > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > > Boolean& bNeedSecurityCheck)
> > > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > > fillCache)
> > > ...
> > >
> > >
> > > Thanks for the help
Reporting Services Configuration Manager reports:
System.ServiceProcess.TimeoutException: Time out has expired and the
operation has not been completed.
at
System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
desiredStatus, TimeSpan timeout)
at
ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
Windows Event Application log contains:
Service cannot be started. System.TypeInitializationException: The type
initializer for 'Microsoft.ReportingServices.Library.Global' threw an
exception. --> System.Configuration.ConfigurationErrorsException: An error
occurred creating the configuration section handler for RStrace: That
assembly does not allow partially trusted callers. (c:\Program
Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
System.Security.SecurityException: That assembly does not allow partially
trusted callers.
at
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
SecurityAction action, Object demand, IPermission permThatFailed)
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
fillCache)
...
Thanks for the helpI have the exact same problem on my machine - did you ever find a solution to
this?
"Automate" wrote:
> SQL Server 2005 SP1 (Express) will not start
> Reporting Services Configuration Manager reports:
> System.ServiceProcess.TimeoutException: Time out has expired and the
> operation has not been completed.
> at
> System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> desiredStatus, TimeSpan timeout)
> at
> ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
>
> Windows Event Application log contains:
> Service cannot be started. System.TypeInitializationException: The type
> initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> exception. --> System.Configuration.ConfigurationErrorsException: An error
> occurred creating the configuration section handler for RStrace: That
> assembly does not allow partially trusted callers. (c:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> System.Security.SecurityException: That assembly does not allow partially
> trusted callers.
> at
> System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> SecurityAction action, Object demand, IPermission permThatFailed)
> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> Boolean& bNeedSecurityCheck)
> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> fillCache)
> ...
>
> Thanks for the help|||The problem was occuring on a large companies computers that used their own
standardized secure Windows install images. They told me they had to open up
the security of DCOM but I don't know exactly what they changed.
"Flayto" wrote:
> I have the exact same problem on my machine - did you ever find a solution to
> this?
> "Automate" wrote:
> > SQL Server 2005 SP1 (Express) will not start
> >
> > Reporting Services Configuration Manager reports:
> >
> > System.ServiceProcess.TimeoutException: Time out has expired and the
> > operation has not been completed.
> > at
> > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > desiredStatus, TimeSpan timeout)
> > at
> > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> >
> >
> > Windows Event Application log contains:
> >
> > Service cannot be started. System.TypeInitializationException: The type
> > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > occurred creating the configuration section handler for RStrace: That
> > assembly does not allow partially trusted callers. (c:\Program
> > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > System.Security.SecurityException: That assembly does not allow partially
> > trusted callers.
> > at
> > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > SecurityAction action, Object demand, IPermission permThatFailed)
> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > Boolean& bNeedSecurityCheck)
> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > fillCache)
> > ...
> >
> >
> > Thanks for the help|||Well, I managed to fix the problem after a bit of research. In the end, all I
needed to do was re-install .Net 2.0 framework. I'm not sure if it got
damaged because of the order I installed applications on my computer, but
repairing Framework 2.0 seems to have done the trick.
"Automate" wrote:
> The problem was occuring on a large companies computers that used their own
> standardized secure Windows install images. They told me they had to open up
> the security of DCOM but I don't know exactly what they changed.
> "Flayto" wrote:
> > I have the exact same problem on my machine - did you ever find a solution to
> > this?
> >
> > "Automate" wrote:
> >
> > > SQL Server 2005 SP1 (Express) will not start
> > >
> > > Reporting Services Configuration Manager reports:
> > >
> > > System.ServiceProcess.TimeoutException: Time out has expired and the
> > > operation has not been completed.
> > > at
> > > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > > desiredStatus, TimeSpan timeout)
> > > at
> > > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> > >
> > >
> > > Windows Event Application log contains:
> > >
> > > Service cannot be started. System.TypeInitializationException: The type
> > > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > > occurred creating the configuration section handler for RStrace: That
> > > assembly does not allow partially trusted callers. (c:\Program
> > > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > > System.Security.SecurityException: That assembly does not allow partially
> > > trusted callers.
> > > at
> > > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > > SecurityAction action, Object demand, IPermission permThatFailed)
> > > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > > Boolean& bNeedSecurityCheck)
> > > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > > fillCache)
> > > ...
> > >
> > >
> > > Thanks for the help
Reporting service virtual directories on non default web
Hi, I installed the two virtual directories on a new, non default web with
the RS Configuration Tool, what was well done and described on
http://msdn2.microsoft.com/en-us/library/ms155921.aspx. If now I try to
access the server by: http://<hostheader>/reportserver it looks up for a
web.config file
(C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\web.config) in
the base directory. So this file is not there, why it shoud be. With
http://localhost/reportserver it works without this file. What must be done
more to use the report service on non default web?
Thanks, JanCheck the value of the <URLRoot> tag in the rsreportserver.config file.
"JanM" wrote:
> Hi, I installed the two virtual directories on a new, non default web with
> the RS Configuration Tool, what was well done and described on
> http://msdn2.microsoft.com/en-us/library/ms155921.aspx. If now I try to
> access the server by: http://<hostheader>/reportserver it looks up for a
> web.config file
> (C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\web.config) in
> the base directory. So this file is not there, why it shoud be. With
> http://localhost/reportserver it works without this file. What must be done
> more to use the report service on non default web?
> Thanks, Jan
>
the RS Configuration Tool, what was well done and described on
http://msdn2.microsoft.com/en-us/library/ms155921.aspx. If now I try to
access the server by: http://<hostheader>/reportserver it looks up for a
web.config file
(C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\web.config) in
the base directory. So this file is not there, why it shoud be. With
http://localhost/reportserver it works without this file. What must be done
more to use the report service on non default web?
Thanks, JanCheck the value of the <URLRoot> tag in the rsreportserver.config file.
"JanM" wrote:
> Hi, I installed the two virtual directories on a new, non default web with
> the RS Configuration Tool, what was well done and described on
> http://msdn2.microsoft.com/en-us/library/ms155921.aspx. If now I try to
> access the server by: http://<hostheader>/reportserver it looks up for a
> web.config file
> (C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\web.config) in
> the base directory. So this file is not there, why it shoud be. With
> http://localhost/reportserver it works without this file. What must be done
> more to use the report service on non default web?
> Thanks, Jan
>
Reporting Service Subscriptions E-mail Configuration
Hello Group,
I am trying to set up a e-mail rendered Standard subscription in Report
Server.
I have edited the RSReportServer.config file according to BOL.
Can anyone give me an example of a working SMTP E-mail enabled config.
Thanks,
Heres the error I recieve in My Subscriptions. I am included in the RS
System Admin role.
"Failure sending mail: The server rejected the sender address. The server
response was: 505 Authentication required"
--
Application Engineer / DBA
UCLA SOMYou will need to grant the report server service account permission to send
e-mail to your SMTP server.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marcial" <no_spam@.antispammer.com> wrote in message
news:1257729F-CE95-4F69-9134-F9DB8A5B59C7@.microsoft.com...
> Hello Group,
> I am trying to set up a e-mail rendered Standard subscription in Report
> Server.
> I have edited the RSReportServer.config file according to BOL.
> Can anyone give me an example of a working SMTP E-mail enabled config.
> Thanks,
> Heres the error I recieve in My Subscriptions. I am included in the RS
> System Admin role.
> "Failure sending mail: The server rejected the sender address. The server
> response was: 505 Authentication required"
>
> --
> Application Engineer / DBA
> UCLA SOM
I am trying to set up a e-mail rendered Standard subscription in Report
Server.
I have edited the RSReportServer.config file according to BOL.
Can anyone give me an example of a working SMTP E-mail enabled config.
Thanks,
Heres the error I recieve in My Subscriptions. I am included in the RS
System Admin role.
"Failure sending mail: The server rejected the sender address. The server
response was: 505 Authentication required"
--
Application Engineer / DBA
UCLA SOMYou will need to grant the report server service account permission to send
e-mail to your SMTP server.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marcial" <no_spam@.antispammer.com> wrote in message
news:1257729F-CE95-4F69-9134-F9DB8A5B59C7@.microsoft.com...
> Hello Group,
> I am trying to set up a e-mail rendered Standard subscription in Report
> Server.
> I have edited the RSReportServer.config file according to BOL.
> Can anyone give me an example of a working SMTP E-mail enabled config.
> Thanks,
> Heres the error I recieve in My Subscriptions. I am included in the RS
> System Admin role.
> "Failure sending mail: The server rejected the sender address. The server
> response was: 505 Authentication required"
>
> --
> Application Engineer / DBA
> UCLA SOM
Friday, March 9, 2012
Reporting Service Configuration Manager
How do I resolve the following error message?
* Reporting Service Configuration Manager not foundSee if you have this tool in place.
Binn\RSConfigTool.exe
Amarnath
"Terry" wrote:
> How do I resolve the following error message?
> * Reporting Service Configuration Manager not found
>|||After deleting the CTP version of SQL Server 2005 w/ Reporting Services and
attempting to install the standard version of SQL Server 2005 w/ Reporting
Services, Reporting Services configuration error message appears as follows:
* Reporting Service Configuration Manager not found
We have made several attempts to install the standard version of SQL Server
2005 w/ Reporting Services to no avail. So, we have decided to rebuild the
server to ensure that the CTP version of SQL Server 2005 did not remove
related registry entries which prevents the standard installation of SQL
Server 2005.
What service accounts should be used for Reporting Services?
Could you provide me with a link that will give me a better understanding on
how service account works?
Thank you in advance for your patience and assistance.
"Amarnath" wrote:
> See if you have this tool in place.
> Binn\RSConfigTool.exe
> Amarnath
> "Terry" wrote:
> > How do I resolve the following error message?
> >
> > * Reporting Service Configuration Manager not found
> >
> >|||search for "Accounts in a Reporting Services Deployment" in the online help.
A failry good info on the service accounts.
It is better to go for a domain account.
Amarnath.
"Terry" wrote:
> After deleting the CTP version of SQL Server 2005 w/ Reporting Services and
> attempting to install the standard version of SQL Server 2005 w/ Reporting
> Services, Reporting Services configuration error message appears as follows:
> * Reporting Service Configuration Manager not found
> We have made several attempts to install the standard version of SQL Server
> 2005 w/ Reporting Services to no avail. So, we have decided to rebuild the
> server to ensure that the CTP version of SQL Server 2005 did not remove
> related registry entries which prevents the standard installation of SQL
> Server 2005.
> What service accounts should be used for Reporting Services?
> Could you provide me with a link that will give me a better understanding on
> how service account works?
> Thank you in advance for your patience and assistance.
>
> "Amarnath" wrote:
> > See if you have this tool in place.
> >
> > Binn\RSConfigTool.exe
> >
> > Amarnath
> >
> > "Terry" wrote:
> >
> > > How do I resolve the following error message?
> > >
> > > * Reporting Service Configuration Manager not found
> > >
> > >
* Reporting Service Configuration Manager not foundSee if you have this tool in place.
Binn\RSConfigTool.exe
Amarnath
"Terry" wrote:
> How do I resolve the following error message?
> * Reporting Service Configuration Manager not found
>|||After deleting the CTP version of SQL Server 2005 w/ Reporting Services and
attempting to install the standard version of SQL Server 2005 w/ Reporting
Services, Reporting Services configuration error message appears as follows:
* Reporting Service Configuration Manager not found
We have made several attempts to install the standard version of SQL Server
2005 w/ Reporting Services to no avail. So, we have decided to rebuild the
server to ensure that the CTP version of SQL Server 2005 did not remove
related registry entries which prevents the standard installation of SQL
Server 2005.
What service accounts should be used for Reporting Services?
Could you provide me with a link that will give me a better understanding on
how service account works?
Thank you in advance for your patience and assistance.
"Amarnath" wrote:
> See if you have this tool in place.
> Binn\RSConfigTool.exe
> Amarnath
> "Terry" wrote:
> > How do I resolve the following error message?
> >
> > * Reporting Service Configuration Manager not found
> >
> >|||search for "Accounts in a Reporting Services Deployment" in the online help.
A failry good info on the service accounts.
It is better to go for a domain account.
Amarnath.
"Terry" wrote:
> After deleting the CTP version of SQL Server 2005 w/ Reporting Services and
> attempting to install the standard version of SQL Server 2005 w/ Reporting
> Services, Reporting Services configuration error message appears as follows:
> * Reporting Service Configuration Manager not found
> We have made several attempts to install the standard version of SQL Server
> 2005 w/ Reporting Services to no avail. So, we have decided to rebuild the
> server to ensure that the CTP version of SQL Server 2005 did not remove
> related registry entries which prevents the standard installation of SQL
> Server 2005.
> What service accounts should be used for Reporting Services?
> Could you provide me with a link that will give me a better understanding on
> how service account works?
> Thank you in advance for your patience and assistance.
>
> "Amarnath" wrote:
> > See if you have this tool in place.
> >
> > Binn\RSConfigTool.exe
> >
> > Amarnath
> >
> > "Terry" wrote:
> >
> > > How do I resolve the following error message?
> > >
> > > * Reporting Service Configuration Manager not found
> > >
> > >
Reporting service configuration in distributed environment
Hi,
Please let me know if the following server configuration is possible?
SQL Server Database Services on machine #1
Analysis Services and Reporting Services 2005 on machine #2 (without SQL Server Database Services)
Post installation, need to setup Reporting services configuration. In that, within Database Setup, point to database installed on machine #1.
I am facing problem in pointing to remote database.
Awaiting some reply.
Thanks!
Hi RSUser08,
This configuration for SQL engine and Reporting Services is supported:
- machine 1: SQL Server Database Services
- machine 2: Reporting Services files-only installation (which means a named instance)
I would suggest to install on both machines the SQL Server Management Tools.
On the machine 1 you could use the tool SQL Server Surface Area Configuration for configuring your engine service to accept both local and remote connections. Be sure you restart the SQL engine service after you made this configuration change.
On the machine 2 you could use the configuration tool for Reporting Services to configure your files-only instance. For the database setup, you could connect from machine 2 to machine 1 and after this you can create a new catalog or choose from the drop-down list an existing catalog on the machine 1. Be sure you press apply after any option you chose.
If you encounter any problems during the database creation or choosing a previous created database, please let me know. In this case please let me know also what version and edition of SQL 2005 you are using.
Mihaela
|||Thanks a lott Mihaela!
We are facing problem in the database setup of Reporting Service configuration.
Following is our machine configuration details:
We are using SQL Server 2005 Standard Edition. (Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) )
1: Machine #1 = SQL Server Database - Database Services only installed. No IIS.
2: Machine #2 = Analysis Services & Reporting Services. Used SQL Server 2005 Standard Edition CD to install only those 2 services. This machine has IIS 6.0 installed.
3:All the services are installed using the local Administrator account (as opposed to using a Windows domain account with administator privileges). The services are running under Local System account.
4: In Database Setup configuration, pointed to remote database. On click of Apply button we got the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.
> System.Runtime.InteropServices.COMException (0x800706B3): The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)
The only reason we guess is that all the services needs to be installed and run under a domain account.
Please do let me know the exact reason for this failure.
Thanks once again!
Reporting service configuration in distributed environment
Hi,
Please let me know if the following server configuration is possible?
SQL Server Database Services on machine #1
Analysis Services and Reporting Services 2005 on machine #2 (without SQL Server Database Services)
Post installation, need to setup Reporting services configuration. In that, within Database Setup, point to database installed on machine #1.
I am facing problem in pointing to remote database.
Awaiting some reply.
Thanks!
Hi RSUser08,
This configuration for SQL engine and Reporting Services is supported:
- machine 1: SQL Server Database Services
- machine 2: Reporting Services files-only installation (which means a named instance)
I would suggest to install on both machines the SQL Server Management Tools.
On the machine 1 you could use the tool SQL Server Surface Area Configuration for configuring your engine service to accept both local and remote connections. Be sure you restart the SQL engine service after you made this configuration change.
On the machine 2 you could use the configuration tool for Reporting Services to configure your files-only instance. For the database setup, you could connect from machine 2 to machine 1 and after this you can create a new catalog or choose from the drop-down list an existing catalog on the machine 1. Be sure you press apply after any option you chose.
If you encounter any problems during the database creation or choosing a previous created database, please let me know. In this case please let me know also what version and edition of SQL 2005 you are using.
Mihaela
|||Thanks a lott Mihaela!
We are facing problem in the database setup of Reporting Service configuration.
Following is our machine configuration details:
We are using SQL Server 2005 Standard Edition. (Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) )
1: Machine #1 = SQL Server Database - Database Services only installed. No IIS.
2: Machine #2 = Analysis Services & Reporting Services. Used SQL Server 2005 Standard Edition CD to install only those 2 services. This machine has IIS 6.0 installed.
3:All the services are installed using the local Administrator account (as opposed to using a Windows domain account with administator privileges). The services are running under Local System account.
4: In Database Setup configuration, pointed to remote database. On click of Apply button we got the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.
> System.Runtime.InteropServices.COMException (0x800706B3): The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)
The only reason we guess is that all the services needs to be installed and run under a domain account.
Please do let me know the exact reason for this failure.
Thanks once again!
Saturday, February 25, 2012
Reporting Servcies Configuration
Hi,
I am new to sql server 2005 and reporting servics.
I have installed sql server 2005 with reporting services on windows vita.
After that when i go to Reporting Servcies Configuration i get follwoing error,
A WMI error has occurred and no additional error information is available.
details,
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() ..........
Any one has any idea?
Regards,
SSRS only will work on Vista Ultimate? If you have Ultimate let me know and I can tell you how to do it. It is still a lot compatibility issues but their is a work around if you want to get it installed.
Subscribe to:
Posts (Atom)