Posts Tagged ‘error’

After 10.5.8 upgrade, -36 error prevents files from being opened

Monday, August 10th, 2009

Description

Customers running outdated versions of ExtremeZ-IP with the Mac OS X 10.5.8 update could encounter a -36 error when opening a file stored on a network volume.

The error seems specific to opening the file using a double click. The problem doesn’t appear to happen when using the “File – Open” dialog.

Solution:

Upgrade to the latest version of ExtremeZ-IP:
ExtremeZ-IP Latest Releases Web Page

Note: For customers running Windows 2000, you must install version 5.4 (the last version to support Windows 2000).

Error: Incorrect Key File For Table [Windows]

Wednesday, January 23rd, 2008

Summary:

The MassTransit Engine may inadvertently shut down, and will not properly restart. Within the Application Log of the Windows Event Viewer, the following error message may be displayed:

SA_Exception[xxxx]: DB_Files_Edit: Incorrect key file for table ‘tablename‘; try to repair it.

Commonly, tablename may be referenced as ‘dfiles’

Description:

This error indicates that the table listed within the error message has become corrupt, and must be repaired. In most cases, the table can easily be fixed with through the MySQL command line. Follow this procedure to repair failed tables:

  1. Open a Windows command prompt
  2. Navigate to the MySQL monitor command-line utility, which may be found at this location:
    C:\Program Files\MySQL\MySQL Server X.X\bin
  3. Invoke the MySQL monitor utility with the following command:
    mysql -uroot -p
  4. Enter your root password as specified during the initial installation of MySQL server.
  5. After successfully logging in, you should see a ‘mysql>’ prompt.
  6. At the ‘mysql>’ prompt, type the command: repair table tablename quick;
    NOTE: tablename should be the name of the table listed in the Event Viewer error message, such as dfiles. Note also that the semi-colon character (;) at the end of the statement is required.
  7. When the repair process is completed, the results of the process will be displayed within the terminal.
  8. You may now close your terminal window.

The status message should indicate that the repair status was successful by indicating “OK.” If any further errors result, it is important to contact Group Logic technical support for additional troubleshooting and repair instructions.

After a successful repair has been completed, you may now be able to restart your MySQL Service, followed by the MassTransit Engine Service.

File Not Found Error when Forwarding a Job

Tuesday, February 15th, 2005

Summary:

MassTransit logs a “file not found” error when attempting to forward a file within a Forward To folder.
This occurs when the file sitting in a Forward To folder has been manually moved or deleted and is no longer present.

Description:

MassTransit logs a “file not found” error when attempting to forward a file within a Forward To folder. This error occurs when a job is no longer located within a Forward To folder in the To Send mailbox of a MassTransit address book entry. The probable cause is that a user has manually moved or deleted the job.

To clear the error, go the MassTransit interface and click on the Job Browser button. Use the selector to choose the corresponding address book entry in which the Forward To folder has been placed. You may also select To Send as a selector. You will then be able to view the job in the browser. Go ahead and click on the job to highlight it. Then click the remove button. The job will be removed from the job browser window and you will no longer receive a file not found error in the log.