Network NPRO database server could not be found

Axxya Systems support contact details
1-800-709-2977 ext 9 within US
1-425-999-4350 ext 9 outside of US
Email – [email protected]
Technical FAQ -- www.nutritionistpro.com/help-center/
Message – “Database Server Could Not be Found” on client workstation in
NPRO Network Nutritionist Pro application
 In order for the user to access the application the client workstation needs to connect and find
the server. In most cases Nutritionist Pro is able to do that by default; however additional steps
may be needed if you are not able to connect to the server.
 After the server and client workstation are installed launch the Nutritionist Pro software from
the client workstation. If you are able to open the application great you are done the client app
is able to communicate with the server portion.
 If the client workstation is not able to find the database then these steps will help the client find
the server.
1. Ping the client machine to see if it is talking to the server. Sometimes firewalls
prevent client machines from talking to the server machines. Make sure this basic
setup is not the issue.
2. If pinging the client was not an issue then try these steps on the client workstation.
a. If the client workstation is a 64 bit machine, launch the odbcad32.exe from
this path below
Launch the ODBC from this folder NOT the control panel.
C:\Windows\SysWOW64\odbcad32.exe.
b. For a 32 bit machine launch the ODBC from the control panel and admin
tools. Windows Icon or Start Button - Control Panel - Administrative Tools Data Sources (ODBC)
c. See image below of what the ODBC looks like
i. Select the "System DSN" Tab - Select "Nutritionist Pro" - Press
"Configure" - Select the "Network" Tab
ii. TCP/IP should say “host=IP address of server” example:
host=192.168.1.1 see image shown below as example
a. NO space between host=andtheipaddressofserver
3. If you’re unable to connect at this point, there is some sort of security device or
setting, (firewall, antivirus, group policy rule) blocking the connection ports.
i. You will need to open port 2638 for both TCP and UDP on the
server.
ii. Note: You should consult your IT group before
creating any firewall rules or opening any ports.
iii. Go to control panel  Windows Firewall Advanced settings (left
pane). Select incoming rules and Right click. Choose new rule and
follow the prompts.
4. If you’re unable to connect after trying these steps above contact out IT team please
note we will need to talk to your IT admin so we can trouble shoot the issue as
needed
OPTIONAL section below for clients that may need to open ports to connect. If it
doesn’t apply to you skip this section.
IF your setup requires opening some ports and as talked about in Item 3 above and you are unsure of
how to do that please follow these steps. If you have resolved the issue and do not need to open any
ports then you can skip this section below
If you’re unable to connect at this point, there is some sort of security device or setting, (firewall,
antivirus, group policy rule) blocking the connection ports.
a. You will need to open port 2638 for both TCP and UDP on the server. Note: You should
consult your IT group before creating any firewall rules or opening any
ports.
i. Go to control panel  Windows Firewall Advanced settings (left pane). Select
incoming rules and Right click. Choose new rule and follow the prompts.
ii. Follow the same steps, except this time choose UDP instead of TCP.