If a BiBusTKServerMain process terminates unexpectedly, a dump file is created in the ../bin directory.  In order to troubleshoot the termination of these processes, follow the steps below to use the Windows Debug (Windbg) tool available from Microsoft.

Use the Windbg tool to open the dump file to help determine the cause of the BiBusTKServerMain crash.

Steps:
Download and Install Windbg from Microsoft here

1. From the Start menu, launch Windbg.
2. From the File menu, choose Symbols File Path
3. In the Symbol Search Path dialog box, enter \\localhost\Symbols\dbg
4. Click Ok
5. From the File menu, choose Open Crash Dump
6. Navigate to the dmp file and click Open
7. Click Yes to the Save Workspace dialog
You may see an error such as:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll –
This dump file has an exception of interest stored in it
The stored exception information can be accessed via .exr

8. On the white line at the bottom of the Command window type .exr -1 and hit enter
9. In the command line at the bottom of the Command window, type  k 20 and hit enter (This will show the to 20 lines of the stack trace)
10. Click on “View” in the top menu bar and select “Call Stack” – A new window will open
11. Click on “View” in the top menu bar and select “command” – a new window will open
12. Click on “View” in the top menu bar and select “locals” – a new window will open
13. Click on “View” in the top menu bar and select “processes and threads” – a new window will open
14. Click on “Window” in the top menu bar and select “Undock all”.
15. Click on “Window” in the top menu bar and select “Vertically tile floating windows” – The screen should show four windows
16. In the call stack window (“Calls”), click on the button “More” at the top until you get to the bottom of the stack
17. We need to locate an entry similar to the following:  RSReportService!RSASyncExecutionThread::run+0x606
18. Double click on this entry. Then move to the “Locals” Window and look for the following thread: “this”
19. Expand the plus sign next to “this” and you should see the following: m_pPrimaryRequest
20. Expand the thread m_pPrimaryRequest and you should see the following: m__objectPath
21. Expand the thread m__objectPath and you should see the following: m__value
22. Note down the value corresponding to the entry. It could be or it could indicate a particular report name.

If the value shows , it could be that the system did not have enough resources but is not conclusive.