Sage 300 Web Screens Posting Batch entry Stuck

Sage 300 v2020 PU4 on AWS cloud Server

 ll works fine on the desktop version, however, when trying to create a batch entry within the Web Screens in  AR Invoice it hangs and does not add an entry, it allows navigation to other modules and adding batch  entries even in AP works. The AR batch entry does not work. I  have tried adding a new entry in a new batch but still stuck.

Has anyone come across this?

Thanks

Top Replies

  • Hi  what version of the Web Screens are you on?  Ideally you want to get to version 2024 PU1 or at least 2023 PU1 as the improvements to the Web Screens have been substantial.  Make sure you check Chapter…

  • Hi are you able to resolve this one?

  • Our client has a similar issue on GL batch posting - if I reset IIS then they post 

    Another issue when a user creates a gl batch - the next user sets it to ready to post - this then says the batch is in use by another user - if I go onto desktop I can post - if they go out of batch list and in again then they can set ready to post - so it looks like a lag or delay.

    Anyone have suggestions - they do connect via VPN to RDP

  • in reply to BCSKZN

    Hi  what version of the Web Screens are you on?  Ideally you want to get to version 2024 PU1 or at least 2023 PU1 as the improvements to the Web Screens have been substantial.  Make sure you check Chapter 2 and 5 on the Installation & Administration guide and check your configuration of the web screens is per the book.  Things you can try:

    1. Don't access the Web Screens via RDP - sure, connect to the VPN but after that have clients access the Web Screens directly via their Local Browser instead of adding the layer of the RDP on top.  All the processing is done on the local server via the Sage.CNA.WindowsService.
    2. Make sure your Online folder under your Sage 300 programs folder has the IIS_IUSRS local account added and permissions granted to it:
    3. Check your Recycle Settings for the Sage 300 AppPool isn't recycling during business hours:
    4. Really important - make sure your Idle Time-out (minutes) settings under the Sage 300 App Pool Advanced Settings isn't still on the default 20 minutes:
    5. Remember you can just recycle the app pool for Sage 300 rather than doing a full IIS reset to bring posting back up to avoid taking all sites down on the server (if Sage 300 is the only site then it isn't too much of a worry).
    6. Make sure you're using a proper SSL certificate bound to 443 on your Default Web Site, and make sure users are accessing the server via the name on the SSL certificate using DNS entries.  The site behaves much better under a proper SSL certificate.
    7. Make sure the IIS server isn't running out of memory and artifically recycling the website prematurely causing you to have to recycle it before being able to post.
    8. Finally, you can try repeating the same exercise on my default Sage 300 2024 PU1 Web Screens available publicly on https://sage300demo.accsysconsulting.com.au/Sage300.  I'll DM you the username and password Thumbsup

    That's all I can think of for now - hope it helps!  Tim.