Skip to main content
Question

assystNET won't load after upgrade

  • October 26, 2023
  • 4 replies
  • 108 views
M
Do Gooder (Customer)
Forum|alt.badge.img+1

We upgraded to assyst version 11.5.1 and I have one user who cannot get assystNET to load at all. She just gets a blank white screen. We have tried the following but nothing has worked.

  • Cleared browser cache/history
  • Cleared temp files
  • Cleared roaming files
  • Restarted machine
  • Tested in a different browser (Edge since it was initially happening in Chrome
  • Tried different instances in Citrix (Chrome and Edge)
  • Tried different instances on a VM (Chrome and Edge)
  • Updated Chrome on the VM to match the newer version locally

4 replies

Arnaud Le Tollec
Do Gooder (Employee)
Forum|alt.badge.img+4
  • Arnaud Le Tollec
  • Do Gooder (Employee)
  • 14 replies
  • October 27, 2023

Hello Mary Kate,

The reported issue here will require a full investigation from our service desk.

I would suggest you to contact the IFS support using one of the option proposed our wiki page.

IFS assyst Service Center - assyst11-7Wiki (axiossystems.com)

Kind regards.

R
Do Gooder (Customer)
Forum|alt.badge.img+5
  • RyanL22
  • Do Gooder (Customer)
  • 16 replies
  • October 30, 2023

Can she access it from a different system?

M
Do Gooder (Customer)
Forum|alt.badge.img+1
  • mwinn2480
  • Author
  • Do Gooder (Customer)
  • 1 reply
  • October 30, 2023

No, she even tried from a virtual machine & has the same problem.

R
Do Gooder (Customer)
Forum|alt.badge.img+5
  • RyanL22
  • Do Gooder (Customer)
  • 16 replies
  • November 7, 2023

I would suggest shutting down your web service(s) and deleting the \standalone\data and standalone\tmp folders.

I have had this problems several times following upgrades. Usually the user’s browser cache does the trick, but if not, then deleting those 2 folders should definitely do it.

You could also check your server.log file, but from what I recall, this issue doesn’t generate any error messages.


Terms & ConditionsCookie settingsAccessibility statement