When Creating Brainstat Images using FuncTool, Images are Not Created due to Software Problem.

When Creating Brainstat Images using FuncTool, Images are Not Created See Long Description CSO 1-2997480461 Trackwise PR # 2811899. When the customer tries to create Brainstat images using FuncTool the images are not created and no errors are displayed or logged. But a FuncTool core file is always written to /usr/g/service/log: core.MRFunctool . The problem occurs using both 15.0 M4 and 15.0 M4A software. This site has two systems, one is 1.5T and the other is 3.0T. The same problem occurs identically on both systems. The problem occurs using the following workflow. It fails at step 21. 1. Select Perfusion Series and Launch Functool 2. Open the wizard and click on "Apply Registration" button. 3. Click Next button once the registration is done. 4. Adjust the threshold to make sure that the brain is outlined in green and all the anatomy inside the image displays green lines. 5. Navigate to the desired slice by clicking on location annotation. 6. Click Next button. Use the default 5 or change the value to desired value 12. 7. Click Next and click Compute. Click Next again. 8. Click on the button "axis of symmetry". 9. Drop an ellipse ROI 10. Press and hold Control key and select Axis line and Ellipse ROI 11. Click on "create Symmetrical ROIs" button on the wizard page. Another ROI is created. 12. Press Spacebar key to generate negative enhancement curves 13. Close the wizard. 14. Click on File/Save/Report button on the control panel. 15. Select "Functional Maps" on the menu. 16. Select "select from Available Maps" and select "Multiple Locations". 17. Select Next. 18. Select a Functional Map 19. Click on Next 20. Select "Save as SCREENSAVE images(s)" 21. Click on Save <--- failure point 22. Click on File/Save/Report button on the control panel. 23. Select "Generate Report" on the menu. 24. Select "SSAVE" tab and select "Multiple Locations" 25. Click on Generate button. The FE tried performing a recover image database, and also reloaded software including upgrading from 15.0 M4 to 15.0 M4A software with no change to symptoms. Since this was happening on both of the customer's scanners, he didn't try replacing any hardware.