Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>

Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>sql

Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?
Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>

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 On Sproc Update Dates?

Does anyone know the system tables I need to query to produce a report of stored procedures (SQL 2005) that had any changes made to them in a user-specified date range?

In SQL 2005, I saw the canned database reports, but this one didn't exist. Any help would be greatly appreciated.

Thanks!

Wow, already off the first page so quickly?

Sorry for the bump, I just wanted to be sure there was no quick answer to this. I would have thought it would be an easy thing to do, I may be mistaken.

Any takers?

Thanks again.

|||

You can get any object now using the sys.objects view. For sprocs, you'd want something like this:

Code Snippet

select * from sys.objects where type='P' and modify_date between getdate() - 1000 and getdate()

-Jessica

|||

Perfect! I knew it must be something simple I was missing.

Thanks, Jessica!

Reporting On Sproc Update Dates?

Does anyone know the system tables I need to query to produce a report of stored procedures (SQL 2005) that had any changes made to them in a user-specified date range?

In SQL 2005, I saw the canned database reports, but this one didn't exist. Any help would be greatly appreciated.

Thanks!

Wow, already off the first page so quickly?

Sorry for the bump, I just wanted to be sure there was no quick answer to this. I would have thought it would be an easy thing to do, I may be mistaken.

Any takers?

Thanks again.

|||

You can get any object now using the sys.objects view. For sprocs, you'd want something like this:

Code Snippet

select * from sys.objects where type='P' and modify_date between getdate() - 1000 and getdate()

-Jessica

|||

Perfect! I knew it must be something simple I was missing.

Thanks, Jessica!

reporting licensing

We recently purchased Stockamp's Clinic Ontrac system. The system has a built in crystal reports viewer module with capability to add our own reports... The backend of the product is SQL Server. To create a report you have to potentially create a stored procedure - if parameter is needed - and a crystal report. Stockamp is requesting that we have written approval of these reports as well as any ad-hoc reports and queries that we run before we run them in the production environment.

I'm used to large vendors (those that understand a database is only as good as the data you get out of it) and I've never seen a license agreement like this before. Is this common?What they are trying to do is to ensure that by creating a report you're not going to impact the production environment in such a way that they may be blamed for poor performance while your report is being generated. Also, since they introduced a "report writer," this means that there are not many "canned" reports in the system that they sold you, and they are trying to piggy-bag on your reports and incorporate them in the next release as "canned" reports.|||If possible, you should consider replicating your data on a dedicated report server. This will avoid potential performance issues.|||Unfortunately the data changes constantly, and I suspect if they won't let me add reports, they won't let me replicate. It took me over 2 months to convince them we needed a seperate test server as making a modification to their system (using their own forms and an approved process) required a 4 hour import that completely paralized the system.
The database tables have grown from 2000 rows 9 months ago to over 21 million, so reporting out of the system will soon become too cpu intensive anyway.
I'd love to work with the vendor and introduce them to datawarehouseing, but they're product is so fragile and Stockamp & Associates employees are so unwilling to listen, that I given up on a friendly working relationship.
So the moral is to avoid software with a canned report viewer, regardless of its backend system.