Created:
Sep 17, 2010
Views:
3279
Author:
JH

Error accessing ProSelect Network Server

If you find that you are occasionally or frequently getting the message:

"The Proselect network server could not be found, could not be accessed or does not have any data available. The data on your computer will be used instead"

when you start ProSelect, then this could be caused by the it taking too long for ProSelect to receive the data from the ProSelect Network server.

Versions of ProSelect up to 2010r1.6 have an internal timeout of 5 seconds for receiving this data. With modern network speeds, this is normally more than enough time for receiving a small amount of data over a network.  However it may not be if you have one or more of the following:

  1. A large number of Prices and/or Templates in ProSelect (this increases the amount of data that needs to be transferred).
  2. You are running the ProSelect Network Server on a slow or busy machine.
  3. You are using a slow or busy network connection between the machine running ProSelect and the machine using the ProSelect Network server. A wireless connection would be the slowest but even a busy 10MB wired connection could be a problem with a very large data file.
  4. You are running ProSelect on a slow computer.

You may have found that your connection to the ProSelect Network Server was working fine but as you increased the amount of data (by adding more prices and templates to the file) that this problem started occurring more often.

Solution

To solve this problem, we have increased the timeout to 30 seconds in ProSelect 2011r1 (due for release in late October/Nov 2010). In the meantime, if you are having this problem, have a look at ways to improve one or more of the items listed above and the problem should go away.


KnowledgeBase Article: Error accessing ProSelect Network Server