Getting a Unsupported operation error when trying to create a New Named View

[Anonymous]

This problem just started after I installed 2018 Service Pack 2. I did not have this issue prior. And non of the rest of our systems seem to be having this issue with SP2.

I am running Windows 10 Enterprise, Civil 3d 2018 with Service Pack 2.

When i go to create a new named view from the View Manager I get an "Attempted an unsupported operation." error message then Civil 3d Crashes.

It is not related to a single drawing as it will do it with any drawing that I open or start from a template.

this is a screen shot of the error

[Anonymous]

I also tried uninstalling all of the C++ redistributables  and reinstall that did nothing to fix the issue either.

[AllenJessup]

If you try -View from the command line. Does it still fail?

[Anonymous]

I had not. But I did try and NO it does not crash using -View from command line.

Thanks.

[AllenJessup]

That seems to point to a fault in the GUI instead of the basic program. If no one else reports this issue. The only thing I can think of is my basic mantra. Restart-Reboot-Repair-Reinstall -[Retire]. You may benefit from a clean reinstall.

[Anonymous]

This has been going on since November. I have tried repair. I did a full uninstall and Reinstall. Did a full uninstall and Regedit to get get rid of all C3d 2018 info out of the Registry. Then did a full install again. I tried removing all of the C++ stuff and Reinstall all of that and it still messes up. At this point working with the command line has been the only work around so far that does not crash.  The only thing left would to be wipe the system and start from Scratch if AutoDesk does not have a solution.

[AllenJessup]

I looked for other instances of this error. I think it averages to 1± per year over the last 15 years. Each occurrence was in a different program except 2 I found in AutoCAD LT. Each occurrence happened under different circumstances. The only ones I found that were solved involved reinstallation. If you are on Maintenance of Subscription. You should start a Service Request directly with Autodesk.

Did you try a Clean Installation?

[Anonymous]

Thanks your help so far has been the biggest help I have gotten. Reinstall you would think would take care of the issue. I just got a suggested fix from Autodesk shortly after yours. Both one of their suggestions had been tried and the other one Wiped out all my Ribbons. Just did another full reinstall again which did nothing including not bring my ribbons back.

[Anonymous]

sounds like the cuix file(s) are corrupt. do you use a custom workspace and did you try rebuilding it?

[Anonymous]

That was their fix that took out my Ribbons. I got my ribbons rebuilt and still have the problem.

[Anonymous]

I have had issues with a custom workspace/menu (.cuix) causing inexplicable ribbon behavior, and a corrupt profile (.arg) causing issues with pressure pipe networks of all things.

do you have a lisp routine (acad.lsp or acaddoc.lsp) running on start that is loading a custom menu? what profile is your desktop icon pointing to when you start C3D?

I would try to revert to original run it as straight "out of the box" as I could then start adding customization to it until I either find the problem or am happy with what works. ou might try resetting (start Menu>All Programs>Autodesk>AutoCAD20whatever>Reset to Defaults), setting the targeted profile on the desktop shortcut to  /p "<<C3D_Imperial>>", then seeing if it works.

[Anonymous]

We do not use any custom menus. The only custom that we have are some tool pallets. No special lsp being uesd on start up. Have reset all defaults as this was one of the first fixes I tried and have tried mulitiple times. We do use profiles and I have tried going back to the basic autocad profile and other and it still Crashes in all of them when I use the GUI View manager.

[Anonymous]

I'm out of ideas. I hope you find the answer.

[Anonymous]

Thanks. I have been searching for MONTHS...........  it sucks. I always seem to have the issues no one has a fix for.... 

[Anonymous]

I feel your pain - I find some of those, too.

[Anonymous · Accepted solution]

Found that I had an AUTOCAD 2018.1.1 Update that needed to be done that seem to fix the problem.

[AllenJessup]

Great. When you're sure that the issue is fixed. Don't forget to mark you post as the accepted solution.