DPR-ERR-2058 The Dispatcher cannot service the request at this time

Technote (troubleshooting)


Unable to open IBM Cognos ReportNet or IBM Cognos 8 BI from a web browser due to the following error.


The generic error normally seen is:

DPR-ERR-2058 The dispatcher cannot service the request at this time

The error message may also include:

The dispatcher is still initializing. Contact your administrator if this problem persists.

Additional errors you may encounter in the log files are:

DPR-CMI-4007 An request to perform an active content manager election failed.
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
CM-CFG-5036 Content Manager failed to connect to the content store. The connection string is 'jdbc:oracle:thin:@<ip>:1521:<service name>'.
DPR-CMI-4006 An attempt to determine the active Content Manager was unsuccessful. Will
retry periodically.
CM-CFG-5023 Content Manager is unable to initialize the content store by using the initialization file "D:\ProgramFiles\Cognos\crn\configuration\schemas\content\oracle\dbInitLock_oracle.sql"
ORA-00955: name is already used by an existing object
CAM-AAA-0064 The function 'CAM_AAA_JniAuthProvider::Configure' failed. Provider initialization failure. Reason: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
CM-SYS-5155 SQL Server is set to use the "Windows Authentication" mode. Content Manager doesn't support that. Please reconfigure your SQL Server to work in the "SQL Server Authentication" mode.


There can be multiple causes for this error, and several ways to troubleshoot the underlying problem. The list below provides several things to verify if this error occurs.

Resolving the problem

For errors such as these, it is always recommended to check the appropriate log files. For ReportNet, check the crnserver.log found by default in your \logs directory. For Cognos 8, check the cogserver.log file.

Use the following checklist to troubleshoot the error:

The source of the problem may be with the Content Store database.

  • Check that the tables have been created in the Content Store database. Also, ensure that a supported version of the Content Store database is being used. A list of Content Store databases is available on the support.cognos.com website.
  • The Content Store database must be set to case-insensitive. The steps to confirm that the Content Store database is case-insensitive will vary depending on the database you are using. Please refer to the database documentation or contact your Database Administrator to find the steps needed for your database .Also, verify the database name being used by comparing the name in SQL Server with the name used in Cognos Configuration.
  • Ensure that the port for the Content Store database is correct. If you are using Microsoft SQL Server 2000 the default port for installation is 1433. The default port for Oracle is 1521. To check the port:

    1. Start Cognos Configuration.
    2. Go to Local Configuration --> Data Access --> Content Manager --> database resource properties --> database server and port number.
    3. If you make any changes to these settings, remember to restart the Cognos ReportNet or Cognos 8 service.
  • You may need to increase the available Oracle table space.
  • In DB2 version 8.1, the DB2 DBA must run a DB2 command line command "Start" with parameters for the database in order to activate the JDBC access. In some cases, it may be necessary to restart the content store.
  • Ensure that the database sign-on has all the privileges required. For example, for Oracle, this means:
    • create, alter, and drop tables, triggers, views, procedures, and sequences
    • insert, update, and delete data in the content store tables
  • If this is a new installation and problems have occurred during the install, there may be residual tables in the content store. Running a database cleanup script (.\cognos\[crn|c8]\configuration\schemas\content\oracle\dbClean_Oracle.sql, for example) may alleviate issues. This script will delete all content in the content store!
  • Ensure that the server being used to provide authentication is active.
  • It might be a timing issue. Both Cognos ReportNet (or Cognos 8 BI) and Java.exe take some time to initialize. When starting Cognos ReportNet (or Cognos 8 BI) as a Windows service, there will be a short delay between the time Windows invokes the software and shows Cognos ReportNet or Cognos 8 BI as started, and the time they have actually completed their initialization.
  • Try using the startup.bat file in order to see the error messages or to ensure that the dispatcher has been initialized properly. In order to do so, follow these steps:

    1. Stop the Cognos ReportNet (or Cognos 8) service.
    2. Navigate to the <em>crn\bin</em> (or c8/bin) directory and run the startup.bat file.
    3. If the dispatcher does not initialize properly, the error messages will be visible in the Command Prompt.
    4. If the message <em>The dispatcher is ready to process requests</em> is displayed, the dispatcher and Cognos ReportNet services have initialized properly.
    5. When all errors are resolved, restart the Cognos ReportNet service.
    6. Errors can also be seen by opening the crnserver.log (or cogserver.log for Cognos 8) file from the ...\crn\logs (or c8/logs for Cognos 8) directory.
  • Ensure that the database server host name is listed in the hosts file (located in the C:\WINNT\system32\drivers\etc directory).
  • In Cognos Connection in the Content Store node, ensure the Service Name Property (the SID) is not fully qualified. The JDBC Driver uses the SID, not the fully qualified name.
  • Do not use any remote software, such as DameWare, to install Cognos ReportNet or Cognos 8. Install the product directly on the server to avoid this error.
  • Ensure that there is adequate tablespace on the database server.
  • If you are using SQL server, ensure you have the lastest service packs installed.
  • Ensure also that SQL Server is using mixed mode authentication. Steps:

    1. Start SQL Server Enterprise Manager
    2. Right click your database server and click Properties
    3. Click the Security tab.
    4. Ensure that SQL Server and Windows is selected under Authentication.
  • Ensure that the name of the database server that contains the content store matches the server name specified in Cognos Configuration.

Cross Reference information
Segment Product Component Platform Version Edition
Business Analytics Cognos 8 Business Intelligence Install and Config

Historical Number


Document information

More support for:

Cognos ReportNet

Software version:


Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Content navigation