Error: 1105, Severity: 17, State: 2

Hi ,

I have a SQL Server 2000 database on my C drive.

Over the weekend my C drive got full due to my transaction log files ballooning up.

At that point none of my users were able to log into their the VB application and enter data.

I freed up some disk space, and then the users were able to log in fine, except for a certain column variable(aggregate) values were negative.

I deattached the DBs and Ldf files and made copies of them on to a test envirnoment. Within the test environment, I ran SQL Query Analyzer with SQL statments that did give me the aggregate values as negative. This matched my VB application values aswell.

I ran

DBCC CHECKDB -- no errors

DBCC DBREINDEX -- no errors

Our programming vendor tells us the DBs are corrupt.

From Error file

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2007-01-30 19:43:56.95 spid52 C:\Program Files\Microsoft SQL Server\MSSQL\Data\tempdb.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-01-30 19:43:56.98 spid52 Error: 1105, Severity: 17, State: 2

2007-01-30 19:43:56.98 spid52 Could not allocate space for object '(SYSTEM table id: -900439724)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..

2007-02-23 09:56:21.21 spid56 C:\Program Files\Microsoft SQL Server\MSSQL\Data\ActgSQL.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-02-23 09:56:21.24 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 09:56:21.24 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 11:11:09.74 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 11:11:09.74 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 15:50:19.27 spid59 Process ID 53 killed by hostname ORCHID, host process ID 3360.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I thought I had backups but I don t. So now I m in a big bind. Help!!

Any suggestions ?

No.. i don't think your database is corrupted. the only thing is that it could not have able to commit the transaction done when there was no space in the desk.. if your statement are not concluded in BEGIN TRAN / COMMIT TRAN.. some data inconsistancy may occur... As such the database may not be corrupted as a whole. This is a common problem when there is no DBA or DBA background person around. You need to keep a track of all backups which u r taking and also TL and TempDb growth etc..

Madhu

Error: ""The transaction has exceeded the allotted time"

I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

XavierWas any one able to find an answer to this? I'm getting the exact same error. Thanks.

Originally posted by xfolch
I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

Xavier|||I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||So what is the difference between the two: "Local Packages" and "Meta Data Services Packages".

Thanks.

Originally posted by xfolch
I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||It works the same, but it's store in a different format:

When you save a Data Transformation Services (DTS) package, you save all DTS connections, DTS tasks, DTS transformations, and workflow steps and preserve the graphical layout of these objects on the DTS Designer design sheet.

You can save a package to:

Microsoft SQL Server.
With this default save option, you can store a package as a SQL Server msdb table, allowing you to: store packages on any instances of SQL Server on your network; keep a convenient inventory of saved packages in SQL Server Enterprise Manager; and create, delete, and branch multiple package versions during the package development process.

SQL Server 2000 Meta Data Services.
With this save option, you can maintain historical information about the data manipulated by the package. However, Meta Data Services and the repository database must be installed and operational on your server. You can track the columns and tables that are used by the package as a source or destination. You also can use the data lineage feature to track which version of a package created a particular row. You can use these types of information for decision-support applications.

error while starting MSDTC service

hey experts!!
I got this from Microsoft Management Console when starting the MSDTC service.
Could not start the Distributed Transaction Coordinator Service on local computer
Error 1067: The process terminated unexpectedly.
Can someone plz tell me wht the hell this means and how can i fix it. it does not gives any other info.
thankscan someone plz help me here. if you need more information
at least derect me somewhere as i am new to this sql and
ms dtc stuff.
thnks

Error while shrinking transaction log

Hi all,

while I shrinked transaction log using command "dbcc shrinkfile (logfile)" in query analyzer, the error message " cannot find logfile in sysfiles" was shown up.

The I list out content of sysfiles, and found that sysfiles doesn't contain logfile.

Can anybody tell me how to eliminate error in order to shrink transaction log?

Thanks in advances.

PaulYou need to enter the correct filename for your tempdb database. Default is templog. Right click on tempdb to find your correct filename.
Try:
USE tempdb
go
DBCC SHRINKFILE (TEMPLOG)|||Martsar,

Thanks for your input.

I checked and found that my syntax and log file name were correct, but preceding error message was still there. But I did successfully to shrink TEMPLOG.|||to check the filenames of db and log execute from your database:

use yourDB
go
sp_helpfile

The syntax to shrink db and log is:
DBCC SHRINKDATABASE (N'dbName/or logName', 0)

Also, try to shrink log in EM.