We recently installed SP2 for reporting services. Everything seemed to work
fine for about 2 days, and now I'm getting errors and I can't access
reporting services at all.
Accessing http://server/reports gives the following error:
Unable to communicate with report server. Please verify that the report
server is operational.
After enabling debug mode, trying to access http://server/reportserver gives
me a COMException (0x800ffff): Catastrophic failure messge.
The only thing helpful in the log file seems to be this:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., Error doing timer action for Memory stats update;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Runtime.InteropServices.COMException (0x8000FFFF):
Catastrophic failure
I can't find any information on anything even remotely similar to this.
Does anyone have any ideas? Additionally, after settings debug=true in the
web.config file, the following page is displaying at
http://server/reportserver :
Server Error in '/ReportServer' Application.
----
Catastrophic failure
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Catastrophic
failure
Source Error:
Line 30: private static bool __initialized = false;
Line 31:
Line 32: public global_asax() {
Line 33: if ((ASP.global_asax.__initialized == false)) {
Line 34: ASP.global_asax.__initialized = true;
Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
Stack Trace:
[COMException (0x8000ffff): Catastrophic failure]
System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo) +0
Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
+46
Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
+5
Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
Microsoft.ReportingServices.WebServer.Global..ctor()
ASP.global_asax..ctor() in
c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
[TargetInvocationException: Exception has been thrown by the target of an
invocation.]
System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
+664
System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes) +200
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance() +160
System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
context) +20
System.Web.HttpApplicationFactory.Init(HttpContext context) +497
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
context) +170
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
----
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032This doesn't sound related to SP2. Software upgrades in my experience do
wait 2 days to totally hose you, they tend to hose you right away.
What happens if you are on the server itself? Can you see the report then.
Be physically on the server and use this URL:
http://localhost/Reports/Pages/Folder.aspx
See anything? Do reports work?
Next try this:
http://localhost/ReportServer
Do you see anything? Will any report work?
The first URL brings you to Report Manager which is the front end (portal)
which ships with RS. The second is the guts of the system. It is where the
reports really reside.
If neither of these work then my guess is you had some sort of hardware
failure that corrupted either the web applications or corrupted the
database. RS uses SQL Server as an object store. All reports (plus lots of
other stuff) is stored in SQL Server databases.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe K" <jmk@.endowmentcapital.com> wrote in message
news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
> We recently installed SP2 for reporting services. Everything seemed to
> work fine for about 2 days, and now I'm getting errors and I can't access
> reporting services at all.
> Accessing http://server/reports gives the following error:
> Unable to communicate with report server. Please verify that the report
> server is operational.
> After enabling debug mode, trying to access http://server/reportserver
> gives me a COMException (0x800ffff): Catastrophic failure messge.
> The only thing helpful in the log file seems to be this:
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more details., Error doing timer action for Memory stats update;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more details. --> System.Runtime.InteropServices.COMException
> (0x8000FFFF): Catastrophic failure
> I can't find any information on anything even remotely similar to this.
> Does anyone have any ideas? Additionally, after settings debug=true in the
> web.config file, the following page is displaying at
> http://server/reportserver :
> Server Error in '/ReportServer' Application.
> ----
> Catastrophic failure
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
> Exception Details: System.Runtime.InteropServices.COMException:
> Catastrophic failure
> Source Error:
> Line 30: private static bool __initialized = false;
> Line 31:
> Line 32: public global_asax() {
> Line 33: if ((ASP.global_asax.__initialized == false)) {
> Line 34: ASP.global_asax.__initialized = true;
> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
> Stack Trace:
> [COMException (0x8000ffff): Catastrophic failure]
> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo) +0
> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
> +46
> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
> +5
> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
> Microsoft.ReportingServices.WebServer.Global..ctor()
> ASP.global_asax..ctor() in
> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
> [TargetInvocationException: Exception has been thrown by the target of an
> invocation.]
> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> +664
> System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes) +200
> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance() +160
> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
> context) +20
> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
> context) +170
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
>
> ----
> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
> ASP.NET Version:1.1.4322.2032
>|||http://localhost/Reports/Pages/Folder.aspx just brings up the error message
"Unable to communicate with report server. Please verify that the report
server is operational." http://localhost/ReportServer is what gives me the
"Catatrophic failure" exception I pasted at the bottom of the last message.
I can't access any portion of reporting services. The only additional change
was SQL Server SP4. I haven't had any problems with any other database
applications.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e1zW%237zdFHA.3012@.tk2msftngp13.phx.gbl...
> This doesn't sound related to SP2. Software upgrades in my experience do
> wait 2 days to totally hose you, they tend to hose you right away.
> What happens if you are on the server itself? Can you see the report then.
> Be physically on the server and use this URL:
> http://localhost/Reports/Pages/Folder.aspx
> See anything? Do reports work?
> Next try this:
> http://localhost/ReportServer
> Do you see anything? Will any report work?
> The first URL brings you to Report Manager which is the front end (portal)
> which ships with RS. The second is the guts of the system. It is where the
> reports really reside.
> If neither of these work then my guess is you had some sort of hardware
> failure that corrupted either the web applications or corrupted the
> database. RS uses SQL Server as an object store. All reports (plus lots of
> other stuff) is stored in SQL Server databases.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Joe K" <jmk@.endowmentcapital.com> wrote in message
> news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> We recently installed SP2 for reporting services. Everything seemed to
>> work fine for about 2 days, and now I'm getting errors and I can't access
>> reporting services at all.
>> Accessing http://server/reports gives the following error:
>> Unable to communicate with report server. Please verify that the report
>> server is operational.
>> After enabling debug mode, trying to access http://server/reportserver
>> gives me a COMException (0x800ffff): Catastrophic failure messge.
>> The only thing helpful in the log file seems to be this:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details., Error doing timer action for Memory stats update;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details. --> System.Runtime.InteropServices.COMException
>> (0x8000FFFF): Catastrophic failure
>> I can't find any information on anything even remotely similar to this.
>> Does anyone have any ideas? Additionally, after settings debug=true in
>> the web.config file, the following page is displaying at
>> http://server/reportserver :
>> Server Error in '/ReportServer' Application.
>> ----
>> Catastrophic failure
>> Description: An unhandled exception occurred during the execution of the
>> current web request. Please review the stack trace for more information
>> about the error and where it originated in the code.
>> Exception Details: System.Runtime.InteropServices.COMException:
>> Catastrophic failure
>> Source Error:
>> Line 30: private static bool __initialized = false;
>> Line 31:
>> Line 32: public global_asax() {
>> Line 33: if ((ASP.global_asax.__initialized == false)) {
>> Line 34: ASP.global_asax.__initialized = true;
>> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
>> Stack Trace:
>> [COMException (0x8000ffff): Catastrophic failure]
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo) +0
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
>> +46
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
>> +5
>> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
>> Microsoft.ReportingServices.WebServer.Global..ctor()
>> ASP.global_asax..ctor() in
>> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
>> [TargetInvocationException: Exception has been thrown by the target of an
>> invocation.]
>> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
>> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
>> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
>> binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +664
>> System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +200
>> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance() +160
>> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
>> context) +20
>> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
>> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
>> context) +170
>> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>> +414
>>
>> ----
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
>> ASP.NET Version:1.1.4322.2032
>|||I have not seen anyone with this problem. I think you should open a service
request with MS. Or, just uninstall and reinstall everything.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe K" <jmk@.endowmentcapital.com> wrote in message
news:%231B6LU0dFHA.228@.TK2MSFTNGP12.phx.gbl...
> http://localhost/Reports/Pages/Folder.aspx just brings up the error
> message "Unable to communicate with report server. Please verify that the
> report server is operational." http://localhost/ReportServer is what
> gives me the "Catatrophic failure" exception I pasted at the bottom of the
> last message. I can't access any portion of reporting services. The only
> additional change was SQL Server SP4. I haven't had any problems with any
> other database applications.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e1zW%237zdFHA.3012@.tk2msftngp13.phx.gbl...
>> This doesn't sound related to SP2. Software upgrades in my experience do
>> wait 2 days to totally hose you, they tend to hose you right away.
>> What happens if you are on the server itself? Can you see the report
>> then. Be physically on the server and use this URL:
>> http://localhost/Reports/Pages/Folder.aspx
>> See anything? Do reports work?
>> Next try this:
>> http://localhost/ReportServer
>> Do you see anything? Will any report work?
>> The first URL brings you to Report Manager which is the front end
>> (portal) which ships with RS. The second is the guts of the system. It is
>> where the reports really reside.
>> If neither of these work then my guess is you had some sort of hardware
>> failure that corrupted either the web applications or corrupted the
>> database. RS uses SQL Server as an object store. All reports (plus lots
>> of other stuff) is stored in SQL Server databases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> We recently installed SP2 for reporting services. Everything seemed to
>> work fine for about 2 days, and now I'm getting errors and I can't
>> access reporting services at all.
>> Accessing http://server/reports gives the following error:
>> Unable to communicate with report server. Please verify that the report
>> server is operational.
>> After enabling debug mode, trying to access http://server/reportserver
>> gives me a COMException (0x800ffff): Catastrophic failure messge.
>> The only thing helpful in the log file seems to be this:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details., Error doing timer action for Memory stats update;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details. --> System.Runtime.InteropServices.COMException
>> (0x8000FFFF): Catastrophic failure
>> I can't find any information on anything even remotely similar to this.
>> Does anyone have any ideas? Additionally, after settings debug=true in
>> the web.config file, the following page is displaying at
>> http://server/reportserver :
>> Server Error in '/ReportServer' Application.
>> ----
>> Catastrophic failure
>> Description: An unhandled exception occurred during the execution of the
>> current web request. Please review the stack trace for more information
>> about the error and where it originated in the code.
>> Exception Details: System.Runtime.InteropServices.COMException:
>> Catastrophic failure
>> Source Error:
>> Line 30: private static bool __initialized = false;
>> Line 31:
>> Line 32: public global_asax() {
>> Line 33: if ((ASP.global_asax.__initialized == false)) {
>> Line 34: ASP.global_asax.__initialized = true;
>> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
>> Stack Trace:
>> [COMException (0x8000ffff): Catastrophic failure]
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo) +0
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
>> +46
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
>> +5
>> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
>> Microsoft.ReportingServices.WebServer.Global..ctor()
>> ASP.global_asax..ctor() in
>> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
>> [TargetInvocationException: Exception has been thrown by the target of
>> an invocation.]
>> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
>> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
>> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
>> binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +664
>> System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +200
>> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance() +160
>> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
>> context) +20
>> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
>> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
>> context) +170
>> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>> +414
>>
>> ----
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
>> ASP.NET Version:1.1.4322.2032
>>
>|||Thanks alot for the advice, Bruce. I'll try a reinstall first and see what
happens.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OcrHR40dFHA.796@.TK2MSFTNGP09.phx.gbl...
>I have not seen anyone with this problem. I think you should open a service
>request with MS. Or, just uninstall and reinstall everything.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joe K" <jmk@.endowmentcapital.com> wrote in message
> news:%231B6LU0dFHA.228@.TK2MSFTNGP12.phx.gbl...
>> http://localhost/Reports/Pages/Folder.aspx just brings up the error
>> message "Unable to communicate with report server. Please verify that
>> the report server is operational." http://localhost/ReportServer is what
>> gives me the "Catatrophic failure" exception I pasted at the bottom of
>> the last message. I can't access any portion of reporting services. The
>> only additional change was SQL Server SP4. I haven't had any problems
>> with any other database applications.
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e1zW%237zdFHA.3012@.tk2msftngp13.phx.gbl...
>> This doesn't sound related to SP2. Software upgrades in my experience do
>> wait 2 days to totally hose you, they tend to hose you right away.
>> What happens if you are on the server itself? Can you see the report
>> then. Be physically on the server and use this URL:
>> http://localhost/Reports/Pages/Folder.aspx
>> See anything? Do reports work?
>> Next try this:
>> http://localhost/ReportServer
>> Do you see anything? Will any report work?
>> The first URL brings you to Report Manager which is the front end
>> (portal) which ships with RS. The second is the guts of the system. It
>> is where the reports really reside.
>> If neither of these work then my guess is you had some sort of hardware
>> failure that corrupted either the web applications or corrupted the
>> database. RS uses SQL Server as an object store. All reports (plus lots
>> of other stuff) is stored in SQL Server databases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> We recently installed SP2 for reporting services. Everything seemed to
>> work fine for about 2 days, and now I'm getting errors and I can't
>> access reporting services at all.
>> Accessing http://server/reports gives the following error:
>> Unable to communicate with report server. Please verify that the
>> report server is operational.
>> After enabling debug mode, trying to access http://server/reportserver
>> gives me a COMException (0x800ffff): Catastrophic failure messge.
>> The only thing helpful in the log file seems to be this:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details., Error doing timer action for Memory stats update;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details. --> System.Runtime.InteropServices.COMException
>> (0x8000FFFF): Catastrophic failure
>> I can't find any information on anything even remotely similar to this.
>> Does anyone have any ideas? Additionally, after settings debug=true in
>> the web.config file, the following page is displaying at
>> http://server/reportserver :
>> Server Error in '/ReportServer' Application.
>> ----
>> Catastrophic failure
>> Description: An unhandled exception occurred during the execution of
>> the current web request. Please review the stack trace for more
>> information about the error and where it originated in the code.
>> Exception Details: System.Runtime.InteropServices.COMException:
>> Catastrophic failure
>> Source Error:
>> Line 30: private static bool __initialized = false;
>> Line 31:
>> Line 32: public global_asax() {
>> Line 33: if ((ASP.global_asax.__initialized == false)) {
>> Line 34: ASP.global_asax.__initialized = true;
>> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
>> Stack Trace:
>> [COMException (0x8000ffff): Catastrophic failure]
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo) +0
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
>> +46
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
>> +5
>> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
>> Microsoft.ReportingServices.WebServer.Global..ctor()
>> ASP.global_asax..ctor() in
>> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
>> [TargetInvocationException: Exception has been thrown by the target of
>> an invocation.]
>> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
>> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
>> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +664
>> System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +200
>> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance()
>> +160
>> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
>> context) +20
>> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
>> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
>> context) +170
>> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>> +414
>>
>> ----
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
>> ASP.NET Version:1.1.4322.2032
>>
>>
>|||Just as an FYI to anybody, a reinstall worked (although a reboot was
necessary).
"Joe K" <jmk@.endowmentcapital.com> wrote in message
news:u25IvR2dFHA.2128@.TK2MSFTNGP14.phx.gbl...
> Thanks alot for the advice, Bruce. I'll try a reinstall first and see
> what happens.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OcrHR40dFHA.796@.TK2MSFTNGP09.phx.gbl...
>>I have not seen anyone with this problem. I think you should open a
>>service request with MS. Or, just uninstall and reinstall everything.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:%231B6LU0dFHA.228@.TK2MSFTNGP12.phx.gbl...
>> http://localhost/Reports/Pages/Folder.aspx just brings up the error
>> message "Unable to communicate with report server. Please verify that
>> the report server is operational." http://localhost/ReportServer is
>> what gives me the "Catatrophic failure" exception I pasted at the bottom
>> of the last message. I can't access any portion of reporting services.
>> The only additional change was SQL Server SP4. I haven't had any
>> problems with any other database applications.
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e1zW%237zdFHA.3012@.tk2msftngp13.phx.gbl...
>> This doesn't sound related to SP2. Software upgrades in my experience
>> do wait 2 days to totally hose you, they tend to hose you right away.
>> What happens if you are on the server itself? Can you see the report
>> then. Be physically on the server and use this URL:
>> http://localhost/Reports/Pages/Folder.aspx
>> See anything? Do reports work?
>> Next try this:
>> http://localhost/ReportServer
>> Do you see anything? Will any report work?
>> The first URL brings you to Report Manager which is the front end
>> (portal) which ships with RS. The second is the guts of the system. It
>> is where the reports really reside.
>> If neither of these work then my guess is you had some sort of hardware
>> failure that corrupted either the web applications or corrupted the
>> database. RS uses SQL Server as an object store. All reports (plus lots
>> of other stuff) is stored in SQL Server databases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> We recently installed SP2 for reporting services. Everything seemed to
>> work fine for about 2 days, and now I'm getting errors and I can't
>> access reporting services at all.
>> Accessing http://server/reports gives the following error:
>> Unable to communicate with report server. Please verify that the
>> report server is operational.
>> After enabling debug mode, trying to access http://server/reportserver
>> gives me a COMException (0x800ffff): Catastrophic failure messge.
>> The only thing helpful in the log file seems to be this:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details., Error doing timer action for Memory stats update;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log for
>> more details. --> System.Runtime.InteropServices.COMException
>> (0x8000FFFF): Catastrophic failure
>> I can't find any information on anything even remotely similar to
>> this. Does anyone have any ideas? Additionally, after settings
>> debug=true in the web.config file, the following page is displaying at
>> http://server/reportserver :
>> Server Error in '/ReportServer' Application.
>> ----
>> Catastrophic failure
>> Description: An unhandled exception occurred during the execution of
>> the current web request. Please review the stack trace for more
>> information about the error and where it originated in the code.
>> Exception Details: System.Runtime.InteropServices.COMException:
>> Catastrophic failure
>> Source Error:
>> Line 30: private static bool __initialized = false;
>> Line 31:
>> Line 32: public global_asax() {
>> Line 33: if ((ASP.global_asax.__initialized == false)) {
>> Line 34: ASP.global_asax.__initialized = true;
>> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line: 32
>> Stack Trace:
>> [COMException (0x8000ffff): Catastrophic failure]
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo) +0
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
>> +46
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
>> +5
>> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
>> Microsoft.ReportingServices.WebServer.Global..ctor()
>> ASP.global_asax..ctor() in
>> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
>> [TargetInvocationException: Exception has been thrown by the target of
>> an invocation.]
>> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
>> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
>> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +664
>> System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +200
>> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance()
>> +160
>> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
>> context) +20
>> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
>> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
>> context) +170
>> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>> +414
>>
>> ----
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
>> ASP.NET Version:1.1.4322.2032
>>
>>
>>
>|||Good. Glad you are back up. Thanks for getting back with the result. It
definitely helps to know what worked.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe K" <jmk@.endowmentcapital.com> wrote in message
news:OU4qO7NeFHA.412@.tk2msftngp13.phx.gbl...
> Just as an FYI to anybody, a reinstall worked (although a reboot was
> necessary).
> "Joe K" <jmk@.endowmentcapital.com> wrote in message
> news:u25IvR2dFHA.2128@.TK2MSFTNGP14.phx.gbl...
>> Thanks alot for the advice, Bruce. I'll try a reinstall first and see
>> what happens.
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:OcrHR40dFHA.796@.TK2MSFTNGP09.phx.gbl...
>>I have not seen anyone with this problem. I think you should open a
>>service request with MS. Or, just uninstall and reinstall everything.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:%231B6LU0dFHA.228@.TK2MSFTNGP12.phx.gbl...
>> http://localhost/Reports/Pages/Folder.aspx just brings up the error
>> message "Unable to communicate with report server. Please verify that
>> the report server is operational." http://localhost/ReportServer is
>> what gives me the "Catatrophic failure" exception I pasted at the
>> bottom of the last message. I can't access any portion of reporting
>> services. The only additional change was SQL Server SP4. I haven't had
>> any problems with any other database applications.
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e1zW%237zdFHA.3012@.tk2msftngp13.phx.gbl...
>> This doesn't sound related to SP2. Software upgrades in my experience
>> do wait 2 days to totally hose you, they tend to hose you right away.
>> What happens if you are on the server itself? Can you see the report
>> then. Be physically on the server and use this URL:
>> http://localhost/Reports/Pages/Folder.aspx
>> See anything? Do reports work?
>> Next try this:
>> http://localhost/ReportServer
>> Do you see anything? Will any report work?
>> The first URL brings you to Report Manager which is the front end
>> (portal) which ships with RS. The second is the guts of the system. It
>> is where the reports really reside.
>> If neither of these work then my guess is you had some sort of
>> hardware failure that corrupted either the web applications or
>> corrupted the database. RS uses SQL Server as an object store. All
>> reports (plus lots of other stuff) is stored in SQL Server databases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Joe K" <jmk@.endowmentcapital.com> wrote in message
>> news:eOm1przdFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> We recently installed SP2 for reporting services. Everything seemed
>> to work fine for about 2 days, and now I'm getting errors and I can't
>> access reporting services at all.
>> Accessing http://server/reports gives the following error:
>> Unable to communicate with report server. Please verify that the
>> report server is operational.
>> After enabling debug mode, trying to access
>> http://server/reportserver gives me a COMException (0x800ffff):
>> Catastrophic failure messge.
>> The only thing helpful in the log file seems to be this:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log
>> for more details., Error doing timer action for Memory stats update;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> An internal error occurred on the report server. See the error log
>> for more details. --> System.Runtime.InteropServices.COMException
>> (0x8000FFFF): Catastrophic failure
>> I can't find any information on anything even remotely similar to
>> this. Does anyone have any ideas? Additionally, after settings
>> debug=true in the web.config file, the following page is displaying
>> at http://server/reportserver :
>> Server Error in '/ReportServer' Application.
>> ----
>> Catastrophic failure
>> Description: An unhandled exception occurred during the execution of
>> the current web request. Please review the stack trace for more
>> information about the error and where it originated in the code.
>> Exception Details: System.Runtime.InteropServices.COMException:
>> Catastrophic failure
>> Source Error:
>> Line 30: private static bool __initialized = false;
>> Line 31:
>> Line 32: public global_asax() {
>> Line 33: if ((ASP.global_asax.__initialized == false)) {
>> Line 34: ASP.global_asax.__initialized = true;
>> Source File: c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> ASP.NET Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs Line:
>> 32
>> Stack Trace:
>> [COMException (0x8000ffff): Catastrophic failure]
>> System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo) +0
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateBytes()
>> +46
>> Microsoft.ReportingServices.Utilities.ProcessUtilities.GetPrivateMBytes()
>> +5
>> Microsoft.ReportingServices.Diagnostics.ResourceUtilities.UpdatePrivateMBytes()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer.DoTimerAction()
>> Microsoft.ReportingServices.Diagnostics.MemoryStatsTimer..ctor()
>> Microsoft.ReportingServices.WebServer.Global..ctor()
>> ASP.global_asax..ctor() in
>> c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\ofoapisc.0.cs:32
>> [TargetInvocationException: Exception has been thrown by the target
>> of an invocation.]
>> System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
>> System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
>> System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
>> Binder binder, Object[] args, CultureInfo culture, Object[]
>> activationAttributes) +664
>> System.Activator.CreateInstance(Type type, BindingFlags
>> bindingAttr, Binder binder, Object[] args, CultureInfo culture,
>> Object[] activationAttributes) +200
>> System.Web.HttpApplicationFactory.GetSpecialApplicationInstance()
>> +160
>> System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext
>> context) +20
>> System.Web.HttpApplicationFactory.Init(HttpContext context) +497
>> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
>> context) +170
>> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>> +414
>>
>> ----
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
>> ASP.NET Version:1.1.4322.2032
>>
>>
>>
>>
>
to upgrade from 2000 to 2005 ?