|
| |
6610 Errors (HW168)
DESCRIPTION:
Generally 6610 errors indicate a communication problem on the network. Some
common causes and solutions for 6610 errors are provided below.
DESCRIPTION:
|
| Following are several problems and solutions
related to 6610 errors and 32-Bit Advantage clients. |
SOLUTION:
|
1. Routers may not be forwarding network
packets between the server and client. There are many causes of this: a
router not forwarding the packets; a server not forwarding packets; a
firewall; or a server with a bad bindery.
2. Setting the desired protocol as the default protocol on the workstation
may avoid the problem. With ADS 5.6 and newer, the desired protocol can also
be set in the ADS.INI file on the client. This setting is documented in the
Advantage help file.
3. Out-dated or 16-bit NIC cards may have problems. Try newer, 32-bit
network cards.
4. When using ADS on Windows NT with NTFS, it is possible to receive 6610 ,
9029 and/or 7013 errors either in the Advantage error log or from the
application on the client PC. This is because the Advantage Server service
does not have rights to the share. The 6610 and 7013 errors may be reported
by the application while the 9029 and 7013 errors will be recorded in the
Advantage error log on the server.
There are two possible solutions to this issue. The recommended solution is
to add the System account to the Share where the data resides and give the
System account Full Control. This will provide access rights for all
services, including the Advantage Service, to all the files in the share.
An alternative method for resolving this issue is to create a new user on
the server, give this user account Full Control on the share where the data
resides, then Advantage Service startup properties (from within the Service
Control Manager) so that the Advantage Service will use this new user
account.
5. It is possible on a WAN that the routers are filtering SAP packets.
Configure the router to allow the Advantage Database Server for NetWare SAP
packet object type to pass through the router. The object type for the
Advantage Database Server for Netware versions 3.0 and newer is 0x77B (1915
decimal).
6. A 6610 error can occurs immediately after connection to the 2.6 version
of the Advantage Internet Server ( AIS ) if the Watch Dog Cleanup Interval
setting was changed and AIS.EXE was not restarted. Restart AIS.EXE after
making changes to the Watch Dog Cleanup interval setting.
7. A client application tries to connect to the Advantage Database Server.
The application hangs and it eventually returns a 6610 error. The CPU
utilization on the server is 100 percent. This problem occurs if the number
of worker threads has been configured to more than 254 threads. This has
been identified as an issue with the Advantage Database Server version 6.0
and will be fixed in the next release. To resolve, use the Advantage
Configuration Utility to reduce the number of worker threads.
8. 6610 errors are generated by an ODBC application attempting to access
data through the Advantage Internet Server when System or File Data Source
Names are used. Use User DSNs only when accessing data over the Advantage
Internet Server.
9. 6610 errors can occur after the Watch Dog process removes the connection.
This error can occur when a third party application, installed on the same
machine running Advantage Internet Server ( AIS ), replaced the MicroSoft
WSOCK32.DLL. Try stopping or un-installing the application that owns the
WSOCK32.DLL. To determine the owner, right click on WSOCK32.DLL from windows
explorer. Click on the "Version" tab and verify the "Company Name" is
Microsoft. If the DLL is not a Microsoft DLL Move the proprietary
WSOCK32.DLL to it's application's directory. Remove and re-install Microsoft
networking. This will cause the WSOCK32.DLL to be a Microsoft's file and the
application that owns the proprietary DLL will use its own DLL.
"WinProxy" is one example of an application that has a proprietary winsock
DLL.
10. Previously working connections of an application get 6610 errors after a
new workstation logs on to the server. This new workstation is usually a
laptop (a workstation that was previously logged into another domain for at
least 30 minutes).
There is an issue with Windows 95 networking where a PC that has its browse
master enabled or automatic will retain it's domain information after it has
been logged into a domain for more than 30 minutes. Then, when the
workstation is connected to another network and logs into a new domain,
other workstations may use it as the browse master, and thereby use it's old
domain information, causing the 6610 errors.
The MSDN library Networking article: "Browsing and Windows 95 Networking:
Part1", p.9, recommends the following solution:
"Note: If a computer is removed from the network before the computer is
logged off the network, it may take up to 45 minutes for that computer to be
removed from the browse list." (This seems to mean that it needs to be on
the new domain for 45 minutes before being corrected, so the following steps
will give a more immediate solution)
"Step 6: Verify that the browse server is available: If your network
includes computers that are frequently powered off or removed from the
network(such as mobile computers), it is a good idea to disable master a
backup browser server duties on these computers."
To disable browse server duties on a Win95 based computer:
1. Go to Network Neighborhood, Properties, Configuration Tab, double-click
the File and Printer Sharing component.
2. In the Property box for File and Printer Sharing for Netware Networks,
click the advanced properties tab, click Workgroup Advertising, and then
click Disabled in the Value box.
Alternatively, for Netware networks, click the Advanced tab, WorkGroup
Advertising, then Disabled.
3. Click OK and shutdown/restart the computer.
Note: At least one computer in each workgroup must have the ability to
become the master browse server. If all are disabled, browse functionality
is lost.
|
BY: MRA - 04/2002
|
