I have a user who is experiencing the subject issue. This apparently only recently started and once I gave him some diagnostic things to try, he's reporting the following:
"SYMBOLSELECTOR doesn’t appear in the list when the (MDL) dialog box is opened, but it does appear when I click on Insert Symbol, though it’s still not opening the popup with the available symbols. MDL LOAD SYMBOLSELECTOR gives the “SYMBOLSELECTOR loaded” message, but as soon as I select the Place Text tool I get the “unknown key-in or command” message and the Insert Symbol command still doesn’t work.And to make things even more complicated, after I closed the session I opened another session just to make sure it still wasn’t working, and now it appears that the Insert Symbol command is working intermittently; I was able to open the Symbols dialog box, but after opening and closing a few more sessions to test it out it seems like it’s a tossup whether it would work during that session."
So while I have given him a potential work-around, the results are not consistent.
Has anyone seen anything similar to this?
Not exactly same issue but.. with stuff like this I usually try the windows programs uninstall REPAIR option program over the microstation folder
A lay person explanation....
sometimes dlls, and mdls with their associated files can get corrupted over networks and if you like us here working remote from home over the vpn and internet files can get out of synch..
In anycase it cant hurt as only factory date install data is replace not any custom data ie preferences etc this seems to fix a lot of stuff that goes wrong from time to time even when VBA wont load or gives and error after vba's have been working for ages all of a sudden they don't..
The next thing I would try is delete/ rename the user upf file and see if its now working, by the way if it larger than 250kb I find letting ustn rebuild it and then tweak it to your standard ( takes me less than 3 mins) ...
Still no joy then check the workspace prefs or project prefs to see if cells and mdl paths are properly defined.
hopefully you havent tried all these yet.
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me
Is the Symbol Selector accessed in the Text Editor dialog? One thing I am noticing by clicking the Insert Symbol for ORD is that the dialog is displaying Symbol Inserter rather than Symbol Selector.
I searched my local drive for both Symbol Selector & Symbol Inserter. Interestingly Symbol Selector showed up for Microstation Select Series & Power InRoads as .dll. SymbolSelector.ma was found for ORD in a Temp folder.
SymbolInserter.ma was only found for ORD, once again in a temp folder. There were no .dll files found for Symbol Inserter.
I do not know what the difference is between the 2. My best guess would be that SymbolSelector.ma is a legacy mdl app required if a file is opened using pre-CONNECT 0r maybe pre-SS10.
One other item to check is within the workspace I opened the configuration variable dialog through the backstage in CONNECT and searched for "symbol". This lead me to the variable MS_DGNTEXTEDITORFAVORITESYMBOLS that points to "DgnTextEditorFavoriteSymbols.xml". I would check that variable to make sure the .xml file is present. It seems that it is since there is intermittent access to the symbols. Maybe there is an issue with that file on the local drive.
I think I would agree with Lorys to Windows program repair as a first step, especially if it is only affecting one user. Deleting the .upf would be the next step. After that I would start a SR.
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453