Skip to main content

Troubleshooting: BRX Error 334 and "Method not Available in SDI mode"

How to clear BRX Error 334 in the Microvellum BSB processing center with the SDI system variable, and how to recover when Microvellum shows "Method not Available in SDI mode" or closes before you can type a command.

J
Written by Jordan Munoz

BRX Error 334 is an unhandled exception error that may occur in the Microvellum BSB processing center. To solve the issue, one must simply adjust the related system variable of the software, the Single Document Interface (SDI) system variable.

  • Step 1: Type the "SDI" in the command bar.

  • Step 2: This will bring up the SDI variable, with the default value of 0. Set the current value to 1.

  • Step 3: Process the work order once again.

  • Step 4: After processing is complete, close and re-open the software.

  • Step 5: Type in the SDI command again and set the variable to its default value of 0.

  • Step 6: Process a test work order to confirm that the error does not occur again. If it does, keep the SDI variable set to 1 consistently.

"Method not Available in SDI mode", or Microvellum Closes Before You Can Type SDI

Use this section only if Microvellum shows the message "Method not Available in SDI mode", or you set SDI to 1 using the steps above and Microvellum now closes before you can type a command. If Microvellum stalls on startup for another reason, these steps will not help; submit a support case instead.

If SDI has been left at 1 and Microvellum now shows "Method not Available in SDI mode", or closes on launch before the command line is usable, SDI cannot be reset from inside the software. It can be reset in the Windows Registry:

  1. Close Microvellum and BricsCAD/AutoCAD.

  2. Open the Registry Editor (regedit).

  3. Go to HKEY_CURRENT_USER\Software\Microvellum\Toolbox\R25.0\Toolbox-8101:409\Profiles\<<Unnamed Profile>>\Drawing Window

    • The version folder (R25.0 here) differs by version. The key name is a literal path the software creates, and it still uses the software's former name.

  4. Set SDIMode to 0.

  5. Start Microvellum again.

If you are not comfortable editing the registry, submit a support case and mark it Production Shutdown.

Did this answer your question?