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

Comments

Popular posts from this blog

Fix HTTP error code 513 on Wildfly

Description :  Many users have reported a network issue where they see a large number of connections in TIME_WAIT and IDLE states. This indicates that the connections are not being closed properly by the server or the client.  When I analyzed the network traffic, I found that the server was sending HTTP Error 513 to the client, which means that the server is overloaded and cannot handle more requests. The client was also logging a socket close event, which means that the client was terminating the connection. This can be simulated using Jmeter. The HTTP error code 153 resulted from the max concurrent connection limit reached, and the allowed queue was also full. This issue can cause performance degradation and resource wastage on both the server and the client. To resolve this issue, we recommend the following steps: Resolution :  1. Investigate the process of holding onto the connection longer than necessary. 2. Increase the server capacity or scale up the server to handle mo

Wildfly EJB Remote Client Exceptions.......

Below are exceptions and the solutions I applied while developing a remote client enterprise application. To start with, enable debug for your application server to see the detail and good luck troubleshooting. Exceptions : Starting with  java.lang.ClassNotFoundException: org.hibernate.collection.internal.Persistent......... Solution : I fixed the exception be adding hibernate Entity Manager Dependencies. Exception: Error javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial Solution : Add JBOSS-CLIENT Dependencies to your project Exception : IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling Solution : Confirm that your EJB module have been deployed. Exception : org.jboss.naming.remote.client.initialcontextfactory wildfly     javax.naming.NamingException: WFLYNAM0027: Failed instantiate Initia