[sims] FMS error - "MIS not found in the location defined as..."

[synaesthesia]

Getting an odd error on FMS now on this new setup. Everything works OK when clicking OK, I've reinstalled it without any problems and checked all the ini files I could find but can't find what's pointing it at this location!

 

MIS not found in the location defined as C:\program files\sims\sims .net\commandpulsar.exe

 

64bit Windows for starters, so no idea why it's looking there!

[matt40k]

Its set within FMS, its used to sync with SIMS for the salary commitments. Something like Tools > MIS Settings. Just need to change it to sims 32bit program files folder

[synaesthesia]

Perfect! Many thanks!

[synaesthesia]

And another one...! The above fixed the message perfectly, however I now have yet another error on startup. Again it works fine once you click OK...

 

Error in XML File - XML document must have a top level element.

Line 0 Column 0

[matt40k]

That occurs if you pick the wrong exe, you did pick CommandPulsar.exe?

[synaesthesia]

I adjusted the shortcut to run finance.exe if I recall. Checking now.

 

* update - Indeed I had changed the shortcut; it was originally commandpulsar but the shortcuts were replaced with those from my template set up which refer to fmsload. No joy whichever of the 3 ways.

Edited August 11, 2015 by synaesthesia

[matt40k]

I adjusted the shortcut to run finance.exe if I recall.

 

Well that would be silly

 

Assuming all your workstations are 64bit you should have:

 

C:\program files (x86)\sims\sims .net

C:\program files (x86)\sims\fmssql

 

The top one is your MIS, the bottom one is your finance system. Shouldn't see pulsar (ie sims .exe) in the finance folder and you shouldn't see the finance(.exe) in the mis folder. The top path is what you'll want to put in, so your finance system can talk to your mis system. What path did you put in the box.

 

To be fair, its pretty stupid thing to have to do, especially as a global setting. Every other app either you do on a per-machine bases or (more likely) it just reads the INI files. Rant for another day.

[synaesthesia]

The full and correct path was there, sorry for confusion. They are indeed in the right places - the shortcuts in my templates point to c:\program files (x86)\sims\FMSSQL\finance.exe

[quaium]

Bringing up an old thread instead of creating a new one but we're getting the error message mentioned by the original poster.

 

However, we have a mixture of 32-bit and 64-bit machines. How do we get around this issue? I thought changing it in FMS would only affect the PC it's installed on but it's changed it for FMS in general on all installations.

[TwistedHelixis]

Would this be fixed by creating a symbolic link in windows?

[Esteban_Child_of_the_Sun]

We use the directory junction of mklink to get round this issue. On 64 bit workstations we run as Administrator

C:
cd "C:\Program Files"
mklink /J SIMS "C:\Program Files\SIMS"

[quaium]

We use the directory junction of mklink to get round this issue. On 64 bit workstations we run as Administrator

C:
cd "C:\Program Files"
mklink /J SIMS "C:\Program Files\SIMS"

 

So what does this do? Create an actual folder in Program Files called SIMS? The commandPulsar file is in the folder C:\Program Files\SIMS\SIMS.net

[Esteban_Child_of_the_Sun]

Here is an article about symbolic links that explains it reasonably well. https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

[quaium]

We use the directory junction of mklink to get round this issue. On 64 bit workstations we run as Administrator

C:
cd "C:\Program Files"
mklink /J SIMS "C:\Program Files\SIMS"

 

Thanks... I managed to get it working using the following command:

 

mklink /J "C:\Program Files\SIMS" "C:\Program Files (x86)\SIMS"

[Koldov]

@synaesthesia

@matt40k

 

 

So I have this problem... I seem to have created it myself somehow... But I can't remember how or why...

 

A while ago we had an issue with the budget transfer to the Access Education Links software (HCSS).

 

To get around this it required the link software and the FMS client to be installed on the server.

 

Among other little issues (like not having a default printer installed directly on the server) it threw an error and I found the solution was to modify:

 

TOOLS > MIS SETTINGS > PATH TO MIS

 

Here is how I have it set...

 

 

We are fully x64, so I presume just changing that line back to say (x86) will set it back to the correct folder and not throw an error anymore?

 

Still can't remember what the error was that meant I had to change it and strange that I did, as obviously the server is x64...

 

Can someone please explain... very... slowly.... what I need to do to correct this...

 

EDIT: OK, so I am bit closer to remembering why I did it... It appears that on the server 'Command Pulsar.exe' is in the Program Files > SIMS > FMSSQL folder and not in the Program Files (x86) folder... But on the Workstation Clients it is the other way around.... Does that mean the server has an x64 install of FMS???

Edited June 24, 2019 by Koldov

[matt40k]

So its the path to your MIS - aka SIMS.

 

Its set in the database, so it has to be the same for all machines that use FMS. Reinstall SIMS on the server so it machines the other FMS clients. Be worth checking any other third party software you might have to make sure it still works.

 

Worth getting your SIMS support team involved as they might spot something not correct - like after reinstall SIMS it didn't update sims.ini or something.