Used AutoLogon But Macro doesn't run

kadelglass · Post by **kadelglass** » Mon Jan 23, 2006 7:23 pm

Hello,

I just downloaded macro scheduler 8.0.1 and I was excited to read that I can now schedule a macro to log into my WinXP Pro computer and run my macro unattended and then log out automatically.

I thought I followed all the instructions and tried 5-10 different things and all that happens is that my computer logs in as me at the time I scheduled and then dies without running the macro. I never see the Macro Scheduler flashing in the System Tray. All this macro is supposed to do is navigate through an IE browser. Any help would be greatly appreciated.

Sincerely,
Ken Adelglass

support · Post by **support** » Tue Jan 24, 2006 8:15 am

Can you get any macro to run with autologon or is it just this macro that fails?

davidadkins · Post by **davidadkins** » Tue Jan 24, 2006 8:08 pm

I am having the same problem with any macro I use Auto-Login on. I have XP SP2. It logs in but then appears to not run the macro or lock my pc back for me. I just bought Macro Scheduler PRO today because of this feature. Hopefully a fix will come soon. Let me know if I can run some kind of trace for you if you need more info. I setup the macro to log but the log is never even created - must not even get to step 1 of the macro. Sent you guys an email as well.

support · Post by **support** » Tue Jan 24, 2006 8:17 pm

Hi,

We need to try to replicate this issue. So far I have been unable to do so. so any and all info you can provide would be great. Windows version and how macro scheduler is set up .. directory structue, macro group directory etc. I also want to connect remotely to one or both of your machines to try to see what is going on.

support · Post by **support** » Tue Jan 24, 2006 8:21 pm

One thing you can check for me... Once logged in by autologon see if the autologon service is running. Look in control panel / administrative tools / services. Is Auto Logon service still running? It shouldn't be.

davidadkins · Post by **davidadkins** » Tue Jan 24, 2006 9:13 pm

When I tried just leaving Macro Scheduler minimized to the task bar it logged in, ran the macro, and locked my pc just as it was supposed to do. When I tried closing Macro Scheduler that's when I have the issue. When it launches it from the scheduler service it's having issues. I don't think it is related to the Login service at all because it won't run any macro from the scheduler service even if I'm logged in already and my pc is not locked.

davidadkins · Post by **davidadkins** » Tue Jan 24, 2006 9:19 pm

OK - When Macro Scheduler (the program) is running the Macro Scheduler Service is stopped (but still setup as Automatic), when Macro Scheduler is not running (the program) the Macro Scheduler Service is 'Started' - I believe this is how it's supposed to work. I know my username and password is setup correctly. Unfortunately though, you can't remote into my pc - it's at my work. (security issues)

badamson · Post by **badamson** » Fri Aug 25, 2006 5:44 pm

I am having exactly the same issue described here. I'm using Macro Scheduler Pro v8.03 running on Windows Server 2003. Has anyone found a solution for this?

Post by **Marcus Tettmar** » Fri Aug 25, 2006 6:07 pm

Please download the debug version of the AutoLogon Service from:

ftp://ftp.mjtnet.com/pub/autologonsvcdbg.zip

Make a backup of the existing autologonsvc.exe which is in your Macro Scheduler folder. Extract autologonsvc.exe from the above zip file into your Macro Scheduler folder.

This creates a debug file in c:\autologonsvc.log

Also enable logging for your macro. In Macro Properties enter the Logging tab and enter a log file and use the full before and after logging option.

Put the following line at the start of your macro:

Wait>20

Now, after running AutoLogon send c:\autologonsvc.log and your macro log file to support AT mjtnet.com

badamson · Post by **badamson** » Fri Aug 25, 2006 6:25 pm

Thanks for the prompt reply. I followed the directions you gave, and just emailed the log file from the autologon debugger. I already had full script logging turned on, but as mentioned by a previous poster, no log is created when this happens.

Edwin.Schwartz · Post by **Edwin.Schwartz** » Wed Aug 30, 2006 8:39 am

I have exactly the same problem - up to now I assumed it was a restriction in the Eval-Version ..... Well, obviously it's not ...

Meanwhile I'm sure it's something with my system configuration:
I downloaded DoLogon.exe an experimented with this tool using the
Windows scheduler. These are the results:

1) DoLogon started from within a batch file: The System logs me in correctly, but then the batch terminates

2) DoLogon started from within a VB EXE program: System logs me in correctly but then the VB EXE "hangs"

3.) DoLogon called from with a MacroScheduler script: again the same problem

System is WinXP Prof SP2; computer is member of a domain; but
the same problems arise when I log in as a local user or local admin.

Hope this helps in troubleshooting ...

Best regards
Ed

Post by **Marcus Tettmar** » Wed Aug 30, 2006 8:43 am

Have you seen this:
http://www.mjtnet.com/forum/viewtopic.php?t=3189

What happens if you disable that Second "Run As.." option in AutoLogon as explained in the above post?

Edwin.Schwartz · Post by **Edwin.Schwartz** » Wed Aug 30, 2006 9:09 am

Thank you very much for this lightnig-fast reply!

Well, I just tried to disable the 2nd "run as .." checkbox and then
scheduled your "displayHelpFile" demo script.:

1) Login works correctly
2) Help file is NOT displayed / not visible
3) after about 1 min or so Win tries to terminate the
(invisible) help file
4) i'm logged out automatically

Note: I Never got logged out BEFORE disableling this 2nd
checkbox.

Regards
Ed

Post by **Marcus Tettmar** » Wed Aug 30, 2006 9:10 am

Can you now try adding a 30 second wait to the start of the script:

Wait>30

Edwin.Schwartz · Post by **Edwin.Schwartz** » Wed Aug 30, 2006 9:12 am

after logging in manually after that test and starting macro recorder,
THEN the help file comes up without beeing activated manually.
Seems that macro recorder remembers the not executed schedule ...

very strange ...

Used AutoLogon But Macro doesn't run

Used AutoLogon But Macro doesn't run

I am having the same problem

New Info

Macro Scheduler Service

AutoLogOn

AutoLogOn

Forgot one point