Secure Lockdown seems to stop the writing of a log file

I have an interactive setup running custom software and the log file that is being open, written to, and closed, is not getting written while Secure Lockdown is running.  Is there any reason for this?  If so, is there a work around that you can suggest?  Thanks in advance.

Where (what path) and how is the log file being written?

The path is directly under C:\ in a folder synced with Dropbox.

and the writing is all done with file open and close.

FILE *tmp = fopen("heartbeat.txt","w");
fprintf(tmp, boost::posix_time::to_simple_string(now).c_str());
fclose(tmp);

What version of Secure Lockdown are you using? Is this script running froma a browser?

Secure Lockdown v.2
The application a local C++ application. run through a batch script calling the executable.  Not browser based.

Are you using the Working Directory feature in Secure Lockdown? Sometimes programs require this to work properly. There is not anything in particular that Secure Lockdown does to prevent writing to a specific folder location if a program wants to do that.

Also, if you're running a script to launch an application, Secure Lockdown may not be able to monitor the running app because it was launched from a script. It wont know what to monitor (for example to Keep it Running if it is closed)