We have a custom screen written for us to be able to use the Move WIP module on the handhelds.
It works fine when tested on a PC running the full client and it works fine tested on a PC running the handheld client, but when I try and run it on our terminal server, it doesn’t work. By “doesn’t work”, I mean I can enter all the data and it all populates just fine, but when you click save it doesn’t do anything.
The question would be, why does it work everywhere except on the terminal server?
I have made sure that the PC testing and the terminal server have the exact same client DLLs.
When you say custom screen, I’m envisioning a windows forms app that references the Epicor services correct?
Do you know if the server where it’s pointed to is exposed to the terminal server?
I have experienced some issues dealing with customs and dll files, but issues almost all the time solved after clearing the client cache and manually remove the c:\programdata\epicor{yourappservernamefolder} or confirm the client is being triggered in the terminal server contains indeed the custom dll files.
As Ruben mentioned, verify the custom DLL exists in the client folder on the terminal server. Also clearing the cache is always worthwhile. Can’t we all just boycott HH screens altogether
Yes, this is a Windows form that calls the Epicor services, not just a customization within Epicor.
The server is exposed to the terminal server running the client and I have verified the DLLs are there; I’ll try clearing the cache
@Chris_Conn Yes–a boycotting needs to be done. I cannot stand the handheld module. We were sold on a promise and delivered a husk of a program.
Any low-cost alternatives? I think we’re likely stuck with the CK75s at this point, but maybe we can leverage some different software?
They used to use iPads and Bluetooth scanners, but there were complaints about the keyboard taking up most of the screen, I believe (it was before my time here).
Do you have users that run Android tablets? Do they like it?
Well, we didn’t really love the android solution. It was very cheap though.
We instead use MS Surface tablets (any windows tablet would be similar). In my opinion, for mobile users (which would be the audience for HH) should rarely have to use a keyboard. If they do, maybe you need some screen customizations to solve that. If you get real fancy, Cortana or google can do your typing for you as well.
Turns out clearing the cache works for a bit and then it goes right back to not working.
I verified that the users have full control on the ProgramData\Epicor folder.
the user has no personalization?
search for the customization in Customization Maintenance - see if it shows up twice, once with a company and once without…
There are no errors. None pop up, none in the event viewer, and none in the logs.
It feels like the button just… stops working.
If I do a server reset, bam, it works for everyone for about an hour.
It’s everyone, including myself as a full system admin.
Hmmm it stops for everyone? Maybe it’s not necessarily the customization but something it’s doing. Memory leaks, event handlers getting wonky, also are there any related BPMs?
Upon some more investigation, it happens for everyone on our 2008 R2 terminal server.
I created a 2012 R2 TS for testing, let one user in and it has been working for 3 days. Let 2 other users in and it does not work for them.
I did a client trace while running it from the main application and it shows activity up until I click save. Save doesn’t generate logs, errors, or traces. It acts like there’s no code behind it, yet when I run the same job, same user, and same job on another server or my PC it works just fine.
As for BPMs, there’s an auto print, but that’s it.
