"Logon failed" connecting to SQL Server database using OLE DB (CR 2008)

[Former Member]

I am getting the following error when I try to connect to a SQL Server database using OLE DB from the Crystal Reports 2008 IDE.

I receive a similar error when trying to access the database by launching the report using the .NET CrystalReportViewer component.

My machine is running Windows XP SP3. I have already tried doing things like uninstall/reinstall Crystal, and have also used Microsoft's Component Checker to verify my MDAC 2.8 SP1 installation (I think this is the right component to check for OLE DB??).

Any help would be greatly appreciated!

Logon failed.

Details: ADO Error Code: 0x

Source: Provider

Description: Multiple-step OLE DB operation generated errors. Check

each OLE DB status value, if available. No work was done.

Native Error: [Database Vendor Code: -2147217887 ]

[former_member11696]

Hi Shannon,

From the error message it appears you are using Ms SQL Server 2008 also. If you are using MS SQL Server 2008 the standard MDAC is not supported for connecting to it. You need to install the MS Client. Then you'll see SQL Server Native Client 10.0 in the OLE DB connection wizard in CR Designer.

Thank you

Don

[Former Member]

Don,

Thank you for your response. We are actually using SQL Server 2000, not SQL Server 2008.

I will try changing the connection, though - I think SQL Native was an option? Pretty sure I tried that already, but I will double-check.

But in any event I am hoping to figure out why I cannot connect using OLE DB.

[former_member11696]

Hi Shannon,

I don't believe Native is an option with MS SQL Server 2000 and MDAC. OLE DB or ODBC is your only option.

Try creating a System DSN using ODBC to see if that works.

Another option is to download our Data Direct ODBC drivers, which I believe also installs an MS OLE DB driver. You can get to it from the link in the start page of Crystal Designer.

I tried searching MSDN at Microsoft and that error does not return any hits.... We do support MS 2000 SP4 only though. I assume by now though you have that MS patch installed?

In CR Designer are you selecting OLE DB and then choosing Microsoft OLE DB Provider for SQL Server or the MS SQL Native Client? Try each to see if either of them work. You could even try the OLE DB for ODBC to see if that works.

If none of the above work then install MS's Server tools and see if you can connect using MS's Enterprise Manager tool.

If non of this works try doing a repair install of Crystal Reports. Make sure you are a local PC administrator or have the same rights. Expand all of the database options and select all of them, except Lotus, it's not required. Unless you are using it also.

If that fails also then go to www.sysinternals.com and download a tool called Process Monitor and add crw32.exe to the filter and try running a report again. The logs may show you where it's failing.

If all of this fails then I suggest you purchase a support case on line and get a dedicated Support Engineer to help you through these steps and debugging the problem.

Thanks again

Don

[Former Member]

Thank you, Don..

The reports run okay when I use ODBC. We are trying to stay with OLE DB in order to simplify deployment, though. But possibly we could switch back to ODBC.

Also, the issue is only happening in my development environment - the user machines seem to be okay. While one might think that all that matters is whether the users can run the software, unfortunately I can't get them an upgraded version of the application unless I can run it in development first.

I'm guessing that there is some sort of version mismatch on something in my development environment (note: I did have a lot trouble installing CR 2008 SP1 initially). I just can't seem to find where that mismatch might be.

OLE DB does not work using either the Provider for SQL Server or the Native Client. Probably OLE DB for ODBC would work, but then we might as well just use ODBC (which we are trying to avoid).

Connections are fine using SQL Management Studio. Full uninstall / reinstall of Crystal did not resolve the problem. Filemon and Regmon did not show me anything that seemed to help. Reinstalling MDAC did not help. Also, I am able to make an OLE DB connection to the same database from Excel, so the problem does seem specific to Crystal 2008.

Any other ideas are of course appreciated - in the meantime I have two other Crystal hurdles I am going to try to work on (an MSI issue and an ASP.NET postback issue). Unfortunately, all these various issues have kept my development pretty much stalled for several weeks now, but I'm hoping to figure out a way to move forward (or around) soon.

Finally, please forgive if some of my comments re: the various drivers and providers don't quite make sense. I haven't really had to work at this level before - our previous development using Crystal 8.5 worked pretty flawlessly without any fidgeting. Some of that magic seems to be gone with Crystal 2008 (at least for me) - it looks like going forward I will need to understand a lot more about the inner workings of the technology (which, of course, is a good thing.. just was unexpected based on my prior experience).

--

sw

[former_member11696]

Hi Shannon,

Thank you for all the info. ODBC was just a test to see if that worked. So it appears the client dll's required are their for ODBC at least.

What development studio are you using for your ASP app? ASP is no longer supported in CR 2008, it used the RDC, craxdrt.dll, which is no longer shipped. ASP.NET is fully supported though using the updated CR assemblies and runtime.

The only file we use to connect through OLE DB is crdb_ado.dll, use Dependency Walker to see some native MS dll's that we have dependencies on. It may be one of these that's causing the problem. The file is located in:

C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86

Use Modules to compare runtime on a working dev PC and your PC. It should list all files being loaded and then has the ability to compare those lists.

https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip

Thanks again

Don

[Former Member]

Don -

Thank you for your help. I think I am going to try going back to using ODBC instead of OLE DB.

I tried using the tools you suggested in your last post, but was not able to find anything which solved the problem yet.