Data Access Worldwide Knowledge Base
Article ID 2042 Article Title ERROR: MSSQLDRV.CFG Article URL http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2042 KBase Category CONNECTIVITY KITS Date Created 09/24/2004 Last Edit Date 09/24/2004
Article Text
PROBLEM:
I have Visual DataFlex 10.0 installed and downloaded the MSSQL Connectivity Kit 3.0 to do some testing. SInce I am evaluating the product, I installed the MSSQL CK without a registration code. When I try to use Database Builder (just clicking on "Database" menu), I get the following error:
ERROR
MSSQLDRV.CFG
STATUS <<12320>> ON LINE # 50905
SOLUTION:
MSSQL CK 3.0 uses a different registration from 2.2 (VDF 10.0 installs 2.2 CKs). Since the Connectivity Kit finds registration information in the (Bin) folder, it does not overwrite the existing registration files. The installtion log for the CK will reflect that -- you should not be able to find the registration files in it as one of the copied files.
Just uninstall Microsoft SQL Server Connectivity Kit 3.0, remove the MSSQL CK 2.2 registration files (e.g. MS4913.dfr and MSSQLDRV.cfg) from VDF10.0 Bin folder and then reinstall MSSQL CK 3.0 for VDF10.0. That should be enough to solve the problem.
Contributed By:
Marcia Booth
Company: Data Access Worldwide
Web Site: http://www.dataaccess.com
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.