Home > Advantage Database > Advantage Database Error 6420

Advantage Database Error 6420


The database is running on a Windows XP machine. If running through a firewall, make sure the Advantage IP send and receive ports are properly configured and opened up through the firewall. [Sign-In] Advantage Developer Zone Search Tips and Tricks Disregard the Internet Port setting, as in nearly all cases it can be left at 0. Top Profile Reply with quote Gavin Walker Post subject: Re: Error 6420 The discovery process for the advantage databPostPosted: Wed May 25, 2011 8:33 am Offline Joined: Wed Apr Check This Out

Ensure visibility of the ADS.INI to the client application. 1. Looking at the Advantage Database configuration utility on the first workstation/server it says that 2 clients are attached. The problem is that the name of the Windows NT server machine is not being resolved to an IP address. a.

Advantage Database Error 6420 Caterease

This will be the configured_port referenced below. Thanks for your help i work at a small software company and found this posting via google. The database server computer responds with information to allow Point of Success to connect to the database server. see all the addresses on a multi-homed server and/or client determine which discovery method located Advantage If the multicast fails then a Winsock error will be reported.

To view and edit the filepaths in the PATH, click on Start - Control Panel - System - Advanced tab - Environment Variables button - select PATH under System Variables - The following data paths would make a direct connection to Advantage without any discovery. \\Server:6262\Data\MyDictionary.add \\\Data\

You can also make a direct connection to an Advantage server by specifying the Access via RDP to the Server is fine and Medisoft has worked great for years. Error 6420 Medisoft This file is generated by the Advantage communications layer (axcws32.dll) and logs all the steps taken to connect to Advantage.

On the Medisoft DVD there is a file called \Documentation\MedisoftClientServInstallation.pdf that explains briefly the installation steps. _________________Gavin Walker MedTech Medical Management Systems 417-890-6777 Top Profile Reply with quote scotsmen Advantage Database Error Number 6420 Error 6420 seems to be connection issue, as I know nothing about how the software works, I can't offer any further assistance here. see the specified server's IP address if it is found on the network. This brings up a command window.

However these errors still occur. Advantage Database Error 7077 Upgrade the client version. Yes No © Copyright 2016, Sybase Inc. On the original workstation it's running fine.The workstations are in a workgroup.

Advantage Database Error Number 6420

Thanks, Steve Reply With Quote October 14th, 2007,02:23 PM #2 Computernerd22 View Profile View Forum Posts Visit Homepage AO's MMA Fanatic! Visit Website June 9, 2014 at 11:55 AM Anonymous said... Advantage Database Error 6420 Caterease A client using a dial-up connection to a network and ADSDOSIP can get 1015 or 6420 errors on either Windows 95 or Windows NT if they started ADSDOSIP before initializing the Error 6420 The Discovery Process After you have read through several of these files you will be able to locate the important information quickly.

Initialize the dial-up connection before starting ADSDOSIP. 8. 6420 Error: "Unable to Find the Advantage Service or Unable to find a Bindery on the Network" When Connecting to Novell from a http://bsnux.com/advantage-database/advantage-database-error-7038.html FAQs Tips Books Screencasts Events Version 11 About Me DevZone About Me Chris Franz I am a Senior Solution Engineer in the OEM Group with SAP. Subscribe Topics Advantage 10 (43) Advantage 11 (17) Advantage 9 (23) Advantage Web API (3) All Clients (1) Announcements (8) ARC Tip (22) Books (29) Database Design (4) Delphi (15) Events Login Register Follow SCNJive Software Version: , revision: 201308121150.54f5b14.release_5_0_6_2 Windows Server TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة Error 6420 The 'discovery' Process For The Advantage Database Server Failed

If the Advantage daemon is already running, you must kill and then restart the daemon on the file server to use the newly changed settings. We have done some recent network upgrades and now we are having issues connecting to Advantage. The connection string that is used in your app needs to connect via yourServerName in order for the IP and port specified under yourServerName in the ADS.INI to be used. this contact form This will list all the ports currently in use.

You may require the use of an ADS.INI file if the ADS server is not on the same subnet. Advantage Database Error 7008 If the address and port are found then a direct connection to the server will be attempted if the connection fails it will return 6097 error. Willing to hire someone for expert consultation who can fix this problem.

Probate Plus knowledgebase Submit a request Sign in Probate Plus support Support Articles (All Versions) Error Codes and Troubleshooting Error 6420 "Unable to discover Advantage Database Server" Law Systems support 23

Now we separated the clients out to a new subnet and now we get the Error 7077. Top Profile Reply with quote Gavin Walker Post subject: Re: Error 6420 The discovery process for the advantage databPostPosted: Mon May 16, 2011 12:03 pm Offline Joined: Wed Apr If I move a client back to the old subnet it works fine. Advantage Database Error 7044 When I try to connect it fails (they use port 3000 so my UNC is "\\\adsdata").

June 22, 2015 at 8:47 AM Anonymous said... The opinions expressed in this blog are mine and do not reflect those of my company. In addition, another program, Focus Reports, which links between Medisoft and Advantage Database Server, is installed on my Server , and the same error is being received....even if I work directly navigate here b.