|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
|
Apprentice |
I am testing setting up Daylite on a network. Daylite is being server on my Powermac G5 with static IP. I am trying to connect with my MacBook Pro. I can not access the database with both computers at the same time. I have set up multiple users but i get this message each time: Unable to connect to the database. Too many users connected. Help!
|
||
|
|
Veteran |
Hi Scott,
Do you have enough licenses (2+) to handle 2 simultaneous users? Please make sure that you have all licenses entered on all computers. If you only have 1 license, and you want to access the database from the MacBook, then you will want to log out of the Daylite database on the server and quit the Daylite application on the server. Then you should be able to log into the database from the MacBook. It is not necessary to have the Daylite app open on the server in order to serve up the database. HTH, Cynthia MacBook Pro OS X 10.5/Daylite 3.7.6 ______________________________________ Daylite Master Partner, Daylite Report Certified www.daylitehelp.com ______________________________________ |
|||
|
|
Apprentice |
With the appropriate licenses, can I have simultaneous access to a shared database file by multiple team members? I see that Openbase supports row-level-locking. How does that work with the database file shared on a server if Daylite isn't running. Or do I need to have Daylite running on my "server."
Thanks! |
|||
|
|
Marketcircle Team |
Kepano,
Yes - with the appropriate number of licenses, you can have multiple team members connect to a single Daylite database and yes - we use row level locking to handle this. Daylite - the app - does not need to run on the server. You only need to install it there and run it once after an install (so it starts the appropriate database processes after the installer is run). The only thing you need running on the server is the OpenBase database and the three OpenBase processes. |
|||
|
|
Marketcircle Team |
This particular issue has be cropping up of late. What is happening that is a Daylite client - for some reason - is not releasing the connection to the database. There are two workarounds: 1) When leaving a database - quit Daylite instead of logging out of a database. 2) When you get the dreaded 'too many users', go to OpenBase Manager (on the machine that has the database) and stop and restart the database. Hope this helps - while we figure out what the cause is. |
|||
|
|
Pro |
One of my clients is getting this issue on a fairly regular basis. To work around it, we have been quitting DayLite on all the clients and then restarting each one.
I could teach them how to stop/start the database, but they are lawyers and would be afraid to try it, and offended that they would have to do it. Is there some AppleScript/Automator Workflow that has been tested for doing this? Ideally something that one person could run and it would gracefully disconnect all users (only three in this case) and then reconnect them? Along that same line, it would be very nice for DayLite to have a method disconnecting all users from one workstation and informing users that the database will be shutting down in X amount of time. Giving users a chance to either ask for more time or to go ahead and shut down. This is one of those GoldMine features that I sorely miss when administering DayLite. Especially when I am having a user do some admin task when I cannot physically be there to do it myself. (I'll also post this last comment to the feature request e-mail.) *********************************** Macsimum News |
|||
|
| Previous Topic | Next Topic | powered by eve community |
| Please Wait. Your request is being processed... |
|

