Skip to main content

AutoCAD® freezes During Startup.

If you are using AutoCAD-based products on isolated networks, you might experience a problem where the program freezes after it starts up. This usually happens after the AutoCAD screen appears, but before any tool palettes show up.

To fix this problem, you have to change your Internet Options settings.

Note: This procedure might be risky if your computer is connected to the Internet.

These are the steps you need to follow:

  1. Go to the Start menu (Windows) > Settings > Control Panel.
  2. In Control Panel, find and open Internet Options.
  3. In the Internet Properties window, go to the Advanced tab.
  4. On the Advanced tab, look for the Security section under Settings.
  5. In the Security section, uncheck the Publisher’s Certificate Revocation box.
  6. Click Apply, and then click OK.
  7. Restart your computer, and then launch the program.
I hope this works for you. If it does, please share the solution with others.


Further Reading
Labels:

Comments

Post a Comment

Popular posts from this blog

Fix HTTP error code 513 on Wildfly

The Mysterious Case of TIME_WAIT and IDLE Connections Have you ever encountered a network issue where your server is consistently showing a high number of connections in the TIME_WAIT and IDLE states? This phenomenon can be frustrating, especially when it indicates that the connections are not being closed properly by the server or client. In our investigation, we found that the culprit behind this issue was an HTTP error code 513 being sent to clients from servers. This error code indicates that the server is overloaded and cannot handle more requests. Furthermore, the client was logging a socket close event, which meant it was terminating the connection prematurely. To replicate this issue, we used JMeter and found that the max concurrent connection limit was reached, resulting in an HTTP error code 513. The allowed queue was also full, contributing to the problem. So, what are the consequences of this issue? Performance degradation and resource wastage on both servers and clients ca...
Post a Comment
Read more

Catch persistence java.sql.sqlintegrityconstraintviolationexception

Handling SQL Integrity Constraint Violation Exceptions This tutorial will guide you through handling `SQLIntegrityConstraintViolationException` when persisting objects that violate database constraints. Step 1: Catch the EJB Exception Catch a `javax.ejb.EJBException` which wraps the underlying exception. try {     // persistence transactions } catch (Exception e) {     if (e instanceof javax.ejb.EJBException) {         logger.debug("Exception instance of javax.ejb.EjbException");     } } Step 2: Get the Underlying Exception Get the underlying exception from the `EJBException` using `e.getCause()`. try {     // persistence transactions } catch (Exception e) {     if (e instanceof javax.ejb.EJBException) {         logger.debug("Exception instance of javax.ejb.EjbException");         Throwable cause = e.getCause();         if (cause != null) {     ...
Post a Comment
Read more

Quick Reminder: Golang subfolder import

Here is a tip for importing into your project. First, you import with the folder path but you use the declared package name in the imported class as the anchor to the methods in the imported class. For example, let's say you have your project in the following structure: example    main.go    pwd/       foldering.go To import foldering.go even if the package name declared in foldering.go is different e.g. secondPwd  into main.go main.go package main import (      "example/pwd" ) func main(){     secondPwd.PrintPWD(); } foldering.go package secondPwd import(      "os"      "fmt"      "log" ) //PrintPWD... func PrintPWD() {     dir, err := os.Getwd()      if err != nil {          log.Fatal(err)      }  ...
Post a Comment
Read more