cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Database Logon Failed, 64 bit OS

Former Member
0 Likes
497

I have an application that simply saves a report to c: . It works on 32 bit machines but not 64 bit. I have installed the 64 and 32 bit runtimes. It works on xp 32( 2 test machines), server 2003(1 machine) but not on win7 64 bit ot server 2008 r2.

Here is the VsappCode:

  private void button1_Click(object sender, EventArgs e)

         {

        // CrystalReport.rpt is attached to the solution.


             using (CrystalReport rpt = new CrystalReport())
             {
                           
                try
                             {
                                 rpt.SetDatabaseLogon("user", "pass");
                                 rpt.ExportToDisk(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat, @"c:\test.pdf");
                             }
                    
                 catch (Exception E)
                 {
                     MessageBox.Show(E.Message);
                 }
             }

         }

I deploy the app thru a setup project and include the merge modules and detected dependencies: CrystalDecisions.Data.AdoDotNetInterop.dll,CrystalDecisions.ReportAppServer.Prompting.dll.

The merge module included is CRRuntime_13_0_1.msm

I believe the issue references this post: http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/10d5fa88-2013-2c10-c9a5-f11963607...

Specifically this quote "Crystal Reports XI Release 2 (version 11.5) and Crystal Reports 2008 (version 12.1.x) support 64-bit operating systems, but in a 32-bit mode only."

Is there something i need to do to the setup project to enforce this?

Thank you for your time.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

If you're connecting via ODBC, make sure the ODBC datasource is 64 bit.

Make sure the database client is 64 bit. Note that with Oracle, you can install one or the other (32 bit or 64 bit client, not both on the same machine).

Provide more info;

Database

DB connection method

What exactly does this mean:

"It works on xp 32( 2 test machines), server 2003(1 machine) but not on win7 64 bit ot server 2008 r2."

Errors? Symptoms? Behavior?

Also re.:

I deploy the app thru a setup project and include the merge modules and detected dependencies:

Only deploy the runtime via the MSI or MSM. Do not add anything else (other than VC++ runtime if using MSM, but until I get more info from you, the VC++ runtime is probably not your issue)

- Ludek

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Share Your Knowledge in SCN Topic Spaces

Former Member
0 Likes

What exactly does this mean:

"It works on xp 32( 2 test machines), server 2003(1 machine) but not on win7 64 bit ot server 2008 r2."

This means i deployed the setup msi to 2 different Xp machines and a server 2003 and they deployed correctly, saving the .rpt file to C:\test.pdf.

I started with OLE DB(Which if i am correct, shouldn't need anything additional to run other than the files in the project)

I changed the report to connect via ODBC but it was also unable to connect. I did install the proper 64 bit Oracle ODBC drivers.

If i had a preference it would be (OLE DB) just so i wouldn't have to install the ODBC drivers

Database is Oracle 10g. And im able to Sqlplus to the database from the 64 bit server.

The error i receive is "Database Logon Failed" for the OLE DB and i believe its the same for ODBC

Former Member
0 Likes

OLE DB Provider: Microsoft OLE DB Provider for Oracle.

Former Member
0 Likes

Don't use Microsoft OLE DB Provider for Oracle. In my experience, this driver does not work very well. Use Oracle's drivers.

- Ludek

0 Likes

Search Microsoft's MSDN, you'll find that their driver only supports Oracle 7.

Also, you never mentioned if you set your Project to build for 32 bit or 64 bit? If the problem is only on the 64 bit OS then make sure all parts are 32 bit only, DB Client, printer driver etc... and you MUST set your project to run in x86 mode only. As noted CR 2008 only supports 32 bit applications.

Don

Former Member
0 Likes

I went thru all the startups and switched it to 86x. Still no luck.

As for the OLE DB, its not this driver. It works on all 32 bit OS's and i was able to get the application to run where i have SAP Server 2011 installed(a 64 bit Server 2008)

So something like a runtime is needed that i cant seem to find. Maybe its to do with the environmental variables on the OS.

I will have more time to look at it tomorrow, i will change the report connection as Ludex mentioned to disprove its a oracle driver issue.

Thanks Don for intel regarding the MS support but i believe i tried oracles driver and it wasnt playing well with VS2010.

Is there any document on deploying applications to 64 bit OS's and exactly what to change in the setup project?

I believe i changed all that was needed and again i had success on server 2008 r2 where a SAP server installation resides so i think its down to a runtime or driver for Crystal.

Is there any newer runtimes than these:

cr120_redist_install.zip

CRforVS_redist_install_32bit_13_0.zip

CRforVS_redist_install_64bit_13_0.zip

?

Thanks in Advance

0 Likes

Hi Steven,

Only prerequisit properties required are the Full Framework and the x86/x64 option.

What it could be then one Windows 32 bit OS it always installs MDAC. On a 64 bit OS I don't think it does, I beleive It may be called WDAC for 64 bit's. Check MS's site. It could be that MS simply doesn't install the driver you are using. Or it seems odd that if you install CR then it works...

Anyways, As long as your database queries are simple then MS's driver will likely support it. If you start using new Oracle functionality after version 7 then you may run into problems.

Use Modules to compare the runtime. Search and you'll find it here or if Ludek see's this he'll paste in the link...

And yes you are on the original release, click on the Overview tab above and you'll see a link to download the latest installer for VS 2010 as well as the redist packages. Do both, update VS and then rebuild your project and redist package.

Don

Answers (1)

Answers (1)

Former Member
0 Likes

The only way i could get this working was to eliminate the Crystal Connectivity to the data. I loaded the oracle stored procedure return to a dataset within the application and then set the source of the report to this dataset.

I tried all available drivers from within the crystal plugin for VS with no luck.

0 Likes

Great you found one work around but be aware that DS's will have memory limts so if the users return a lot of data you are going to generate out of memory errors...

Don