Almost daily I seem to be getting AM errors. Today its a "aaplication error"....instruction at XXX referenced memory at XXX. The memory could not be written bla bla bla.

I have had "abnormal program terminations", eaccessviolations, as well as another one that I forget what it was called.

Anybody else?

Category Survey

Are there specific tasks running when the errors occur or is it intermittent and across the entire product?

Category Survey AutoMate 7 version: Windows version:

-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665

Seems random due to different times of day and different errors, but it is possible its related to one task that run. Ill keep eye on whats erroring.

Just curious as to if others noticed an increase in AM program errors.

For some reason the AM logs are helping less in AM7....most of the time when there was a AM crash I cant go back through the logs to see what actually happened. Either nothing shows up in the log, there is no step number where the tasked stopped at, etc.

Category Survey

Another helpful place to look for clues after problems occur is the Windows Event Viewer. Do you notice any errors logged there when you encounter problems?

Category Survey

-------------------------
- Rick Johnson
Network Automation

Never checked before. There are some errors:

Attempt to establish local pipe "\\.\pipe\AM7EMPipe" failed with code 997

Attempt to wait and establish pipe from AMEM to Service timed out with code 121


Mostly the second one. Any idea what that is related to?

Category Survey

Hi Allen,

Can you in anyway match the timing of the pipe errors with a specific task that might be scheduled around the same time? This error message is usually caused when AM7EM.exe starts and AM7TS.exe is not started. For the most part, these error messages in Event Viewer are more of a logging message than a real error. If it was a real error, you would know because hotkey and window watcher triggers would no longer function. That's what actually uses the pipe. It's the communication channel between the AM7EM and the AM7TS.

It's possible that if you encountered the referenced memory or eaccess violations, if may have put AM7TS.exe in a hung state. In this case, logging off and logging back on will cause the pipe messages. You will need to either reboot the machine or end the AM7TS.exe process in order to restore the pipe.

I believe we need to determine what is causing the initial error messages you are seeing on the desktop, which in turn should alleviate the pipe error messages too.

Category Survey AutoMate 7 version: Windows version:

-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665

HI,

was this ever resolved? We have started getting the same problem. Looking at event viewer against the task log, this morning for example, there was no job running when event log showed AM7 failed.

Category Survey AutoMate 7 version: 7.1.3 Windows version: Windows 2008 R2

Hi Graham,

Can you please confirm what version of AutoMate 7 you are running?

Do you have any errors in the Windows Event Viewer?

Category Survey

-------------------------

Ricardo Castaneda | Principal Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700