Errors That Can Occur When You re Running a Report From Tigerpaw s SQL-based System (Version 9 and Above) Modified 10/2/2008

Transcription

1 Errors That Can Occur When You re Running a Report From Tigerpaw s SQL-based System (Version 9 and Above) Modified 10/2/2008 1

2 Introduction The following is an explanation of some errors you might encounter when running a report, either from within Crystal, or from within Tigerpaw s Enterprise (SQL-based) system. In some cases, the errors are caused by a problem in the Crystal Report itself, in most other cases the problem is in the Selection Formula in the Reports Explorer. Except for the very first error listed ( No error message, however, the report does not contain any database fields ) the errors are listed in alphabetical order. In a few cases, the exact description of the error may have changed, possibly causing the error to be listed out of sequence. There aren t that many errors so we recommend that you scan the entire list to make sure the error you re getting isn t shown anywhere in the list. If you get an error that is not in this document, please the specifics to eds@tigwerpawsoftware.com so we can document the error. There are several places in this document where reference is made to a document titled Converting Custom Reports to Tigerpaw CRM+. That document is available from: 2

3 Table of Contents Introduction... 2 No error message, however, the report does not include any database fields... 4 A statement is expected here... 4 Database Connector Error... 5 Error: Error: Invalid TLV record... 6 Error 6 - Overflow... 7 Error (9): Subscript out of range... 8 Error 52: Bad file name... 8 Error 525: Failure to load report... 8 Error: A Crystal Reports job failed because a free license could not be obtained in the time allocated... 8 Error: A number, currency amount, boolean, date, time or string is expected here... 8 Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Failed to open a rowset - Native Error Error: Invalid Procedure call or argument Error Number Error: Logon Failed - Native Error Error: The matching for this string is missing Error: The report file XXXXX.rpt does not exist Error: The string is non-numeric Failed to load database information Failed to open the connection.. Database Vendor Code: Failed to open the connection.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Failed to retrieve data from the database.. Database Vendor Code: Invalid Argument provided Not implemented. Details: Error Code 0x800a0cb The page size was not large enough to format the contents of an object in the report This document could not be opened. It does not appear to be a Crystal Report Document Unable to login to Crystal Reports and open the report

4 No error message, however, the report does not include any database fields If a specific report prints only headings and labels, but does not include any data from the dadabase, assuming that there really is data to be printed, then the problem is most likely that the report includes a Selection Formula which does not return any data to the report. Prior to Crystal Version 10 (possibly Version 9), the Selection Formulas used in the Crystal Report were ignored when the report was run from Tigerpaw. That is no longer true. Now, with Version 11 of Crystal, Selection Formulas in the report itself are evaluated and processed after the Selection Formulas supplied by Tigerpaw are evaluated and processed. A second cause of a data-missing report, is an invalid link between tables in the report. If this happens with a system-supplied report, please contact our support department. If this happens with a custom report you ve modified, check the links between the tables in the report more than likely, at least one of the links is not correct. A statement is expected here The cause of this problem is not known. If you get this error, please contact our support group. 4

5 Database Connector Error The only known instance of the Database Connector Error was caused by a table that had two links pointing to the table. Removing the invalid link solved the problem. You can display the links by clicking Database Database Expert Links. One user reported that the table with two links was caused when Crystal added a new link (even though the Smart Link function was turned off), when a new table (tblsyslistviewprint in this case) was added to the report. Error: This is actually a class of errors the text that follows the large negative number varies depending on the cause of the specific error. The problem in the message box above, in one instance, resulted from a table and or a formula that was missing from a report. There is a new requirement in our SQL version, that all the reports that are run from the Service Order View or the Service Order List View must include the tblsyslistviewprint table, with the proper link to the Service Order table, and they must also include a Selection Formula in the report itself. These two requirements are explained thoroughly in the document titled Converting Crystal Reports from Access to Enterprise. Refer to the section titled New Requirements for Reports Printed From Either the Service Order View or the Service Order List View. Another inception of this error was the result of a report that used the wrong database driver. You can check the driver being used by clicking Database Database Expert to display the Database Expert form. In the Selected Tables window on the right side of that form, right-click the Server Name at the top of the window to display the Properties form (see below). On that form, the Database Type must have a Value of OLE DB (ADO) ; any other value will probably cause this error. 5

