Dear All,

I don't know much about the ins-and-outs of how networking actually works ... which is a
disadvantage I know, but hasn't mattered with setting up DBISAM systems up to now.

I use C/S V3.3

Usually I:

- install DBSRVR on the customers server,
- add the database files
- set up the DBSVR INI file with ports & addresses.
- set the DBSRVR to start at the Server machine's start up.
- run the DBAdmin utility to set up users & database settings, with passwords.

The INI file is just a few lines, as per the help file.

--

I have gone through these steps today with a customer & the DBSRVR is still registering

Main Address: "All Addresses"

(i.e. it doesn't seem to have read the IP address from the INI file)

I can connect to it on 127.0.0.1 & run Admin on it on this address, BUT opening my EXE
(which usually takes perhaps 20 seconds) takes MINUTES (not sure how long, but the whole
of the time I have been writing this it has been starting up & hasn't even got to the main
screen yet!).

--

Is it possible that something on the customers server is messing with the SRVR?

Customers Machine is a vanilla DELL, brand new, XP SP2, OK spec with NOTHING installed on
it except anti-virus software. Could this be interferring with the application??

Adam

adam


If you trawl these newsgroups you'll find lots of posts where anti-virus software is the culprit. If possible disable scanning on the directories used in your app. If not possible, or it makes no impact change the av software.

From memory Norton is one of the bigger offenders.

Roy Lambert

Adam,

<< I have gone through these steps today with a customer & the DBSRVR is
still registering

Main Address: "All Addresses"

(i.e. it doesn't seem to have read the IP address from the INI file) >>

Is the INI file in the same directory as the dbsrvr.exe ?

<< I can connect to it on 127.0.0.1 & run Admin on it on this address, BUT
opening my EXE (which usually takes perhaps 20 seconds) takes MINUTES (not
sure how long, but the whole of the time I have been writing this it has
been starting up & hasn't even got to the main screen yet!). >>

Is the EXE being loaded across the network, or locally ?  If locally, then I
would check any AV software like Roy suggested.  If the EXE is being loaded
across the network, then most likely the issue has something to do with the
network configuration.  A copy test will help confirm this.

<< Is it possible that something on the customers server is messing with the
SRVR? >>

Sure.

<< Customers Machine is a vanilla DELL, brand new, XP SP2, OK spec with
NOTHING installed on it except anti-virus software. Could this be
interferring with the application?? >>

Most definitely.

--
Tim Young
Elevate Software
www.elevatesoft.com

Adam,

> I can connect to it on 127.0.0.1 & run Admin on it on this address,
> BUT opening my EXE (which usually takes perhaps 20 seconds) takes
> MINUTES (not sure how long, but the whole of the time I have been
> writing this it has been starting up & hasn't even got to the main
> screen yet!).


I remember one system where the exe was loaded from server...
(server w2k P4..) 1 server, 10 clients..

It took ~ 40 seconds before the main sreen of the application was
there.. (when connecting session & db), doesn't matter which client...
Normally it should be around 3 seconds to start the app.

after a search we found a lot of gateways installed in the tcp settings
of the server which doesn't make any sense..
after we deleted the nonsense settings everything was working like
expected... I can't remember all the settings..
But it sounds similiar to what you saw...

HIH
ralf

My favourite goes back to Paradox and W98. They'd bought a load of new high spec PC's but the idiot who supplied them installed every network  protocol he could find (TCP/IP, NetBUI, IPX/SPX if my memories right) and most of the PC's had at least 2 network cards defined (one had 4) even though there was only one fitted.


Strangely they were getting "blob has been modified" all over the place.

Roy Lambert

Roy,

That was the IPX/SPX *compatible* protocol that cause the errors.
Microsoft's implementation of Novell's protocol was flawed. That
protocol should never be installed on a computer unless you like trouble.

Sean

Roy Lambert wrote:
> My favourite goes back to Paradox and W98. They'd bought a load of new high spec PC's but the idiot who supplied them installed every network  protocol he could find (TCP/IP, NetBUI, IPX/SPX if my memories right) and most of the PC's had at least 2 network cards defined (one had 4) even though there was only one fitted.
>
>
> Strangely they were getting "blob has been modified" all over the place.
>
> Roy Lambert
>