We have recently started encountering the error "The change to the "No Project" project will not be remembered for future sessions because the current user configuration file could not be updated" when switching from a Project to No Project during startup. I know this question has been asked before, but it seems as if none of our user permissions vary within the folder that houses our PCF and UCF files. Are there other folders to check for varying user permissions as this is only occurring on a small group of people and seems to be affecting access to standards such as Print Organizer preferences.
Any help is appreciated.
Thanks,
Bryan
As you are changing which project is being selected it may be that this change would be saved to the User Preference File (UPF). These files are located in a separate folder to the UCF/PCF which is most likely on the users local C:\ drive. You can check where their UPF is siting for their current session in V8i under:
> Workspace > About Workspace
Your users would need Read+Write access to these folder to enter operations like this are working as expected.
https://communities.bentley.com/products/microstation/w/microstation__wiki/13452/troubleshooting-user-preferences-issues
RegardsAndrew BellTechnical SupportBentley Systems
The permissions seem to be the same (Read & excecute, List folder contents, and Read) for the UPF folder for all users in this case as well, and it still seems to be working find for some. Is there a user config variable that may overriding how/where MicroStation searches for the PCF?
Bryan Larson said:Is there a user config variable that may overriding how/where MicroStation searches for the PCF?
Your best bet is to use MSDEBUG on one of the computers that fails. Then examine the msdebug.txt file to find where a variable is defined or changed.
msdebug.txt
Regards, Jon Summers LA Solutions
Thanks, Jon. I used the debug function to compare my variables with the affected users'.
I noticed a few issues with what was being populated in the _USTN_PROJECTCFG and _USTN_PROJECTNAME variables was incorrect (already known), but was unable to change it. I was able to resolve the issue by sending the affected users my UPF and having them replace theirs on their local drive. I couldn't determine the root cause and issue, so I'm hoping this was an isolated issue.
Thank you all for your input.