• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Disk Full Error - transaction rolled back

I verified that there was plenty of memory after getting this error.  It occured when trying to connect ISQL to the database.  Any idea what I should check next?
0
rickwinterkorn
Asked:
rickwinterkorn
1 Solution
 
rickwinterkornAuthor Commented:
Edited text of question
0
 
gilmerCommented:
Could you give some specs on the system, and the exact error message.
0
 
vsriksCommented:
Get back to me on the following things.  What does sp_who output give?  if it is under unix what does ps -ef gives.  Also sp_lock shows what types of lock.  lastly give me information on what version (Excat) of dataserver and ISQL version

0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
kaos87Commented:
Are you getting this message from a Client connected to a database server?

If yes, the system partition on the server where the database server is installed is very low on space.

If no, (the case you are using a local database) the partition where the database engine and/or database file are on is very low on space.  

I had this problem once and I clear up some unused files to do some space on the hard drive and it was ok after.

0
 
rickwinterkornAuthor Commented:
Kaos87..thanks for the info, I cleared some space in the partition and it works fine now.  
0
 
spacebrainCommented:
you should reject the answer from vsriks
Koas87 post an answer if rickwinterkorn does
Just a thought like that....
0
 
rickwinterkornAuthor Commented:
Koas87 - Post an answer..or just something ...so that I can accept it as answer and give you credit..Thanks again
0
 
kaos87Commented:
Are you getting this message from a Client connected to a database server?

If yes, the system partition on the server where the database server is installed is very low on space.

If no, (the case you are using a local database) the partition where the database engine and/or database file are on is very low on space.   

I had this problem once and I clear up some unused files to do some space on the hard drive and it was ok after.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now