Pamela Dillon said:

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

That is OK and expected as the template was simplified to remove unnecessary folders, or folders that are only used in some circumstances, as this can significantly speed up the creation of new companies.

Pamela Dillon said:

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.

That setting just changes where the reports are loaded from. Essentially it tells the software to use a shared location for the reports rather than the default local one. It is a little slower to do this as you are going out over the network whenever you want to find or access a report, but is useful for when you share reports with other users. I would not expect the setting to have any bearing on your problem except for the fact that if you have upgraded the data you likely had reports in the data location already from the earlier version of the software. However these reports will not be up to date so may be missing some changes/fixes or new reports added in v29.

Pamela Dillon said:

I carried out the installation as usual with the individual packages installed in the correct order

I suspect this is the problem. Installing the individual packages isn't intended as the normal way to install, although it is sometimes used as a workaround for unexpected errors with the normal EXE installer.

Given the error message you are seeing I strongly suspect that you have installed the client and server MSI files but not installed the "Sage50Accounts_ReportPack.msi" one, or possibly have but installed it out of order. This would result in you having no report files and the error message you see, as when the software opens and you connect to a company a check is made to see if you have the up to date reports in the correct location based on your current settings (local or in the data path) and the latest ones are applied to this location if necessary. It is this step that is failing and giving you the error message as the source report files do not exist.

Should be a simple fix to just run the "Sage50Accounts_ReportPack.msi" installer file and reopen Accounts.

Hope that helps

When you install Sage 50 on a server, since version 25 you have no choice except to install the packages individually, this has worked for every versionup to now on every server of mine and my clients.I had ran them in the order that v25 - 28 had to be done then realised that the order had changed for V29 as the new package is now there. Lockstrap or what ever it is called.

I definitely installed Report Pack, also uninstalled it and reinstalled after installation several times.  Ran repair a couple of times.

Sage Technical support also checked installation order and uninstalled the program and reinstalled themselves.

Same issue.

I have now had to move one of our Remote Access company datasets from the the programdata 2022/company.008 which was in v29 and after Tech support had managed to get reports to open for all those companies over to 2023/company.002.  This dataset now won't even open the reports window, just gets the error message below: -

I have checked that the box for use datapath for reports is ticked and gone to help/about and made sure that the data directory is correct and clicked through to it.

I have also opened the other dataset that is in the 2023 data folder to make sure that the report windows are still opening even if the reports are not there, and a couple of the datasets that are still in the 2022 company folders and I can run their reports in v29.

I am stumped.

Hi, have you ever figured this out? we are getting the same error from your initial post. Got around it by enabling the path (thank you), but the error remains. 

I finally have it working in v29 but it still shows in v30 for some reason and I did the same fix in both.  I zipped the report folder in v29 on my desktop and sent it to the server then extracted it to the report folder in Sage v29 and v30 on the server.  On the day I did that process both Sage versions worked then from the day after only v29 works and v30 still has the error. Really bizzare

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

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.

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

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.

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