IBM Support

** Troubleshooting ** Intermittent "The ConnectionString property has not been initialized" errors

Technote (troubleshooting)


User performs actions inside Controller. From time to time (occasionally / intermittently) the user receives an error message.

The exact error message will vary (depending on what the end user is doing), but it will include the phrase "The ConnectionString property has not been initialized".


Example error:

Standard Error

Error Details
Source: ControllerProxyClient
Description: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ArgumentException: The ConnectionString property has not been initialized.
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)
at ControllerServerCommon.RaiseErrSrv.RaiseError(String sUser, Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)
at FrAccountS.AccountSet.ISet_SelectAll(String sGuid, String sSelectCriterion, String sUser, Int32 lLLocale)
at Cognos.Controller.Proxy.CCRWS.AccountSet_SelectAll(String sGuid, String sSelectCriterion, String sUser, Int32 lLLocale)


There are several possible causes:

  • Scenario #1 (common) - Defect (reference APAR PI32861) in Controller 10.2.0.
    • TIP: See separate IBM Technote #1683841 for more details.
  • Scenario #2 (rare) - CGI timeout occurring on 'gateway' server
    • NOTE: This only affects customer who use the (rare) "t=controller" configuration (where they have a dedicated gateway server, acting as a proxy/relay-server).
  • Scenario #3 (common) - Defect (reference APAR PI54534) in Controller 10.2.1.
    • TIP: See separate IBM Technote #1973433 for more details.


Scenario #2 - Customer has their client device configured to use the 't=controller' parameter.

  • For more details, see separate IBM Technote #1367311.

Resolving the problem

Scenario #1 - Defect in Controller 10.2.0

    Upgrade to Controller 10.2.1 (10.2.5100) or later.

    Increase the application pool timeout value.
    • TIP: See separate IBM Technote #1683841 for more details.

Scenario #2 - CGI timeout occurring on 'gateway' server

Increase the value for 'Time-out' for the CGI system on the gateway server.


    The following steps are based on Windows 2008. The steps may vary slightly for different operating systems.

    1. Obtain a short period of 'downtime' for Controller

    2. Logon to the 'Gateway' server, as a Windows administrator

    3. Right-click on "Computer" and choose "manage" (to launch 'Server Manager')

    4. Expand "Roles - Web Server (IIS)" and click "Internet Information Services (IIS) Manager"
    5. In the right-hand window, expand your webserver's name, and expand "Sites" and then select "Default Web Site"
    6. In "Features View", double-click "CGI".
    7. Under 'Behavior', increase the time-out value in the 'Time-out (hh:mm:ss)' property.

    • This needs to be longer than the longest operation that you perform in Controller (for example a database optimisation). For example to "02:00:00" = 2 hours

    TIP: If your database optimisation takes longer, then increase this further.
    • For example, increase it to "10:00:00" = 10 hours to be sure!

    9. Click 'Apply' (in the 'Actions' pane)
    10. Launch a command prompt (Start - Run - 'CMD' <Enter>)
    11. IISRESET <Enter>
    12. Launch Controller, and test.

    Scenario #3 - Defect in Controller 10.2.1
    See separate IBM Technote #1973433 for details.

Related information

1683841 - Intermittent "The ConnectionString property h
1367311 - How to configure Gateway server in DMZ for a
1973433 - Intermittent "The ConnectionString property h

Document information

More support for: Cognos Controller

Software version: 10.2.0, 10.2.1

Operating system(s): Windows

Reference #: 1963432

Modified date: 22 December 2015

Translate this page: