Jump to content

Recommended Posts

Posted

OK, I think this one's a collector's item. I haven't seen it before and it is quite spectacular. I had just opened a drawing and the first thing I did was to click the Layer Manager button and I was presented with this:

 

Assertion.png

 

What does it all mean? Although I was offered 3 alternatives, AutoCAD just crashed and I had to close it down using the Task Manager.

 

Has anyone seen this before or is this a real rarity?

  • Replies 22
  • Created
  • Last Reply

Top Posters In This Topic

  • CADTutor

    10

  • ReMark

    9

  • Mike Shilton

    2

  • skipsophrenic

    2

Top Posters In This Topic

Posted Images

Posted

OK, so AutoCAD had managed to reproduce a previously reported defect - cool :huh:

 

I hope those Autodesk boys are watching - it looks like they've been waiting for this one.

 

Yep, service packs up-to-date.

Posted

"ReadProperty failed" would lead me to believe a problem within the drawing file itself.

 

What happens if you just load the drawing but don't click on the Layer Manager button? Can you work with the drawing?

Posted

I can open the drawing and I can navigate etc but I get the same problem when trying to open the Layer Manager. I'll try Wblocking.

Posted

OK, Wblocking doesn't work and the error also occurs in a larger drawing that Xrefs the problem one. The weird thing is they were all OK yesterday when I was working on them and I haven't changed them since.

 

I'm hoping to find a workaround because this project has a deadline tomorrow.

Posted

And you tried Audit and Purge before working on the drawing?

Posted
And you tried Audit and Purge before working on the drawing?

 

Oh it's worse than I thought. It now happens on ALL drawings - even ones I created ages ago. I don't think it has anything to do with the drawing - it's AutoCAD. I'll try a restart.

Posted

So now we've gone from bad to worse? Not good. What else is running besides AutoCAD? Have you had any hardware problems lately (hard drive acting up)?

Posted
So now we've gone from bad to worse? Not good. What else is running besides AutoCAD? Have you had any hardware problems lately (hard drive acting up)?

 

This is BAD. A restart hasn't helped and AutoCAD now crashes every time I try to open the Layer Manager - even in a new drawing (before drawing anything). Basically, AutoCAD has broken and I can't use it for the intended purpose.

 

Deadline looming!!!

 

I'm coming to the conclusion that a reinstall may be required :x

Posted

AutoCAD reinstalled - problem remains. I'm guessing this must be a registry problem but I'm all out of ideas.

Posted

Registry problem? Why? Did you add any new hardware or software prior to the problems you have experienced?

 

What OS are you running? You can try using the old standby REGCLEAN program (an unoffical release by Microsoft). It's relatively safe.

Posted

It looks as though this may be related to the .NET framework. The Layer Properties Manager uses .NET and on Friday, Microsoft released the .NET Framework 3.5 Service Pack 1, which I installed because it was flagged as "Important". It just seems too much of a coincidence to be anything else.

 

Advice for everyone: DO NOT install the .NET service pack if you are running AutoCAD on Vista until the problem can be identified.

Posted

I think I saw something about the possibility of it being a NET Framework problem but I considered it to be fairly remote. That's the price you pay sometimes for immediately downloading and installing service packs I suppose. I usually wait a couple of weeks and see if there are any bugs in the bug-fix. Looks like you caught yourself a fine specimen. Glad you were able to sort it out. Gonna make that deadline?

Posted

Is there a way to uninstall the .NET service pack? - if so would that "undo" the error's your getting?

Posted
Is there a way to uninstall the .NET service pack? - if so would that "undo" the error's your getting?

 

I haven't tried uninstalling the .NET service pack yet because I have found a workaround to the problem. It seems to be something to do with the modeless nature of the Layer Palette. If I set it back to legacy mode (LAYERDLGMODE = 0) everything works fine.

Posted
:huh: odd, how a single variable can cause such a headache

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...