SQL Database Login failure

[Former Member]

I'm getting a SQL database login failure on one customer after many successful installations at other customers. My app uses OLE DB (ADO) database type with the SQLOLEDB provider to access the database. I create the table logon info structure internally in my app and use that to connect the Crystal Report for.Net framework to the database. I've verified that the server name is correct and the database allows access from SQL Management Studio and from the rest of my app, which uses VB SQL connection objects. But on this one customer I get a "Database Login" prompt when the Crystal Report is run. The prompt shows the correct user name and password. When I hit "Login" the login fails (as it failed internally leading to the dialog being shown in the first place).

Anyone have any idea on what's going on here? Any idea on where else to look? I suspect some software the customer is running is interfering somehow with Crystal Reports. But I don't have any idea of what to check for. Any help will be appreciated.

Jon Webb

PEP Systems, Inc.

[Former Member · Accepted solution]

John,

You can create a UDL file to check the database connectivity in your client's machine.

To do this you need to create a txt file and change the extention from txt to udl. Double click on the udl file and select the provider and then the database and test the connection. It would tell you if there is any issue with the connectivity with your database.

Also you need to make sure that you are not changing any schema of the report.

Regards,

AG.

[Former Member]

Thanks. It is not a network connectivity problem. The server is on the PC I am trying to connect from. I can connect with SQL Server Management Studio. I believe it is a software issue, but I am having a hard time figuring out what could be causing the problem. I upgraded the SQL Native Client driver.

[former_member11696]

Above cr 8.5 we no longer support MS Native client. MS stopped support at the time 8.5 was released and told everyone to go to OLE DB or ODBC.

[former_member203619]

Some of the more common causes for this are:

1. Firewalls - If you have a firewall between the database server and your computer

2. Different SubNets. If your database server is on a different sub-net than the computer you are trying to connnect from - then it might not be able to see it / resolve the name. To verify this, trying pinging the database computer by machine name (e.g. ping myDBServer). This can also be caused by the computer not being able to see the DNS server, and so not able to resolve the DB server machine name.

3. Wrong DB driver version. Sometimes if you are trying to connect to a newer version of SQL server using older drivers - it won't work. Verify what version of the SQL server drivers are being used.

4. MDAC is not installed. To connect via ODBC you sometimes need MDAC installed. You can check the version using the info in this kbase http://support.microsoft.com/kb/301202

Shawn

[Former Member]

Thanks. I did that and there is, indeed, a connectivity problem. The question is, what do I try next? The server is installed locally on the customer PC and I can connect to it using SQL Management Studio. The problem is with the UDL connection. I can also see the problem using the ODBC Control Panel in Administrative tools. The server name will not populate when I click on the drop down. I am sure there is something wrong with the software setup to connect between ODBC and SQL, but I don't know what to check for. I did try updating the SQL Native Client driver but it was already up to date.