Catastrophic Failure, MSDASQL, Linked Servers and MySQL

When executing a query which joins against a large resultset from a linked server, SQL Server reports the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "foo" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "foo".

This is using SQL Server 2005 with SP2, and MyODBC version 3.51.16 (although previous versions also seem to have the same behavior).

Once the error occurs any subsequent query against the linked server (even something as simple as select top 3 * From foo...users) fails with the same error message. Queries using the OpenQuery syntax also fail with this error.

I've tried to determine if there are some error logs that might give me more insight into what's going on, but the above events don't seem to log to the ODBC trace logs. And I can't seem to figure out a way to trace the MSDASQL (i.e., oledb) events.

I initially thought there might be a problem with the MySQL myODBC driver, but the ODBC layer itself does not seem to have a problem. But the following steps indicate otherwise:
1. Create a new Linked Server to MySQL. Same error as above
2. Execute a query against the ODBC DSN directly, using a shell program. This works fine

I'm trying to clearly identify if the problem is with the MySQL driver or with the MSDASQL provider. It would appear that the latter is at fault, given the error message, and the lack of any ODBC logging.

Would anyone have any insights about what might be going on here, and if there is any possible resolution?
Here is a link to the tracing article : http://msdn2.microsoft.com/en-us/library/aa964124.aspx
MSDASQL does not produce sufficient trace information, since it was not extensively instrumented, but you might get some traces from other layers and modules - ODBC driver manager, MSDART, MSDATL3.
The ODBC driver manager contains much more ETW-enabled tracing in Vista than in the previous versions.|||

Hello Cybertoast:

Can you resolve this problem ?

I have the same error.

Thanks a lot

Daniel Hefez

Catastrophic Failure, MSDASQL, Linked Servers and MySQL

When executing a query which joins against a large resultset from a linked server, SQL Server reports the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "foo" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "foo".

This is using SQL Server 2005 with SP2, and MyODBC version 3.51.16 (although previous versions also seem to have the same behavior).

Once the error occurs any subsequent query against the linked server (even something as simple as select top 3 * From foo...users) fails with the same error message. Queries using the OpenQuery syntax also fail with this error.

I've tried to determine if there are some error logs that might give me more insight into what's going on, but the above events don't seem to log to the ODBC trace logs. And I can't seem to figure out a way to trace the MSDASQL (i.e., oledb) events.

I initially thought there might be a problem with the MySQL myODBC driver, but the ODBC layer itself does not seem to have a problem. But the following steps indicate otherwise:
1. Create a new Linked Server to MySQL. Same error as above
2. Execute a query against the ODBC DSN directly, using a shell program. This works fine

I'm trying to clearly identify if the problem is with the MySQL driver or with the MSDASQL provider. It would appear that the latter is at fault, given the error message, and the lack of any ODBC logging.

Would anyone have any insights about what might be going on here, and if there is any possible resolution?
Here is a link to the tracing article : http://msdn2.microsoft.com/en-us/library/aa964124.aspx
MSDASQL does not produce sufficient trace information, since it was not extensively instrumented, but you might get some traces from other layers and modules - ODBC driver manager, MSDART, MSDATL3.
The ODBC driver manager contains much more ETW-enabled tracing in Vista than in the previous versions.|||

Hello Cybertoast:

Can you resolve this problem ?

I have the same error.

Thanks a lot

Daniel Hefez

catastrophic failure when refreshing a report from a cube

there is a cube that refreshes each night. in the morning there is an excel pivot table report that refreshes from the cube.it has worked fine for years, but now when i try to refresh it gives me the error "catastrophic failure". Recently i have had to archive the time dimensions of the cube, as the business only want the cube to contain 6 months of data, not 4 years. so i deleted all time dimension members older than 6 months, and deleted all fact data relating to the deleted time dimensions. this seems to be the cause of the issue, but i cant see why. can anyone shed light on this?

What type of query did the Excel pivot table execute? Did the data in the pivot table span more than 6 months of data? Did it have a member of the time dimension selected that is now missing? In general, if you will be purging data from a time dimension and cube, you'll likely want to implement some type of calculated member or named set that refers to the "current" or "most recent" set of time dimension members and have things like Excel pivot table reports refer to these things instead of referring directly to members of the dimension (since they might disappear)...

HTH,

Dave Fackler

Catastrophic Failure after SP2 Upgrade

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
>>
>>
>>
>>
>

Catastrophic Failure

I have a site that has had 70+ pc with msaccess frot end connected to sql200
0
server back end. This site has been in production for 12 months.
With in the last week we have experienced an increasing frequency of
-2147418113 Catastrophic Failure errors. The application writes data from a
tempory in access table back to a table in SQL server. The error doesnot
occur
I have run trace on the server and no sql errors are shown.
The registry on a few machines i have checked have data access version of
2.81.1117.0 the rollback version is 2.70.9001.0.
If i change the ado version in access to 2.5 or 2.1 from 2.8 the frequency
of the error diminishes. Also the adox version shows as 2.7 whenin the list
of available references after selection when re checked it chows as adox 2.8
.
Any ideas would be appreciated.
Craig BJust a thought, but have noted this error in the past when using MS
DTC, e.g. if the DTC service is stopped or crashes, or if a COM+
package is "Shut Down" while active transactions in the package are
running.|||Thanks,
I checked the things you mentioned, nothing obvious shows in services or the
event log.
I have been doing some more cheking and on sql side a trace showns no
errors.
One thing i have found is if say 6 records are writen back then things are
ok, when only 2 or less then the error occurs.
I am currently running an odbc log.
I have looked at kb q243349, but that problem was fixed in mdac 2.5
CraigB
"NonNB" wrote:

