Sage 100

The Windows login used for the task needs a real print object as the default printer.  It cannot be a PDF printer, because that hangs the task with an invisible prompt for file location (auto-printed job log).

In earlier versions we did have problems with multiple tasks in the same job, and had to separate them into multiple schedules to avoid frozen tasks.

Thanks Kevin.

They all use the same real network printer.

I will be separating the Tasks as well.

The Windows login used for the task needs a real print object as the default printer.  It cannot be a PDF printer, because that hangs the task with an invisible prompt for file location (auto-printed job log).

In earlier versions we did have problems with multiple tasks in the same job, and had to separate them into multiple schedules to avoid frozen tasks.

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.  

Have the jobs ever worked or is this the first time setting them up a Windows Task Scheduler Job?   

Because those 4 journals update, separate those onto 4 different task scheduler runs 15 minutes apart and see if you have better luck.

Here is my list I compiled yesterday for Task Scheduler issues:

• Sage Service user must be setup with a real printer and set as Default on Sage Server.
• Sage Service user must be given  "Log on as a batch job" privileges in gpedit

• In User Maintenance - Preferences tab verify that the Prompt for Company Code check box is unchecked for User setup to run job.
• Company Key 000000001 must exist in ..\mas90\mas_system\sy_company.m4t
• Check 'Run with Highest Privileges' in Windows Task Scheduler Job

For emailing

• For Sage 100 Advanced or Premium select option: "Use as Default Company for Server Settings" 
• Must have a Company Email entered in Company Maintenance Main Tab

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.  

Have the jobs ever worked or is this the first time setting them up a Windows Task Scheduler Job?   

Because those 4 journals update, separate those onto 4 different task scheduler runs 15 minutes apart and see if you have better luck.

Here is my list I compiled yesterday for Task Scheduler issues:

• Sage Service user must be setup with a real printer and set as Default on Sage Server.
• Sage Service user must be given  "Log on as a batch job" privileges in gpedit

• In User Maintenance - Preferences tab verify that the Prompt for Company Code check box is unchecked for User setup to run job.
• Company Key 000000001 must exist in ..\mas90\mas_system\sy_company.m4t
• Check 'Run with Highest Privileges' in Windows Task Scheduler Job

For emailing

• For Sage 100 Advanced or Premium select option: "Use as Default Company for Server Settings" 
• Must have a Company Email entered in Company Maintenance Main Tab

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.  

Thanks Christine.

In a test production clone environment, I added the Sage Service User permission in gpedit.  I created the multi-task Task Scheduler job.  I did not have a Printer so I used Microsoft PDF.  I did not have a Company Code Key "0000000001" so I cloned one.

The 2 sub-tasks completed successfully.

Have the jobs ever worked or is this the first time setting them up a Windows Task Scheduler Job?   

Because those 4 journals update, separate those onto 4 different task scheduler runs 15 minutes apart and see if you have better luck.

Here is my list I compiled yesterday for Task Scheduler issues:

• Sage Service user must be setup with a real printer and set as Default on Sage Server.
• Sage Service user must be given  "Log on as a batch job" privileges in gpedit

• In User Maintenance - Preferences tab verify that the Prompt for Company Code check box is unchecked for User setup to run job.
• Company Key 000000001 must exist in ..\mas90\mas_system\sy_company.m4t
• Check 'Run with Highest Privileges' in Windows Task Scheduler Job

For emailing

• For Sage 100 Advanced or Premium select option: "Use as Default Company for Server Settings" 
• Must have a Company Email entered in Company Maintenance Main Tab

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.  

You really don't want to use the PDF print object.

Link to a thread on this exact subject:

https://community.90minds.com/discussion/task-scheduler-v2022-adv#bm2ee65df0-7d5c-4d14-b77f-018fa7498cae

Thanks Christine.

In a test production clone environment, I added the Sage Service User permission in gpedit.  I created the multi-task Task Scheduler job.  I did not have a Printer so I used Microsoft PDF.  I did not have a Company Code Key "0000000001" so I cloned one.

The 2 sub-tasks completed successfully.

Have the jobs ever worked or is this the first time setting them up a Windows Task Scheduler Job?   

Because those 4 journals update, separate those onto 4 different task scheduler runs 15 minutes apart and see if you have better luck.

Here is my list I compiled yesterday for Task Scheduler issues:

• Sage Service user must be setup with a real printer and set as Default on Sage Server.
• Sage Service user must be given  "Log on as a batch job" privileges in gpedit

• In User Maintenance - Preferences tab verify that the Prompt for Company Code check box is unchecked for User setup to run job.
• Company Key 000000001 must exist in ..\mas90\mas_system\sy_company.m4t
• Check 'Run with Highest Privileges' in Windows Task Scheduler Job

For emailing

• For Sage 100 Advanced or Premium select option: "Use as Default Company for Server Settings" 
• Must have a Company Email entered in Company Maintenance Main Tab

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.  

Agreed.  Just reporting that it worked.  Will get IT to install a printer then change it.

You really don't want to use the PDF print object.

Link to a thread on this exact subject:

https://community.90minds.com/discussion/task-scheduler-v2022-adv#bm2ee65df0-7d5c-4d14-b77f-018fa7498cae

Thanks Christine.

In a test production clone environment, I added the Sage Service User permission in gpedit.  I created the multi-task Task Scheduler job.  I did not have a Printer so I used Microsoft PDF.  I did not have a Company Code Key "0000000001" so I cloned one.

The 2 sub-tasks completed successfully.

Have the jobs ever worked or is this the first time setting them up a Windows Task Scheduler Job?   

Because those 4 journals update, separate those onto 4 different task scheduler runs 15 minutes apart and see if you have better luck.

Here is my list I compiled yesterday for Task Scheduler issues:

• Sage Service user must be setup with a real printer and set as Default on Sage Server.
• Sage Service user must be given  "Log on as a batch job" privileges in gpedit

• In User Maintenance - Preferences tab verify that the Prompt for Company Code check box is unchecked for User setup to run job.
• Company Key 000000001 must exist in ..\mas90\mas_system\sy_company.m4t
• Check 'Run with Highest Privileges' in Windows Task Scheduler Job

For emailing

• For Sage 100 Advanced or Premium select option: "Use as Default Company for Server Settings" 
• Must have a Company Email entered in Company Maintenance Main Tab

We are working a very similar problem with a client this week.  @Christine Kuhn may be able to share more information about the Printer Setup.  The HOST Service user account needed a defaulted physical printer.  Once we set that up; it stopped the sessions from hanging, even though nothing needs to physically print.