Sage 100

I am not 100% sure of the cause yet but it appears Sage 100 2018 advanced stops for all users when payroll checks are printed. I normally run as a service but have run for the last day as an application with the same results. an Error #26: Variable Type Invalid popped up at the server at the same point in the process each time. Once appears the application (or Service prior to change) must be stopped and the following files removed/renamed (locate.pvk, session.pvk, sy_console, sy_workstation). Anyone have this post upgrade to 2018.

@LarryBradford we have a customer with the exact same issue. Problem occurs when you print register directly when prompted from check print. Work around, is to say No to register and then manually run it. We've logged it with Sage.

I can check with our help desk but I don't think we have to rename/remove those files.

This action is corrupting the sessions and locate files for this client. Thank you for checking @BrettLyder . If you have the case number, that would be great as well.

Thanks for the heads up! I've not done a 2018 Advanced with PR yet. Hope this is fixed soon.

Ah, TG I am not crazy. Posted this issue back in March when I encountered it. I finally figured that it occurred when printing the PR check. Guess I was one click off with PR check register update. Never did resolve it. Rebooted the server to get going again. Started running the PR cycle in MAS 90 mode. Last week I forgot. **Now** I just run v2018 entirely in M90 mode. Too tired to reboot the server. Is there a fix on the way with PU2?? Might be a good topic for the next PR session? Post case number so I can add my two cents. This is a **CRITICAL** bug!!! https://90minds-com.socialcast.com/messages/38415628?ref=stream

Check your user settings to see if using ""Spawn Tasks"" in User Maintenance. Ran into this a while back and unchecking that setting / restarting service resolved.

Turn off Spawn Tasks? Didn't we have to turn that on in the last version to stop the same issue? :)

Have seen that setting cause a few issues. Needs to be either all enabled or all disabled it seems. In PR 2.0 Advanced, all disabled to get past Check Printing issue. Think it's really DD stubs specifically if remember correctly.

**to spawn or not to spawn, that is the question**!! Sometimes I think Shakespeare is easier to follow and understand. We should really make a stink next at the PR round table. For now, I will just run everything in M90 mode. Why is it that when ADV has an issue, the solution is to run it in M90 mode???

My solution will be to NOT upgrade any Advanced or Premium clients to 2018 until I hear of a fix. Sage really needs to figure this out ASAP! I'm just lucky I've been taking it slow with 2018 and PR and only upgraded some of our smaller clients.

@AndyAdkisson you might be right about the DD thing, our customer has DD employees as well. Our support team is telling me we can't uncheck Spawn Tasks because of server timeouts that occur. @LarryBradford does your customer print DD stubs too?

They have DD and turning off Spawn Task for all users seems to have eliminated the issue.

Brett, if the reason for not disabling Spawned Tasks is due to experiencing ""NoDelay;Stream"" errors or ghost / hung pvxwin32.exe processes on server, have found the key is to have all users configured the same. Have seen those issues too, and think most KB's on solution indicate to enable Spawned Tasks for ALL users. However, have found that DISABLING for all users has worked too in the few cases had to do so. Admit to having some clients with all enabled, and some with all disabled. Hope this helps.

Thanks Andy , I'll pass that along! Thank you too, Larry!

Hi All, we have a client with precisely the same issue in v2018 Adv. Clicking the Print button or the Direct Deposit button in PR Check printing causes the error. We've found that running as a service and as an application yield different results. As an application, we get an error 26 in a ProvideX window; as a service, we get a WindX Client Connection ""The Server has Disconnected"" error. We're going to try adjusting the Spawn Tasks setting and run in MAS90 mode to see if either is a temporary path forward. Thanks!

I reached out to Ronnie Aspe since so many had had the issue. He's writing it up for engineering. He's working on a case with the same issue right now.

From Ronnie: DE 109515 / KB:91695 created.

Running in MAS90 mode works for my client's Advanced installation. Thanks for the KB:91695, Robert. I checked the software release notes for Sage 100 v2018 PU3 and Payroll v2.18.2 that were released by Sage yesterday, and it appears that this fix is not in them. Hopefully Sage will release a hotfix soon, before the scheduled PUs next quarter! I'm holding off on the upgrade to v2018 until then.

Was on a PAC call with Sage this morning and brought this issue up. Diane Coffman said they were just able to duplicate the issue - and they think it occurs specifically when you have both checks AND direct deposits. Regardless - Engineering now has it, and Diane says it is at the top of the list of things to get fixed.

Confirmed they have a fix and are testing it now, but in the meantime, I've been sent this KB short term fix: 1.Exit all users in Sage 100 and close any open sessions at the server. May need to stop the Sage 100 Service if running and end all pvxwin32.exe task running at the server. 2.Deselect Spawn Task from Application Server in User Maintenance for users printing Payroll Checks and Direct Deposit Stubs. Users must exit Sage for this to take effect. 3.Rename Sessions.pvk and Locate.pvk in ..\MAS90\Home\Lib\_Appserv\ folder at the server where Sage 100 is installed. Then launch the Application Server Configuration which will generate the 2 files renamed above. 4.Start the Sage 100 service or desktop application

And...now I have a Beta for the program fix that seems to be working. Sage hasn't published it yet - because it is still in ""testing"", but we've put it at a client site and it has solved our check printing/hanging issue! If you would like the fix, email me (sue@benpor.com), let me know whether you are using Payroll 2.18.1 or 2.18.2 (released this past Tuesday) and I'll send it to you - with the qualification being you have to let me know if it works so I can let Sage know your results. So we can get it published sooner rather than later! (And again, the caveat is that it is still a Beta!)

I have a Sage 100 Standard (MAS 90) client on Payroll 2018 for whom the prompt for last check printed, remove stock, print/update check register never occurs. Just prints checks (successfully) then hangs and never advances. System doesn't recognize checks as printed. This happens on any workstation, but if PR is run directly on the server everything goes perfectly. Do you think this would help in that situation as all? Already been through 3 Sage support techs on the case and none have helped. Hoped PR update 2 would be the magic fix, but no luck. Client is not happy about running PR on the server every week.

I think it would be worth a try. And I, too, been amazed at the lack of communication between the support techs and engineering. As in: I don't think there is any communication.