I am unable to open previous preference files when I using Rail Track in a read-write format (installed software Bentley Rail Track v8i SS4 08.11.09.878, Microstation v8i SS4 08.11.09.832, Windows 10 OS). BRT explorer indicates that preference file has loaded successfully. The Preferences tab shows that the file has been opened "read-only". When I open preference manager, it does not show the saved preferences. File is loaded from my local drive to which I have read-write access. File properties are set to writeable. I have administrator rights assigned to my windows profile.
When I open the file, a LCK file is created. This file also removes itself when BRT explorer is closed.
I was able to open, edit and save changes to preference files 2-3 business days ago. I have checked whether there is an issue with the preference file itself by testing on another users machine and have confirmed that the issue appears to be unique to the configuration on my primary machine.
Manually setting the preference file to read-write within the preference tab in the BRT explorer yields the same result.
All other tools within BRT appear to be working satisfactorily.
Can any shed light on what might be causing this issue?
I've seen this problem before and it is related with a wrong version of some dlls. Can you try this?
Download and install the following two DLLs from the Microsoft website. They should be in the C:\Windows\system32 directory on a 32bit machine or C:\Windows\SysWOW64 on a 64bit machine. Even if they already exist on the machine, it may be worthwhile to download and reinstall them, since these are the controls InRoads uses to read and write the XML data in the XIN file. Please refer the installation instructions that can be found on the Microsoft website.
Hope it helps.
Answer Verified By: Scott Lundgren
The first reason that comes in mind is the MSXML4.dll not present on the computer. In SS4 the XIN file may not open when starting Rail Track and looks empty when using Style Manager.
You can download it here:
Thanks for the detailed reply - the issue with my machine was the missing msxml4.dll file from the C:\Windows\SysWOW64 folder. Downloading and running the msxml.msi file from the Microsoft website resolved the issue without the need to register the DLL file. I did not need to run as administrator and I have not tested with another profile on this machine.
Are you able to advise some of the likely causes for the msxml4.dll being deleted? It seems to be associated with the uninstall of an older version of Projectwise and install of a newer version.
Thanks JPLN - this was the issue with my machine.
Could this be because SS4 was installed without the updated pre-requisites?