MEP 2011 Tool Palettes (msscript.ocx)

[jdaulton]

Receiving this error when dragging & dropping a standard tool palette:

"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."

This is a fresh install of MEP 2011 x64 on Windows 7 x64.

Another error that is occurring during the same process is:

"ERROR: Calculation Failed with Part Table Bell - Heavy Duty - Double Hub Fitting"

Any ideas or solutions to these problems?

[jdaulton]

I have some more information to add to this problem:

We have identified that while in MEP Default Tools - Imperial and you try and move the whole catalog for "Electrical" or "Piping" we receive the error mentioned above. If you go into the "Electrical" catalog and move individual palettes we receive the error message on the "Cable Tray & Conduit" palette but the other palettes move over just fine. Also, if you go into the "Piping" catalog and move just the "Fitting" palette we receive the error but other palettes move over just fine.

Again this is a fresh install of MEP 2011 x64 on Windows 7 x64. This has been tested on a local install and with an install that uses shared content and both have the same results.

I wonder if anyone is reading these... 🙂

[Keith.Brown]

The same problem existed in 2009, 2010, and now again in 2011. I generally have to drag the individual palettes over because dragging the palette groups over never works.

[andymp2000]

I have found that if you drag the files directly from the containing folder (i.e. C:\Users\user_namel\AppData\Roaming\Autodesk\MEP 2011\enu\Support\WorkspaceCatalog (UK)\Palettes) the palettes import with any of the msscript.ocx errors...(NOTE - the 'WorkspaceCatalog (UK)' folder will obviously be different for non-UK installations)

It would be nice however for Autodesk to sort this 'issue', it has been around for a while, and even if a fix can't be found maybe a little utility to rebuild the default palette groups or an step-by-step of how to do this.

Andy

[Andrew_T]

I've been having this issue in 09, 10 and 11 as well with a little variation.  All of our tool palettes, with the exception of all Piping palettes, have been brought forward for each release since ABS2004.  The Piping palettes were supplied by Autodesk for MEP2009.  Strange as it may be, the piping palettes are the ones giving the error. All other palettes come in fine.

[MIKE_ST]

We are getting an error message on the 64 bit machines (running MEP cad 64bit version)  when transferring tool catalogs. The 32 bit machines don’t have this issue.Also seems like the problem appears only for the electrical and piping catalogs.

Is there a way to solve this or we need to run 32bit MEP cad version. I tried reinstalling the explorer, misscript file and nothing works.

thanks

[Keith.Brown]

Did you try moving over individual palettes vs the entire palette group?  I have found that by doing it that way it will work.  It takes a little longer but better than nothing.

[MIKE_ST]

yes i did. I was able to transfer all the tool palettes except electrical conduits and piping.

[MIKE_ST]

is autodesk planning to resolve this issue any time soon ?

[INTOOCAD]

Here is what I received from AutoDesk Tech support. Which it did not work for us, maybe it will for someone else.

1) The simplest and most common fix is to reboot the computer.
 
2) The next most common fix is to try a repair, from the Add/Remove Programs > AutoCAD MEP > Change/Edit button > Repair or Reinstall > Repair.
 
3) The scripting file is actually a Microsoft system file. You can try downloading the Windows Scripting components from (Note: this is for Windows XP customers)
http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&displa...
 
2) Next thing to try would be a repair installation. Go into Add/Remove Programs or Programs/Features in the Control Panel, find the entry for AutoCAD MEP 2010, click the Change/Remove button, select the option to Repair.  Test to see whether the error persists and the installation repair completes.
 
3) The 64-bit version of Internet Explorer 7, and IE8, may be preventing it from operating.  Please follow this link to roll Internet Explorer back to IE7 32-bit.
http://www.technologyquestions.com/technology/internet-explorer/110486-how-do-i-set-ie7-32-bit-defau...
 
