Error while committing an Edit Set:  Unable to create SQL Command and/or create export files required for commit. Database not altered.

Version 1

    Details

    When attempting to commit an edit set (even one with no actual changes), I receive an error just after the commit starts: "Unable to create SQL Command and/or create export files required for commit. Database not altered." Then Administrator crashes.  The only modification to the database is in the DBStatus field of HEATDb which is set to a value of: "C!Building Commit files - started at 08:09:57 by Admin.", which prevents users from logging in (CallLog or Admin) until that field is cleared.


    Resolution

    This is usually a rights issue on the creation of the Commit.000 file which is a file HEAT creates prior to and during all Edit Set commit processes.

    Initially you need to clear out that DBStatus value in the database, otherwise no further commits can be applied and no logins will be allowed.  To clear this value run the following to your SQL Server:
    UPDATE HEATDb
    SET DBStatus = ''


    Then to get past the commit error:

    First Option:
    When launching the Administrator module to commit your Edit Set, launch it by right-clicking and selecting Run as Administrator.

    Second Option: 
    Depending on the host OS of where you are launching Administrator from, this Commit.000 file may be created in different directories.  You could look into re-directing where the file is being created.  To do this:
    Create or alter the "Directory" string value for the following registry key to include the full path to the preferred location where the login has write rights:

    HKEY_CURRENT_USER\Software\FrontRange Solutions\HEAT\Admin\Commit\Directory.