Hi Shandy have you checked the named range Spec to check its correct, and that the default print driver is a valid printer selected for generating the Preview?  Check the default printer is not a label writer etc.  I'm running Office 365 64-bit with version 2024 and encountering no errors.  Also, try a stock report from \\<sageprogramspath>\GL71A\ENG i.e. Balsum01.xlsx

Hi, Thanks for your reply.

My colleague and I tried to change named range Spec in the excel template, error still there. We did try to print Balsum01.xlsx, but still getting the same error message as mentioned earlier on. Could it be MS Office 2016 64-bit issue? My colleague is able to print the excel without error msg, and she is using MS Office 365 32-bit.

The following picture is the default printer.

Best Regards,
Shandy

Hi Shandy, I don't think its your office edition because the official version 2024 compatibility guide says:

Could you please open Programs and Features on your workstation, select your Office 2016 and select Change -> Quick Repair?  Your office integration components might not be installed properly and this should repair them.

Hi, repair office did not work. :( 

Best Regards,
Shandy

Hi laushandy ,  did you change office versions or re-install it after installing Workstation Setup?  All I can think of is to re-install Workstation Setup now.  Other than that, you will need to get in touch with a Sage 300 Business Consultant to log in and resolve it.  Only so much can be done through the forums unfortunately.  Otherwise, re-install Office 2016 32-bit (your product key should work with both) or go to Office 365.  Again, when you change office editions, its a good idea to uninstall/re-install Workstation Setup.  Good luck!

Hi laushandy did you manage to solve the problem? I'm encountering the same problem

Hi MicrotekID and laushandy I forgot to ask whether this error is occurring with FR Web or FR Classic?  I'm trying to think of any other causes for you as I'm still yet to encounter it in the wild.  All the best...Tim

Accsys Consulting AU it happen on FR Classic.

Not solved yet, since client still can do view the FR report after click OK button at the error msg. We intend to do workstation setup on the particular workstation PC, but haven't do so.

Yes, our case also happened on FR classic.

Workstation setup does not help, tried that also

MicrotekID and laushandy thank you both for letting me know.  I'm wondering whether the error appears as soon as you click FR View -> set Year/Period -> OK ...or whether the error appears while the report is refreshing.  If you could use ScreenToGif or similar to record your screen opening the report, refreshing it and capturing the error occurring that would be even more helpful  If you record the time the error occurs, then open the Event Viewer and check all events (Particularly Critical, Error and Warning)e occurring just before, the same time and immediately after the FR error.  Often terminations by AV on processes, app crashes or other things show up in the Event Viewer that doesn't display in office.  I'm hoping you can spot an obvious one :-)

hi Accsys Consulting AU on my case it happen after clicking statement designer , it load up the excel and pop up the error immediately. After click ok it still open the excel , FR menu is there only the FRACCT got problems that all field under FRACCT Become ACCTID only.

Hi MicrotekID two things you can check.  First is check you can create and run a Macro.  1.  Turn on the Developer tab on the Ribbon under Excel Options:

Then click on the Developer tab and click on Visual basic to open the Visual basic editor.  Now expand Sheet1 and enter the following code:

Click Save and save the workbook at as a "Macro Enabled Excel Workbook *.xlsm" i.e. Test.xlsm.
Now back on the Developer ribbon click on Macros and run the test macro:

You should see the Message Box appear:

If you don't get this message and receive an error or something else, then you need to troubleshoot this - likely ask IT to add the Sage 300 programs and shared data paths to "Trusted Locations".

However if Macros work fine and you're still receiving the error then please create the error in FR again then open the Event Viewer and locate any entries that occur immediately before or at the same time as the error occurrs such as Application Errors, Microsoft Office errors/notifications, Antivirus errors or notifications.  The problem is going to be in the Event Viewer but its going to be a bit hard to find.  Once you do, let us know what you find.  Good luck!

Hi Accsys Consulting AU Done the macro testing as your advice and it works fine. Then i re run the problem , check the event viewer and got this error message

Error: System Registry Error.  The operating system reported "The system cannot find the file specified.
" on attempting to create or open the ACCPAC International, Inc. registry subkey of the \HKEY_LOCAL_MACHINE\Software key (writable was 0)

Nice work!  That's a very interesting error.  Is there a chance Sage 300 is running as a different user (as Administrator maybe?) to the standard Windows user's domain account?  Or is there a chance the Windows user account can't access the Sage 300 share or registry entries, and you're having to run Sage 300 as Administrator to get it to work? The error indicates to me is that the account launching Excel cannot access the SharedData and Programs paths listed under HKEY_LOCAL_MACHINE\Software\Wow6432Node\Accpac International, Inc.\Accpac\Configuration.  I would open the registry, navigate to this location and check the standard user can access the SharedData and Programs paths there in Windows Explorer, and has read/write access there.

(in this example ensure the user can access and read/write to \\ERPSERVER\Sage\*)

Also you could try opening Regedit as Administrator and navigate to HKEY_LOCAL_MACHINE\Software\Wow6432Node\ACCPAC INTERNATIONAL, INC. then right-click on ACCPAC INTERNATIONAL, INC. and change the permissions (only do this if you're confident with desktop administration):

Good luck!

Hi laushandy I now have this same problem at a client site I just upgraded to Sage 300 2024 PU1 - exactly as you described.  I've escalated it to Sage Support and am awaiting their reply.  I've tried everything I can think of to solve it.  Did you happen to resolve it yet?

We have a suggestion from local Sage Support, but not yet test. Will update here if successfully solve it.

Hi @Laushandy thank you so much for the note, if you want me to help test feel free to DM the solution or post it if its not sensitive :-)

Hi laushandy we have found a workaround but its not ideal - uninstalling Microsoft 365 64-bit from workstations and Office Access Database 64-bit (v2016) components then re-installing Microsoft 365 32-bit instead resolves the error.  I know its not ideal to have to switch back to 32-bit Office and some sites are particularly against it (as I've experienced in the past) but it is a workaround I've confirmed works and have informed Sage support.  The issue somehow appears to be server side in 2024 PU1 so hopefully the Dev or Support teams at Sage will come up with a permanent solution soon.