ORD - 10.07.00.056
CONNECT - 10.12.00.40
When adding file/s in print organizer from within CONNECT everything works as expected. BUT when trying the same exact steps in ORD the process does not complete and ends with a "Unable to load design file......"
Does not crash ORD but does not ever add files either. I can open a previously created pset file apparently without problem.
Has anyone else run into this problem or know of a CR to this matter?
Are you sure that CONNECT and ORD are looking at the exact same resources? They are two different products, and it's possible that the configurations aren't identical. If they are looking at different resource files, that could explain why ORD isn't finding "something".
Microstation 08.11.09.829orPower InRoads 08.11.07.615
Yes, I am positive they are looking at the exact same resources. BUT you reminded me to try it without any resources and it works as expected on the same files i tried before. SO, i will start digging in the resources and see what might be causing the problem.
I am trying to get this set up for our users in case projectwise interplot organizer is discontinued or not brought forward to Connect Licensing.
Thanks for the direction i needed. I will report back if i find out what is causing the issue.
So in my many restarts of ORD to find the offending variable, the winner is.......MS_CURSORPROMPT
I had it set to 1 and it worked just fine except for Print Organizer and adding files to a pset. At least that is all i had run across. it has only been set for about a week and then only on our development server so nothing in production was affected. i checked and it does appear in ORD when not set by me. I thought it might have been deprecated and I stumbled across it while reading stuff here. But I remembered that I ran across it while perusing the variables to see if there was any new ones that we might want to utilize. This is one but unless it is fixed it won't be possible. I will see about putting in a SR for it soon.
And it did not seem to matter what level the variable was set either.
Oh, that's strange...I'll keep that in mind if I run into any Print Organizer weirdness.
Defect 1036555*:Adding files to Print Organizer does not work when MS_CURSORPROMPT =1 has been filed on this problem.