Issues configuring a distributed installation

Hi all

I’ve been having problems with putting together a distributed installation and was hoping for some assistance.

Everything is being installed on Windows 2008 R2. I’m installing Cognos 8.4.1 x86 and the content store is on SQL Server 2008 x86. There are a total of 4 Cognos servers, but whilst I’m troubleshooting I have taken one of the application tiers out of the equation. So basically one server per component and to make it simple I’ll call them GW (gateway) AT (application tier) and CM (content manager). The content store is on a separate SQL dedicated server.

When I start up everything there is no reported error but when I open the webpage on GW it comes up with the following error:

DPR-ERR-2008 “The dispatcher is unable to process the request. The request is directed to an unknown service name: cognos8.”

In the logs on AT are the following errors:

Message: View in XML viewer | Save XML as... <?xml version="1.0" encoding="UTF-8"?> DPR-DPR-1035 Dispatcher detected an error. Log Data: SOAPAction does not map to any known service.
Message: Log Data: SecureErrorId: 2010-11-05-14:59:51.434-#1 Original Error: DPR-ERR-2008 The dispatcher is unable to process the request. The request is directed to an unknown service name: . Handler trace back: [the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler

If I log onto gateway server and type in http://CM:9300/p2pd/servlet I get the state: running message.
If I type in http://AT:9300/p2pd/servlet/dispatch the non-graphical login screen comes up, I can authenticate and log in.
However, when I try http://GW:80/cognos8/cgi-bin/cognosisapi.dll these errors occurr.

I’ve stripped back all configuration settings in order to try to isolate the problem. I’ve put together plenty of environments but unfortunately only single server ones and I suspect there is something I’ve overlooked that is key or my understanding of how things are supposed to be set up is not quite right for a distributed install. So here is the current configuration:

CM Config
External Dispatcher URI = http://CM:9300/p2pd/servlet/dispatch
Internal Dispatcher URI = http://CM:9300/p2pd/servlet/dispatch
Dispatcher URI for external applications = http://AT:9300/p2pd/servlet/dispatch
Content Manager URIs = http://CM:9300/p2pd/servlet
The dispatcher service is disabled
I’ve added Active Directory Authentication (which validates)
In Cryptography Store symmetric key locally = True
Password under Certificate Authority settings has been set
Content Manager is a content store on a dedicated SQL server, database name Cognos8_content using a SQL account with db_owner privileges

On startup, messages are as follows:

15:29:28, 'LogService', 'StartService', 'Success'. 15:29:32, CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started. 15:29:32, CM-SYS-2216 A Content Manager internal PRECACHEINITACTIONS task is complete. 15:29:33, CM-SYS-2215 A Content Manager internal POSTINITACTIONS task started. 15:29:33, CM-SYS-2216 A Content Manager internal POSTINITACTIONS task is complete. 15:29:33, 'ContentManagerService', 'StartService', 'Success'. 15:29:33, CM-SYS-5159 Content Manager is running in active mode. 15:29:33, DPR-DPR-1002 Successfully registered the dispatcher http://CM:9300/p2pd in Content Manager. 15:29:34, 'SystemService', 'StartService', 'Success'. 15:29:35, 'MonitorService', 'StartService', 'Success'. 15:29:35, 'DeliveryService', 'StartService', 'Success'. 15:29:35, 'EventService', 'StartService', 'Success'. 15:29:35, 'JobService', 'StartService', 'Success'. 15:29:36, 'CPS Producer Registration Service', 'StartService', 'Success'. 15:29:35, 'PresentationService', 'StartService', 'Success'.

AT Config
Gateway URI = http://GW:80/cognos8/cgi-bin/cognosisapi.dll
External URI = http://AT:9300/p2pd/servlet/dispatch
Internal URI = http://AT:9300/p2pd/servlet/dispatch
I’ve set dispatcher password
Dispatcher URI for external applications = http://AT:9300/p2pd/servlet/dispatch
Content Manager URIs = http://CM:9300/p2pd/servlet
Store symmetric key locally = False
Password under Certificate Authority settings set to same as CM
Notification store pointed to the content store used by CM

On startup messages are as follows:

