Connect Crystal Report to Database via ODBC

Juliana Zhou 21 Reputation points
2022-11-04T00:55:36.353+00:00

I am trying to connect Crystal Report via ODBC; when I am about to create a new DSN source it won't work and below error popped up:

---------------------------

Microsoft SQL Server Login

---------------------------

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

---------------------------

OK   

---------------------------

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,122 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Olaf Helper 42,576 Reputation points
    2022-11-04T06:00:57.917+00:00

    SQL Server does not exist or access denied.

    I would say: As the message says.
    Sure you entered the right SQL Server (instance) name?


  2. CathyJi-MSFT 21,111 Reputation points Microsoft Vendor
    2022-11-04T06:15:57.797+00:00

    Hi @Juliana Zhou ,

    >>[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

    According to the error message, please make sure SQL Server Service is running. If a named instance, make sure SQL Server browser service is running. Make sure the instance name is spelled correct in server box and there is actually such an instance on your machine.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".


  3. Juliana Zhou 21 Reputation points
    2022-11-10T16:49:23.8+00:00

    I don't know why - I tried another SQL account - the connection is complete. However, the both of them can connect the database through SSMS.


  4. Juliana Zhou 21 Reputation points
    2023-03-29T15:52:38.73+00:00

    This has been addressed;

    It's simply the issue of user name's case-sensibilities.

    0 comments No comments