[sims] FMS SQL CONNECTION - GENERAL SQL ERROR

[Koldov]

I've moved SIMS and FMS over onto a new VM but I'm having trouble connecting to FMS.

 

 

SIMS work fine and I can log onto FMS from the client on the server, so it seems there is something missing in the workstation install.

 

The workstations haven't been reinstalled, but the FMSCONNECT.ini has been updated to the new server.

 

Is there anything else on the FMS client installation that needs changing (Borland and OBDC is something I've seen mentioned on other old threads about it, but I don't know if that needs reconfiguring - or how)?

[Steve21]

Not used FMS recently but if I remember right the connect ini for it isn’t the one you’d expect to use as it used the whole wow64 virtualisation option

 

In their appdata there will be a virtual store/program files folder that holds a copy of the original connect ini that FMS really uses

 

Might be worth a check on a user

 

Steve

[Koldov]

Yeah thanks, I've found that and it was incorrect, changing it does reduce the error from the previous screenshot to this (with correct server.)..

 

Edited July 27, 2023 by Koldov

[Koldov]

I think I'm going to try to reinstall FMS on a client (luckily it's not SIMS and there's only a few FMS users).

 

From the SIMS (FMS) setups folder there are 3 installation programs:

 

FMSApplicationSetup.exe

FMSInst.exe

FMSSQLApplicationSetup.exe

 

Which one is for the client?

[Steve21]

Inst is the automated one (it then installs both the others via wizard)

 

Steve

[Koldov]

After a bit more research I added 'Connect Timeout=30' to the FMSCONNECT.ini and it connected!

 

So I'm still feeling that this VM isn't quite as snappy as I'd like it to be... anyone got any advice for that?

[tech-man]

FMS speed for us is diabolical… some bits are very snappy, others really really drag.

[Koldov]

Not used FMS recently but if I remember right the connect ini for it isn’t the one you’d expect to use as it used the whole wow64 virtualisation option

 

In their appdata there will be a virtual store/program files folder that holds a copy of the original connect ini that FMS really uses

 

Might be worth a check on a user

 

Steve

 

Just wanted to say thanks again to @Steve21 - I spent a few hours a while ago trying to figure out why a remote user couldn't get on to FMS...

 

https://www.edugeek.net/forums/mis-systems/235171-fms-remote-access-via-cisco-vpn.html

 

Obviously being a remote user on a VPN added some extra potential issues, but as I couldn't work it out I eventually did a different quick and dirty workaround (which I'm not going to admit to on this forum).

 

Anyway... the user brought their laptop in today but logged in to the domain directly it gave the same error!

 

However, it worked signed on as admin but not as the user (which I couldn't have checked before as I didn't have the laptop) so after another 15-20 minutes of testing why and checking all the FMS/CONNECT/SIMS ini files etc. I thought I'd check for anything that might be a user setting... couldn't find anything, so I thought I'd re-check for posts on EDUGEEK for 'FMS'...

 

BINGO!

 

But why the is this file even there and why doesn't it get updated when all the other 'normal' .ini files do!

 

 

Good job this place is here and full of awesome (if sometimes a bit random and niche) technical knowledge , it's so much easier than having to write up my own notes...