Unable to open the Process Overview report in K2 Workspace 

  • 24 February 2022
  • 0 replies

Userlevel 4
Badge +17

Opening the Process Overview report in K2 Workspace returns a "Cannot open database 'K2' requested by the login. The login failed" error 


K2 blackpearl 4.6.6
K2 blackpearl 4.6.6
K2 Reports
K2 Workspace
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
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.


When opening the Process Overview report in K2 Workspace, the following error appears: 

Service: K2GenericSettings Service Guid: f832fc2c-55eb-4635-8837-61879cb1feff Severity: Information Error Message: Cannot open database "K2" requested by the login. The login failed. Login failed for user 'sa'. InnerException Message: at SourceCode.Workspace.OOBReports.K2ReportSettingsHelper.GetReportConfigString(String reportID) at SourceCode.Workspace.OOBReports.K2ReportSettingsHelper.LoadReportConfigEventArgs(String reportID) at SourceCode.Workspace.OOBReports.K2ReportViewer.LoadReportConfig(Boolean mustSetValue, Boolean isDrillThrough, LocalReport localReport)


The error is coming from the 'K2 Generic Settings Service' service instance.

Troubleshooting Steps

To resolve the issue, please follow these steps:

1. Open the SmartObject Service Tester and go to ServiceObject Explorer > K2 Generic Settings Service.
2. Right-click on the 'K2 Generic Settings Service' instance and choose 'Edit Service Instance'.
3. In the ConnectionString key, ensure that the Data Source is pointing to the correct SQL server name.

0 replies

Be the first to reply!