Multi User Mode

M

mediamarket.gi

New Member
Hi Guys,

I wonder if you can help me....We have been called in to restore a server that died ..We have done that succesfully along with the other apps and SQL dbs that he had hosted on it :)

We are having problem with a particular App called OpenAccounts. I have restored the Progress DB Susscefully and we can access the Program and DB by remote desktoping on the server..But when we try a second user to remote desktop and open the application we get an error that says DB is in Single User Mode..

Do you guys have any idea on how to change the database to be Multi User Mode so more that one user can access the Program via remote desktop ??

Kind Regards
 
Got any documentation?

You need to start a server. There should be a script or shortcut that was used to do this. Starting a server is easy, but getting all the right parameters so that it will be optimally functional isn't a task for someone with no knowledge of Progress, so hope that there is a script and parameter file around somewhere. Of course, most databases are poorly tuned, but that is another topic.
 
There are a million or so ways that the original system might have been launching the multi-user startup so hopefully there is some documentation ;)
 
Hey Guys thanks for your responses.

I have managed to start up two of the DBS in Multi User Modes with no knowledge at all on Progress DB and works fine. I have also set up a startup.bat so if the server needs rebooting it will automatically start :)

For the record this is how i did it proserve -db <location of db> -H <servername/hostname> -S <portnumber>
 
I hope you aren't trying to put this machine into production with only those parameters ...
 
I hope that he has ;)

Seriously though, that's fine, what you have done will certainly "work" at least insofar as the goal is simply to get multi-user access available.

It might even be all that is needed if this is a very small and lightly used system.

That isn't usually the case. Generally a system that is deployed and in use will also have things like batch processing that need to operate. It might have also have a need for non-default parameters due to size or system load. There may also be other services that need to run either for application functionality purposes or for optimization.

Without documentation knowing what those things are (if there are any) isn't possible in this forum.
 
The Server is currently in production use...

It is running a low level application which does around 100 transactions a day.

I think it is OK untill they move on to there new application with SQL backend
 
You must log in or register to reply here.
Back
Top