error opening Enterprise manager

Greetings,
When I open up SQL Server 2000, I get the error:
"Run-time error!
Program: C:\Winnt\system32\mmc.exe
R6025
-pure virtual function call"
Any ideas what I need to do? I really appreciate it.
Thank you,
Jimuh reinstall sql client tools?|||Well, I did reinsatall SQL DMO 2000; is that what you mean, or do you mean something else.

I know there's SQL Server 2000 installation, and sqldmo2000 installation.

Is "sql client tools" something different?

Thank you,
Jim

Error msg in OLD DB provider

I use OLE DB to call a series of stored procedures to add records to databas
e
tables within one transaction. I got the following errors:
Description: Cannot create new connection because in manual or distributed
transaction mode.
Source Description: Microsoft OLE DB Provider for SQL Server
The stored procedures are very simple. I do not try to create a new
connection explicitly. Neither do I try to use distributed transactions. The
only thing that might be a little complicate is I use ISequentialStream to
write blobs to table fields. The error msg confuses me. Any one has ideas
about this?Anothing might be interesting is that the error happens randomly and if I se
t
a break point in the code where it crashed and wait for a while before the
rest of stored procedures, you will not see the error and the save is
successful.
Roy
"Roy" wrote:

> I use OLE DB to call a series of stored procedures to add records to datab
ase
> tables within one transaction. I got the following errors:
> Description: Cannot create new connection because in manual or distributed
> transaction mode.
> Source Description: Microsoft OLE DB Provider for SQL Server
> The stored procedures are very simple. I do not try to create a new
> connection explicitly. Neither do I try to use distributed transactions. T
he
> only thing that might be a little complicate is I use ISequentialStream to
> write blobs to table fields. The error msg confuses me. Any one has ideas
> about this?|||The URL below mayhelp.
http://support.microsoft.com/defaul...&NoWebContent=1
Thomas
"Roy" wrote:

> I use OLE DB to call a series of stored procedures to add records to datab
ase
> tables within one transaction. I got the following errors:
> Description: Cannot create new connection because in manual or distributed
> transaction mode.
> Source Description: Microsoft OLE DB Provider for SQL Server
> The stored procedures are very simple. I do not try to create a new
> connection explicitly. Neither do I try to use distributed transactions. T
he
> only thing that might be a little complicate is I use ISequentialStream to
> write blobs to table fields. The error msg confuses me. Any one has ideas
> about this?

Error message with stored procedure

This error message appears when you try to call a stored procedure and
supply more parameters than those declared for that procedure. Look at the
code where you call the UpdateResources procedure and check that you pass
the correct parameter list.

HTH,

Plamen Ratchev
http://www.SQLStudio.comI see only the definition for the update parameters, not the actual data
binding. Look at the asp:BoundField tags and make sure the DataField values
are correct and there is no duplication of names. Data bound fields
automatically are added to a collection that gets submitted as parameters.
See more details here:
http://msdn2.microsoft.com/en-us/library/ms228051.aspx
Also, make sure that ConflictDetection (a property of the data source) is
not set to CompareAllValues (it is set to OverwriteChanges by default). If
you have it set to CompareAllValues then two sets of parameters are passed,
one for the updated and one for the original values.

HTH,

Plamen Ratchev
http://www.SQLStudio.com|||Forgot to say - a good way to troubleshoot something like this is to use SQL
Profiler to see what SQL statements actually get submitted.

Plamen Ratchev
http://www.SQLStudio.com|||On Oct 29, 4:19 pm, "Plamen Ratchev" <Pla...@.SQLStudio.comwrote:

Quote:

Originally Posted by

Forgot to say - a good way to troubleshoot something like this is to use SQL
Profiler to see what SQL statements actually get submitted.
>
Plamen Ratchevhttp://www.SQLStudio.com

okay Thanks will try that.