Anybody seen this error? - 37000 - Storage Allocation record not available

Hi Jonathan

I am not familiar with the error message, but is there any more information
in the SQL Server error log. Does Stopping/Starting SQL server help? Have you
tried defragmenting the disc? Are you using a fixed value for file growth on
all the databases (including tempdb).

John

"jonathan.beckett" wrote:

> Hi all,
>
> I have a problem with a SQL Server database throwing an error I have
> never seen before, and cannot remember ever seeing anywhere else either
> (even a google search doesn't throw anything up).
>
> Here's the exact text...
> 37000
> [Microsoft][ODBC SQL Server Driver][SQL Server]Storage Allocation
> record not available
>
> The error was originally caused by the database server running out of
> space on the system volume (containing the log files), but that has now
> been rectified, and we have confirmed that the growth rate of the log
> files are smaller than the amount of free space.
>
> What on earth does it mean anyway - "storage allocation record not
> available" ?
>
>

Hi Jonathan

I am not familiar with the error message, but is there any more information
in the SQL Server error log. Does Stopping/Starting SQL server help? Have you
tried defragmenting the disc? Are you using a fixed value for file growth on
all the databases (including tempdb).

John

"jonathan.beckett" wrote:

> Hi all,
>
> I have a problem with a SQL Server database throwing an error I have
> never seen before, and cannot remember ever seeing anywhere else either
> (even a google search doesn't throw anything up).
>
> Here's the exact text...
> 37000
> [Microsoft][ODBC SQL Server Driver][SQL Server]Storage Allocation
> record not available
>
> The error was originally caused by the database server running out of
> space on the system volume (containing the log files), but that has now
> been rectified, and we have confirmed that the growth rate of the log
> files are smaller than the amount of free space.
>
> What on earth does it mean anyway - "storage allocation record not
> available" ?
>
>

First, what version of SQL server are you using?
2nd, is the the error still recurring?
I never seen it before but i expect it has to do wit the SQL engine- which
generates this message when the log was full.

Greetz,

Fling Dutch men.

First, what version of SQL server are you using?
2nd, is the the error still recurring?
I never seen it before but i expect it has to do wit the SQL engine- which
generates this message when the log was full.

Greetz,

Fling Dutch men.

> I am not familiar with the error message, but is there any more information
> in the SQL Server error log. Does Stopping/Starting SQL server help? Have you
> tried defragmenting the disc? Are you using a fixed value for file growth on
> all the databases (including tempdb).
>
> John


It's SQL Server 7 on NT.

Stopping and starting SQL Server does not resolve the problem.
Defragmentation is not an issue either. We're really stumped, and have
opened a call with the makers of the software that is reporting the
error from SQL Server.



>
> "jonathan.beckett" wrote:
>
> > Hi all,
> >
> > I have a problem with a SQL Server database throwing an error I have
> > never seen before, and cannot remember ever seeing anywhere else either
> > (even a google search doesn't throw anything up).
> >
> > Here's the exact text...
> > 37000
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Storage Allocation
> > record not available
> >
> > The error was originally caused by the database server running out of
> > space on the system volume (containing the log files), but that has now
> > been rectified, and we have confirmed that the growth rate of the log
> > files are smaller than the amount of free space.
> >
> > What on earth does it mean anyway - "storage allocation record not
> > available" ?
> >
> >

> I am not familiar with the error message, but is there any more information
> in the SQL Server error log. Does Stopping/Starting SQL server help? Have you
> tried defragmenting the disc? Are you using a fixed value for file growth on
> all the databases (including tempdb).
>
> John


It's SQL Server 7 on NT.

Stopping and starting SQL Server does not resolve the problem.
Defragmentation is not an issue either. We're really stumped, and have
opened a call with the makers of the software that is reporting the
error from SQL Server.



>
> "jonathan.beckett" wrote:
>
> > Hi all,
> >
> > I have a problem with a SQL Server database throwing an error I have
> > never seen before, and cannot remember ever seeing anywhere else either
> > (even a google search doesn't throw anything up).
> >
> > Here's the exact text...
> > 37000
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Storage Allocation
> > record not available
> >
> > The error was originally caused by the database server running out of
> > space on the system volume (containing the log files), but that has now
> > been rectified, and we have confirmed that the growth rate of the log
> > files are smaller than the amount of free space.
> >
> > What on earth does it mean anyway - "storage allocation record not
> > available" ?
> >
> >

Hate_orphaned_users wrote:

> First, what version of SQL server are you using?
> 2nd, is the the error still recurring?
> I never seen it before but i expect it has to do wit the SQL engine- which
> generates this message when the log was full.

SQL Server 7 on NT

The error is still recurring, but only for a specific operation within
the software that uses the database. Everything else appears to be
fine.

It is very, very strange - we have opened a call with the makers of the
software that is reporting the error (annoyingly it does not appear in
their knowledgebase, and Microsoft have no information on this specific
error from SQL Server either).

Hate_orphaned_users wrote:

> First, what version of SQL server are you using?
> 2nd, is the the error still recurring?
> I never seen it before but i expect it has to do wit the SQL engine- which
> generates this message when the log was full.

SQL Server 7 on NT

The error is still recurring, but only for a specific operation within
the software that uses the database. Everything else appears to be
fine.

It is very, very strange - we have opened a call with the makers of the
software that is reporting the error (annoyingly it does not appear in
their knowledgebase, and Microsoft have no information on this specific
error from SQL Server either).

Hi Jonathan,

This is a memory storage allocation error. You can get more details by
running the DBCC MEMORYSTATUS command. For more info go to:

http://support.microsoft.com/kb/907877/en-us

The first I'd check is to make sure you haven't run out if space on
TempDB.

On 27 Dec 2006 03:08:11 -0800, "jonathan.beckett"
wrote:

>Hi all,
>
>I have a problem with a SQL Server database throwing an error I have
>never seen before, and cannot remember ever seeing anywhere else either
>(even a google search doesn't throw anything up).
>
>Here's the exact text...
>37000
>[Microsoft][ODBC SQL Server Driver][SQL Server]Storage Allocation
>record not available
>
>The error was originally caused by the database server running out of
>space on the system volume (containing the log files), but that has now
>been rectified, and we have confirmed that the growth rate of the log
>files are smaller than the amount of free space.
>
>What on earth does it mean anyway - "storage allocation record not
>available" ?