< class="prominent-subhead ">

Running a report on dd MMM yyyy date range causes an error

This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


Using a custom date format (i.e., dd MMM yyyy) when running a report in K2 Workspace will cause an error. The error will occur on standalone and or/distributed installations when the end user changes a report date to a custom format and runs the report.

Example Scenario

Note: The details below describe symptoms from systems where the error has been known to occur.
The end user is attempting to run a report that uses the date format dd MMM yyyy with the following items installed:
  • Microsoft .NET Framework 2.0 SP1
  • K2 blackpearl SP1

Error Messages

The following error message relates to this KB Article:

  • An internal error occurred on the report server. See the error log for more details. (rsInternalError) Index was outside the bounds of the array.


The error occurs when using a custom date format. Use a standard date format to run the report. K2 blackpearl does not support the date/time format dd MM yyyy or any variation thereof. Standard date formats separated by / or - or . are accepted. For example:


  • dd/MM/yyyy is accepted
  • dd-MM-yyyy is accepted
  • dd.MM.yyyy is accepted
  • dd MM yyyy is NOT accepted