English > Support
Network - connect to server - 401 Error - (Updated)
Markk:
Having issues getting it to run from a network machine
After much Failing, Searching, More Failing, and the such... and finally found this thread http://www.videodb.info/forum_en/index.php/topic,1696.40.html
great help there solved most of my issues...
Last Error 401 - due to resource not shared - hence why moved as below
LOCAL PC (Marks-PC)
Windows 7 Home (192.168.1.66)
PVD 1.0.2.3 Beta
Installed Firebird-2.5.1.26351_1_Win32 on Local Machine
Moved Database to local shared folders path C:\Users\Public\Documents
Wifes Lan Computer
(Win 7 home + PVD 1.0.2.3 Beta)
Connect to server
192.168.1.66:C:\Users\Public\Documents\MOVIES.pvd
From Wifes PVD just now crashes
Problem signature:
Problem Event Name: APPCRASH
Application Name: viddb.exe
Application Version: 1.0.2.3
Application Timestamp: 4f777337
Fault Module Name: fbembed.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e89568b
Exception Code: c0000005
Exception Offset: 060ab0a8
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 5129
Additional Information 1: 0f31
Additional Information 2: 0f3137665bbf0bb676c8a16f3fa76e52
Additional Information 3: 734c
Additional Information 4: 734ccfe73f17be1bff15d862f90cba92
Any Suggestions ?
EDIT Crashing solved was using \\Computer Name:...... \\ = instant program crash
Markk:
Update - More farting around and just getting 401 errors - have moved Movies.pvd to other locations on local machine under fully shared r/w dir locations and still no joy
Possibly the Firebird client is not running correctly - no idea how to check this out
Maybe ill just have to sync the Database across the network from time to time - kinda totally defeats the purpose of the wife adding notes/rating etc...
also in the 401 error - ref to 13:98 a file in the firebird dir so i will reinstall it see what happens
It will some simple stupid thing i have overlooked
- its always the easy stuff that's so complex in simplicity
rick.ca:
Welcome.
--- Quote ---Any Suggestions ?
--- End quote ---
A stab in the dark... I may not understand the 'problem signature', but I wonder about...
--- Quote ---Fault Module Name: fbembed.dll_unloaded
--- End quote ---
That's the embedded Firebird, which shouldn't be involved if the server is being used.
Did you use the Firebird Server Manager (a Control Panel applet) to start the Firebird service? Are you sure it's running? Check in Resource Monitor or Process Explorer.
I find PVD finicky when it comes to changing from a local connection (i.e., using Firebird Embedded) to the server. Sometimes I have to load some other database, then enter the server connection string to the original database.
Sorry, I don't know what the 401 errors are about, but...
--- Quote ---Possibly the Firebird client is not running correctly - no idea how to check this out
--- End quote ---
...maybe we're both right. ;)
Markk:
Ty for your quick Response
Originally crashing was occurring from the lan pc trying to get to the shared Movie.pvd file (now just 401 errors)
FireBirdDefaultInstance - Service is running - confirmed by task manager /services
Full details on the error 401
---
Fail to open database
ErrorCode: 401
Unable to establish a connection.
can't format message 13:98 -- message file c:\Program Files\firebird.msg not found
Error Code: 401
---
Just to confirm in doing the right amount of silly
2 computers - PVD installed on both
1st Computer - Local PC Firebird installed and Database file
2nd computer - LAN trying to connect to database using - Connect to server - Option in PVD
Failing miserably
Have tried loading empty DB on Local PC, with the PVD program open / closed
Do I need to do something else ? ¿
goddert:
Quick shot. Did you modify the configuration file of the server?
--- Quote ---# ----------------------------
# Remove protection against opening databases on NFS mounted volumes on
# Linux/Unix and SMB/CIFS volumes on Windows.
#
# This also permits creating database shadows on mounted network volumes.
#
# ***WARNING*** ***WARNING*** ***WARNING*** ***WARNING***
#
# This option removes an important safety feature of Firebird and can
# cause irrecoverable database corruption. Do not use this option unless
# you understand the risks and are prepared to accept the loss of the
# contents of your database.
# Unless this configuration option is changed from 0 to 1, Firebird can
# open a database only if the database is stored on a drive physically
# attached to the local computer - the computer running that copy of
# Firebird. Requests for connections to databases stored on NFS mounted
# drives are redirected to a Firebird server running on the computer that
# "owns" the disk.
# This restriction prevents two different copies of Firebird from opening
# the same database without coordinating their activities. Uncoordinated
# access by multiple copies of Firebird will corrupt a database. On a local
# system, the system-level file locking prevents uncoordinated access to
# the database file.
#
# NFS does not provide a reliable way to detect multiple users of a file on
# an NFS mounted disk. If a second copy of Firebird connects to a database on
# an NFS mounted disk, it will corrupt the database.
# Under some circumstances, running a Firebird server on the computer that
# owns NFS mounted volumes is inconvenient or impossible. Applications that
# use the "embedded" variant of Firebird and never share access to a database
# can use this option to permit direct access to databases on NFS mounted
# volumes.
#
# The situation for SMB/CIFS is quite similar to NFS with not all configurations
# providing file locking mechanisms needed for safe operation. Using SuperServer
# engine with the database on NT file server may be considered relatively safe
# as file locking protects the database from being used by the several engines.
# Network stack can still change order of writes so you may get a corrupted
# database in case of network errors or power outage.
#
# The useful and safe case is working with a shared database marked read-only.
#
# DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING.
#
# Type: boolean
#
#RemoteFileOpenAbility = 0
--- End quote ---
Navigation
[0] Message Index
[#] Next page
Go to full version