Help - RDAPull problem

  • Thread starter Thread starter chris-s
  • Start date Start date
C

chris-s

Hi folks,

Our app uses RDA pull's to retreive it's data from several tables and this
all works fine when devices are either connected on a LAN or on a dial-up
connection, EXCEPT at a new site where they have been using LAN connections
fine, but have now started to implement remote dial-up connections and we
are finding that the first few tables are pulled ok, but when it gets to the
first one of significant size, the product table, the transfer grinds to a
halt. This table isn't overly big, about 600 rows.

The devices, Intermec 700's, sit in a dock that has a built in modem with
tx/rx lights on the front so you can see any activity. It seems to start out
ok on the products table but eventually all activity seems to stop.

We have tried different docks, handsets dial-in lines and dial-out lines,
all of which show the same behaviour. Remote dial-up comms works on other
sites.

The problem table is about the fourth one it processess. W tried emptying
the product table and it continues on to the next table.

Machine Spec: Win2K Server, SP4, 1024 RAM, twin cpu, SQL Server, IIS. It is
a dedicated machine for this role.

I'm thinking that some sort of tweaking to IIS maybe required, but don't
know where to start.

Any suggestions would be greatly appreciated!

Chris
 
Chris,

You might still want to try loading your product table but only with 50,
100, 150 and so on records. If you can confirm that the process is working
for a small subset of data... then the big question is 'where exactly in the
recordset is the process failing' and second, 'does it fail at this point
each time.' It may be a data problem if there is consistency in the point
of failure.

I have done a dozen or more RDA applications pulling anywhere from 100 to
70,000 records... so, I really don't think that you are overloading
anything... 600 records should come down in a blaze!

I did notice (on the 70,000 record job) that - if the signal quality on the
wlan or dialup was poor... RDA would react just as you described. I spoke
with a few people at M$ about the issues - and their response was... "RDA
has build in failover..." However, we all know that failover doesn't run
forever and if the packets are bad enough - the connection will fail and the
device will stop responding.

Try pulling a small sub-set of data from that table and let us know what
happens.

Rick Winscot
www.zyche.com
 
Hi Rick,

Thanks for the reply. I agree that it is not the volume of data. We copied
the database back to a pc in the office which is just an old < 1Ghz Win2k
pro pc with 512Mb Ram and loads of stuff running and then they dialled in to
this pc and we got past this product table and onto a 'params' table that
just retreives ONE row, and it then showed the same symptons. After hanging
up and dialling again, it got stuck on the original products table, so it
does not seem to be related directly to the table or its contents.

I was able to look at the SSCE log file, but it didn't appear to be showing
any errors of any kind.

We're going to 'go-back-to-basics' with it and start with a known working
database and go from there.

Thanks,

Chris
 
Back
Top