Since upgrading recently to V13 I have a strange issue with network credentials. Whenever I launch Opus, I get logged out of our domain server for too many invalid password attempts on my domain account. Clearly Opus is trying to reconnect network drives using an old password, but all of the obvious UNC paths I have assigned to tabs in Opus are all connecting fine with the correct credentials. It's as though there is some other share Opus is conencting to which has invalid cached creddentials. I've cleared out all the windows credentials using Credentials Manager, but the problem persists. It re-occurs at some interval of around 1 hour probably as Opus retries the share in question at some sort of time interval. All my shares use UNC paths.
Is there any way to see all the network paths that Opus is trying to reconnect to on startup?
It could be something in your config pointing to an old UNC path, maybe. For example, in the Favorites list, or a toolbar button that goes to that path or that uses an icon or program from it.
Old File Collections (e.g. Find Results) pointing to the old paths could be involved (although I think we avoid accessing those these days, it's worth clearing out old, unneeded collections in case they are involved).
Check if you have any other Opus windows open, as they can persist across restarts (depending on config) and some people have accumulated them without realising.
If there are shortcuts in the folders you're viewing, and one of those points to an old UNC path, those might be involved as well, although I'm not sure.
Process Monitor can do that. If you filter the path to ones starting with \\ then it should show all the UNC paths that are being accessed and which process is accessing them.
Many thanks Leo. I fired up Procmon and the only UNC paths that Opus requests on startup that do not have a result of "SUCCESS" are the paths \my server name\IPC$ (most of these have a result of NOT FOUND though some have SUCCESS) and \my server name:aOpusPinnedFileMarker\ which have a result of NAME NOT FOUND. Any suggestions of what these are?
I have fixed the issue but not sure why it fixed it. I made a new Lister Layout which had all the tabs that were network locations removed. I then added them one at a time again and once completed everything was still fine. Then I went back to the lister that caused the issue and removed each network location tab one at a time until the problem went away. I found the culprit - but the strange thing was that that tab still connected fine so how it was using incorrect credentials that locked me out I have no idea. The tab concerned belonged to a Navigation lock group - but that may be coincidental. It had not been touched since V10 so something about it changed with the V13 update. Anyway all solved now thanks for your help.