Successfully launched a test JVM with the memory setting of '768'. Note that this does not guarantee that IBM Cognos 8 will start and run successfully.

To see which JVM options are based on this setting, view c8_location/bin/bootstrap_.xml and see your JVM documentation for an explanation of those options.
15:34:30, ‘LogService’, ‘StartService’, ‘Success’.
15:34:32, DPR-DPR-1002 Successfully registered the dispatcher http://AT:9300/p2pd in Content Manager.
15:34:35, ‘BatchReportService’, ‘StartService’, ‘Success’.
15:34:35, ‘SystemService’, ‘StartService’, ‘Success’.
15:34:36, ‘PresentationService’, ‘StartService’, ‘Success’.
15:34:36, ‘ReportService’, ‘StartService’, ‘Success’.
15:34:36, ‘ReportDataService’, ‘StartService’, ‘Success’.
15:34:36, ‘MonitorService’, ‘StartService’, ‘Success’.
15:34:36, ‘AgentService’, ‘StartService’, ‘Success’.
15:34:36, ‘MetadataService’, ‘StartService’, ‘Success’.
15:34:36, ‘DeliveryService’, ‘StartService’, ‘Success’.
15:34:36, Start a BIBusTKServerMain because the start count 1 is larger than 0.
15:34:36, ‘EventService’, ‘StartService’, ‘Success’.
15:34:36, ‘JobService’, ‘StartService’, ‘Success’.
15:34:36, Start a BmtMDProviderMain because the start count 1 is larger than 0.
15:34:37, ‘CPS Producer Registration Service’, ‘StartService’, ‘Success’.
15:34:38, Start the BmtMDProviderMain with pid 3392.
15:34:38, Start the BIBusTKServerMain with pid 576.

GW Config
Dispatcher URIs for Gateway = http://AT:9300/p2pd/servlet/dispatch/ext
Store symmetric key locally = False
Password under Certificate Authority settings set to same as CM
All saved and validated

IIS7
• Server node
o In ISAPI and CGI Restrictions, added cognosisapi, pointed to cognosisapi.dll in cgi-bin and allowed to execute
o In Authentication enabled Anonymous Authentication (for now)
o In WebDAV Authoring Rules, allowed all users read only to everything
• Application Pools
o Created an Application Pool called Cognos8 and set to allow 32 bit applications.
• Set virtual directory Cognos 8 = c8_location/webcontent (Read)
o Configured samples folder for directory browsing
o Configured pat/images folder to not expire for 90 days
• Set application cgi-bin = c8_location/cgi-bin (execute)
o Allow execute
o Assign Cognos8 Application Pool to this folder
• Set virtual directory help = c8_location /webcontent/documentation

Now the actual error message refers to an unknown service name called cognos8. Is this referring to the actual Cognos Service that is registered with Windows? All services are named as default (IBM Cognos 8 ) why or how is it looking for Cognos8??

Think that’s everything! :smiley: Can anyone help??

Wow! This has been bugging me for days and I’ve just cracked it 8)

For the benefit of anyone who might stumble across similar issues, the problem was in IIS7 (which is a pain imo compared to IIS6). Anyways, I had configured everything correctly EXCEPT I forgot to amend the config file. The best instructions I’ve found for configuring IIS7 so far are here.

The bit I failed to do was amend the config file in order to add the allowPathInfo=‘true’ switch (which actually should be allowPathInfo=“true”) so added that and it all worked ;D

I’ve also removed the full file location…ehat I’ve experienced so far with IIS7 is when you come to set up cognosisapi.dll in Handler Mappings under cgi-bin, it suggests that the “Executable” field is optional BUT you cannot close the window without putting something in the field ??? so I simply add a path to it then remove it again when I manually amend the config file. Don’t know if anyone has found a better way to do this…

Still, thanks if anyone has been looking into this, but everything seems to be ok for now…until I start adding to the configuration again no doubt!!

funny,

i used the same steps for my installation a few days ago with IIS7 :smiley: I had to edit the config file as well to add the cognosisapi.dll.

Keep in mind for the new installations that cognos.cgi is running on a 32 and 64 bit server but isapi is made for 32 bit. There is a best practice document for IIS6 64 bit and isapi, but i have not seen it for IIS7, yet… :-[