4) Try reregistering the msscript.ocx file.  Open a command prompt in Windows (from the Start menu, select Run, type in CMD and then enter.) At the command prompt, enter regsvr32.exe msscript.ocx /u and then hit enter. You will receive a dialog box that says “DllUnregister Server in msscript.ocx succeeded.” Click OK. Still in the command prompt, enter regsvr32.exe msscript.ocx and then hit enter. You should receive a dialog box that says “DllRegisterServer in msscript.ocx succeeded.  If it does not say that, it failed to reregister.
 
5) The AutoCAD MEP 2011 error may be fixed by the above suggestions, though we have one other possibility.  We recently encountered that 2011 error when a user opened a file that contains electrical objects, with the desktop icon that launches AutoCAD MEP 2011 as Classic AutoCAD.  Classic AutoCAD does not have the resource modules needed to draw the electrical objects.  Check your 2011 desktop icon and see if it is launching MEP as classic AutoCAD.  look for a different desktop icon the says AutoCAD MEP US Imperial.

[Dallaskt]

Hello Autodesk!!!

We need your help on this immediately. The solutions you've provided does not work! I along with INtooCAD believe that it is a failure on your part to fix this problem.

Please advise.

Thank you.........

[mspatz]

Any resolution yet?  I'm having the same issue and getting nowhere fast.

[Dallaskt]

Nope.

As usual nothing, but anyways, myself and other CAD support folks think we might have a solution, although a crappy one that may take extra time, but this is what we are considering....

1.  Repath your Tool Palette File Location to a folder on your C: drive called Palettes or whatever you choose to name it.

2. Create a NEW Content Catalog with your tools organized in the Catalog using Categories, having Categories is a must.

3. This should path all your tools to the specified C: drive folder and should create sub-directories called Categories and Palettes.

4. Open up the Categories folder thru Windows Exlporer and then drag and drop the .ATC files individually from your Categories folder on to the Tool Palette bar (the bar is where you can select different options, etc...)

5. This will "hopefully" bring in your tools along with the Tool Palette Groups.

Give this a shot!

Feel free to reply anytime, I'm here all day.

DT

[MIKE_ST]

Nothing helps.

The problem just got worse....

My out of the box tools dont work specifically cable trays and conduits (they were working fine before except when I was creating new catalogs). Same error appears "msscrip.oscx". I tried everything already, reinstalling MEP cadd, reinstalling msscript and every trick which was posted here... nothing helps. Is the only solution left to format my 64 machine? But what if the problem appears again? We pay so match for the software and we get no support. Thank you Autodesk.

Is Autodesk planning to resolve this issue any time soon? I just dont understand why Audesk neglecting this issue?

[Joshua.Benoist]

Good news.  We have been working on this MSscript.ocx issue.

We recently discovered the cause and developed a solution.
 
Would you please have a look at folder:
C:\Program Files (x86)\Common Files\Autodesk Shared, and verify the existence of the following files.

 Aec32BitAppServer.dll
 Aec32BitAppServer57.exe
 Aec32BitAppServer57.tlb

If missing please find the attached zip file, unzip and copy the above 3 into the above location.
 
Next, let's import the attached registry settings file.  To import registry, save the txt file attachment to your desktop, rename the txt file's extension to .reg, and then double click on it.  That will fix the registry.  Go ahead and test for the MSscript.ocx error to be gone.
 
Please let us know your impression on the above material and if this helps.  Have a great day.

[MIKE_ST]

Unfortunately this solution does not work.

[mspatz]

It did not work for me either.  I have a Support Request with Autodesk submitted on this issue and they said this a partial solution and they have 'teams from around the world' working on the issue.  Cross your fingers.

[Dallaskt]

That bites!

My company just abandoned the MEP out-of-box Tool Palettes all together and we built our own syncing and project file that we can edit much more easily and doesn't have any constraints....or script errors for that matter...

Good Luck~!

D

[dmcmillian]

Hate to bring back an old thread. This actually worked for me on Civil 3D 2011. You guys have any success with this issue?

[Ixath]

I'm still having this issue. Nothing I can do is fixing it. I'm able to import one palette without receiving the error and the other two popup the msscript.ocx error.