SSH CLient 126.96.36.199 Installed on Win 7.
Next time user log into system SSH Broker pops up error
Broker Initialization failed: No such file or directory c:\users\<user>\Application Data\SSH\ssh-broker-config.xml:19 Failed to read......
This is not where the broker file is located. The file is located users\<user>\AppData\Roaming\SSH
Only recourse to correct so far is to re-install the client.
Any ideas on why this is not pointing to right location for broker?
I am not sure what exactly are you experiencing. Broker's user's configuration file does not need to exist. If it does not exist, broker will use default configuration. In your case I see that there is an error in one of the configuration files on line 19.
Broker reads user's configuration file from the following location by default (but the location can be changed by global system-wide broker configuration file):
In Windows Vista and newer operating systems the "Application Data" is not a folder but directory junction which points to:
which is the same place where environment variable APPDATA points to. See example directory listing from my Windows 7 Home Premium system:
That means the 2 places you are talking about should be exactly the same. The 2 files should be one. That is if all is set up right. You could experience similar problems if the directory junction "Application Data" would not exist, or if it is a folder instead, or if it has wrong access control list assigned on it.
User Account Control (UAC) may also be source of problems. For example if folder redirection would be configured in some special way.
To confuse the whole situation a bit more: in 6.2.1 we have changed all Client/Server/Events/ConnectSecure products to use the %APPDATA% environment variable instead. I mean that starting version 6.2.1 broker will look in this folder by default for its user configuration file:
But it should still be the same location, just defined in different way. We have done it because some people may experience similar issues to what you are probably experiencing. The directory junction "Application Data" only exists to ensure that old legacy applications created for Windows XP will work also on newer systems; This junction has been source of confusion to great many people.
Did my answer help in any way?
answered Mar 02 '12 at 22:52
Martin Dobsik ♦