"Not enough server storage is available to process this command"

Hi,
We have several customers using replication on similar databases - all with the same schema, published using essentially the same script. One of them has been getting the "Not enough server storage" message when they try to access any network shares on th
e server with the published database on it. This starts happening between 24-36 hours after they first run the snapshot agent.
The application log contains an entry saying "The process could not create file \\[SERVER]\REPLDATA\unc",
and the system log has one saying "The server was unable to allocate from the system paged pool because the pool was empty".
When they turn off the replication everything is fine.
I suggested increasing the IRPStackSize value in the registry, as this was mentioned in the closest article I could find on MSDN/KB (something about Norton AntiVirus), but this didn't make any difference.
This is SQL Server 2000 running on Windows 2000 Server, all with up-to-date service packs.
Any ideas or suggestions would be appreciated.
Mark
from your earlier post i understand that the snapshot creation part gives
out this message.
If the error occurs while the snapshot is being generated, check the
following"
1. Check if the sql server service account has appropriate NTFS and share
level permissions to write to the repldata directory.
2. Check if there is enough storage space on the disk for creating files
in repldata directory.
3. Check if you can run xp_cmdshell "dir
\\distributorname\c$\mssql\repldata"
and dir \\distributor\c$\mssql\repldata from command prompt.
If the error occurs after the snapshot has been completely generated, Refer
-
* KB : 285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Pls do let me know of the SQL server version (build number). and the event
id's of the event log messages.
Does this message stop replication? are the subscribers and publisher in
sync? - Just to confirm if this message is obstructing replication from
being in sync.

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
Peja
I'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> Hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
PejaI'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
PejaI'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> Hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Default bound to column

I am running a script against a couple of databases on my SQL Server 2000 Standard Edition Instance and I am getting the following in the results pane:

"Default bound to column" I have searched the MS Knowledge base and found a couple of vague references to this. Does anyone know why I might be getting this? the script 'seems' to run fine.. except for the funky error in the results pane. Script is attached. Thank you!!maybe no one has answered because zip files make people nervous (viruses). Just post the code using the tags. I know I am not opening your zip file.|||IIRC the sp_bindefault will give that message; just run one of them to confirm that.

ALSO never zip up a SQL script as a DOC file and think you are going to get an answer.

Change it to a text file and then only if it is very large zip it up.

doc files are the most common file used to tranmit virii to other people followed by zip files so very few people word open your file.

I have both zip & doc files set to open with non-MS software so I should be safe but I almost did not open the doc.

Tim S