Issue with report files not opening in Sage 50 V29, Sage Tech support thought fixed but still error, any suggestions.

I have Sage 50 v27, 28 & 29 on my office Server running Server 2019 essentials, also pulling through to several pcs and laptops, all reports work on the pcs but have an issue on server.  I know that technically we are advised to not install Sage 50 on a server with essentials however until someone comes up with another way for accountant practices to run it in another way since we had to stop holding the data on a NAS drive pulling through to the pcs there is no other option.

I carried out the installation as usual with the individual packages installed in the correct order, I initially had the above error message with no reports available in any dataset, even demodata.  I carried out the whole uninstall, reinstall a few times, repair installation etc then gave up as the reports were pulling over to the pcs fine.  I then went to a client's office and carried out the update on their server, in that case I updated their Sage program as they don't need the older version.  I had more serious issues with their installation so contacted technical support, after managing to get the upgrade installed they found the same report issue so tried numerous fixes.  They finally found that the use data path for reports box was not ticked so changed it and although we still got an error message when opening the program the reports were available.

We thought that fixed the issues as I did it on some of my datasets and it worked, however I have now restored a backup of a Sage dataset for a client that we have moved back from QBO to Sage 50 into the Accounts\23 folder (all the other datasets are in either \21 or \22 folder) and no matter what I try I can not get any reports in the list, even when I open report designer in that company although the folders are shown when you select one, it is blank.  See below:-

I have checked out the program data folders and found a difference in the Company Template folder in Accounts\2023 compared to 2021 & 2022.

Below is screenshot of that folder from 2022

and 2023 only has the below:

I really need to get this sorted out as when we are working remotely we have to work on the server Sage 50 for the non remote access companies and not being able to even run a aged creditors report will be a pain in the butt.

Parents
  • 0

    Are you installing the program directly via the .msi and to a custom directory? If so it's logged as a bug.

    You can either install using the full .exe rather than individual .msi

    or copy the ZippedReports folder from C:\Program Files\Sage\Accounts or for the 32 bit version C:\Program Files (x86)\Sage\Accounts


    and then paste it into your custom install location (example C:\MySageInstallation)

    You should no longer get the error, as the missing folder is now present.

    Ian

  • 0 in reply to Ian C

    That is not the answer, that was done several times since I installed V29, it has finally worked for V29 but not V30 as per my previous reply.

  • 0 in reply to Pamela Dillon

    Great. I've been advised the same by the support. just re-doing our scripts to see what its gonna do. I'll let you know how i get on

  • 0 in reply to Pamela Dillon

    Pamela, there’s no need to copy it manually to the server or extract it to the reports folder, neither of those actions will do anything.

    The ZippedReports folder just needs to be in the same directory as the program, on every machine and the software will take care of the rest.

    Hope it worked Tom.

  • 0 in reply to Ian C

    Hi Pam, Ian is right. this fixes the issue.

    The ZippedReports folder has to go into the root of C: on your local device(Citrix VDI in our case), won't make any difference server side.

    If you by any means cannot use the original Sage/Accounts folder (like in our case where we run 2 versions at the same time - 29 and 30.1), you have to install the reports pack.msi into the same location where you've put the Sage versions.

    In our case it was C:\Program File(x86)\Sage2024\Accounts & Sage2023\Accounts

    I had to re-do the scripts for msi install to point to the same directory as the actual install location of both of the versions.

    I have however also tested this manually by simply copying the zippedreports folder into those locations and it does the trick (provided noone is logged in at the time as the report extraction happens upon opening a client)

    Hope this helps

    Tom

Reply
  • 0 in reply to Ian C

    Hi Pam, Ian is right. this fixes the issue.

    The ZippedReports folder has to go into the root of C: on your local device(Citrix VDI in our case), won't make any difference server side.

    If you by any means cannot use the original Sage/Accounts folder (like in our case where we run 2 versions at the same time - 29 and 30.1), you have to install the reports pack.msi into the same location where you've put the Sage versions.

    In our case it was C:\Program File(x86)\Sage2024\Accounts & Sage2023\Accounts

    I had to re-do the scripts for msi install to point to the same directory as the actual install location of both of the versions.

    I have however also tested this manually by simply copying the zippedreports folder into those locations and it does the trick (provided noone is logged in at the time as the report extraction happens upon opening a client)

    Hope this helps

    Tom

Children
No Data