I'm not an SQL person by any stretch but the error I received today while tinkering around here did indicate the db was full. I ran into this on an old version of SQL at work and had to purge the logs and then set Autogrowth. Pulled my hair out over it. Still don't really understand it.
But perhaps could try using SQL Server Management Studio (SSMS), enable autogrowth and unrestricted file growth for the db. Also purge any logs.
Just thinking out loud.
-Karl
1986, 32' Sedan, twin 360ci, 275hp Chrysler's w/ K&N flame arrestors