You were running the TRUNCATEONLY in the shrinkfile. Did you try the backup log with truncateonly?

We actually aliased the admin account as the dbo user in the database.

From BOL...

Removes the inactive part of the log without making a backup copy of it and truncates the log. This option frees space. Specifying a backup device is unnecessary because...

It does not actually create a physical backup file, it's a way of clearing data from the transaction log.

Before you go through the whole detaching the db situation try running

BACKUP LOG <dbname> WITH NO_LOG

GO

Then run your dbcc shrinkfile.

Script out the proc and check the quoted_identifier and arithabort settings on the create procedure statement.

I have the compiled DLL, but can't find the pre-compilation source (lost in the job changeover a few months back). I can email you the dll and the procs if...

There was a patch between sp2 and sp3a that had a copy of the sqlmap70.dll in it. We had the same problem at my last place, when we replaced the...

Is this with sp3a?

Are you running VS.Net? I had the same problem, you'll need to compile in VB6.

Looks like you are trying to update (or insert) a record that is too long for the value specified in the column definition, ie. inserting a 10 character word into...

128 is the number of pages to shrink the file to. I usually use that if I want to shrink the file but still leave some space in it.

A small futz around with the dll will allow you to do puts as well. That and the creation of a new proc.

Run the following, replace DBNAME with your database name and FILEID with the file id.

BACKUP LOG DBNAME WITH NO_LOG

GO

USE DBNAME

GO

DBCC SHRINKFILE (FILEID, 128, TRUNCATEONLY)

GO

Try shrinking it using the fileid (SELECT NAME, FILEID FROM SYSFILES), use the same syntax, just replace the filename with the fileid.