Connection failed for (localdb)\V11.0 (MS-SQL2012)

[Former Member]

I've successfully migrated our web apps and reports through VS2005 and VS2008 using the same login code for the Crystal report viewer (dynamic database information from web.config. We migrated to VS2012 and the same login code will work for MSSQL default instance, as well as MSSQL\SQLExpress, however it fails with the new (localDB) engine provided by MS with the following error: Failed to open the connection. Details: [Database Vendor Code: 17 ] Failed to open the connection. rptVASCodes {988AC187-9046-4B3A-B132-D32138E57C88}.rpt Details: [Database Vendor Code: 17 ] This is on a Windows 7 Pro (32), VS2012, .net 4.5 and the just released SAP Crystal Reports version for Visual Studio. Database name passed as default of (localdb)\V11.0. Any ideas would be appreciated as this is a show stopper for us at this point.

Thanks - Paul

[former_member183750 · Accepted solution]

Hello Paul

Database Vendor Code: 17, is being passed from the DB client through the CR engine unmodified. E.g.; see if you can find what the error is all about in your DB documentation.

Also, see the following;

http://forums.asp.net/t/997655.aspx/2/10

Posts from April 8 and April 12, 2011.

[Former Member · Accepted solution]

Thanks for your reply Ludek. 

I did check that posting among others. I am going to go out on a limb here, but I think it is an SAP Crystal Report issue. MS released framework 4.02 to accomodate the "special" server name for localDB version of SQL-2012 Express which is (localDB).  Within the MS environment, you can only refer to localDB as (localDB)\<instanceName> or with the generated Named Pipes data. This holds true for SSMS as well as all database connections from the Visual Studio app. I've opened a connection on the VS IDE for (localDB) but I cannot create an SAP CR with it as the connection is not recognized (OLEDB NC11) by the SAP CR connection wizard. I will keep looking though.

Thanks......

[former_member183750 · Accepted solution]

Hello paul

I'll ask Don W to have a look at this alos. He is my DB guru

- Ludek

[Former Member · Accepted solution]

I have screen snaps showing the errors generated by the Set Datasource Location dialog on a report. Let me know if you would like to see them. Thanks

[former_member11696 · Accepted solution]

Hi Paul,

SQL 2012 has a new dll Client driver dll called SQLNCLI11.dll. We had to add this to our Driver list when SQL 2008 came out so CR would recognize the client dll. MS doesn't support MDAC to SQL 2008 and likely not SQL 2012 either, or it's limited support only by MS.

As for supporting SQL Express 2012 if you can't select a PC name, User, PW and database in our UI then I doubt this is going to work.

I have the SQL 2012 client installed, so when I create a report in the .NET IDE and use the database wizard I see these drivers:

but then to actually connect I MUST fill in the next screen with valid info:

If you can't then CR won't support it, if SQL 2012 doesn't support an interface then how would you fill the info in manually just to test?

Possibly a UDL might work. Open Notepad and create an empty text file and save it to your Desktop. Rename the file to *.UDL. Now double click the file and it should bring up MS OLE DB Log on dialog box and you cna select the 11 driver but now you need to fill in the Server name, User, PW and DB info so not sure if you can get past this point from the notes you posted on what SQL Express limits you to.

I'll ping the PM to see if this is something we can support.... likely answer is no if you can't fill in the info in our log on UI.

As much as I hate to suggest it but you may have to move to a Dataset. Limitation with this type of connection though...

Don

ALSO NOTE: SQL 2012 is not officially supported yet... and the Express versions usually don't work due to limitations Microsoft builds into those "lite" versions.

[Former Member · Accepted solution]

Hi Don. Just want to clarify that the reports work with SQLExpress, just not the new (localDB) database engine (which is derived from SQLExpress). Also I had already attempted connection as shown above,

When I select update, I got the following two errors, in succession....

I understand that SQL2012 is not supported  yet, but I thought I would try pushing this up the SAP ladder to see if support for (localDB) can be considered when SQL2012 is supported by SAP. MS are pushing this (localDB) as a need/want item by developers, but it would be detrimental if reporting is not supported as well and of no use to developers.  Anyhow, I will continue to look for workarounds but thanks for the feedback.  Cheers!

[former_member11696 · Accepted solution]

Thanks Paul,

The issue then is likely due to MS renaming their client dll. CR will not use it and would default to some SQL Syntax that MS doesn't support.

I'll ping the PM to see when and what SP this product will add support. We will eventually but not sure what the plans are yet.

Don

[former_member11696 · Accepted solution]

Hi Paul,

So it's officially not supported yet. The problem is the client dll name, CR doesn't recognize it.

They are looking at trying to get it into SP 6. I'll know more tomorrow if they decide anything.

You could try using the MDAC driver, either MS OLE DB Prvider or through ODBC and the MS Native.

It has limited support by Microsoft but may get you by until a patch has come out that supports it.

Don

[Former Member · Accepted solution]

Thanks Don. Appreciate your input on this. We decided to use ODBC on this for now, limiting as it is. At least we can move forward, although in a slightly different path (for now we hope). Cheers!

[former_member11696 · Accepted solution]

Update....

PM and R&D Product owner have agreed we will add Native 11 driver support in Service Pack 6. Should be out in a few months-ish.... lol No exact date yet.

Don

[Former Member · Accepted solution]

Awesome news, even if a date hasn't been established as yet. Thanks again for keeping us updated on this. Cheers!