If "read socket failed error 10054" is received and the NT event viewer application log has an error"rc is -1 and Error is 10038":Įrror 10038 means its an Invalid socket.This would indicate the need to check for the file's existence or location and copy the file from a different working Windows remote agent if needed. If it returns an error, then the same error is likely occurring when the auto_remote process is being launched by the RA service resulting in the Win Socket error.įor example, the result of "auto_remote -x" may be that it reports an error stating ntwdblib.dll was missing. ![]() A good troubleshooting method for this is to login to the Windows client and run 'auto_remote -x 'from the AutoSys Command prompt. The auto_remote process is dying due to some other execution errors.A system reboot may also correct this condition as well. The auto_remote process that is being spawned by the Remote Agent service is dying due to system resource issues.Re-cycling the system will cause the new system Registry updates from the RA install to be read in by the OS. The Windows machine was not rebooted after installing the client as suggested in the AutoSys Windows Installation manual.The following are possible causes for windows socket errors: ![]() ![]() Read failed stream socket: Connection reset by peer This document lists a number of possible causes for the following 'windows socket' errors:ĪutoPinging Machine AND checking the Remote Agent's DB Access.
0 Comments
Leave a Reply. |