We have an SQL Server app written in ASP that suddenly has an error after 2
years of operation, and we're having trouble locating the problem. Here is
the error message below. The reference in the Knowledgebase for this error
doesn't seem to apply to us. There is plenty of space left on the drive. I
believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
. . .This is a multi-part message in MIME format.
--030408090501090704060408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
You say there is plenty of space left on the disk, but is there a max
size limit set on the file(s) contained in the PRIMARY filegroup? Can
you post the results of this (for your particular DB name that is):
USE <dbname>;
EXEC sp_helpfile;
--
*mike hodgson*
http://sqlnerd.blogspot.com
Dean J Garrett wrote:
>Hello,
>We have an SQL Server app written in ASP that suddenly has an error after 2
>years of operation, and we're having trouble locating the problem. Here is
>the error message below. The reference in the Knowledgebase for this error
>doesn't seem to apply to us. There is plenty of space left on the drive. I
>believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>is full.
>/Household.asp, line 298
>a.. Browser Type:
>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>a.. Page:
>POST 700 bytes to /Household.asp
>a.. POST Data:
>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>.. . .
>
>
--030408090501090704060408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>You say there is plenty of space left on the disk, but is there a
max size limit set on the file(s) contained in the PRIMARY filegroup?
Can you post the results of this (for your particular DB name that is):<br>
<br>
USE <dbname>;<br>
EXEC sp_helpfile;<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Dean J Garrett wrote:
<blockquote cite="midefWu9xELGHA.2796@.TK2MSFTNGP10.phx.gbl" type="cite">
<pre wrap="">Hello,
We have an SQL Server app written in ASP that suddenly has an error after 2
years of operation, and we're having trouble locating the problem. Here is
the error message below. The reference in the Knowledgebase for this error
doesn't seem to apply to us. There is plenty of space left on the drive. I
believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
.. . .
</pre>
</blockquote>
</body>
</html>
--030408090501090704060408--|||I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.|||This is a multi-part message in MIME format.
--=_NextPart_000_0007_01C62CB5.99712670
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
The database properties is set to "Unrestricted Growth" but for some =reason when the data file gets to 928MB, we get that error message even =though there is plenty of free space on the drive. Why would that =happen?
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message =news:Ocs8eJFLGHA.984@.tk2msftngp13.phx.gbl...
You say there is plenty of space left on the disk, but is there a max =size limit set on the file(s) contained in the PRIMARY filegroup? Can =you post the results of this (for your particular DB name that is):
USE <dbname>;
EXEC sp_helpfile;
--
mike hodgson
http://sqlnerd.blogspot.com=20
Dean J Garrett wrote: Hello,
We have an SQL Server app written in ASP that suddenly has an error =after 2 years of operation, and we're having trouble locating the problem. Here =is the error message below. The reference in the Knowledgebase for this =error doesn't seem to apply to us. There is plenty of space left on the drive. =I believe we're using SP3 of SQL Server 2000. Can anyone point us in the =right direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space =for object 'tblTabl31' in database 'Database1' because the 'PRIMARY' =filegroup is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR =1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=3DSave&InID=3D25449&SSN=3D531067163&FileClosedDate=3D&FileNu=mber=3D&FirstName=3DMARY&MiddleInitial=3D&DAP=3D1&LastName=3DTARDIN&SAT=3D=101&ApplicationDate=3D02%2F06%2F2006&EffectiveDate=3D10%2F17%2F2003&Las .. . .
--=_NextPart_000_0007_01C62CB5.99712670
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
The database properties is set to ="Unrestricted Growth" but for some reason when the data file gets to 928MB, we get =that error message even though there is plenty of free space on the drive. Why =would that happen?
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com Dean J Garrett wrote: Hello,
We have an SQL Server app written in ASP that suddenly has an error =after 2 years of operation, and we're having trouble locating the problem. Here =is the error message below. The reference in the Knowledgebase for this =error doesn't seem to apply to us. There is plenty of space left on the drive. =I believe we're using SP3 of SQL Server 2000. Can anyone point us in the =right direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space =for object 'tblTabl31' in database 'Database1' because the 'PRIMARY' =filegroup is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR =1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=3DSave&InID=3D25449&SSN=3D531067163&FileClosedDa=te=3D&FileNumber=3D&FirstName=3DMARY&MiddleInitial=3D&DAP==3D1&LastName=3DTARDIN&SAT=3D101&ApplicationDate=3D02%2F06%2F=2006&EffectiveDate=3D10%2F17%2F2003&Las .. . .
--=_NextPart_000_0007_01C62CB5.99712670--|||THe database is set up for automatic unrestricted growth, and there is
plenty of disk space on the drive. For some reason, whenever the data file
gets to 928MB, we get the error message and can't run the app until we
shrink the database to below 928MB. Why does that happen?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
>I would also assume taht the datafile in the filegroup are not setup
> for automatic growth.
> HTH, Jens Suessmeyer.
>|||This is a multi-part message in MIME format.
--030903070503060406070405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
"The database"? Which part of the database? Are you talking about the
log file(s)? One of the files in the PRIMARY filegroup? All of the
files in the PRIMARY filegroup? Files in some secondary filegroup?
Can you please post the results of:
EXEC sp_helpfile;
In the DB in question. It's not that we don't trust you, it's just that
we prefer to deal in black & white (this is a troubleshooting process).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Dean J Garrett wrote:
>THe database is set up for automatic unrestricted growth, and there is
>plenty of disk space on the drive. For some reason, whenever the data file
>gets to 928MB, we get the error message and can't run the app until we
>shrink the database to below 928MB. Why does that happen?
>
>"Jens" <Jens@.sqlserver2005.de> wrote in message
>news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
>
>>I would also assume taht the datafile in the filegroup are not setup
>>for automatic growth.
>>HTH, Jens Suessmeyer.
>>
>
>
--030903070503060406070405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>"The database"? Which part of the database? Are you talking about
the log file(s)? One of the files in the PRIMARY filegroup? All of
the files in the PRIMARY filegroup? Files in some secondary filegroup?<br>
<br>
Can you please post the results of:<br>
</tt><tt> EXEC sp_helpfile;<br>
In the DB in question. It's not that we don't trust you, it's just
that we prefer to deal in black & white (this is a troubleshooting
process).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Dean J Garrett wrote:
<blockquote cite="midO3v5omPLGHA.2300@.TK2MSFTNGP15.phx.gbl" type="cite">
<pre wrap="">THe database is set up for automatic unrestricted growth, and there is
plenty of disk space on the drive. For some reason, whenever the data file
gets to 928MB, we get the error message and can't run the app until we
shrink the database to below 928MB. Why does that happen?
"Jens" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:Jens@.sqlserver2005.de"><Jens@.sqlserver2005.de></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com">news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--030903070503060406070405--|||This is a multi-part message in MIME format.
--=_NextPart_000_0007_01C62CD1.B9030E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Here is the output from sp_helpfile. When I use Enterprise Mgr. and edit =the properties for the database "CAA" I see that the Checkbox for ="Unrestricted Growth" is checked. There is several GB on the drive, so =we thought the database would continue to grow unrestricted until all =the space is taken up. Instead we get the error once the CAA_Data.MDF =file grows to around 928MB. The only way we can get the ASP application =running again is to delete records thus reducing the size of the .MDF =file.
CAA_Data
1 F:\MSSQL\Data\CAA_Data.MDF PRIMARY 950272 KB Unlimited 5% data only
CAA_Log
2 F:\MSSQL\Data\CAA_Log.MDF NULL 5120 KB Unlimited 5% log only
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message =news:%23UNbpnQLGHA.3944@.tk2msftngp13.phx.gbl...
"The database"? Which part of the database? Are you talking about =the log file(s)? One of the files in the PRIMARY filegroup? All of the =files in the PRIMARY filegroup? Files in some secondary filegroup?
Can you please post the results of:
EXEC sp_helpfile;
In the DB in question. It's not that we don't trust you, it's just =that we prefer to deal in black & white (this is a troubleshooting =process).
--
mike hodgson
http://sqlnerd.blogspot.com=20
Dean J Garrett wrote: THe database is set up for automatic unrestricted growth, and there is plenty of disk space on the drive. For some reason, whenever the data =file gets to 928MB, we get the error message and can't run the app until we shrink the database to below 928MB. Why does that happen?
"Jens" <Jens@.sqlserver2005.de> wrote in message news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.
--=_NextPart_000_0007_01C62CD1.B9030E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Here is the output from sp_helpfile. =When I use Enterprise Mgr. and edit the properties for the database "CAA" I see =that the Checkbox for "Unrestricted Growth" is checked. There is several GB on =the drive, so we thought the database would continue to grow unrestricted until all =the space is taken up. Instead we get the error once the CAA_Data.MDF file =grows to around 928MB. The only way we can get the ASP application running again =is to delete records thus reducing the size of the .MDF file.
CAA_Data
1 F:\MSSQL\Data\CAA_Data.MDF PRIMARY 950272 KB =Unlimited 5% data only
CAA_Log
2 F:\MSSQL\Data\CAA_Log.MDF NULL 5120 KB Unlimited =5% log only
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com Dean J Garrett wrote: THe database is set up for automatic =unrestricted growth, and there is plenty of disk space on the drive. For some reason, whenever the data =file gets to 928MB, we get the error message and can't run the app until we shrink the database to below 928MB. Why does that happen?
"Jens" =wrote in message news:=1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
I would also assume taht =the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.
--=_NextPart_000_0007_01C62CD1.B9030E10--|||I don't know either.
There are some funky things that Windows sometimes does in the way of
reserving disk space for virtual files, that could be involved.
Have you tried the simple expedient of rebooting the server?
Josh
On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
wrote:
>We have an SQL Server app written in ASP that suddenly has an error after 2
>years of operation, and we're having trouble locating the problem. Here is
>the error message below. The reference in the Knowledgebase for this error
>doesn't seem to apply to us. There is plenty of space left on the drive. I
>believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>is full.
>/Household.asp, line 298
>a.. Browser Type:
>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>a.. Page:
>POST 700 bytes to /Household.asp
>a.. POST Data:
>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>. . .
>|||OH yes, we've tried everything. We keep trimming out records to allow the
app to keep running, but over time (usually just a few days), the MDF file
size grows to that magical limit of around 928MB and then we see the error
again. The drive has 17GB of available storage.
"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>I don't know either.
> There are some funky things that Windows sometimes does in the way of
> reserving disk space for virtual files, that could be involved.
> Have you tried the simple expedient of rebooting the server?
>
> Josh
>
> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error after
>>2
>>years of operation, and we're having trouble locating the problem. Here is
>>the error message below. The reference in the Knowledgebase for this error
>>doesn't seem to apply to us. There is plenty of space left on the drive. I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the
>>right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space
>>for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>|||Why would you notice this several times? If the file grow to this limit (and the problem occurs),
then clearly you need a database size > that size. So just expand the database size and monitor so
you have fr ee space. Autogrow has its issues and these things does happen (files doesn't
autogrow -> error message), search the archives for old posts and technical details. So, just expand
the file size manually and you will be fine. Oh, and don't shrink:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
> OH yes, we've tried everything. We keep trimming out records to allow the app to keep running, but
> over time (usually just a few days), the MDF file size grows to that magical limit of around 928MB
> and then we see the error again. The drive has 17GB of available storage.
>
>
> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error after 2
>>years of operation, and we're having trouble locating the problem. Here is
>>the error message below. The reference in the Knowledgebase for this error
>>doesn't seem to apply to us. There is plenty of space left on the drive. I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>|||We tried to expand the size, but it won't let us type in a value larger than
1200MB for some reason. I have no idea why since the drive has 17GB is free
space. So our problem is that we must keep deleting records in the database
so the MDF file won't exceed this "magical" limit.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
> Why would you notice this several times? If the file grow to this limit
> (and the problem occurs), then clearly you need a database size > that
> size. So just expand the database size and monitor so you have fr ee
> space. Autogrow has its issues and these things does happen (files doesn't
> autogrow -> error message), search the archives for old posts and
> technical details. So, just expand the file size manually and you will be
> fine. Oh, and don't shrink:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
>> OH yes, we've tried everything. We keep trimming out records to allow the
>> app to keep running, but over time (usually just a few days), the MDF
>> file size grows to that magical limit of around 928MB and then we see the
>> error again. The drive has 17GB of available storage.
>>
>>
>> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error
>>after 2
>>years of operation, and we're having trouble locating the problem. Here
>>is
>>the error message below. The reference in the Knowledgebase for this
>>error
>>doesn't seem to apply to us. There is plenty of space left on the drive.
>>I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the
>>right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space
>>for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY'
>>filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
>>1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||Additionally, when we try to manually increase the size, we get the error
message:
Error 5149: MODIFY FILE encountered operating system error 112 (There is not
enough space on the disk) while attempting to expand the physical file. When
we look at the drive, there is 17GB of free space as reported by Windows.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
> Why would you notice this several times? If the file grow to this limit
> (and the problem occurs), then clearly you need a database size > that
> size. So just expand the database size and monitor so you have fr ee
> space. Autogrow has its issues and these things does happen (files doesn't
> autogrow -> error message), search the archives for old posts and
> technical details. So, just expand the file size manually and you will be
> fine. Oh, and don't shrink:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
>> OH yes, we've tried everything. We keep trimming out records to allow the
>> app to keep running, but over time (usually just a few days), the MDF
>> file size grows to that magical limit of around 928MB and then we see the
>> error again. The drive has 17GB of available storage.
>>
>>
>> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error
>>after 2
>>years of operation, and we're having trouble locating the problem. Here
>>is
>>the error message below. The reference in the Knowledgebase for this
>>error
>>doesn't seem to apply to us. There is plenty of space left on the drive.
>>I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the
>>right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space
>>for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY'
>>filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
>>1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||> We tried to expand the size, but it won't let us type in a value larger
> than 1200MB for some reason.
What is 'it' referring to? Enterprise Manager? What happens if you run a
statement like this one:
ALTER DATABASE <db_name>
MODIFY FILE
(NAME = <logical_datafile_name>,
SIZE = 5GB);
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:eTxxNspLGHA.3960@.TK2MSFTNGP09.phx.gbl...
> We tried to expand the size, but it won't let us type in a value larger
> than 1200MB for some reason. I have no idea why since the drive has 17GB
> is free space. So our problem is that we must keep deleting records in the
> database so the MDF file won't exceed this "magical" limit.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> Why would you notice this several times? If the file grow to this limit
>> (and the problem occurs), then clearly you need a database size > that
>> size. So just expand the database size and monitor so you have fr ee
>> space. Autogrow has its issues and these things does happen (files
>> doesn't autogrow -> error message), search the archives for old posts and
>> technical details. So, just expand the file size manually and you will be
>> fine. Oh, and don't shrink:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Dean J Garrett" <info@.amuletc.com> wrote in message
>> news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
>> OH yes, we've tried everything. We keep trimming out records to allow
>> the app to keep running, but over time (usually just a few days), the
>> MDF file size grows to that magical limit of around 928MB and then we
>> see the error again. The drive has 17GB of available storage.
>>
>>
>> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error
>>after 2
>>years of operation, and we're having trouble locating the problem. Here
>>is
>>the error message below. The reference in the Knowledgebase for this
>>error
>>doesn't seem to apply to us. There is plenty of space left on the
>>drive. I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the
>>right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space
>>for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY'
>>filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
>>1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||This is an error thrown from the OS to SQL Server, so you need to investigate why the OS doesn't
think there is more space or allow SQL Server to use more space. Perhaps there's some kind of user
quota (the user being the SQL Server service account)? Or database files being compressed (not
supported)?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:OROqI0pLGHA.1532@.TK2MSFTNGP12.phx.gbl...
> Additionally, when we try to manually increase the size, we get the error message:
> Error 5149: MODIFY FILE encountered operating system error 112 (There is not enough space on the
> disk) while attempting to expand the physical file. When we look at the drive, there is 17GB of
> free space as reported by Windows.
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> Why would you notice this several times? If the file grow to this limit (and the problem occurs),
>> then clearly you need a database size > that size. So just expand the database size and monitor
>> so you have fr ee space. Autogrow has its issues and these things does happen (files doesn't
>> autogrow -> error message), search the archives for old posts and technical details. So, just
>> expand the file size manually and you will be fine. Oh, and don't shrink:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Dean J Garrett" <info@.amuletc.com> wrote in message
>> news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
>> OH yes, we've tried everything. We keep trimming out records to allow the app to keep running,
>> but over time (usually just a few days), the MDF file size grows to that magical limit of around
>> 928MB and then we see the error again. The drive has 17GB of available storage.
>>
>>
>> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error after 2
>>years of operation, and we're having trouble locating the problem. Here is
>>the error message below. The reference in the Knowledgebase for this error
>>doesn't seem to apply to us. There is plenty of space left on the drive. I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||If you have enough disk space my guess is you are possibly using another
file system other than NTFS ?
I had a client a while ago that hit this same issue they were using FAT32
and were hitting the max file size limit due to the file system maximum
which in there case i think was 4GB if i remember correctly...
Are you using NTFS?
possibly maybe also some form of disk quota for the user account ?
my 2 cents
HTH
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:usAL8etLGHA.1048@.TK2MSFTNGP10.phx.gbl...
> This is an error thrown from the OS to SQL Server, so you need to
> investigate why the OS doesn't think there is more space or allow SQL
> Server to use more space. Perhaps there's some kind of user quota (the
> user being the SQL Server service account)? Or database files being
> compressed (not supported)?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OROqI0pLGHA.1532@.TK2MSFTNGP12.phx.gbl...
>> Additionally, when we try to manually increase the size, we get the error
>> message:
>> Error 5149: MODIFY FILE encountered operating system error 112 (There is
>> not enough space on the disk) while attempting to expand the physical
>> file. When we look at the drive, there is 17GB of free space as reported
>> by Windows.
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> Why would you notice this several times? If the file grow to this limit
>> (and the problem occurs), then clearly you need a database size > that
>> size. So just expand the database size and monitor so you have fr ee
>> space. Autogrow has its issues and these things does happen (files
>> doesn't autogrow -> error message), search the archives for old posts
>> and technical details. So, just expand the file size manually and you
>> will be fine. Oh, and don't shrink:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Dean J Garrett" <info@.amuletc.com> wrote in message
>> news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.gbl...
>> OH yes, we've tried everything. We keep trimming out records to allow
>> the app to keep running, but over time (usually just a few days), the
>> MDF file size grows to that magical limit of around 928MB and then we
>> see the error again. The drive has 17GB of available storage.
>>
>>
>> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.4ax.com...
>>I don't know either.
>> There are some funky things that Windows sometimes does in the way of
>> reserving disk space for virtual files, that could be involved.
>> Have you tried the simple expedient of rebooting the server?
>>
>> Josh
>>
>> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
>> wrote:
>>We have an SQL Server app written in ASP that suddenly has an error
>>after 2
>>years of operation, and we're having trouble locating the problem.
>>Here is
>>the error message below. The reference in the Knowledgebase for this
>>error
>>doesn't seem to apply to us. There is plenty of space left on the
>>drive. I
>>believe we're using SP3 of SQL Server 2000. Can anyone point us in the
>>right
>>direction? Thanks!!
>>
>>a.. Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate
>>space for
>>object 'tblTabl31' in database 'Database1' because the 'PRIMARY'
>>filegroup
>>is full.
>>/Household.asp, line 298
>>a.. Browser Type:
>>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
>>1.0.3705)
>>a.. Page:
>>POST 700 bytes to /Household.asp
>>a.. POST Data:
>>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>>
>
No comments:
Post a Comment