Revenue recognition job hangs and needs reboot of servers

Question

We are on SAP BPC v7.0 SP6.1, using Microsoft Office 2007 and Internet Explorer 7.  We have two environments - Production and QA.  Production so far is running fine; QA is on a smaller environment. 
I am an application user and load final production files into QA each month.  For the past two months when trying to run the revenue recognition job for April 2010 and again for May 2010, the job just hangs where it would normally take about two minutes to complete.  Both times it was the only job running at the time, as no one was using the QA environment.  I had to terminate the job (which might leave the job running in the background) and have our Server team reboot our two servers (Application and SQL Server Analysis Services).  Then the revenue recognition job completes.
Depending if I terminate and resubmit the revenue recognition job, I might get the following detail log message:
Execute formulasError
Failed to commit transaction
1 errors writing data
Send through SendGovenor failed
Last week, our DBA set the QA databases to Simple instead of Full recovery and shrank the transaction log files.  I ran a test revenue recognition for July 2010 and the DBA tried to monitor the environment, but he could not see any job committing or any activity on the database.  I ended up rebooting our servers to complete the test.
Has anyone experience similar problems and was able to resolve it.  Any ideas would be appreciated.  Thanks.
Bucky

Answer 1

Hi Sorin Radulescu,
I load the initial billing file using the Import logic script and select the data file and transformation file.  I click on the Merge data values option; click No to run default logic; and click No, do not check work status settings.  Once the import completes, I run the revenue recognition logic for the accounts and periods I am working with.
I compared our Production transformation file, default logic script (which I am not running), and revenue recognition logic script to QA and they both match.  My problem is when I run the exact same revenue recognition job in QA, the job just sits in running status but should finish in a couple of minutes.  I would let it run for a couple of hours in QA, then terminate the job and have our two servers rebooted, then the same revenue recognition job runs to completion within a couple of minutes.
I am just wondering if there could be some other setting that does not let the job submission kick off the actual update to the database.  To make sure the database was not hosed from the terminated revenue recognition job, I ran a different but smaller job and it completed.  Then I would ask for the reboot and resubmit the revenue recognition job and it completes.
I will let our DBA know about monitoring the dllhost.exe for amount of memory used.  But the last time he tried to check for any activity on the database he could not see anything, but I do not know if he was checking dllhost.exe or some other files.
Thanks for your response and suggestions.  Since this is our QA environment (which I try to keep current with Production), I am trying to see if I can identify the cause and fix it, in case it carryover to our Production environment.
Regards,
Bucky