Server Busy Error (or startup lag) with Solid Edge

Server Busy Error (or startup lag) with Solid Edge

If a user has the default printer set to a Network Printer, and the printer is off or not-contactable, then Solid Edge may experience a significant lag or a Server Busy Error while checking the printer connection.

It is recommended in SE2024 that users have the default printer set to a local printer (it can by a physical printer, or a virtual printer such as Print to PDF) to avoid lag on startup.
    • Related Articles

    • Replace Background Sheet in Solid Edge Drawing (Draft)

      To replace the Background Sheet (template) in a Solid Edge Drawing (Draft), ensure you can see the Background sheets (if not, right click on a sheet and toggle Background on). Right-Click on the Background sheet to replace, and choose Replace ...
    • Tip - using the Solid Edge 2023 Open-Save Macro

      Tip - Run the Open-Save Macro It is often helpful after upgrading Solid Edge to a new version to also update all of your files to the new version too (this avoids some issues we have seen with working with very old files). The Open-Save macro is ...
    • Online Solid Edge 2023 videos and tutorials

      Siemens provides Solid Edge 2023 online help, which has a lot of resources available: Videos - Index of Solid Edge videos (siemens.com) - Solid Edge Video Gallery (siemens.com) - ensure you check topic groupings on the Left-Hand side. Tutorials and ...
    • Latest supported releases of Solid Edge

      The latest release of Solid Edge is Solid Edge 2024 Update 4. Please ensure that you disable your Antivirus program before installing the software or update, and run the installer by right-clicking on it and selecting "Run As Administrator". After ...
    • NOTICE: Problem with SE2024 Update 02, Build 003

      It has come to our attention that on the first day that Solid Edge 2024 Update 002 was released, the incorrect build (003) was posted to the Siemens Download Center instead of the correct build of Update 002 which is build 004. The incorrect build ...