Jump to content

Recommended Posts

Posted
The bursar was using FMS when she accidently hit the power button and shut the computer down. After the restart she complained she was unable to access a record she had been previous editing in FMS. Restarting the server solved the problem but it’s a real pain restarting the server in the middle of the day. Is it possible to restart a service that would fix this problem if it happens again?
Posted
I try to keep my distance from Sims but I'm told it's FSM6 and it looks like the old dos modules.

 

If it has a predominantly white splash screen and starts up in under 2 days it's the new database (MS SQL); if not it's the old one

Posted
The old version runs SQLAnywhere which can be restarted via services.msc, same as anything else. It may (never checked) spew lockfiles somewhere and if a client disconnects unexpectedly they may not be cleared correctly.
Posted
It may (never checked) spew lockfiles somewhere and if a client disconnects unexpectedly they may not be cleared correctly.

 

If you search the supportnet solution search for PDOXUSRS.NET you will probably find the related info. Bafflingly, that file is still required to have user:modify permissions with the new mssql version of fms as I found out to my cost this morning!

Posted
The old version runs SQLAnywhere which can be restarted via services.msc, same as anything else.

 

We used to have to do something similar every now and again, but our route was to go to Start, Run, then type in DBSVMN50 , which gives you a little app from where you can restart the service.

 

It shouldn't affect sims, and you may even be able to run it from a non-server machine, but i've never tried it.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...