Sami, Do you know the secret of what appears to be random file names of the $$$ files?
----- Original Message ----- From: "Sami Aaron" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 22, 2002 8:23 AM Subject: Re: problems after installing in-line patch 1 > Bernie - > > The bad network connection can be elusive - but one way might be to take a > look at the old $$$ files that get left when a user loses connection or > doesn't exit the app properly. From a network administrator program (or > even Windows Explorer, in some systems) you can see who created the file. > > If the users are getting the I/O error on a regular basis, that definitely > indicates a network problem - it shouldn't happen. > > Sami > > ----- Original Message ----- > From: "Bernard Lis" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, January 21, 2002 7:50 PM > Subject: Re: problems after installing in-line patch 1 > > > > Sami, > > thanks for your response. > > My customer told me that they do a reload when they get the disk I/O > > problem. > > And how do you find a bad network card amongst a dozen computers if > they're > > all working? > > > > But they told me that one user just started using the database over the > web > > on a VPN. The vpn was set up months ago and I thought they were using it > > right along but it was too slow so they went back to the dial up modem. > But > > they just started using it again this past week. Could a vpn connection > be > > causing the "waiting for required resources"? > > Over the vpn, the client is: > > 1. printing picking slips > > 2. sometimes making adjustments to the quantities shipped, if they are > short > > of stock and > > 3. printing invoices. > > > > > > ----- Original Message ----- > > From: "Sami Aaron" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, January 21, 2002 12:21 PM > > Subject: Re: problems after installing in-line patch 1 > > > > > > > Bernie - > > > > > > The "I/O Problems - disk full" message usually means a corrupted > database > > or > > > corrupted indexes. > > > > > > Do a RELOAD and see if that fixes that problem! > > > > > > The other message - "unavailable resources" (did you mean "Waiting for > > > required resources"?) often means a bad network card or network > > connection > > > for one workstation on the network. It may be resolved when you do the > > > reload - if not, check for connection problems. > > > > > > Sami > > > > > > ----------------------------------------------------------- > > > Sami Aaron > > > Software Management Specialists > > > 13214 W. 62nd Terr, #139 > > > Shawnee KS 66216 > > > 913-915-1971 > > > http://www.softwaremgmt.com > > > ----- Original Message ----- > > > From: Bernard Lis > > > To: [EMAIL PROTECTED] > > > Sent: Monday, January 21, 2002 10:38 AM > > > Subject: problems after installing in-line patch 1 > > > > > > > > > We are getting 2 situations that did not exist b4 installing the patch. > > > 1. I/O problems - disk full > > > 2. Unavailable resource and starts counting up to 100% > > > > > > These problems occur mostly during data entry. > > > 10 computers are using the dos version, running a combination of pure > dos, > > > win95 and win98. > > > One computer is running the windows version under NT 4.0 sp5. No > changes > > > have been made to the programs. > > > > > > At first I shrugged it off as something we've seen b4, but now it is > > > happenning too frequently. > > > > > > Any suggestions on what to look for? > > > > > > Bernie Lis > > > Megabytes, Inc. > > > > > > > > > ================================================ > > > TO SEE MESSAGE POSTING GUIDELINES: > > > Send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: INTRO rbase-l > > > ================================================ > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
