Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
bogey
Posting Yak Master
166 Posts |
Posted - 2008-07-01 : 10:08:53
|
We are not able to get past this on the Configure Report Server for sql server reporting services 2005. Our database(s) reside on a remote machine.Here is the Report Server Configuration ExecptionException Details:System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String machine) at ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String dbServer) at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String connectionString, String server, String database, ConfigurationCredentialsType credsType, String account, String password, Boolean upgrade, String dbVersion) |
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-07-02 : 15:37:30
|
Is the SQL Server behind the Firewall?Then you need to check that your firewall allows DCOM traffic between the two boxes while setting them.The operation you’re trying to do is an administrative operation that should be carried out inside the safety of your network either locally on the computer or through a secure channel inside your networkManinderDatabase Painter.. Leaving strokes, that amaze! and inreturn, put value to your Work. I am a Database [Architect / Administrator] |
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2008-07-02 : 16:39:16
|
This error is really not an error at all. We were on the phone with MSFT last night for about 8 hrs discussing this. Seems that some errors can be ignored in SSRS. Happily we are up and running today. |
|
|
|
|
|