6 To correct the error, you must specify the proper (OLE DB) driver, as explained in the document titled Converting Crystal Reports from Access to Enterprise in the section titled Mapping the Access-based tables and fields to the SQL-based tables and fields. Error: Invalid TLV record Crystal s documentation basically indicates that this is a.dll problem. On at least one occasion, this error was cleared by closing and then rebooting Tigerpaw s software. In one other instance, the user had just installed Tigerpaw s Software and had gotten errors during the installation process, indicating that some files did not get properly installed. When he tried to print a report, he got the Invalid TLV record message. To resolve the problem, he had to uninstall and reinstall the Tigerpaw Software. The following information was copied from Crystal s Knowledge Base: The "Invalid TLV Record" error message may appear for the following reasons: There are missing runtime files on the client computer. Check the Developer Runtime Help file (Runtime.chm) installed with Crystal Reports for a list of required runtime files. 'UFManager.dll' is not distributed to the client computer. Ensure that it is located in the "C:\Program Files\Common Files\Crystal Decisions\2.0\bin" folder. Crqe.dll is not registered on the client computer. On the taskbar, click the 'Start' button, and then click 'Run'. In the 'Open' text box, type 'regsvr32 <path to crqe.dll>'. For example, regsvr32 "c:\program files\common files\crystal decisions\2.0\bin\crqe.dll" The report file has become corrupted. For more information, refer to knowledge base article c

7 The client computer does not have the 'CommonFiles' registry subkey. To create this registry subkey, follow these steps: =================================================================== WARNING: Using the Registry Editor can cause serious problems that may require reinstalling the operating system. Neither Crystal Decisions (nor Tigerpaw Software) is responsible for any problems resulting from using the Windows Registry Editor. Use the Registry Editor at your own risk. It is recommended that you back up the registry before you edit it. =================================================================== 1. On the taskbar, click the 'Start' button, and then click 'Run'. 2. Type 'Regedit' in the 'Open' combo-box, and then click 'OK'. 3. Expand the registry key: \HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\9.0\Crystal Reports 4. Right-click the 'Crystal Reports' folder, select 'New' 'String Value', and name the new key 'CommonFiles'. 5. Right-click the 'CommonFiles' subkey, select 'Modify', and type the following value in the 'Value data' text box: "C:\Program Files\Common Files\Crystal Decisions\2.0\bin\" Error 6 - Overflow This error is caused by an invalid Selection Formula in the Report Definition record in the Reports Explorer. In the formula below, the characters > are missing from the right side of the command, causing the error: tblcontracts.description = '<!For Contract Description:tblContractDescriptions.ContractDescription 7

8 Error (9): Subscript out of range The only known instance of this problem was caused because an ODBC driver was used, rather than the OLE DB (ADO) driver, when the database connection was made. To correct this problem, you have to point the report at the database using the correct driver, the OLE DB (ADO) driver, and remap each of the tables, following the process described in the document titled Converting Reports to Tigerpaw CRM+ V10, referred to at the beginning of this document. Refer to the section titled Converting a Report a Summary of the Steps Involved". Error 52: Bad file name There are apparently several sub-messages you can get with this error. In every know instance of this error, every report generated the error - users got the error no matter which report they tried to run from a specific workstation. In all cases, the problem is easily solved by setting the Reports Path field in the Rep record of the person trying to run the report, to the correct folder, the one that contains the reports. To do that: click Edit Master Tables Rep Account Reps. Double-click on your Rep record entry on the right side of the form. The "Reports Path" is in the bottom-right corner of the Manager tab. Browse to the proper folder and click Ok to select that folder in the Reports Path field. Click Save and Exit to close your Rep record. At that time, you ll be asked if you want to use that same folder for all the other Reps? That s up to you. Error 525: Failure to load report The only known cause of this error is trying to run a report written for SQL (using Crystal 9.x) against an Access database (which requires a report to be written in Crystal version 8.x). Error: A Crystal Reports job failed because a free license could not be obtained in the time allocated The cause of this error is not known. Crystal Reports documentation refers to.net applications and other causes that are not relevant to our application. Rebooting Tigerpaw clears the error. If you get this error, please contact our support department and give us any information you consider relevant. Error: A number, currency amount, boolean, date, time or string is expected here The most common cause of this message is an error in the Selection Formula in the Report Definition record in Tigerpaw s Reports Explorer. In the formula below, there is a double-quote before the equal sign it should be a single-quote. tblserviceorders.status = "<!SO Status:tblSOStatuses.SOStatus>' 8

