Hi Everyone
I'm still fighting this error and now with 2 clients, both Premium v2018. I can now reproduce the error on demand!
On the Terminal Servers and guessing on the locals, WKSetup was done via UNC Path. However, in the data entry windows (GJ Journal Entry, AP Invoice Data Entry, etc), clicking in the area of the SageU button (whether visable or not) throws the Error 65.
When I click on the icon in Customizer it brings up the Button Definition (BT_SageU) and then an error referencing the location from the Server side (D\Sage\Sage100v2018\mas90\cm\blc-cmWRK.tmp not found). See Attached.
Sage was installed as D:\Sage..... using drive letter (vs UNC) on the App Server, which is what I've always done. Is this a problem on Premium or with 2018?
This is consistent on both customers.
I tried this on a terminal server for an Advanced Customer and didn't have this issue.
Any ideas on how to fix?
WKSetup has been uninstalled and installed several times on both customers.
Happy Mothers Day to all the Moms out there.
N
------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------
Original Message:
Sent: 04-16-2020 02:29
From: Alnoor Cassim
Subject: Error 65 - Rebuild custom office utilities is not working
Nancy - This is a very well known type of Error 65 that I've troubleshot half a dozen times myself. It means at least 1 screen element / control is sitting outside of a boundary.
E.g. Let's say you are in Customizer for A/R Invoice Data Entry and noticed a button near bottom of the DMAIN panel but it is incorrectly sitting in the PMAIN area. This causes the error. You have to move the position of that offending button or field back into the DMAIN area.
In Customizer simply look for buttons and fields that look out of place. But if you don't visually see anything wrong, use the Panel Map button and it tells you the Row / Column of each control for the panel and makes it easy to tell what's outside the boundary you need to fix.
This issue happens when new fields and buttons are added because of new features on Sage upgrades, also sometimes on mod installations b/c of the installer, and sometimes self inflicted b/c you placed a UDF on a screen in the way I described above. It could also be too far to the left or right. I once posted about it here.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------
Original Message:
Sent: 04-15-2020 11:00
From: Jeff Fiddelman
Subject: Error 65 - Rebuild custom office utilities is not working
You can try info and debug
then
Print N$
this might give you the name of the screen element that is causing the problem....
------------------------------
Jeff Fiddelman
Exeplex, LLC