Failed to reserve contiguous memory

Guys,
does anyone know what to do when you get this kind of
error message: My server is windows 2000 sp4, sql2000
sp3a, Here is the min and max memory configuration in
sp_config
min memory per query (KB) 512 2147483647
min server memory (MB) 0 2147483647
WARNING: Failed to reserve contiguous memory of Size= 65536.
Buffer Distribution: Stolen=4294948690 Free=412
Procedures=142775
Inram=0 Dirty=1232 Kept=0
I/O=0, Latched=41, Other=105186
Does anyone know what needs to be done. It happened
yester at 4pm and hasn't happened again. Let me know
please. Thanks.
Mary LouChances are it is related to one of these:
http://support.microsoft.com/default.aspx?scid=kb;en-us;832674&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;818095&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;316749&Product=sql2k
Andrew J. Kelly SQL MVP
"Mary Lou" <anonymous@.discussions.microsoft.com> wrote in message
news:197a01c4a25a$62bf7f50$a301280a@.phx.gbl...
> Guys,
> does anyone know what to do when you get this kind of
> error message: My server is windows 2000 sp4, sql2000
> sp3a, Here is the min and max memory configuration in
> sp_config
> min memory per query (KB) 512 2147483647
> min server memory (MB) 0 2147483647
>
> WARNING: Failed to reserve contiguous memory of Size=> 65536.
> Buffer Distribution: Stolen=4294948690 Free=412
> Procedures=142775
> Inram=0 Dirty=1232 Kept=0
> I/O=0, Latched=41, Other=105186
>
> Does anyone know what needs to be done. It happened
> yester at 4pm and hasn't happened again. Let me know
> please. Thanks.
> Mary Lou

Failed SQL 7.0/SQL200 Database copy

I recently used the copy data base wizard to copy an existing database from SQL7.0 to SQL2000. The copy was in general a success except for the fact that the copied database gives the error "could not open database "MainDB" version 5.25. Upgrade to the latest version. I performaed a detach on the database and then a reattach to force an upgrade but the reattach process fails with the error

Error 3624:
Converting database "MainDB" from version 525 to current version 539.
Database "mainDB" running the upgrade step from verion 525 to vesrion 526.
Location:Upgraddb.cpp:2230
Expression:0
SPID:53
ProcessID:1088
Description:Database upgrade failed due to MovePage

I earlier successfully moved another database between the same two servers without any problems.

Any ideas?

Thanks

JohnTry taking a backup on SQL7 and then restore on the SQL2000 server instead of copying.
--jfp

Failed Replication

I use SQL2000 and Transactional Replication from server A to B. It is
success to replicate the changes in "Add" and "Deleted" records. But, if I
change the record in server A and then find that fails to replicate. In "Log
Reader" in server A, I can see 1 log is delivered but no any changes in
target. It hasn't any error in log.
Then I tried to rename both tables in server A and B and build the
replication again. It's in normal operation. i.e. Add/Change/Delete are also
ok in replication. Once use back the original table name, it fails to do
"update" replication.
Please advise. Thanks.
Tommy,
can you do an update and check the MSrepl_commands table by using
sp_browsereplcmds. Also, have a look at the article properties (elipsis
button) and check the commands section. It might be that somehow NONE has
been set for the updates. Finally, check that there are no triggers set on
the table which are preventing updates.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)