Invalid argument

[Bob]

No one mentioned the switch. Any power interrution here can cause some very 
flacky issuses.

----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at spamcop.net>
To: "Richard Kreiss" <rkreiss at verizon.net>
Cc: "'Filepro 2 List'" <filepro-list at lists.celestial.com>
Sent: Friday, June 22, 2012 11:43 AM
Subject: Re: Invalid argument


> On 6/22/2012 12:00 PM, Richard Kreiss wrote:
> [...]
>>>> Well, *something* happens right around 5PM every day.  Maybe it's not
>>>> even computer-related, or even related to with the client does.  For
>>>> example, do they share an electric circuit with the office next door,
>>>> and *they* turn a bunch of stuff on/off at 5PM?
> [...]
>> Not possible!!!
>>
>> All of the computers here are run off of a master battery backup system
>> consisting of 100 large UPS batteries.  This power is filtered and all 
>> power
>> connections are to this system.  The batteries are constantly being
>> recharged through a power regulator.
>
> So it's probably not an issue with the power to the computers.  :-)
>
>> I think I once sent some of you pictures of this setup which takes up a
>> whole room in the warehouse.
>>
>> As for the IP address being reset, that is something I need to look at.
>>
>> So, does "invalid argument [path to a file]" always indicate a lost
>> connection to the server or can it have another meaning?
> [...]
>
> There are many possible causes.  We're just trying to remotely diagnose a
> problem that is occurring daily, at almost exactly the same time each day,
> and something interfering with the network and/or electric at that time
> (5PM, "quitting time" in many workplaces) that could be the cause.
>
> What about examining the Windows event logs?  Usually, they're just filled
> with a lot of noise, but if you know when the problem is happening, there
> may be something in the event logs at that same time.  For example, 
> another
> user is having errors and aborting programs at the exact same time that 
> the
> event logs include this message:
>
>> Windows cannot access the file for one of the following reasons: there is 
>> a
>> problem with the network connection, the disk that the file is stored on, 
>> or
>> the storage drivers installed on this computer; or the disk is missing.
>
> Sometimes, the specified filename is the .exe itself which Windows was
> unable to access, causing Windows to abort the program.  The logs always
> indicate the same "ERROR_STATUS_DISCONNECTED" error code.  (Of course, it
> doesn't indicate *why* it was disconnected, but it did confirm a network 
> issue.)
>
> Perhaps the event logs will help in this case, too?
>
> -- 
> Kenneth Brody
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list