Skip to content
logo Knowledgebase

TSSimba64 and Crystal Reports errors after upgrading to 26.1

Created on  | Last modified on 

Summary

After upgrading to 26.1, when running Crystal reports in Sage 300 CRE on large datasets, you receive a TSSimba64 error. The report can also appear to take longer to run.

Description

Sometimes, the TSSimba64 error stays hidden in the background, making it appear that the report is taking longer to generate. Perform the following steps to bring it to the foreground:

  1. Open Windows Task Manager.
  2. Under Apps, expand Sage.CRE.CoreProxy.
  3. Double-click on TSSimba64 to bring the error message to the foreground.

If you don’t see TSSimba64 right away, the report can still be generating. Sometimes, the TSSimba64 didn’t appear until the memory usage reached a certain threshold (approximately 5300-5500 MB).

After a TSSimba64 error occurs, other Crystal Reports that previously ran successfully can also begin to fail. These subsequent failures can manifest as additional TSSimba64 errors or as the misleading messages (like "is not a valid Crystal Report design"). The issue persists until you reboot the system.

Initial error message variations

  • Could not get output column data via TSSimba proxy. Error = 80004005
  • Could not get output column data via TSSimba proxy. Error= 8007000E
  • Could not invoke TSSimba proxy. Error = 80004005
  • Could not invoke TSSimba proxy. Error = 800700A4

Subsequent error message variations

  • Could not create TSSimba invoker object.  Error= 800700A4
  • Could not invoke TSSimba proxy. Error= 8007000E

Subsequent error messages without the TSSimba64 heading

  • Crystal Report Windows Forms Viewer "Unknown Database Connector Error" 
  • [Application] [report file path]: needs to be upgraded or is not a valid Crystal Report design
  • [Application] [report file path]: is not a valid Crystal Report design
  • This program has quit. Memory reallocation failed [TS 3806]

Resolution

We're currently investigating this issue. We'll provide updated information as we have it.

Workarounds

  • Reboot the machine to restore functionality of Crystal reports that were functioning before the error
  • Use a Report Designer report or an Inquiry with similar information as a replacement
  • Limit the data by using parameters in reporting (if applicable)
  • Archive data to reduce database size before running the report