Intersection always Fatal Errors

[Anonymous]

I'm trying to do a basic intersection and even use the parameters in the dialog boxes and everytime fatal errors me. I've audited and recover and it always does this. Are there any hotfix/service packs to this? Any ideas? BTW. I get a notice that the macro does not find the assembly where its suppose to be?

Thxs

Andy W.

[Mike_Hurtado]

Can you upload a file and maybe a screenshot so that I can try to reproduce the issue on my end?

[Anonymous]

Sorry for the delay in response. The first file is my actual project file. The second is a completely generic file where I used all the default numbers in dialog boxes. Both always fatal error.

Thanks in advance for any help you can give me.

Andy W.

[BrianHailey]

Troubleshooting 101.

1) Can you replicate this issue with other files?
2) Can you replicate this issue on your computer logged in as someone else?
3) Can you replicate this issue on someone else's computer?

The answers to these questions will help you determine where the issue is, the file, your computer, your user profile, or the software in general.

[Anonymous]

I sent the generic file to another civil company and they got same fatal errror. I wonder if the problem is the template. In the panorama, I get a message that the templete is not found where it should be, but finds it at another location. Could this be problem?

Andy

[Mike_Hurtado]

I managed to create the intersection by unchecking the "Create Offset and Curb Return Profiles" box

I would play around with the settings in the lane slope parameters and the curb return profile parameters to see where the problem is. Hope this helps.

[Anonymous]

Thank you for looking into this. Still would like to know why this is happening, whethers its my install, profile, drawing, template?

[fcernst]

Turn off "Create Offset and Curb Return Profiles"

I have a fatal crashing intersection drawing Support Case currently submitted to Autodesk, Michael H just told me the same thing.

This is not a resolution.

We need to create the curb return profiles.

[Mike_Hurtado · Accepted solution]

Well this has been an interesting issue. I played around with the file some more and I have a workaround but I'm not sure why...

1) In the prospector tab, create a new site (you can then delete it or leave it)

2) Try creating the intersection now

It created the intersection without a problem. I'm going to dig a bit to see why this happened but it is starting to look like a bug. 

[Anonymous]

Thanks for the workaround Mike_ADSK.   I've been plagued with this for a couple days and just created a new site in the prospector - it worked aftwards.  Hope to see a solution soon.

Thanks,

Craig

City of Fort Lauderdale

[gerry_alvarez25]

This is a great temporary solution. I've also noticed that after creating an intersection and adding it to an existing corridor, it disurbs the first baseline in the corridor properties.  It starts creating a several regions with blank assemblies.

I'll probably start a new thread on this, but wanted to post here since it might be related.

[Anonymous]

Thanks, Michael!

I had a similar problem. Creating a new site helped.
Perhaps the search for the causes will be useful number of fatal errors?
He kept the same.

[jwg]

We also had success with the new site approach.  We noticed that when we did this that the ACAD default assemblies were added to the drawing.  It appears that possibly in a previous purge those had been eliminated, or perhaps by something else we did.  I suspect the problem occurs when ACAD, for some reason, makes a call for standard assemblies (even if they are not being used in the drawing) and does not find them.  Don't see how that makes a lot of sense but do know that we noticed these assemblies were added to the drawing when we added the new site.  This would be consistent with the notices we were getting in the Panorama box.