> Just a thought, but have noted this error in the past when using MS
> DTC, e.g. if the DTC service is stopped or crashes, or if a COM+
> package is "Shut Down" while active transactions in the package are
> running.
>|||i have will have my client check for client machines to see if dtc or com+
errors. on futher checking on my machine i found dtc had stoped the log was
missing. but every thing worked ok except for what appear to be random event
s
when low records rows are returned. Given the writeback code has been in
production for a year i am perplexed.
Thanks for youe input, something has changed or caused the issues.
CB
"NonNB" wrote:

> Just a thought, but have noted this error in the past when using MS
> DTC, e.g. if the DTC service is stopped or crashes, or if a COM+
> package is "Shut Down" while active transactions in the package are
> running.
>

Catastrophic failure

Hello there!

We have recently upgraded our SQL server to SQL server 2003.
Not entierly without problems i might ad..

The latest one is if you via Excel (2000 or 2003 is tested) try to make a local cube file, using the built-in query wizard, you get an errormessage that only say "Catastrophic failure" and nothing else.

If you instead of using the wizard, do the same thing directly in MsQuery (uncheck the box at the first "new database query window") you dont get the error.

Why!? Many of our users does not have the knowledge on how to write SQL querys and find the wizard very useful. So it is not an option to have them using MsQuery.

And ideas?

From the reference to cube I assume that you are trying to access Analysis Services. I will be moving the thread to the "Data Mining" forum, which has a higher chance to provide an answer.

|||

Well.. That is not correct..

You can create a "local cube" directly from any datasource in Excel..

Call it a lightversion.. ;)

//P?r

|||

[moving thread to the Analyis Services forum]

Did you install Excel or other Office components after you installed SQL Server 2005? In that case, you'll need to re-register "Program Files\Common Files\System\Ole DB\msolap90.dll" to regain connectivity to AS 2005 servers and local cubes.

FYI: The local cube functionality in Excel is provided by a "local server" version of Analysis Services.

|||

Well.. We first tried with the old installation of office 2000 and got the same error, but then we installed 2003 with no success.

But why does it work if you not use the query wizard?

|||If you've upgraded to 2005, the other thing you may want to do is download the SP1 update (which is available soon) as it fixes some issues with local cubes as well, although this may not be the issue you are seeing here.|||

We have now updated to SP1. But the problem remains.

Works without the wizard.. (using MsQuery)

|||

Not sure if you're seeing the same issue, but there was a recent fix made for the OLEDB provider in an upcoming service pack to accomodate an issue where the connection string was being limited to 256 characters when taking a cube offline from XL. You could try to choose a very short path for the local cube and see if this avoids the error.

Sorry you hit this issue and I hope that helps.

Catastrophic Error.

Hi. I've Windows 2000 Advanced Server with Service Pack4. Sql-Enterprise with Service pack3.
There's a strange error when i try to open a table for records through Enterprise-Manager; it says "Catastrophic Error" and some times it says "Class not registered". However Query-Analyzer works fine. I can't connect through any Client-Server application to any database, same error.
I've reinstalled SQL thrice but the same problem. Please suggest if any one has faced this problem.
Regards.Its problem with the client tools installed on the machine and never use EM tool to return the records, QA is the best bet.

Replace the client tools alongwith service pack to get rid of the issue.|||Thanx for ur kind response, Satya. As i mentioned; i've tried reinstalling SQL. If i remove the database and reinstall only the client tools, the same problem persists. Neither i can connect through any Client-Server application with or without the client tools. I need to reinstall the operating-sys i guess.
Regards.|||Before going for big-shot lets go this way :
Uninstall client tools and remove all SQL referenced registry keys then reboot.

Perform fresh install from another CD (if avilable) and see the results.

If the problem persists then think about replacing the OS files and I'm sure this is something to do with SQL tools only in some sort of mis-match of DLLs.

BTW,|||Same error; "class not registered". However i am greatful to u for ur kind replies. How do i replace the operating system files; by choosing the "repair" option while installation of operating-system?|||Yes|||I have the exact same problem, did you get a solution for this?|||I have also heard of this but have not had the problem. Is it the case that the OS was installed and patched to SP4 before installing SQL? I think that's the cause, but it's only a theory. Maybe this order is better:

O/S to SP3
SQL to SP3a
O/S to SP4

?

OSCI|||In my case I use windows 2003 server (standard) then SQL 2000 and sp3.
I tried to reinstall everything except the OS..