Invalid database specification

Posted By Enabling over 7 years ago

Hi,

We have a client who have a few Windows 10 workstations. After running the Sage 300 workstation setup, the error "Invalid database specification" appears.

The client is using Sage 300 v2014 PU3

The SQL Server uses SQL Server 2008 R2

I’ve done the following:

UAC settings on the W10 machine is set to the lowest setting
Re-ran the workstation setup (right click mouse > Install as Administrator)
Ran Regacc (right click mouse > Install as Administrator)
In database setup > Changed the server name to an IP address
User has full rights to the Sage folder
User has local admin rights
Right click mouse on Sage 300 Icon and “run as administrator”
recreated the ODBC System DSN connections (in the SYSWOW64 folder)

Would anyone have any other suggestions.

Many thanks in adance

Jay Converse Acumen over 7 years ago

Run Sage as Administrator
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Enabling over 7 years ago in reply to Jay Converse Acumen

We tried that
Right click mouse on Sage 300 Icon and “run as administrator” but the error still occurs
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jay Converse Acumen over 7 years ago in reply to Enabling

Then there's something strange about their environment. Maybe virus checkers getting in the way. Maybe Active Directory group policies.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
LloydSmith over 7 years ago in reply to Enabling

Make sure the SQL Server native client is 10 for Sage 2014 I believe.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Eva Paterson over 7 years ago

If you go into ODBC's and remove any that are there. Then run as administrator and it should recreate and let you in.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jay Converse Acumen over 7 years ago in reply to Eva Paterson

And the server name in database setup should _never_ be an IP address. Use the server's real name.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
WWOOLMER over 3 years ago

Bumping this thread - same error on one workstation, Sage 300 2018.

Eventual solution was to open the Sage Database Setup / Edit screen.

This seemed to force the update of the ODBC32 DSN, which wasn't working up to then. Even after rebooting workstation.

After opening / save on one company in the Sage Database Setup edit screen, Sage connected fine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Sage 300

Invalid database specification

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING