Forum Discussion

jevanxbase's avatar
jevanxbase
Member
12 days ago

Issue Generating Reports

Hi Team,

 

Since installing MYOB AccountRight 2026.6 PC Edition on our Remote Desktop Session Hosts, we have encountered issues generating/exporting reports that use AccountRight's Excel template files.

 

According to the following MYOB article, for AccountRight PC Edition 2021.1 onwards the template files should be located under:

 

C:\Users\<user.name>\Documents\MYOB\AccountRight\Current\Reports\Spreadsheet

 

https://www.myob.com/au/support/myob-business/reporting/exporting-reports/microsoft-excel-templates?productview=Browser

 

We have deployed AccountRight 2026.6 using the new .exe installer with the -allusers switch, as documented for managed/terminal server environments.

 

When attempting to export the General Ledger Summary report, AccountRight returns the following error:

 

C:\Users\Public\Documents\MYOB\AccountRight\Current\Reports\Spreadsheet\GENJRLS.XLT

 

This indicates that AccountRight is attempting to locate the template under Public Documents, rather than the per-user Documents path described in the article.

 

On the server, the 2026.6 installer has installed the template successfully under:

 

C:\Program Files (x86)\MYOB\MYOB AccountRight 2026.6\app-2026.600.10011\Reports\Spreadsheet\GENJRLS.XLT

 

However, no corresponding template files appear to be created under either:

 

C:\Users\<username>\Documents\MYOB\AccountRight\Current\Reports\Spreadsheet

or:

C:\Users\Public\Documents\MYOB\AccountRight\Current\Reports\Spreadsheet

 

As a test, I copied GENJRLS.XLT from the 2026.6 application directory into the exact Public Documents path shown in the error. After doing so, the General Ledger Summary export completed successfully.

 

Could you please clarify:

 

With a 2026.6 PC Edition -allusers installation on a Terminal Server/RDS environment, where are the Reports/Spreadsheet templates expected to be stored?

Is the installer expected to populate these templates into each user's Documents folder, or into Public Documents?

Is this a known issue with the AccountRight 2026.6 .exe installer using -allusers?

Is copying the Reports / Letters content from the 2026.6 application directory into the expected Documents location a supported workaround?

 

Environment:

 

AccountRight 2026.6 PC Edition

Installed using the .exe installer with -allusers

Windows Remote Desktop Session Host environment

FSLogix Profile and Office Containers

 

Thanks.

Desktop

3 Replies

  • Genreve_S's avatar
    Genreve_S
    MYOB Moderator
    12 days ago

    Hi jevanxbase, 

     

    Thanks for the detailed information. That certainly is odd; MYOB’s guidance says PC Edition should use each user’s Documents folder, not Public Documents.

     

    As 2026.6 is looking in Public Documents, this may be an installer issue. Copying GENJRLS.XLT there works as a workaround, but it isn’t confirmed as an officially supported fix.

     

    Please raise this with MYOB Support and include your -allusers, RDS, and FSLogix setup, along with the error path and workaround.

    Reference: https://www.myob.com/au/support/myob-business/reporting/exporting-reports/microsoft-excel-templates?productview=Browser

     

    You can create a ticket in My Account or connect with our live chat team through MOCA, our virtual assistant. 

     

    Regards,
    Genreve

  • joshwau's avatar
    joshwau
    Member
    11 days ago

    Were havings the same reported issue on our RDSH, this has come about after moving from the msi to the new PC version.

    We get the error that the templates cannot be found, the work around looks like the right fix for now

    Once of the challenges with RDSH is that this may use external profiles, so the devs have likely seeking to use the public folder, but as raised the templates are not placed into the public template folder so staff get this error.

    Should we submit a support request or has this already been submitted  

  • Doreen_P's avatar
    Doreen_P
    MYOB Moderator
    11 days ago

    Hi joshwau,

     

    Thanks for flagging that, and yes, the workaround does sound like the right short-term fix. For this one, it’s best to submit a support request so the team can check what’s happening. If you need to follow up directly, you can use the Contact Us page to get through to support.

     

    Cheers,

    Doreen

Looking for something else?

Search the Community Forum for answers or find your topic and get the conversation started!

Community home