Report-Specific Errors

My favourite thing, some variety of error is being generated but HIFIS does not have an error message configured to tell you what the error is. We have seen some reports generate this error, but then the report runs fine. We have also seen some reports generate this error, and the report doesn't work. You should try running the report in Crystal Reports, which often provides more helpful error messages.

Similar to "No Error", an error is being generated, but HIFIS can't tell you more about it. However, the error would be recorded in your server's ELMAH logs.

This can be fixed by your Database Administrator (DBA), or someone with access to make changes directly on the server. If that describes you, here are the instructions to modify this value: Locate your web.config file (located in the root folder) Search for the string HifisReportService Find the endpoint element for HifisReportService. It should look something like this: <endpoint address="http://HIFIS_DOMAIN_ADDRESS/HIFIS.DOMAIN.BusinessServices.HifisReportService.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_Standard" contract="HifisReportServiceReference.IHifisReportService" name="WSHttpBinding_IHifisReportService"> Identify the bindingConfiguration being used (for example: bindingConfiguration="WSHttpBinding_Standard") Search for the binding element identified in step 4  (for example: WSHttpBinding_Standard). It should look something like this: <binding name="WSHttpBinding_Standard" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:05:00" sendTimeout="00:01:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="10485760" maxReceivedMessageSize="10485760" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"> Increase the receiveTimeout and sendTimeout attributes to the desired values Repeat steps 1-8 for the file located at Domain\web.config

This can be modified by your Database Administrator (DBA), or someone with access to make changes directly on the server. If that describes you, here are the instructions to modify this value: Locate your web.config file (located in the root folder) Search for the string HifisReportService Find the endpoint element for HifisReportService. It should look something like this: <endpoint address="http://HIFIS_DOMAIN_ADDRESS/HIFIS.DOMAIN.BusinessServices.HifisReportService.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_Standard" contract="HifisReportServiceReference.IHifisReportService" name="WSHttpBinding_IHifisReportService"> Identify the bindingConfiguration being used (for example: bindingConfiguration="WSHttpBinding_Standard") Search for the binding element identified in step 4  (for example: WSHttpBinding_Standard). It should look something like this: <binding name="WSHttpBinding_Standard" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:05:00" sendTimeout="00:01:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="10485760" maxReceivedMessageSize="10485760" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"> Within the binding element identified in step 5, locate the readerQuotas object. It should look something like this: <readerQuotas maxDepth="32" maxStringContentLength="4194304" maxArrayLength="101943040" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> Increase the maxStringContentLength and/or the maxArrayLength property to the desired values Repeat steps 1-7 for the file located at Domain\web.config

This can be modified by your Database Administrator (DBA), or someone with access to make changes directly on the server. If that describes you, here are the instructions to modify this value: Locate your web.config file (located in the root folder) Search for the string HifisReportService Find the endpoint element for HifisReportService. It should look something like this: <endpoint address="http://HIFIS_DOMAIN_ADDRESS/HIFIS.DOMAIN.BusinessServices.HifisReportService.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_Standard" contract="HifisReportServiceReference.IHifisReportService" name="WSHttpBinding_IHifisReportService"> Identify the bindingConfiguration being used (for example: bindingConfiguration="WSHttpBinding_Standard") Search for the binding element identified in step 4  (for example: WSHttpBinding_Standard). It should look something like this: <binding name="WSHttpBinding_Standard" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:05:00" sendTimeout="00:01:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="10485760" maxReceivedMessageSize="10485760" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"> Increase the maxReceivedMessageSize attribute to the desired values Repeat steps 1-6 for the file located at Domain\web.config

There's a formula in the report that is trying to divide by zero. For example, maybe you are trying to divide the number of beds in use by the number of non-overflow beds, but all your beds are overflow, so there are 0 non-overflow beds. Figure out what formula is using division, and then fix the formula.

One or more parameters is not configured correctly.

You are using a subreport and you are passing a value from the main report to the subreport as a parameter, and it is linked incorrectly.

There's some error that could be a few different causes. One possible reason for this is because your report isn't actually pulling any data.

Solution 1: you selected parameters that resulted in no data being pulled. For example, you may have mixed up the start and end dates, so your end date is before your start date. Solution 2: if it's not because the report is correctly displaying no data, it could be due to the report having a long runtime and incorrectly handling a GETDATE() function, or similar. In other words, you get the current date and time at the start of the report and by the time the report is finished loading, the current date and time has changed, so it gets confused and wants to correct itself.

This error would be present on the Community Homelessness Report (CHR) and others. Most likely, this is related to a DROP TABLE IF EXISTS command, relating to a temporary table. This command is only recognized in MS SQL Server 2016 and up. See https://www.mssqltips.com/sqlservertip/6769/sql-server-drop-table-if-exists/ 

This happens when the report is referencing a view or a database field that doesn't exist or doesn't match what is expected. For example, this could occur if you update your version of HIFIS and the database structure changes. Or it could occur if you're trying to run a report that references a view you do not have installed. One possible fix is to install the missing view, if that is the problem. Another possible solution is to update the report definition in Crystal Reports. Open the report in Crystal Reports. Under the menu "Database", select "Verify Database" When it display the message: "The database file <Report Name> has changed. Proceeding to fix up the report.", click "OK" You may need to map some fields Once completed, it will display the message: "The database is now up to date" Save the new version and run it again, or re-upload it to HIFIS and run it again.

As the error message describes, the report cannot generate because the Page Header or the Page Footer is longer than a page, therefore it can't fit it all onto a page, and it's supposed to display this on every page, so your report would be infinitely long and every page would be identical. Usually, the problem is something like you're listing all the service providers you selected for parameters in the page header, and you selected a lot of them. Or you just have too much information in the header.

There's an issue with how your report is trying to connect to the database, because you (the report writer) have different permissions than HIFIS (the report user). It could be that you are using integrated security to login to the server, and your HIFIS doesn't like that. It could be that you're using a driver on your computer to make your report, and the same driver is not installed on the server.