error 21770 on SQL2k upgrade

We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.