Invalid Database Specification

Question

Hi 
 I have a user who cannot access one of our databases. Other users can access the database, and the user can access our other databases (we have 3 companies plus intercompany and consolidations). 
 The user has a new computer so am wondering if the ODBC aren't working correctly (but these are created using a script and the other ODBC are fine, since other databases are accessible). The script has been used to set up other computers recently (including mine) and I can access the database. 
 Any suggestions? 
 Regards 
 Anna

Jay Converse Acumen · Accepted Answer

There's no reason to use scripts to set anything up. Database setup should use the SQL server name for _all_ companies.

Ettienne Schwagele · Answer

That's a dumb way of setting it up - to be clear: using the scripts and ODBC DSNs is really a dumb way of doing things. Clearly the consultants are clueless as to what they are doing. 
 It is far easier to use the SQL server name in Sage 300/Accpac Database Setup - you enter the server name instead of using a Data Source. 
 The DSN is created automatically when you runs Sage 300/Accpac. 
 It is easy to change over, edit each database in Database Setup (start with the system database), select Server and then enter the server name - done.

Vanessa Ho · Answer

We have a KB article that addresses the error "Invalid Database Specifcation" 
 support.na.sage.com/.../viewdocument.do 
 To summarize what is in this article, it could be that the Microsoft SQL Native client drive may be damaged. Try installing or repairing it. 
 Hopefully, this will resolve your issue.

Sage 300

Invalid Database Specification

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING