Error after install with Remote SQL Server Instance

Hi,
I've been having a lot of problems with installing Reporting Services on our
webserver. We want the Report Server to be available externally so I've
installed the Report Server and Report Manager on our webserver and the
ReportServer database is located on a separate database server. The install
goes OK and a first test of http://xxx/ReportServer looked fine but when I
try to open Report Manager I get the below error. I've tried various
configurations with the install, so with NT AUTHORITY\SYSTEM as the user that
starts the Report Server service and then with various domain users and sql
logins that all should have access to the database server. Also, if the
service is stopped (it starts OK directly after it is installed) then it
cannot be restarted. In the log is says that it cannot connect to the
database, but there are no errors during the install or in any of the log
files the first time the service starts. If I try to restart the service then
it hangs and usually the server has to be rebooted to stop it.
This is a clean install of Reporting Services, we've never had a previous
version of it on the server. Both the webserver and database server are
Win2000 (sp4) with IIS 5.0 on the webserver. And it is the Standard Edition
of Reporting Services.
So far I have tried the following measures to fix this:
Reinstall ASP .NET 1.1 (v1.1.4322) and have registered it with IIS and
registered aspnet_isapi.dll.
Set file permissions on the winnt\temp directory and the Temporary ASP .NET
Files directory and the C:\Documents and Settings\xxx\ASPNET\Local
Settings\Temp directory. (ASPNET account, SYSTEM acount and even tried giving
Everyone full control)
Checked that all file associations in IIS are correct (aspx files are
associated with the correct version of the .NET framework)
Installing and uninstalling numerous times.
Installing service pack 1 (this fails everytime)
I have not been able to find any post on google with exactly the same error
and symptoms so any help would be much appreciated.
Regards,
Daniel Lee
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: HTTP status code --> 500
--Details--
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
aspnet_wp!ui!fb4!10/11/2004-16:53:42:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)In case anyone else ever gets a simliar error, this seems to have been
something to do with corruption of a windows dll due to a hard disk failure.
However, my bad experience with Reporting Services continues on a new server.
Would find it hard to recommend this product (at least just now) to anyone
who wants to use this in a normal production environment (i.e. separate web
server and database servers), especially if trying to connect to an OLAP cube
and using MDX. I have wasted an unbelieveable amount of time just trying to
get reporting services installed properly. All this is a real pity as I
really like what it can (should) do. Maybe next year with SQL 2005?