reinstalling reporting services

so i uninstalled reporting services and rebooted

now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

what do i have to do to get it to reinstall from scratch?

i tried using the .ini file and using the command line utility with no luckwelcome to the hell that Reporting Services 2000. read chapter 7 of this...

http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1

and then read the whole thing.

SQL 2005 reporting Services is a lot more agreeable.|||so i uninstalled reporting services and rebooted

now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

what do i have to do to get it to reinstall from scratch?

i tried using the .ini file and using the command line utility with no luck

Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...|||Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...

using all of the latest service packs, and i rebooted twice with the same results :o|||welcome to the hell that Reporting Services 2000. read chapter 7 of this...

http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1

and then read the whole thing.

SQL 2005 reporting Services is a lot more agreeable.

i did read this chapter, and looked over the whole thing

i also read the entire sql reporting services book from the people at www.sqlreportingservices.net

none of their solutions helped

i think i am going to try an unattended installation to try to force it to use my ini file, after that i'm out of ideas|||Some info for your help...

Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer).

In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:

Run rsconfig at the command line to update the encrypted connection information in the report server database. Use this syntax when running rsconfig (your values may be different).

rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>

Reset IIS. To do this at the command line, type iisreset.

In the RSWebApplication.config file, modify the ReportServerURL setting to reflect the new server name.

In the RSReportServer.config file, modify the URLRoot setting to reflect the new server name.

Update the URL property of the program item used to access Report Manager from the Start menu. To do this, point to Start, point to Program Files, point to Microsoft SQL Server, point to Reporting Services, right-click on Report Manager. On the Web Document page, update the URL to the new server name.
Open Report Manager and update any shared data sources or report-specific data sources that contain references to the old computer name.
If you are running Windows 2000 server, perform these additional steps:

Manually start the ReportServer Windows service.

Run rsactivate at the command line. Use this syntax when running rsactivate (note that your actual values may be different if you did not install to the default path).

rsactivate -c"%installdir%\Reporting

Services\ReportServer\RSReportServer.config"

Reset IIS. To do this at the command line, type iisreset.

For a period of time, the report server and Report Manager may continue to be available under the previous name if you are using Windows Internet Naming Service (WINS) on your corporate network. WINS maps an IP address to each computer it services. Once WINS refreshes the IP address for the renamed computer, the old computer name can no longer be used to access a report server or Report Manager.|||i did this as well, the problem is that RSCONFIG does not support Named Instances as per Microsoft's website. plus the config files are envrypted - i dont think you can see server names listed in the config files, i remember checking before i did anything

it has to be reinstalled through the GUI which does support named instances

i solved the problem to my issue once again:

asp.net 2.0 was installed on this machine as well, which caused the registry key RootVer to be set to ASP 2.0. This is why the install package was saying that 1.1 was not installed (even though it was). YOu have to temporarily change the RootVer key to 1.1, install, and then set it back. This allows you to reinstall report server etc...

[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"

Reindexing has different behaviour in 2005

I noticed that when I use Maintenace plan wizard to create maintenance plan
to reindex a database, it runs different than it did on SQL2000.
On SQL2000, the job was running about 15 minutes on my 10GB database. During
that time there was a lot of disk activity (loging) and CPU was around 30%.
Now on SQL2005 if I run reindexing maintenance plan on the same 10 GB
database, it first utilizes CPU to maximum (one thread on hyper-threaded
CPU - 3.4GHz Xeon) and during that time there is no disk activity at all.
Profiler tells me that it selects data about database schema. That runs
about 30 minutes and after that actual reindexing begins that also couses a
lot of disk activity and lasts about 15 minutes (same as on SQL2000).
I'm a bit confused about that first 30 minutes when only CPU is doing all
the work. That part was not there in SQL2000. If it takes 30 minutes on 10GB
database, what will happen on 100GB or larger databases? Has anyone some
info if that behaviour has changed in SQL2005?
TomCan you tell us what command(s) the mp is running? You should be able to
script it out.
"Tom" wrote:

> I noticed that when I use Maintenace plan wizard to create maintenance pla
n
> to reindex a database, it runs different than it did on SQL2000.
> On SQL2000, the job was running about 15 minutes on my 10GB database. Duri
ng
> that time there was a lot of disk activity (loging) and CPU was around 30%
.
> Now on SQL2005 if I run reindexing maintenance plan on the same 10 GB
> database, it first utilizes CPU to maximum (one thread on hyper-threaded
> CPU - 3.4GHz Xeon) and during that time there is no disk activity at all.
> Profiler tells me that it selects data about database schema. That runs
> about 30 minutes and after that actual reindexing begins that also couses
a
> lot of disk activity and lasts about 15 minutes (same as on SQL2000).
> I'm a bit confused about that first 30 minutes when only CPU is doing all
> the work. That part was not there in SQL2000. If it takes 30 minutes on 10
GB
> database, what will happen on 100GB or larger databases? Has anyone some
> info if that behaviour has changed in SQL2005?
> Tom
>
>

Registry entries not found

I have a Notification Services instance/application running on the same machine that runs the website that manages the Subscribers. The instance is registered and it is running perfectly fine as a Windows service.

However, when running the subscription-management website i get the following error:

"The registry entries for the specified instance of Notification Services could not be found."

Please note, that the website is running on the same machine as the instance (and the SQL Server as well).

Any suggestions on how to solve this problem will be greatly appreciated.

Thanks.

Double check the string you are using to specify the instance name. It should be what you've defined in the following node of the ICF.

<!--Instance name-->
<InstanceName>MyInstance</InstanceName>

It's not the name of the service.

HTH...

Joe|||

Thanks for your reply.

Yes I know that the service name and the instance name is not the same. My instance name is PWNotifications and the name of the service (which is running fine by the way - chronicle tables are updated as scheduled) is NS$PWNotifications.

The error I get is in the ASP.NET code when this statement gets executed:

new Instance("PWNotifications");

It is very likely that there are some security-restrictions of the process running ASP.NET, I haven't looked into that yet, but the research I done so far tells my that this error is not security related - it is simply a matter of the service not being found.

I have also checked the registry - there is plenty of NS$PWNotifications-related nodes in there.

Another thing that might be relevant: The subscription-management part (the website) was originally written for an application running in .NET 1.x and Notification Services running on MS SQL 2000. It has now been converted to .NET 2.0, but otherwise it has not been changed. Is the [new Instance("PWNotifications")] syntax obsolete in the NS 2005 API?

/Henrik

|||

The problem is solved.

I had not updated the Microsoft.SQLServer.NotificationServices.dll used by the webproject from version 2.x to 9.x.

/Henrik

Register DLL

i want to register some dll's for my application with regards to crystal reports

the application runs off a citrix server...however when i run the regserver32

it produces an error <filename>.dll was loaded but dllregisterserver entry point was not found. the file cannot be registered

As a shot in the dark i wondered whether anyone had encountered this problem and new how to fix it

thanks

frankDo you want to register that dll in local system or remote system?