Do you have a designer license?

I would say yes because in the License Manager it says we yes to Reporter, Connector and Designer Licences. Its 1 licence only.

I ran into something similar with an upgrade. I had to delete all the existing reports in the BXDATA folder (there were no custom reports) and then import all the new reports - Report Manager, Tools, Bulk Import/Update. That rebuilt all the new reports and got them working.

In your case you have existing custom reports that you need to keep - you can export your custom reports (Report Manager, right click custom report, Export) then delete everything in BXDATA, then import all the new reports, then import all your custom reports (Report Manager, File, Import Report).

In both instances of our install, we did not import old reports into BI. We tried the new reports first, then realised it didnt work, so we imported the old reports and they worked.

Each time, there was a clean install so, i dont know if deleting after installing will help but i will ask his opinion. Anything we try now can only help as this is 2 months we have been trying to find a solution to this problem. Many thanks!

In both instances of our install, we did not import old reports into BI. We tried the new reports first, then realised it didnt work, so we imported the old reports and they worked.

Each time, there was a clean install so, i dont know if deleting after installing will help but i will ask his opinion. Anything we try now can only help as this is 2 months we have been trying to find a solution to this problem. Many thanks!

Since I don't know what steps were followed with your upgrade etc, was the old version uninstalled before installing the new version? Is the PATH clean - i.e. you do not have multiple references to a Runtime folder for different versions.

It was a clean install because we had to get new servers. We wanted to have separate servers for database and software as our database is so big...

I'm actually asking about the workstations.... not the server. You are running Sage 300 on workstations right? Or are you using terminal server?

yes we are running on workstations. and all older versions were uninstalled. we switched from pervasive to SQL so had to ensure any files related to pervasive was removed.

What about the PATH? I see it all the time, people forgot to clean up the PATH and there is a PATH pointing to the old version on the old server - and that causes a lot of issues.