Vantage 3.00.632 error 1432 cannot connect to DCDV7.db

Hosts and Services files were just fine. Removing & re-adding TCP/IP
followed by re-application of Service Pack 5 did the trick.

Thanks All

At 12:45 PM 5/18/2001 -0400, you wrote:
>The following is an EraNet article on the error. It sounds like a TCP
>problem, so check your services file and make sure that there is a line
>for vantage with the right port number for Vantage. The client setup
>should have made the entry, but who knows.
>
>Troy Funte
>Liberty Electronics
>
>Page: 465MPS
>Summary: XA Trouble shooting the 1432 Error
>AnswerBook: Vantage ChangeRequests
>
>PROBLEM DESCRIPTION:
>
>Unable to connect to any database getting 1432 error.
>
>STEPS TO TROUBLESHOOT:
>======================
>
>At the problem workstation, go to a MSDOS command prompt. Begin with step
>#1 below using the Telnet command.
>
>(Sample syntax: at the C:\Windows> prompt type: telnet ntserver vantage
>
>1 - telnet {hostname} {service}
>This should fail if you're getting error 1432 at all.
>
>2 - telnet {hostname} {port#}
>If this fails, proceed to step 3.
>
>If this worked, it means your service to port# mapping is not
>working. The servies file is not correctly set. check that you
>are editting the correct services file. Also check that the
>service you are specifying is mapping to the right {port#}.
>See your network administrator for help locating your services
>file.
>
>3 - telnet {serverip} {service}
>If this fails, proceed to step 4.
>
>If this worked, it means you are having a hostname to IP
>translation problem. Ping {hostname} should work, while
>ping {serverip} should fail, indicating that there is either
>a hosts file problem or a DNS problem. See your network
>administrator for help with this problem.
>
>4 - telnet 127.0.0.1 {port#} (from the server machine)
>If this fails, goto step 5
>Getting here indicates that the problem is not related to hosts,
>DNS or services files on the client. It means that the local
>telnet to the database server worked, so the database server is up
>and listening to the correct port. The problem is that the remote
>connection is not getting through the network.
>
>ping {serverip} (from the client machine)
>
>If this fails, then the TCP/IP packets are not getting through to
>the server or that you're using the wrong {serverip}.
>
>if this works, This probably means that you have a firewall or
>some other device that is not propagating the connection on that
>specific TCP/IP port. See your network administrator.
>
>5 - The database is probably not up, or you're not using the right
>{port#}. Make sure that the database server is up, that it is
>using -N TCP and that a -S {servicename} was suplied as well.
>Make sure that your server services file maps {servicename} to
>{port#} correctly. If you still think that everything was
>correctly set, call PROGRESS technical support.
>
>======================================================
>SUGGESTED SOLUTION: If you are unable to Telnet to the appropriate port
>with the message: "Telnet can not connect to host"
>
>A)Cause:
>
>wrong version files for NT TCP/IP services
>
>B)Steps for Correction:
>
>Remove and reinstall the TCP/IP services and rerun the NT service pack 5,
>please note that service pack 6 has known problems with TCP/IP
>applications of which Vantage is one. Do not load SP6, make sure you load
>SP6a. If you have loaded SP6a on the Server, make sure you load SP6a to
>ALL NT workstations as well.
>
>WORKAROUND: N/A
>
>ADDITIONAL INFORMATION: Try the Microsoft web site.
>
>
>REFERENCES TO WRITTEN DOCUMENTATION:
>====================================
>
>Your operating system TCP/IP documentation.
>PROGRESS Networks guide.
>PROGRESS System Administration
>
>XA400
> ----- Original Message -----
> From: Dan Maddox
> To: vantage@yahoogroups.com
> Sent: Friday, May 18, 2001 12:34 PM
> Subject: [Vantage] Vantage 3.00.632 error 1432 cannot connect to DCDV7.db
>
>
> The error message occurs when attempt is made to fire up Report Builder OR
> Vantage. User killed the HD & I THOUGHT I had re-installed everything
> correctly. Even SAP R/3 works again as well as NetSoft Portfolio
> Elite. Novell's Netware client (v4.80.200007) killed user's environment
> variables, but those, too, have been re-set. What am I doing wrong?
>
> Thanks in advance,
>
> Dan Maddox
> Pactiv Corp
> v207-756-6448
> v207-774-3654
>
>
> Yahoo! Groups Sponsor
>
> www.
>
>
>
>
> To access the Files Section of our Yahoo!Group for Report Builder and
> Crystal Reports and other 'goodies', please go to:
> http://groups.yahoo.com/group/vantage/files/. Note: You must have
> already linked your email address to a yahoo id to enable access.
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>
>
>[Non-text portions of this message have been removed]
>
>
>To access the Files Section of our Yahoo!Group for Report Builder and
>Crystal Reports and other 'goodies', please go to:
>http://groups.yahoo.com/group/vantage/files/. Note: You must have
>already linked your email address to a yahoo id to enable access.
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
The error message occurs when attempt is made to fire up Report Builder OR
Vantage. User killed the HD & I THOUGHT I had re-installed everything
correctly. Even SAP R/3 works again as well as NetSoft Portfolio
Elite. Novell's Netware client (v4.80.200007) killed user's environment
variables, but those, too, have been re-set. What am I doing wrong?

Thanks in advance,

Dan Maddox
Pactiv Corp
v207-756-6448
v207-774-3654
The following is an EraNet article on the error. It sounds like a TCP problem, so check your services file and make sure that there is a line for vantage with the right port number for Vantage. The client setup should have made the entry, but who knows.

Troy Funte
Liberty Electronics

Page: 465MPS
Summary: XA Trouble shooting the 1432 Error
AnswerBook: Vantage ChangeRequests

PROBLEM DESCRIPTION:

Unable to connect to any database getting 1432 error.

STEPS TO TROUBLESHOOT:
======================

At the problem workstation, go to a MSDOS command prompt. Begin with step #1 below using the Telnet command.

(Sample syntax: at the C:\Windows> prompt type: telnet ntserver vantage

1 - telnet {hostname} {service}
This should fail if you're getting error 1432 at all.

2 - telnet {hostname} {port#}
If this fails, proceed to step 3.

If this worked, it means your service to port# mapping is not
working. The servies file is not correctly set. check that you
are editting the correct services file. Also check that the
service you are specifying is mapping to the right {port#}.
See your network administrator for help locating your services
file.

3 - telnet {serverip} {service}
If this fails, proceed to step 4.

If this worked, it means you are having a hostname to IP
translation problem. Ping {hostname} should work, while
ping {serverip} should fail, indicating that there is either
a hosts file problem or a DNS problem. See your network
administrator for help with this problem.

4 - telnet 127.0.0.1 {port#} (from the server machine)
If this fails, goto step 5
Getting here indicates that the problem is not related to hosts,
DNS or services files on the client. It means that the local
telnet to the database server worked, so the database server is up
and listening to the correct port. The problem is that the remote
connection is not getting through the network.

ping {serverip} (from the client machine)

If this fails, then the TCP/IP packets are not getting through to
the server or that you're using the wrong {serverip}.

if this works, This probably means that you have a firewall or
some other device that is not propagating the connection on that
specific TCP/IP port. See your network administrator.

5 - The database is probably not up, or you're not using the right
{port#}. Make sure that the database server is up, that it is
using -N TCP and that a -S {servicename} was suplied as well.
Make sure that your server services file maps {servicename} to
{port#} correctly. If you still think that everything was
correctly set, call PROGRESS technical support.

======================================================
SUGGESTED SOLUTION: If you are unable to Telnet to the appropriate port with the message: "Telnet can not connect to host"

A)Cause:

wrong version files for NT TCP/IP services

B)Steps for Correction:

Remove and reinstall the TCP/IP services and rerun the NT service pack 5, please note that service pack 6 has known problems with TCP/IP applications of which Vantage is one. Do not load SP6, make sure you load SP6a. If you have loaded SP6a on the Server, make sure you load SP6a to ALL NT workstations as well.

WORKAROUND: N/A

ADDITIONAL INFORMATION: Try the Microsoft web site.


REFERENCES TO WRITTEN DOCUMENTATION:
====================================

Your operating system TCP/IP documentation.
PROGRESS Networks guide.
PROGRESS System Administration

XA400
----- Original Message -----
From: Dan Maddox
To: vantage@yahoogroups.com
Sent: Friday, May 18, 2001 12:34 PM
Subject: [Vantage] Vantage 3.00.632 error 1432 cannot connect to DCDV7.db


The error message occurs when attempt is made to fire up Report Builder OR
Vantage. User killed the HD & I THOUGHT I had re-installed everything
correctly. Even SAP R/3 works again as well as NetSoft Portfolio
Elite. Novell's Netware client (v4.80.200007) killed user's environment
variables, but those, too, have been re-set. What am I doing wrong?

Thanks in advance,

Dan Maddox
Pactiv Corp
v207-756-6448
v207-774-3654


Yahoo! Groups Sponsor

www.




To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please go to: http://groups.yahoo.com/group/vantage/files/. Note: You must have already linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]