AutoCAD Script Error

[Anonymous]

Hi,

We have recently installed AutoCAD 2017 on 5 of our computers in our organisation however, two of them display the errors below, seen in the screenshots.

The program will then show an empty box attempting to "Activate AutoCAD" which hangs. If you close this window via the taskbar AutoCAD will continue to open and appears to work fine.

Any assistance would be greatly appreciated.

Thanks, Jake

[stevetamplen]

Hi Erik, and welcome to the Forums!

It is not a matter of leaving it in, it is something we just discovered, and are working to correct, hopefully by the time the next service release comes out. 

Even with Beta testing, there are always scenarios no company can anticipate, with millions of users and, consequently, tens of millions of possible hardware/software/configuration possibilities that can cause a problem when they are encountered. You will see this in any software release from any company, from Microsoft, Adobe, and Autodesk, down to the smallest made-it-in-the-garage software creator.

Autodesk maintains a customer-centric attitude regarding their products, which is one of the reasons why these Forums exist, and why I (and thousands of other unpaid users) are here trying to assist fellow users every day.

When we find workarounds to issues, we post them here so users with the issue can find them (like both of the above) until such time as we can get a Hotfix or Service Pack out with those fixes included.

[CivilLAH]

Hi Steve,

Thank you for replying 🙂

I do apologize if my last post has been kind of agressive, that was not my goal, at all.

I didn't mean to blame anyone in the forums, and certainly not poeple kind enough to share sollutions with us, witch I do appreatiate a lot, really.

I simply mean that a customer is not a beta tester, and that I feel it's not normal that we have to troublesoot a brand new product.  period.

When I buy a new car, I turn the key and it starts. That's ok, that's the deal between the manufacturer and me.

You are right, other software company also release softwares with "issues". Call it 'issues" or bugs, whatever, the reality for the customer is just a product witch does'nt work, and who need troubleshooting. Something new should work out of the box.

That said, I know the reality is different, and I do appreciate the good work (unpaid work, I know the concept 🙂 of forums members.

Best regards,

[stevetamplen]

Not a problem, I have been working in tech since '96, and I know from the other side what it is like to have problems with brand new software or hardware. I really do feel your pain, and that's why we are here to help in any way that we can.

Sometimes you just gotta vent, and we understand that and take it in stride. We have moderators who will delete things if it gets out of hand, however.

I only wanted to let you know that when Autodesk releases a product, it is tested as fully as it can be with a small database of Beta Testers, and when it hits the BIG database of Real Users, that is usually when these types of issues crop up, stuff that never shows up in Beta testing, and so is not discovered until after product release.

You only have to look at all of the recalls that are going on in the automotive industry to realize that it even happens to them too.

[Anonymous]

you are awesome. it worked. thank you

[steica]

I have the same problem. using Windows 7 , 32 bits. With norwegian language in windows. I removed the Laguage reference in the shortcut as suggested. But that did not help. IE compability change, did not help. I then logged in with a user who had local admin rights, and then started Autocad LT 2017, and it went fine, i did not get any script errors. The installation was licenced with STAND-ALONE,  (5 licenses).

I then logged in with the user again who had normal user rights (more limited), and then it was no problem starting Autocad LT 2017 anymore, no script errors.

So it seems Autocad LT 2017, writes to a place in registry or on the disk, where it needs more rights than a normal user. So maybe in HLMK in registry, or in c:\programdata\Autodesk\ ? Most likely its in the registry maybe? Maybe something for Autodesk Support to look into? It seems that when AutoCAD has been able to write to that certain place on the disk or registry, that it then its okay, and will work for any user after that. Just my 2 cents.

[Anonymous]

Hi,

I had the same problem. Your solution fixed it. Thank you!

KitBim

[jfe100090]

I also meet this error. Auto Cad files in our file server can't open directly. Script Error welcome to us. How can I solve this?

Please don't give the way of unplugging network cable,

[Anonymous]

https://www.youtube.com/watch?v=IUos7nfpV5Q

[Anonymous]

Thank you for taking the time to post this. Very helpful!

Greg