Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sage 300 Advanced 2024 Workstation 'No Supported Databases'

Peter Kolbe

Technical User
Oct 21, 2017
12
ZA
Hi All

We have Sage300 on a Windows 2016 Server, with several PC's accessing it fine.

I have just installed the Sage300 Workstation Software on another Windows 10 PC, with pointing it to the server when installing.
But, when I open the Workstation Software, it comes up with "No Supported Databases Are Set Up" .....
Clicking 'Start Database Setup' does nothing, Clicking Cancel brings me to the Open Company screen, but password is greyed out.

I have tried running as administrator, and the PC does have full access to all of the Sage files and folders on the Server.

Previously on another PC, a sage technician logged in, and sorted out the same problem. But he did not tell us how he did it. I would prefer to be able to sort this out without having to open a ticket each time I have to refresh a PC.

Thank You
 
Thanks Ettienne,
Unfortunately that did not work, I uninstalled and reinstalled, making sure the SharedData folder matched what was on the other machines on the LAN, even checking that the registry settings are the same, but I still get the same "No Supported Databases Are Set Up" error.

If I run the System Diagnostic, I see right at the bottom, it gives the error :
Code:
*** Unable to Open Orgs Table in SITE directory, error = 5 ****

If I run the same diagnostic on other machines, it is able to list the databases.
All directories on the Diagnostics (from Both Non-Working and Working Machines) look the same.

From the Non-Working Machine, I am able to browse using file server to the MFFM folders on the server, and I can open the orgs files in notepad (so file access permissions do not seem to be a problem).

Attached is the A4WDIAG file (I have changed the server name to sanitize the data)

I know we could log a ticket and get this sorted out, but I would like to figure out what I have done wrong.
Thanks
 

Attachments

  • A4WDIAG SANTIZED.txt
    17.1 KB · Views: 1

Part and Inventory Search

Sponsor

Back
Top