If you have been a follower of my blog for sometime now, you will recall that back in January of 2009 (ok, I don't expect you to remember this) I posted an article on the subject - see How to schedule Dynamics GP to automatically log in and run an Integration Manager integration. In short, the article looked at using the Windows Task Scheduler to launch a batch file, which in turn would launch Microsoft Dynamics GP, which in turn would use a macro to log into the system, then run a previously created shortcut to run the integration...in summary, a very complicated set of steps if you ask me. This method also presented a problem for users running Windows Server 2008 and above, since the Windows Task Scheduler no longer supports desktop interaction, which is required by the macro system to execute a macro.
Fast forwarding one year and almost half later, and I still get this question regularly: How can I schedule an Integration Manager integration?
Here is my new secret...
I use a (non-Microsoft) product called System Scheduler Professional by Splinterware. It turns out that System Scheduler has no ties to the Microsoft Windows Task Scheduler - none whatsoever! In turn, it allows the product to do some really cool things like running as a service application which is just exactly what's needed if you are going to schedule stuff when locking down your computer before leaving for the day is a must.
![]() |
| System Scheduler - Event Setup |
System Scheduler allows you to setup an event or a list of events to be executed and even more cool, it allows you to send key sequences to an application with a complete help file that illustrates what's possible. In older systems (like Windows XP) you can even set it up to unlock the computer and lock it as part of the list of events. Due to restrictions in the way Windows 7 is built this is not possible, but still, not needed if you consider that System Scheduler can run as a service under the LocalSystem account or a named account.
![]() |
| System Scheduler - Advanced Options |
System Scheduler Professional by Splinterware.
The Professional version allows you to try it out for 30 days before you need to register it. It is really very simple to use and if you had had any exposure to Windows Task Scheduler then this should be a breeze. Now, instead of the complex steps mentioned in the previous article, you can schedule Microsoft Dynamics GP to launch with the typical parameters and use a macro to log you in (if not using Microsoft Dynamics GP 2010 to remember the user and company for you). Once GP is up and running, you can use a the SendKeys function to lunch IM (or IMRun) and execute the integration of your choice.
As it turns out, you can also have a multi-event schedule that first launches GP then launches IM with the integration as a parameter. Please try the tool out and let me know what you think.
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/


6 comments:
An interesting post.
I was directed to your post by a Microsoft support technician after having repeated problems running an Automated Integration against the latest versions of GP. This has never been a problem in the past, but seems to be getting more and more difficult and soon to be dam near impossible if running under Windows Server 2008.
One issue your blog doesn’t address is the issue of logging out of and then into another company. I’ve automated GP in the past before the AutoDim tool came onto the scene, but the issue has always been switching companies once the integration has completed. The AutoDim tool resolved those issues. How does this scheduler resolve those issues, or is it simply a case of using the scheduler to launch the batch file that still uses the AutoDim tool?
I love the tool and your tips. But I am having an issue with it. I can run a task the exact same way three times and get three different results. I have a macro that runs the AR Aging process. I can run the task, and GP opens, the aging process runs, and GP closes. Then I can run it again, and GP opens the aging process runs, but GP doesn't close. And finally (and unfortunately this seems to be the most frequent), I can run it again. GP gets to the login screen and stops without ever entering my password. Finally I get a box labeled Add-in Initilization Error. It has a lengthy message that starts with "Microsoft.Dynamics.GP.OnlineServices.dll: unable to get valid config from serialized string. Client proxy can not be configured properly...."
I have noticed at this client that sometimes when I open GP, it takes forever before I can click in the password box and enter my password. Prior to that, the window doesn't even seem to be active. I wonder if this is causing the hang. Any ideas? Thanks!
Follow up to 5/4/12 post - I am using System Scheduler to run the macro. If I manually run the System Scheduler task, it seems to be running fine now; I've run it several times today, and it has not failed at all. But it will NOT run if I schedule it and log off the server. It leaves dynamics.exe hung in task manager processes, and it has this error in the macro log file:
:C:Program Files (x86)/Microsoft Dynamics/GP2010/data/AgingCAN.mac Started 05/08/2012 11:27:41
:C:Program Files (x86)/Microsoft Dynamics/GP2010/data/AgingCAN.mac Aborted 05/08/2012 11:27:41
:C:Program Files (x86)/Microsoft Dynamics/GP2010/data/AgingCAN.mac Elapsed 0:35 Last Line 4
Error: Field on window is inactive or disabled.
Last Line: 4
Line: MoveTo field '(L) SQL_DataSource' item 2 # 'GP2010'
Location: dictionary 'Microsoft Dynamics GP' form Login window Login field
I don't understand what that error means. Not sure how to change System Scheduler to get it to run when I'm logged off.
Any ideas? Thanks!
Make sure you are setting up your Logon Keypresses under Preferences to unlock the computer before the integration runs. That's the only thing I can think of.
MG.-
I checked with Spliterware Support. Here's what they said:
According to the link you sent over, it seems that in order to login GP needs to be able to interact with the desktop - so this wont work while the computer is logged out or locked.
System Schedulers own built-in sending keypresses works in the same way.
So I'm just not sure this works :(
Sherry,
Thanks for the update. I will post back with my findings, however, I have this working at a few clients and so do some fellow MVPs who actually directed me to this product.
All environments are different and there may be some settings that need to be changed in yours for the product to work.
MG.-
Post a Comment