I'm trying to create a sheet seed for creating a profile drawing, but I'm having problems with the named boundary. When I place a named boundary, all seems to go well until I click to accept my named boundary. Instead of the Create Drawing window popping up, I get a "Group Unnamed Profile not found" error on the message centre. Any ideas on how to sort this one out? I'm using OpenRoads Designer Update 3.
Does the path to your file or its name contains any period, comma or any special character?
No special characters in the file name or file path. I've also tried creating a brand new Plan or Profile Start Seed file to use for my sheet seed, but the error is still happening.
Marc. I've managed to sort it out. I just binned my organisation level workspace, and pulled out my backup version. But one other question related to Named Boundaries. Is there a way to set assign a feature definition or element template to the boundaries? At the moment they are drawn on the Default level.
Thanks for letting me know.
Good question! I don't think you can modify the level in which it is created, you might change it manually after. I'll have a look at it.
I am having a similar problem in ORD Update 4. After I create a named boundary and a drawing model is not created even with the create drawing option checked. Then if I try to create the drawing it gives an error that it can't find the group, but the group is in the named boundaries dialog (see screenshot). I have attached the config variables for the workspace. What configuration variable could be causing the problem. I am working on ProjectWise so I would rather adjust the workspace than export locally and use a different workspace every time I need a section. Thanks.
log.configVariables.txt
This issue was resolved after installing ORD Update 5.
Answer Verified By: Marc Blancher
I'm still getting same issue as @Dave Hansen in ORD 2019 Release 2 Update 7... No matter how I'm making named boundaries I can't make Drawings out of them. Does anyone found a workaround for this issue in latest version? Any help would be appreciated.
Regards
Did you ever get this resolved? If so what is the fix? I am having the same problem.
Thank you
Hello Mandi,
yes we did, but I'm not sure whether this answer would satisfy you... On many PCs in our organization it worked fine, only for two of us such an error occured. However this was resolved by reinstalling Windows... Not a great answer but I was really fed up with these problems, I was desperate and reinstalled the OS from scratch... and it worked... How? Why? I don't know... But I'm no longer getting these errors anymore.
Cheers
Thank you. We figured out that my problem leading to this error was a comma in the name of the server folder the files were located in. However, I am have several other issues that might be tied back to a recent upgrade to Windows 10 prior to installing ORD and we may need to look into the same fix you had for an overall solution..