Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Extensible Storage Engine wikipedia , lookup
Oracle Database wikipedia , lookup
Microsoft Access wikipedia , lookup
Concurrency control wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Relational model wikipedia , lookup
Database model wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Crystal Reports Troubleshooting database errors when using Crystal Development tools Overview This document provides troubleshooting resources for solving database connectivity related errors when using Crystal Reports development tools. Contents INTRODUCTION ............................................................................................2 532 OR 20532 – MISSING DATABASE DLL ..................................................2 533 OR 20533 – UNABLE TO OPEN DATABASE FILE ....................................3 534 OR 20534 – ERROR DETECTED BY DATABASE DLL ..............................3 535 OR 20535 – UNABLE TO CONNECT: INCORRECT SESSION PARAMETERS 3 536 OR 20536 – UNABLE TO CONNECT: INCORRECT LOGON PARAMETERS ..4 599 OR 20599 – CANNOT OPEN SQL SERVER ............................................4 ADDITIONAL TROUBLESHOOTING ARTICLES/DOCUMENTS ...............................5 CONTACTING CRYSTAL DECISIONS FOR TECHNICAL SUPPORT ......................6 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. Page 1 Crystal Reports Troubleshooting database errors when using Crystal Development tools Introduction Database connectivity errors represent a large percentage of errors encountered when running a Crystal Report at runtime through a custom application. Usually these errors occur due to: IMPORTANT NOTE! • Missing database client software or dependency files. • Missing or older version Crystal database DLLs (such as P2sodbc.dll). • Missing or incorrectly configured ODBC Data Source Name (DSN). • Incorrect logon information. • Missing logon information for a subreport • Incorrect syntax in a database related call, method or property. Always ensure that a report first runs correctly in the Crystal Reports designer. A report that fails to connect successfully in the Crystal Reports designer will always fail to connect through a custom application. For information on troubleshooting connectivity issues in the Crystal Reports designer, refer to the document cr_dbconn_troubleshooting.pdf. The following sections list Knowledge Base articles on Crystal Print Engine (Crpe32.dll) errors related to database connectivity issues. These error numbers include: 532 or 20532 – Missing Database DLL 533 or 20533 – Unable to Open Database File 534 or 20534 – Error Detected by Database DLL 535 or 20535 – Unable to Connect: Incorrect Session Parameters 536 or 20536 – Unable to Connect: Incorrect Logon Parameters 599 or 20599 – Cannot Open SQL Server Each Knowledge Base article number listed below is a hyperlink to the actual article itself on the Crystal Decisions Support site (http://support.crystaldecisions.com). In addition, this document provides other troubleshooting documents relating to database connectivity at runtime. 532 or 20532 – Missing Database DLL c2007789 -- Error: "20532 Cannot locate Database DLL" c2007127 -- "Error 20532" Returned when Calling a Report Through Active Server Pages (ASP) 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. cr_dev_dbissues.pdf Page 2 Crystal Reports Troubleshooting database errors when using Crystal Development tools c2006609 -- 20532 error: 'Cannot find database DLL' when previewing a bound report c2006479 -- Error 532: 'Cannot find database dll. LogonServer.Logon <PELogonServer>' c2001740 -- The library "pdsmon.dll" cannot be found; Runtime error '20532': 533 or 20533 – Unable to Open Database File c2003092 -- Using StoredProcParam property causes a 20553 error with Oracle c2002371 -- Error 20553: "Unexpected type for parameter field" c2001160 -- Setting the path to a database which is more than 128 characters causes an error c2000230 -- 533: Error Detected By Database Dll - Paradox/C++ Builder 534 or 20534 – Error Detected by Database DLL c2009179 -- Error "20534: Error detected by database DLL" with Visual Studio Service Pack 3 c2007694 -- Error 20500 and 20534 using the OCX and a secured MS Access database c2006737 -- Upgrading to Access 2000 causes Crystal Reports 4.6 application errors c2006736 -- Crystal Reports 4.6 application and Microsoft Access 2000 c2001455 -- Error 20534, using True Grid and Crystal OCX 535 or 20535 – Unable to Connect: Incorrect Session Parameters c2009985 -- Error: "535 Unable to connect: incorrect session parameters" with 8.x VCL c2008262 -- Error 20535: 'Unable to Connect, Incorrect Session Parameters' c2006914 -- 20535 - Connecting natively to Microsoft Access c2006737 -- Upgrading to Access 2000 causes Crystal Reports 4.6 application errors 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. cr_dev_dbissues.pdf Page 3 Crystal Reports Troubleshooting database errors when using Crystal Development tools c2006736 -- Crystal Reports 4.6 application and Microsoft Access 2000 c2003789 -- Possible causes of error messages generated by P?bdao.dll c2002472 -- Access database in read only location c2000272 -- Setting Informix Stored Procedures Parameters via OCX 536 or 20536 – Unable to Connect: Incorrect Logon Parameters c2005677 -- Incorrect Session Parameters when using Access 2000 c2002521 -- Using LogonServer with a report using the P2soledb.dll driver c2001630 -- Error 536/599 - Incorrect LogOn Parameters c2000606 -- Error 20536 - Invalid Logon Parameter c2000302 -- Error 20536 appears when using a trusted connection c2000028 -- Seagate Crystal Reports and Integrated Security Connections for SQL Server 599 or 20599 – Cannot Open SQL Server c2008952 -- Connecting to SQL Server 2000 natively with integrated security and OCX fails c2008680 -- Error: '599' when using PELogonSQLServerWithPrivateInfo c2008291 -- Using a Trusted connection or Integrated Security with the OCX at runtime c2007612 -- Distributed report using ODBC fails to run on a Windows NT/2000 computer c2007257 -- "Error 20599 Could not open SQL Server" when using the OCX and Lotus Notes c2006438 -- Error: Data source name not found and no default driver specified c2005827 -- "Error 20599" When Using a Trusted Connection c2005632 -- Limitations of using Crystal Queries and Dictionaries for development purposes c2005615 -- Error 20599 when changing the Server name and Stored Procedure at runtime. 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. cr_dev_dbissues.pdf Page 4 Crystal Reports Troubleshooting database errors when using Crystal Development tools c2004937 -- Using a Trusted connection or Integrated Security with the OCX at runtime c2004178 -- "Error 20599 Cannot Open SQL Server" Calling a Report from Active Server Pages c2003803 -- "CRPE Error 599" & "Cannot Open SQL Server" when connecting to Microsoft Access c2002982 -- Error 599 or 20599 when running a report using active data c2002782 -- Active Data Report is Still Looking for ODBC Datasource c2002650 -- What is the difference between LogOnServer and SetLogOnInfo methods c2001630 -- Error 536/599 - Incorrect LogOn Parameters c2001383 -- Visual FoxPro applications and database connectivity c2001142 -- Changing servers using LogonServer creates error 20599 c2000510 -- SQL Server Error Connecting to Microsoft Access through ODBC Additional troubleshooting articles/documents c2008238 -- Runtime file requirements for Crystal Reports c2002649 -- Troubleshooting the error "Server Not Yet Opened" when using the RDC c2007701 -- An error has occurred on the server.: -2147192184 Server has not yet been opened (Troubleshooting article on using Crystal Reports in an ASP application) cr_error_detected_by_db_dll_pdf -- A troubleshooting whitepaper on the error ‘Error Detected by Database DLL’ c2002296 -- Changing database and table location using the RDC c2007576 -- Changing a report's database location through ASP c2002650 -- Comparing the LogOnServer and SetLogOnInfo methods of the RDC c2008208 -- Troubleshooting Active Server Pages (ASP) and Active Data Objects (ADO) c2004884 -- Using the Connect property of the Crystal ActiveX (OCX) control cr_dbconn_troubleshooting.pdf -- Database connectivity troubleshooting document for the Crystal Reports designer and Seagate Info 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. cr_dev_dbissues.pdf Page 5 Crystal Reports Troubleshooting database errors when using Crystal Development tools Contacting Crystal Decisions for Technical Support Along with this document, and the Crystal Reports User’s Guide, we recommend that you visit our Technical Support web site for further resources and sample files. For further assistance, visit us at the web sites below. Technical Support web site: http://support.crystaldecisions.com/homepage/ Answers By Email Support: http://support.crystaldecisions.com/support/answers.asp Phone Support: Tel: (604) 669-8379 3/21/2002 4:44 PM Copyright 2001 Crystal Decisions, Inc. All Rights Reserved. cr_dev_dbissues.pdf Page 6