Login Fails "Error connecting To Database"
PrimeCut Client fails to log into Server database with "Error connecting to Database" message or similar
DNS issues are quite common, particularly .
•Obtain IP address of both client and server using ipconfig or similar, do not use ping for this!
•Ping the server from the client using the IP address and then ping client from server using the IP address
•Ping the server from the client using the short server name, eg SERVER01. Then ping client from server using the short client name, check that the IP address used for both matches the IP addresses retrieved above. You might have to force it to use IPV4 e.g. "ping -4 SERVER01".
•Ping the server from the client using the fully qualified server name, eg SERVER01.thecompany.local, and then ping client from server using its fully qualified name, check that the IP address used for both matches the * IP addresses retrieved above
•If pinging by IP address fails then you either have the wrong address or there is a network problem that the customers IT team will need to resolve
•If pinging by IP address works but not by name then this will be a DNS related issue and the customers IT team will need to resolve this.
•If pinging by IP address and by name works, but not using the fully qualified domain name, then it will be a DNS issue.
•If the IP address does not match that used by the ping then either there is an incorrect entry in the hosts file or there is a problem with the customer's DNS
A solution that has worked in the past:
•Run command prompt on the server as admin.
•Try typing "nslookup" into command prompt on the server. If you get an error, it could well be the DNS is not registered. If working, you should get a display back showing the Name and IP address.
•If you got an error, try typing "ipconfig /registerdns"
•Then try nslookup again.
A short term work around (which is best not to do as it can cause future problems) is to place an entry in the Hosts file on the client computer:
•Open Notepad 'As Administrator'
•Within Notepad browse to C:\Windows\System32\drivers\etc
•Change the file type to open to '* All Files'.
•Open the Hosts file
•Place a new entry with the IP address of the server [SPACE] name of the server. Be sure to include the .domain.local if this is indeed the address of the server rather than just the servers short name.
Try renaming fbclient.dll in the primecut folder to gds32.dll
If a gds32.dll is found in the system path it will be used instead of fbclient.dll, and it is likely to be the wrong version and/or 32 bit instead of 64bit.
Has Client been "Properly" installed?
Sometimes just the files have been copied over, resulting in ODBC in particular not being setup. If Primecut is not listed in Control Panel, Programs and Features, this is likely. Reinstall using the proper clientinstaller program.
•Check spelling of production datastore matches the server. Eg Capital P vs lowercase p.
•Check firewalls, Port 3050 and 2020 TCP must be open between the client and server.
Firebird2.5 may still be running on the server, "running interference"
We have seen this before, particularly after a Firebird 3 upgrade of an old database. The Firebird 2.5 service may still be active and intercept requests on port 3050; we have seen cases where it intercepts external requests (client running on other machines) but not internal requests (client running on the server)
