Quatermass Posted September 14, 2012 Posted September 14, 2012 I've just successfully installed FMS on several new workstations, but on my own one it cannot connect. Looks like the act of running the client (i.e. bringing up the FMS logon box) causes the Server value under HKCU\Software\ODBC\ODBC.INI\SIMS_FMS_DATABASE to be truncated to just the server name (rather than the correct value of servername\sql2008). So logging on then fails. If I set it manually in the registry, running FMS again truncates it again! Any ideas folks?
british_government Posted September 14, 2012 Posted September 14, 2012 I had something similar happening with win7, this happened with us because the fms client didn't have access to read the ss_fms_companies.ini properly. Running as administrator was an instant solution. Although not sure if it will work for you as the client has registry access I assume it is elevated already?
Quatermass Posted September 14, 2012 Author Posted September 14, 2012 It is a Win7 client but we don't have that file anywhere - I seem to remember it was a relic of either an FMS migration or sites with multiple FMS databases? Anyway I'm on as an admin so not sure what's going on...
british_government Posted September 14, 2012 Posted September 14, 2012 Yeah we have multiple databases so that is why, could be worth right click and run as administrator just to test, UAC can do funny things....
matt40k Posted September 14, 2012 Posted September 14, 2012 Check in c:\users\\appdata\Local\VirtualStore 2
Quatermass Posted September 14, 2012 Author Posted September 14, 2012 @matt40k : SOLVED! Nice one. There was an older, incorrect copy of FMSCONNECT.INI lurking in there. A nice W7 gotcha which I may feed back to our LEA...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now