Home > Advantage Database > Advantage Database Error Number 6420

Advantage Database Error Number 6420


There is a lot of great information in the Knowledge Base on the most common connection errors such as 6060, 6420 or 6610 . If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? or a workaround would be to use local server to open the table to be restructured, or use ALTER TABLE or AdsRestructureTable( ). 11. For example an entry for MyServer is specified in the ADS.INI file (see syntax below) so the connection string \\MyServer\Data\MyDictionary.add will become \\\Data\MyDictionary.add. [MyServer] LAN_IP = LAN_PORT = 6262

Check This Out

Configure a port for Advantage on the server computer. May 5, 2016 at 9:01 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Advantage Announcements Loading... This brings up a command window. If the IP address cannot be reached a 6097 error will be returned.

Posted by Chris Franz at 6:00 AM Labels: Server Tip, Tips 8 comments: Paul said...

Caterease Advantage Database Error Number 6420

If IP address and port, attempt to connect directly to it. I started working with Advantage Database Server in 1999. With the initial release of Advantage Database Server (ADS) v5.7, there existed the possibility of some client connection problems. We have a VPN configured.

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 c. Verify the Advantage Database Server Service is running on the computer hosting the Medisoft data.  Use the Advantage Configuration Utility on the hosting computer to review the Advantage Database Server Service's Medisoft Error 6420 For the ADS.INI to be visible to Advantage, it must be located in one of the following folders.

Was Here Rethinking dev.idaho 1 year ago The Invisible Database I'd rather play golf Wandering Data Rows and Columns My Shared Items Friday, November 7, 2008 Tip #5 - Bypassing the If you need more detailed information is required add COMMCALLTRACE=1 to the ADS.INI file under the [Settings] heading. I am glad that you found the information useful. this Join & Ask a Question Need Help in Real-Time?

You will easily come to know if it is a your created problem/sybase vs OS version compatibility/bug in OS or sybase which leads to the error => solve it yourself/put in Error 6420 Axserverconnect If all the discovery threads fail then an error code is returned. This will be the configured_port referenced below. A Month of Tips ► October (13) ► September (10) ► August (7) ► July (11) ► June (13) ► May (10) ► April (5) ► March (1) ► February (1)

Advantage Database Server Error 6420

After you have read through several of these files you will be able to locate the important information quickly. http://blog.advantageevangelist.com/2008/11/tip-5-bypassing-advantage-discovery.html The error I get is "you have no rights to this server", but that might be an error phrase from Medisoft rather than ADS. Caterease Advantage Database Error Number 6420 February 14, 2014 at 12:36 PM jmaybe said... Error 6420 The 'discovery' Process For The Advantage Database Server Failed Click on Start - Search and follow prompts to initiate a file search for files named ADS.INI.

Proposed as answer by Michael ShaoMicrosoft contingent staff, Moderator Thursday, March 31, 2016 9:02 AM Marked as answer by Kate LiMicrosoft contingent staff, Moderator Friday, April 01, 2016 10:26 AM Wednesday, his comment is here You can also specify a different port to use in the Advantage Database configuration manager. For a limited time this address is kept for quick reference. The time now is 04:27 AM. : Hi, GuestLog OnJoin UsSearch for: HomeActivity0CommunicationsActions0BrowseMoreContentPeoplePlacesRecent Bookmarks More documents in SAP Advantage Database ServerWhere is this place located?All Places SAP Advantage Database Server Caterease Advantage Database Error 6420

When the client connects it will check for the server name specified in the connection string with the headings in the ADS.INI file. I've tried lots of combinations like using ADS.INI and such for lan_ip and lan_port.The actual ADS server resides remotely on their subnet at, but of course since I'm VPN'd in, The opinions expressed in this blog are mine and do not reflect those of my company. this contact form Earlier versions of the Advantage client communications layer DLL used an obsolete Microsoft API call that sometimes worked when the standard method of discovery of the Advantage Database Server failed.

You will also need to verify that UDP traffic is not being blocked across the VPN.If you are still getting connection errors I would recommend doing a search in our knowledgebase Ads.ini Location At the prompt, type "ipconfig" without the quotes. 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

6420 Unable to "discover" the Advantage Database Server Advantage Error Guide Problem: The Advantage application was unable to connect to the Advantage Database Server.

This will ensure that name resolution is working and it will return the IP address. If this is your first visit, be sure to check out the FAQ by clicking the link above. 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 Advantage Ip Send And Receive Ports December 2, 2008 at 9:34 AM Chris said...

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. At the prompt, type "netstat -a" without the quotes. However, the discovery process can be avoided by changing your connection string or by specifying details in the ADS.INI file. navigate here Ping the server computer IP address from the client computer.

Upgrade the client version. I ran into this issue after some network changes and your fix worked! These steps are generally executed very quickly and the server is found and a connection is made. This can be done via the Query Options dialog that is accessed by clicking the button that has the screwdriver, hammer, and wrench on it.

Perhaps, a firewall? Privacy Policy Site Map Support Terms of Use 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)Россия (Русский)ישראל (עברית)المملكة العربية السعودية