Sage 100

Sage 100c Advanced 2017 (5.4.5.0) (Scanco MB) Task Scheduler question. I'm trying to set up a register update for PO and it will not process, it shows up in Master Console but hangs without any errors or prompts, if i run it manually from windows task scheduler, i get the attached error. I have attached the error listing as well. I tried setting up a task to print a report to the same printer used in the register update and it runs without any issues. I can also manually run the register update and select batch/es and update using the selected printer. I can't find anything on the KB or 90 minds related to this error. Anybody run into this before or have any ideas? Any MDs out there that can find out what it is trying to do at line 382 (i've attached the SY_TaskLauncher.M4P)?

UPDATE: I've narrowed this down to the SY_TaskLauncher.M4P on this install. I made a backup and then copied over a version of that file from another 5.4.4 install and everything worked as expected. I've attached the working version to this post. Definitely something wrong in the 4/13/2018 file.

0382 oReport'DisableUseOfUI() Don't know why that would hang.

Thanks for checking it out. Odd thing is, i can't find any references to oReport in either the dump in the previous post or this output of the OBJ command during debugging of the error that i've attached to this post. I also can't find any reference to that method in the program information docs. Is there any info in the non-working one that indicates what version and PU it is for?

Funny since those screens tend to be NOT customizable. Wonder if the server monitor has a different resolution/etc.

That may be a possibility but i think it is an issue with an object handle not being initialized. Almost like the InitReportEngine method is failing for some reason. See the attached image.

Are you able to determine at what line/point the oReport variable should be assigned an object handle?

Only 3 lines in the disable: DISABLE_USE_OF_UI: LET cCanUseUI=isFALSE RETURN retSUCCESS What was the calling program again that you Debugged?

PGN = SY_TaskLauncher.M4P LPG = ..\SOA\SY_StartupLegacy.M4P TSM = 0SY_TaskLauncher.039200004100002

In this screen shot, you can see any attempt to reference a method or property of the oReport object results in error 65. So i believe something, somewhere is failing to initialize that variable to whatever object handle it is expecting.

Did you see any notable differences between the working and non-working SY_TaskLauncher.M4P files i attached to this thread? If i had a text version of both, i'd comb through it myself but not an MD.

I had thought it would be the task-program you were running itself rather than the TaskLauncher.M4P program. Sy_StartUpLegacy.M4P is for running non-framework (Mas90) programs. Is that appropriate? Scanco have any ideas?

i haven't gotten a response from scanco yet. It works fine if i set up the task type as Report or Other (for Rebuilding the Search Index). I only get this error when it is set to Journal/Register and i get it on IM and PO. From what i understand, when you set up a task using the task scheduler, it creates a command string to launch a legacy program called SWZURL and it accepts the final argument in the command string. which is ""D:\Sage\Sage 100 Advanced 2018\MAS90\Home\pvxwin32.exe"" -MN ""D:\Sage\Sage 100 Advanced 2018\MAS90\SOA\swzurl"" -ARG ""windx:\\\\SY_TaskLauncher.M4P^TASK_NAME_IN_TASK_SCHEDULER^"".

Submitted a support case with sage and they finally acknowledge that the issue can be reproduced in 2017.5 and 2018.3. Said they are aiming to have this resolved in the next product update but if needed, i may be able to get a pre-release once they have it fixed.

@DavidSpeckII - Did Sage provide any ETA on the date of the SP would be available? I have a customer that just upgraded to 2018.3 and really needs the IM journal/register fixed asap.

I did not get an ETA. Here is the supposed kb link from my ticket's notes but it doesn't seem to exist. https://support.na.sage.com/selfservice/documentLink.do?externalID=92735language=en_US Also according to the notes, it is written up under Defect#109740

@ShannonStanley , I meant to mention that i could not identify any crucial reason for the inclusion of the line causing the error so you may be able to get by with renaming/backing up the current 2018.3 version of SY_TaskLanucher.m4p and then grab a copy of the 2018.2 version and place it in there instead.

Thank you

Scott Brady (Scott.Brady@sage.com) said to email him so he can write up a pre-release agreement for your client to sign or wait until the PUs that are scheduled to be released next month.

Thanks @DavidSpeckII , I did put in a pre-release request last week. Appreciate your help!