Supernzb logging on hangs1/4/2024 Troubleshooting for conflicts with other software Other software on the computer may conflict with the AutoCAD startup (e.g., antivirus, anti-spyware, or other security programs). If AutoCAD runs, remove /safemode and inspect the folder %appdata%\Autodesk\ApplicationPlugins to remove any plugin one by one to see which one causes AutoCAD to crash. Run AutoCAD with the start-up switch /safemode, see How to launch an AutoCAD Product without any plug-ins or add-ons.If there more than one display adapter exists, try to disable one of them from device manager in Windows.Then download the software installation files with Download Now and reinstall. Uninstall and reinstall Visual C++ libraries (see How to remove and reinstall Microsoft Visual C++ Runtime Libraries).Remove custom content. Custom content such as shortcuts, templates, menu/cui files, and tool palette files, may not be compatible, especially for previous releases of AutoCAD.The DLL file may have a version number as part of its file name, such as OGSCertificationUtility-6_3.dll. Rename the OGSCertificationUtility.dll file in C:\Program Files\Autodesk\AutoCAD 20xx by adding.If the Autodesk Desktop App launches with a spinning circle, open the Task Manager and end the task for the Autodesk Desktop App.Uninstall A360 Desktop (see How to uninstall A360 Desktop and A360 Desktop Retirement - June 19th, 2018).Make sure that all system requirements are met:.Delete temporary files (see How to delete temporary files in Windows).Try using only one monitor if multiple monitors are used.Disable hardware acceleration (see Starting AutoCAD-based products without hardware video acceleration).Reset license files (see Reset license activation for an Autodesk product for stand-alone license with single-user access).Force software to use the high-performance graphics adapter (see How to configure Autodesk software to use high performance graphics).Update to the latest graphics driver (see How to update to the latest certified video driver).Reset AutoCAD to default settings (see How to reset AutoCAD to defaults).Install the latest updates for AutoCAD (see Install Updates, Add-ons, and Enhancements).The only side effect is that the first user that logs in on Monday may be greeted with a Sage error (if smartporsting or w3dbsmgr.exe fail to restart with the script) or a lethargic performance until the Sage's memory cache is repopulated.Do one or more of the following, testing AutoCAD after trying each solution: No errors whatsoever, just a (not responding) text on the application title bar.Īnyhow, perhaps a script to restart the smartposting and the w3dbsmgr.exe services over the weekend may make rebooting the server unnecessary. Logging in would take up to 5 minutes, users already logged on would not experience any slowdowns, but if they logged out and tried to log back in, they would experience a long wait before Sage would respond. I have not seen that issue in a few months, perhaps that license check is not performed anymore or at least not in the same way now on 2017.1 or 2017.2, but when it used to happen, this was the very same behavior. A reboot is the only thing that has dramatically reduce the number of instances of this type of issue.Īnother unlikely cause is the calling-home or licensing check Sage50 would do when logging in. There seems to be a memory leak w3dbsmgr.exe, because the longer you keep the machine up, the more memory that process takes. That is why a reboot is the only way to kill peachw.exe, smartposting and w3dbsmgr.exe. You would not know until you open Sage again and notice it goes straight to the main screen without asking to log in or when you try to reboot and windows tells you that peachw.exe is preventing windows from restarting. Sometimes Sage is still open, even when the application is not visible on the taskbar, the sneaky peachw.exe is still running. We have a 40-user Sage50 Quantum installation on a dedicated WS2012 R2.Īfter quite a few of these log-in freezes, I ended up having to reboot our server every week and having the users to reboot their machines every day at the end of the day to kill any lingering open sessions to Sage. I have experienced something somewhat similar. How many days past before you need to reboot?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |