English > Support

Network - connect to server - 401 Error - (Updated)

<< < (2/3) > >>

Markk:
Goddert - No

Update: As noted by Buah in his post: http://www.videodb.info/forum_en/index.php/topic,1696.40.html he referred to port 3050 - I added an exception to windows 7 firewall to allow traffic

Note: 192.168.1.66:C:\Dump\MOVIES.pvd - Worked to open database
but: MARKS-PC:C:\Dump\MOVIES.pvd - Failed to open database

So 1/2 Solved can now open 1 version at a time from either PC
If the PVD is open on 1 PC then it locks the DB

Failed to open database Errorcode 664 .... database is probaly already open in another engine instance in another windows session ... blah blah

It this working as intended? is this a limitation? or is something still not right?
At least its kinda working

rick.ca:

--- Quote ---or is something still not right?
--- End quote ---

Right. The very point of a server, of course, is to support multiple connections. Both instances of PVD have to be connected via the Server. If one of them is connected via the embedded version, that will lock the database. Does that help?

Markk:
As I Thought - yes your right
Also From Local PC:  192.168.1.66:C:\Dump\MOVIES.pvd - working as intended

Now to set this up on my friends computer...  ;)
Thanks everyone for your help - see it was simplistic after all...

So Basically from the Top in order to Run PVD from Multiple Computers on a typical LAN

1) Install PVD on all computers
2) Install Firebird on Master PC
3) Set UP Database on Master PC (must be a local drive - not on a network share or NAS)
4) On Master PC Open Port 3050 in your firewall to accept local traffic
5) Get your Path Information Correct (ie start run - cmd - ipconfig get your PC IP for Master PC) so you will use IPaddress:Location  ie(192.168.1.66:C:\Dump\MOVIES.pvd)
6) on all Computers Use the Connect to server and use the 5) correct Path ie(192.168.1.66:C:\Dump\MOVIES.pvd)

rick.ca:
Well done. Thanks for sharing the correct method.

goddert:
Warning... the locking mechanism on NFS/SMB shares isn't safe (except with super server - but this is overkill for PVD). So be sure your database is always locally attached to your server machine (physical drive of the server machine). E.g. accessing concurrently with two servers to a shared db isn't save and destroys your data.
In a scenario like this you should consider your use case. How often do you change the db? Maybe a solution with a regular synchronization would be more convenient. In the end it's only one file.
Or use, e.g., a php framework. Nice with tablets in front of the TV :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page