Jeff, I would check with the sys admin people and if you are running a large raid at the centre that is using proprietary caching. We had the same problem with our Saggita raid and also the HP raid systems and I had to disable;e the caching for them to give consistent results.
Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Johnson Sent: 21 December 2007 13:01 To: [email protected] Subject: Re: weird Network Problem Dave: This is on a corporate network for a very large company so that option is out. Why would all of the other sites not have this problem? Jeff Jeff Johnson [EMAIL PROTECTED] SanDC, Inc. 623-582-0323 Fax 623-869-0675 Dave Crozier wrote: > Jeff, > Definitely sounds like a write caching problem on the O drive. Right click > on drive in system manager and look at properties to turn it off. > > Dave Crozier > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Jeff Johnson > Sent: 20 December 2007 17:52 > To: [email protected] > Subject: Re: weird Network Problem > > Thanks Peter. "Down the line" means that at the same site, running the > same program it has no problem opening up and closing the same tables. > > Let's call it the O drive. The process that is failing, reads a text > file on the O drive and populates records in several tables. After the > process it attempts to close the tables. The first table in the list is > not getting written back to the O driver when the USE is issued to close > it. The next step in the process opens up the tables and populates > other tables on the O drive. At the end of the process, the tables are > opened up again and a text file is created on the O drive. Each one of > these processes are classes with a .Closetables() method. > > It only fails in the first process when attempting to close the first table. > > I am able to copy the application and the data to my system and > duplicate the process but not the error. > > Jeff > > Jeff Johnson > [EMAIL PROTECTED] > SanDC, Inc. > 623-582-0323 > Fax 623-869-0675 > > Peter Cushing wrote: >> Jeff Johnson wrote: >>> It is also consistently failing at the >>> same place. >>> >>> All other table reads and writes in the application at this location >>> work fine. The only thing different about this is that it is in a class >>> and is failing in a .Closetables() procedure. There are other classes >>> down the line that do the same thing and aren't failing. >>> >> Hi Jeff, >> >> Not sure what you mean by "down the line". Do you mean classes used by >> the faulty site or another site. >> >> Sounds like you have proved to yourself that the code works fine as the >> application has been working for that long. If there was an error in >> that class then it would fail for all sites. >> >> We occasionally get "Error reading file" problems and they are always >> due to a dodgy cable or someone has unplugged their laptop to go to a >> meeting etc. >> >> I would try to get hold of some sort of network monitoring software to >> try to see the state of the connection for this site compared to the > others. >> Peter >> > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
