RS Installation Woes

Hey reporting Gurus.
I've spent the last eight hours or so trying to get reporting services
reinstalled without success. I had a full blown installation, uninstalled
it thinking I would try SQL 2005, changed my mind and attempted to reinstall
after installing VS2005.
I tried the following (and a little more):
1. Reinstalling SQL2K w. SP4
2. Removing the 2.0 framework
3. Targeting a new installation directory
4. Cleaning all directories
5. Clearing my downloaded assembly cache.
6. Trying various priviliged accounts to run the RS Service under.
No matter how I slice it, the installation is fine until it attempts to
start the reporting services service. It logs the following in the event
log:
Service cannot be started. System.TypeInitializationException: The type
initializer for "Microsoft.ReportingServices.Library.Global" threw an
exception. --> System.TypeLoadException: Could not load type
Microsoft.ReportingServices.Diagnostics.EnumParameter from assembly
Microsoft.ReportingServices.Diagnostics, Version=8.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91.
at Microsoft.ReportingServices.Library.Global..cctor()
-- End of inner exception stack trace --
at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start()
at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object
state)
My best guess is there is a versioning issue of some sort, possibly between
some Reporting services SP2 stuff on my system. Any thoughts?
Many thanks!Hi,
I'd find out where the DLL Microsoft.ReportingServices.Library.Global
is as that is the one that cannot find the code in another DLL,
indicating that it is a newer version than the other DLL it is calling.
To get some more background, try using FileMon from SysInternals.com to
see what DLLs are being loaded and then back them up to somewhere the
system won't find them. Then reinstall.
Ryan|||Justin,
I haven't come across this exact error. But just a hunch from the error
message, open "Services" console and verifiy Report Service (MSSQLSERVER) is
set to running. By default the service is not running after install. You can
also set to Auto Start.
Rob Gerwing
MVP Wanna Be..
"Justin Weinberg" wrote:
> Hey reporting Gurus.
> I've spent the last eight hours or so trying to get reporting services
> reinstalled without success. I had a full blown installation, uninstalled
> it thinking I would try SQL 2005, changed my mind and attempted to reinstall
> after installing VS2005.
> I tried the following (and a little more):
> 1. Reinstalling SQL2K w. SP4
> 2. Removing the 2.0 framework
> 3. Targeting a new installation directory
> 4. Cleaning all directories
> 5. Clearing my downloaded assembly cache.
> 6. Trying various priviliged accounts to run the RS Service under.
> No matter how I slice it, the installation is fine until it attempts to
> start the reporting services service. It logs the following in the event
> log:
> Service cannot be started. System.TypeInitializationException: The type
> initializer for "Microsoft.ReportingServices.Library.Global" threw an
> exception. --> System.TypeLoadException: Could not load type
> Microsoft.ReportingServices.Diagnostics.EnumParameter from assembly
> Microsoft.ReportingServices.Diagnostics, Version=8.0.242.0, Culture=neutral,
> PublicKeyToken=89845dcd8080cc91.
> at Microsoft.ReportingServices.Library.Global..cctor()
> -- End of inner exception stack trace --
> at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
> at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start()
> at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
> args)
> at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object
> state)
> My best guess is there is a versioning issue of some sort, possibly between
> some Reporting services SP2 stuff on my system. Any thoughts?
> Many thanks!
>
>|||Hi Justin,
it doesn't help you, but it might help others...
My recommendation when dealing with beta software like SQL Server 2005
is to only ever install it on an entirely separate operating system
image, if not a different machine!!
Installing beta software on a machine you want to actually use is
fraught with danger...many years ago when we only had small drives I
offered to be a beta tester for IBMs DB2....and I put it on my OS/2
laptop...it destroyed the entire desktop and the only way to get back
was to re-install...and that was before we had burnable CDs...I was
very lucky in that a colleague had a scsi tape drive and I had backed
up the whole pc before installing the beta software....but this whole
exercise took 3-4 days...10 years later...nothing has changed with
installing beta sotware.. ;-)
Peter|||Ryan,
Many thanks for the advice! Worked like a charm.
RS was invoking a newer versioned DLL from the GAC that apparently wasn't
uninstalled when I attempted to uninstall RS. Without your help I'd be
rebuilding my machine right now.
Thanks again,
Justin Weinberg