[sims] FMSConnect.ini reverting back to old SQL Server

[defrostie]

I have just performed an upgrade from SQL Server 2008 to SQL Server 2014. It went relatively smoothly.

 

SIMS is working correctly, but FMS is not.

 

I have set in Solus3 for the Connect.ini and FMSConnect.ini files to point to the new SERVER\SIMS2014 database instance, but FMS keeps changing the FMSConnect.ini as soon as you try and sign in.

 

On one of the machines I have even manually changed the FMSConnect.ini file to point to the new SQL Server, but it will change back as soon as you try and log into FMS, giving this error: "Invalid user ID/Password or Database Name".

 

Is there an additional step I was supposed to take for FMS? As the SIMS Connect.ini is working fine.

[ITJS2015]

Is the FMS connect.ini locally or on a mapped drive ?

 

We do not use mapped drives with solus 3 deployment , I would copy it to your local machine and edit the file.

[defrostie]

The FMSConnect.ini file that is in G\SOLUS3\UpdateRepository is correct and doesn't change. SOLUS3 3 is set to 'Update' the clients based on the info in that file.

 

When I checked the file on the local machine, it has the correct details in the C\Program Files (x86)\SIMS\FMSSQL initially, but after attempting to sign in to FMS it will revert back to the previous SQL Server 2008 details.

 

There must be an auto-config file or something doing this... Can't work this one out.

[ITJS2015]

Depending who ever is your sims provider, I would ring your 3rd party to remote in. I do not deal with capita as they are a terrible at getting back to you but if your use a 3rd party company just give them a call and I'm sure it would be quickly resolved

[Banjo]

Can you login on the Server to FMS (SQL2014)? As has been said, most likely a local FMSconnect.ini on the workstation that needs changing. As a quick workaround put a redirect for FMS on the 2008 instance to point to 2014.

[mrwoberts]

Having a similar issue on one of the admin PCs. We've recently upgraded from 2012 to 2014 and the user in question has been able to successfully login since the migration, but just a couple of days ago we deployed the latest updates from Solus, and now just one user cannot login to FMS, but can login to SIMS...

She can login to FMS on the server, but when she tries the same credentials from her PC we get the same message...

"Invalid user ID/Password or Database Name"

I'm just going to take a look (remotely) at her local setup.

[Arthur]

When I checked the file on the local machine, it has the correct details in the C\Program Files (x86)\SIMS\FMSSQL initially, but after attempting to sign in to FMS it will revert back to the previous SQL Server 2008 details.

 

There must be an auto-config file or something doing this... Can't work this one out.

Do you have an SS_FMS_Select.ini in %ProgramFiles(x86)%\SIMS\FMSSQL?

 

This will contain a line named Companies File Location which tells FMS to look at a file called SS_FMS_Companies.ini in the path specified and will override the settings in your FMSConnect.ini.

 

SS_FMS_Select.ini

[sELECTORPATH]
Current Company Selection=02
[color="#FF0000"]Companies File Location[/color]=[color="#800080"]S:\Sims\fms\[/color]
FMS Location=C:\Program Files (x86)\SIMS\FMSSQL\
DfE LA Code=987
DfE School Code=6543
Include LA School Info in Shortcut=NO
View=Detail

 

SS_FMS_Companies.ini

[9876543]
Licence=ABCXYZ

[987654301]
Company Code=01
Company Name=School FMS
SQL Database=FMS
STAR Database=
Server Name=SIMSSERVER\SIMS2016
Trusted Connection=No

[987654302]
Company Code=02
Company Name=School Academy FMS
SQL Database=FMSACAD
STAR Database=
Server Name=SIMSSERVER\SIMS2016
Trusted Connection=No

 

Edit. Check %LocalAppData%\VirtualStore\Program Files(x86)\SIMS for old INI files too.

Edited September 28, 2017 by Arthur

[mavhc]

As Capita never finished their How To Program For Windows 3.1 book, remember to check the VirtualStore for per user copies of Windows and Program File files.

[mrwoberts]

VirtualStore was the culprit for me!!

[defrostie]

Thank you @Arthur and @mavhc for your suggestions regarding VirtualStore. I couldn't see any VirtualStore folders on this particular machine, but it seems to have helped @mrwoberts, which is good.

 

I think the issue is now solved. The user has been able to log in successfully, but I'm not completely satisfied that it is 100% sorted.

 

After diving into the computers program files it turned out that the user had two separate instances of FMS installed. One in 'Program Files' and the other in 'Program Files (x86)'. After changing both the 'FMSConnect.ini' files and making sure that Solus3 is set to 'Overwrite' and not 'Update' the .ini config files, things are now working. I am not sure whether it was the Solus3 change or making sure both .ini files were set correctly that cured it, but at least it is working for the time being.

 

Thank you all for your help with this - I hope that this will stick and not revert back like what was happening before!