You will most probably see this issue when you perform an upgrade to RightFax FP1 SR4. Although the OneText KB claims this is fix, but it is not. Anyway, a workaround for this is to run an SQL script to fix the disk space to 10GB. You really don’t want RightFax to tell you that there is 0% free space as it might stop process even if there is a lot of space in your database.
A caveat of this workaround is, of course, if your database is indeed 0%, RightFax will not know about it. However, if your database administrators have their own monitoring for database space, then this will mitigate the issue.
** NOTE: I am not a DBA admin, use at your OWN RISK ***
----------------------------- SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON GO ALTER PROCEDURE [dbo].[FreeDBSpace] AS /*WARNING: This version of the Stored Procedure called FreeDBSpace is to eliminate any system database calls. It returns only hard coded values to the FaxServer. This will eliminate the ability for the server to detect when the database is low on space available. If the database runs out of space with this version of FreeDBSpace, RightFax will not respond to low database space. This could result in loss of data or data corruption. ONLY USE THIS version of FreeDBSpace when you are sure that you have other SQL methods and alerts to protect your database from running out of space. */ SET NOCOUNT ON /* Declare a table variable that we can use to return the result set. */ declare @Drives table( Drive char(1), MB_Free int) INSERT INTO @Drives (Drive, MB_Free) VALUES ('C', 10000) SELECT * FROM @Drives RETURN -----------------------------