Stream Read Error

When attempting to launch Cyrious SMS the loading halts just after the “Loading Reports…” and an error appears notifying you of a Stream Read Error.

High. The user is unable to load the program until resolved.

There may potentially be several causes for this error, in the case that prompted this article the user experienced corruption in the memo fields on the Store Information Database table. Below is a summary of a few most likely causes of this problem.

  • Inadequate security permissions to the database files or other critical system files utilized by Cyrious.
  • Inadequate share permissions to the database files or other critical system files utilized by Cyrious.
  • Corruption on essential database files utilized by Cyrious.
  • Ensure the sharing and NTFS permissions on the database files utilized by Cyrious are appropriately set.
  • Check the database for corruption using the dbrebuild utility.

If you have confirmed the sharing and NTFS permissions are properly set and you're receiving this error from the server as well you may try these advanced level troubleshooting steps. It is highly recommended that you make a backup of all files before performing these steps. Proceed at your own risk.

  • Swap the Data for a new blank database. If the program opens you have isolated the problem to the database itself. To determine the table causing the problem follow the next series of steps.
  • Begin copying database tables from the backed up Data into the blank database you just tested. Re-test after updating a block of database tables. The purpose of this step is to isolate which set of files is actually causing the error. It's best to choose relatively large blocks of files then narrow down your testing once you've identified which block of files started causing the error to occur.
  • In the issue that prompted this article the user was found to have corruption in the memo fields of the Store Information Database table. The final resolution required the restoration of a backup of the Store Information Database table.
  • Reported : 08/12/2010
You could leave a comment if you were logged in.