9 Error: Failed to open a rowset - Native Error 17 This message further states that the SQL Server does not exist or access denied. The cause of this error has not been determined. If you get this error, contact our support department. Error: Failed to open a rowset - Native Error 105 This error is the result of a bug in the software; the problem has been fixed and will be included in the next release of the software (after version ). If you encounter this error, contact our support department. Error: Failed to open a rowset - Native Error 107 The error above has several known causes: 1. The error can be the result of a table name that wasn t correctly changed in the Crystal report during the conversion / mapping process. To check for / solve this problem, see Changing the Table Names in the document titled Converting Crystal Reports from Access to Enterprise. 2. The error can be the result of the table name being spelled incorrectly in a formula in the Reports Explorer. This is one of the most common causes, and, in fact, this is the cause of the message displayed above - note that the table tblquotes still has a { as part of the name in the message above - that s what s causing the problem in this case. 9

10 3. The error can be the result of an invalid link between tables in the report. To solve the problem, see Fixing the Links Between Tables in the document titled Converting Crystal Reports from Access to Enterprise. Specifically, see Figure 10 more than likely, you will find that the Return all rows before joining checkbox is checked. If that checkbox is checked, uncheck it, and then set the Join Type to Left Outer Join and set the Link Type to Equal ( = ). 4. The error is often caused by a formula in the Reports Explorer that references a table (tblquotes, in this case) that is not in the From Clause of the SQL statement. There are at least two reasons a table isn t in the From Clause of the SQL statement - either the table is not even included in the report, or the table is included but none of the fields in that table are used in the report. Worst case, solving the problem is a simple matter of adding the table to the report (if necessary) and then dragging some field from that table to the report, and then probably suppressing that field so it doesn t really print. I usually put the field in the Report Header, which I then Hide. This problem, it turns out, is specific to Crystal Version 9. Previous versions of Crystal (8.5 and below) included a table in the From Clause if the table was included in a report, even if none of the fields in the table were used in the report. Those reports worked fine in the Access-based version but had to be modified to work in our SQL-based system. Crystal changed the way this works in their Version 9 system, as part of their attempts to optimize the system. Also, Crystal s Version 10 includes an option that forces a table to be included in the From Clause, even if none of the fields from the table are included on the report, so the problem is not a problem in Crystal Version 10 (or 11), if that option is set. You can check the SQL statement in the report to see if the table specified in the error message is included in the From Clause by clicking Database Show SQL Query. You can also check that the table specified in the error message is included in a report by clicking the Field Explorer toolbutton (located below the word Help in the Menu bar, with an icon that looks like a spreadsheet), and then checking for the table name under the Database Fields heading. If the table is not included in the report, you ll have to add it to the report see Adding and deleting tables in the document titled Converting Crystal Reports from Access to Enterprise. Even though a table is included in a report, it won t be included in the From Clause of the SQL statement unless the report includes at least one field from that table. If necessary, you can drag a field from the table to a section of the report that is Hidden or Suppressed. I generally put fields I don t really want to print in the (unused) Report Header. You can even suppress printing of the field, by right-clicking on the field, clicking Format Field, clicking the Common tab, and then clicking the Suppress checkbox. 10

11 Error: Failed to open a rowset - Native Error 156 In general, this error is caused by a bad Selection Formula in the Reports Explorer s Record Definition. In one case, a Selection Formula did not have spaces in front and behind the equal sign. The formula read: tblquotes.quotenumber='<%for Quote #>' Inserting spaces before and after the equal sign solved the problem. In another case, the error was caused by an invalid character in the third character position. The formula read: '<+Invoice Since Date 5>' The correct formula reads: '<&Invoice Since Date 5>'. Error: Failed to open a rowset - Native Error 170 This error message always seems to be caused by an incorrect Selection Formula in the Reports Explorer. In this case, the error is caused by the extraneous a, the last character in the formula below. tblserviceorders.status = '<!SO Status:tblSOStatuses.SOStatus>'a Removing the a from the end of the formula solved the problem. 11

12 In another case, the Selection Formula included a command that caused the Rep dropdown to be displayed at report run-time, and the error was generated only if the user did not select a Rep from the dropdown (indicating the all Reps condition). The problem was resolved by moving the command that displays the Rep table to the end of the formula that is sometimes, but not always, required to make a formula work properly. As a general rule then, if you need to use the command that calls the Rep table, you should always make it the last command in a formula. Here s a formula that generats the Failed to open a rowset Native Error 170 message, if the user does not select a Rep from the Rep dropdown: '<$Print the Detail records (y\n) 5>' tblopportunities.closedate Is Null and tblopportunities.opportunityowner = '<^For Rep>' and tblopportunities.opportunitytype = '<!For Opportunity Type:tblOpportunityTypes.OpportunityType>' To eliminate the error, move the Rep command to the end of the formula, like this: '<$Print the Detail records (y\n) 5>' tblopportunities.closedate Is Null and tblopportunities.opportunitytype = '<!For Opportunity Type:tblOpportunityTypes.OpportunityType>' and tblopportunities.opportunityowner = '<^For Rep>' Error: Failed to open a rowset - Native Error 207 This error is the result of an incorrect (misspelled?) field name in the Selection Formula in the Reports Explorer. The following formula, for instance, generated the error because the Service Order Status field (on the left side of the equal sign) is missing the s at the end of the word status : tblserviceorders.statu = '<!S. O. Status:tblSOStatuses.SOStatus>' 12

13 Error: Failed to open a rowset - Native Error 209 This error is being investigated. If you get this error, contact our support group. Error: Invalid Procedure call or argument Error Number 5 The cause of this error is not known. If you get this error, please contact our support group. 13

14 Error: Logon Failed - Native Error To correct this problem, you have to point the report at the database and remap each of the tables, even though you may have already done that, following the process described in the document titled Converting Reports To Tigerpaw CRM+ V10, which is available from our web page. Refer to the section titled Converting a Report a Summary Of The Steps Involved". When appropriate, make sure you check the Integrated Security checkbox, as explained in Figure 3. If the problem persists after you have remapped the database and the tables, contact our support department. Error: The matching for this string is missing This error is the result of an error in the Selection Formula in the Reports Explorer s Report Definition the formula below includes a double-quote at the end of the formula where a single quote is required. tblserviceorders.status = '<!SO Status:tblSOStatuses.SOStatus>" Error: The report file XXXXX.rpt does not exist This error message means the system can t find the specified report (the Crystal.RPT file). The XXXX.rpt in this message is the directory path and file name of the report. This message is usually the result of a typing error when the report name was manually entered on the Report Definition form in the Reports Explorer. Error: The string is non-numeric The only known instance of this problem resulted from a report that included a USERPARAMx formula (where x is a number from 1-8), expecting to get that value from the Reports Explorer Selection Formula at report run time, but the Selection Formula did not include the 14

15 USERPARAMx function. The problem was solved by adding the USERPARAMx function to the Selection Formula. Failed to load database information If you get the error message shown above, then you probably have a corrupt or missing dll. The easiest way to resolve this problem is to uninstall our software (using the Uninstall program supplied with our system), and then reinstall our software. If you need assistance with the uninstall process, contact our support department. Failed to open the connection.. Database Vendor Code: 17 This error seems to be the same as Failed to open the connection.. Database Vendor Code: See below. Failed to open the connection.. Database Vendor Code: 4060 The only known instance of this error was caused when a report was run from Tigerpaw and that report was pulling data from two different databases. This error,.vendor Code: 4060 was encountered on one machine, but a second machine, using the same report, got a different error - Failed to open the connection Vendor Code: 107. See above 15

16 Pointing all the tables to the same database on the same server (from Crystal), and then verifying the database corrected the problem on both machines. An easy way to check for this problem, is to click Database Database Expert, to display the form shown below. Note that, in this case, the server name LEWIS is displayed twice on the right side of the form (highlighted in green). The report could have shown two different server names and (I think) the result would have been the same (error 4060). At any rate, seeing more than one server name, or a server name listed more than once, should alert you to the error. If you see the same server name listed more than once, that s because you are calling data from more than one database, all of which reside on the same server. In this case, all the tables listed under the first instance of the server name LEWIS, were from a database called Scratch10 (for instance), but the one table listed under the second instance of the server name LEWIS was from a database named XYZ (something other than Scratch10, the name of the first database). You can check the name of the database that contains a specified table, by right-clicking the table name in the list in the Selected Tables box on the right side of the Database Expert form, and then selecting properties. The field labeled Initial Catalog is the name of the database, on the server named (in this case) LEWIS. As indicated previously, pointing all the tables to one database on one server, and then verifying the database, solved this problem. To resolve that problem, you must verify the database, as explained in the document Converting Custom Reports to Tigerpaw CRM+ V10.doc see the section titled Converting a Report a Summary Of The Steps Involved. You can also refer to Crystal s Help text for an explanation of this process see Verify Database Command in the Help index. Note: there may be security considerations related to accessing the database involved in this problem, but as soon as I determined how to fix the problem, I suspended further testing of the possible conditions. 16

17 Failed to retrieve data from the database.. Database Vendor Code: 102 There are several causes of this error. Disconnected tables, tables that are not connected to any other table, such as any of the tblsys tables, can cause this error. In one instance, the error was caused by a field from the disconnected tblsyscompanysettings table the field was the Company Name. In another instance, it was caused because the following line of code was commented out: {tblsyslistviewprint.syslistviewprintkeyid} > 0 The line of code above is required in many reports that are run from the many list views in TPS. In another instance, the Vendor Code 102 error was caused by the formula: tblpricebook.itemid in ['00055', '00070'] If you use ( and ) characters rather than the [ and ] characters used in the formula used above, the formula works properly. Failed to retrieve data from the database.. Database Vendor Code: 107 This error is most often caused by a failure to include the tblsyslistviewprint table and / or the applicable record selection formula in the Crystal report, as explained in the document, titled Converting Custom Reports to Tigerpaw CRM+ V10. In one case, this error is caused by an invalid view name in the Selection Formula in the Report Definition record in the Reports Explorer. It is the view name, which is on the left side of the period in the view name.field name construct that contains the error. 17

18 In another case, the error occurred in a report that had been modified by a customer, and that had been mapped incorrectly to the customer s database. The problem was solved by remapping the tables. For instructions on mapping the tables used in a report, refer to the document titled Converting Custom Reports to Tigerpaw CRM+ V10. One of our customers reported that he got this error because a field that he used in the Selection Formula in the Report Definition record in the Reports Explorer, was not used on the report. To solve the problem, he put the field on the report; because he didn t really want that field to print, he suppressed printing of the field. Failed to retrieve data from the database.. Database Vendor Code: 145 The cause of this error is unknown. If you get this error, please contact our support group. Failed to retrieve data from the database.. Database Vendor Code: 207 This error is caused by an invalid field name in the Selection Formula in the Report Definition record in the Reports Explorer. It is the field name, which is on the right side of the period in the view name.field name construct that contains the error. Failed to retrieve data from the database.. Database Vendor Code:

19 This error message is most likely the result of an invalid entry into a prompt generated by the Selection Formula in the Reports Explorer. You will get this error, for instance, if you enter alphabetic text into the prompt that is generated by the formula: tblcircuits.accountnumber = '<#Circuits for Account No.>'..because the # character in the formula specifies that a number must be input. Failed to retrieve data from the database.. Database Vendor Code: 1540 The only known instance of this error was caused because a field was larger than the allowable maximum of 8094, per a message produced by Microsoft s SQL Enterprise Manager. The field was produced by a stored procedure in the report, and that field was populated from the Work Requested field on a service order in Tigerpaw s database. The field had multiple unprintable characters at the end of the (Work Requested) field, possibly Line Feed and Carriage Return characters. Deleting from the apparent end of the data in that field to the real end of the data in that field resolved the problem. How the unprintable data got into the field is not known, but it might have resulted from someone (unintentionally?) holding down the Enter key on the keyboard, or that key getting stuck somehow. Failed to retrieve data from the database.. Database Vendor Code: 4104 This error also has multiple causes. In one case, the error was caused by the following formula: tblinvoice.status <> 'Void' The correct formula is: tblinvoices.status <> 'Void' You can also get the 4104 error if the report has not been verified against the current version of the database. To resolve that problem, you must verify the database, as explained in the document Converting Custom Reports to Tigerpaw CRM+ V10.doc see the section titled Converting a Report a Summary Of The Steps Involved. You can also refer to Crystal s Help text for an explanation of this process see Verify Database Command in the Help index. You can also get this same error if the system is not setup properly to print a report that can be printed from any of the List Views in the system. In the document Converting Custom Reports to 19

20 Tigerpaw CRM+ V10.doc, see the section titled New Requirements For Reports Printed From Specific Forms and List Views. Invalid Argument provided The only known instance of this error occurred when a report was being converted from Version 9 of our software to Version 10. On the Set Datasource Location form, when you re mapping a V9 table to its V10 equivalent, after clicking on both tables and then clicking the Update button, sometimes nothing seems to happen. Specifically, the V9 table is not replaced by in the Current Data Source window, with the equivalent V10 table in that same window. If you then close the Set Datasource Location form, you get the error message. To prevent the problem, before you map any of the tables, you must first map the database names. All you have to do is simply highlight both database names, the V9 database name in the Current Data Source window, and the V10 database name in the Replace With window, and then click the Update button on the right side of the Replace With window. Note that you must do that before you map any of the tables in the V9 database to their V10 equivalents. Not implemented. Details: Error Code 0x800a0cb3 This error is caused by a period or possibly some other illegal character in the database name. Although SQL won t let you use a database name that includes illegal characters (a period, for instance), you can use illegal characters when changing the database name during a restore operation, which will end up causing you to get this error. 20

21 The page size was not large enough to format the contents of an object in the report This error is caused by a field in the page header of a Crystal report that is longer than one page. In most of the cases I ve seen, it appeared as if someone had held down the Enter key (maybe without realizing what they were doing), at the end of the visible data, causing multiple blank lines at the end of the field. Being blank, it was not obvious the blank lines were there. Deleting those lines solved the problem in most cases. If a field does in fact, contain more than one page s worth of data, you should move that field and print it somewhere other than in the page header. Presumably, you can have the same problem trying to print an object that is larger than one page, in a page footer. This document could not be opened. It does not appear to be a Crystal Report Document The cause of this error is not known. If you get this error, please contact our support group. Unable to login to Crystal Reports and open the report.. The only know instance of this error occurred when a user tried to run a report that had not been connected to a database. To solve this problem, you must make a proper connection to a valid 21

22 Tigerpaw database. This process is thoroughly explained in the document mentioned at the beginning of this document, titled Converting Custom Reports to Tigerpaw CRM+ V10. 22