msscript.ocx Error in AutoCAD MEP 2013

[paulwood1577]

I recently downloaded the trial of AutoCAD MEP 2013 and installed it on my Win7 x64 system. When I go to place a section of ductwork, I receive the following error message:

"ERROR: There is a problem with the Script Control (msscript.ocx). This problem may be corrected by reinstalling Internet Explorer or by reregistering the control."

I would have liked to proceeded through the video tutorials prior to my 30 day trial expiring, but if I cannot get this issue resolved it may be a moot point.

I've already tried the following solutions to no avail:

1. Reboot
2. Repair installation via the Control Panel
3. Downloaded the msscript.ocx from Microsoft (even though I already had it located in (C:\Windows\SysWOW64\), and installed, copied it to it's respective directory )C:\Windows\System\msscript.ocx), unregistered it with the command "Regsvr32 -u msscript.ocx" and finally reregistered it with the "Regsvr32 msscript.ocx" ...I also tried the "Regsvr32 C:\Windows\System\msscript.ocx"
4. I tried uninstalling Internet Explorer (8/9)
5. I tried replacing the files missing/located in the C:\Program Files(x86)\Common Files\Autodesk Shared\ directory with the files supplied by the Autodesk Senior Support Specialist, Joshua Benoist, P.E. I will note that his *.zip file was packaged for Autodesk MEP 2011 not 2013 and as such I was only about to find Aec32BitAppServer57 and Aec32BitAppServer57.tlb in my C:\Program Files (x86)\Common Files\Autodesk Shared\ directory.
6. I even tried a complete uninstallation of AutoCAD MEP 2013 and reinstallation.

Can anyone please assist me, as I'm going to need to get AutoCAD MEP 2013 up and running on my workstation prior to starting my new job. Thank you ahead of time for any and all advice.

-

Paul D. Wood, E.I.T.

[AutoCAD-AL]

I have the same problem in Windows 7 Pro with AutoCAD MEP 2015. I have tried to fix the problem but no one company will take credit for this brain fart in programming. It was caused either by Autodesk or Microsoft. Personally, I think they both are at fault. Neither has a rock solid fix for this error as none of the suggesttion other than nuke and reload will work. We all know neither will admit or apologize for the oversight, hence, piss poor customer service.

You have a choice here. Nuke and reload or hope to hell Microsoft or Autodesk gets their head in the right place and develpopes a rock solid fix. Their suggestions are no better than a bad opinion.

[AutoCAD-AL]

Sorry about spelling in a great hurrry.