Hi, first the checklist:

1.) Version of AutoMate.: 7.1.3.0
2.) Version of Windows.: Windows 2008 R2 SP1
3.) Error Messages from AutoMate and Event Viewer.: none
4.) Reproduction Instructions.: reboot the server, wait for a little while and then all tasks are stuck in running, and the rest is queued
5.) Task Steps (if applicable). Use the "attach code" button to include steps. Not relevant

 

A while after each reboot  all tasks get stuck in "running" it's stuck on the last step and it doesn't end, I've changed _all_ tasks to include the "stop this task" now, it did not help.

if I click end all running taks from the view running tasks view, it works for a while, but then the same problem occurs again after a little while

I think this problem started after a recent windows update, any ideas on what I can do to resolve this quite urgent problem?

Category Survey

it seems like Network Automation refuses to help me with this,

I think I've found a temproary workaround, I've set up a user to automatically log on to the server and start automate at every boot.

I do not like this workaround and would prefer an actual solution, does anyone have any ideas?

Category Survey

Martin,
Christmas time is not the season where support help desks are heavily populated. Hence some patience may be needed.
However :
- did you check in the service console that the service is set to Automatic ?
But as per your post, it seems that upon reboot the service starts nicely then some time later it stops.
- You should be able to identify in the Windows events log when both the start and the stop occur. Maybe you could find some correlation between the stop time and some external event on the system ?

Category Survey AutoMate 7 version: Windows version:

-------------------------
Jean Delfosse - Automate Beta Tester
Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4

They did reply, the just said that automate 7 was unsupported because it was too old, when I responded to that message I didn't hear anything back, their inital response was quite quick

We have automate 6,7,8 and 9 and we're only having this issue on the automate 7 server, however, the other servers aren't all Windows 2008 R2 SP1

 

I'll see if I can find anything in the windows eventlog later

Category Survey

I found something in the windows eventlog.

automate crashed at 18:00:46 (CET) today

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

Faulting application name: AM7TS.exe, version: 7.1.3.0, time stamp: 0x00000009
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0x0eedfade
Fault offset: 0x0000c41f
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

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

Category Survey

Hi Martin,

You have 4 licenses of AutoMate but your support agreement only covers v8 and v9. We can try to help you identify what the issue is with the understanding that the only solution may be to upgrade to a supported version in which the issue has already been fixed.

Please check the following folder and let me know the file name and size of each file in that folder:

C:\ProgramData\Network Automation\AutoMate 7


It's possible that the .txt log files are either too big for AutoMate to write to them in a timely fashion or the files have been corrupted. You can try shutting down the AutoMate 7 task service and rename the 3 .txt files and then restart the service again. This will create brand new .txt files and may correct the problem.

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