Home
Follow us on Twitter
first
  
last
 
 
start
stop


Countries

49.2%United States United States
7.4%India India
6.9%United Kingdom United Kingdom
5.2%Australia Australia
5.1%Canada Canada

Visitors

Today: 405
Yesterday: 323
This Week: 728
Last Week: 2855
This Month: 6809
Last Month: 12906
Total: 553689


MSAS SSAS 2008 64 bit issue with Cgnos BI server PDF Print E-mail
(1 vote, average 4.00 out of 5)
Written by Roger   

Product:

Cognos BI 10.1.1
Windows 2008 R2 server
MSAS SSAS 2008

Symptom:
You have created a data source to a SSAS 2008 cube, and test it in Cognos connection.
It works for CQM but you get a error for DQM.

Error message:
http://sr01634:9300/p2pd  Microsoft Analysis Services 2008 / Compatible  Succeeded

http://sr01634:9300/p2pd  Microsoft Analysis Services 2008 / Dynamic  XOD-CON-0001 Failed to connect to OLE DB for the provider (Microsoft Analysis Services 2008) and server (sr01868): ERROR [category=ASSERTION,statusCode=0,causeCode=0,source=CODBOConnection::UpdateConnectionProperties(CNativeEnv&) at Java_com_cognos_xqe_data_providers_olap_odbo_ODBOConnection_cUpdateConnectionProperties]: CCLAssertError: CCL_ASSERT(NULL != m_pIDBInitialize);

Cause:
The DQM report service is 64 bit JAVA program and need the 64 bit version of the driver to be installed on the Cognos BI server.

In control panels add/remove programs the driver is listed as
111 MB version 10.50.1600.1    (the working version)
or
77,5 MB version 10.52.4000.0   (not working version)


Possible Solution:
Download the x64 version of Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server® 2008 R2 from site http://www.microsoft.com/en-us/download/details.aspx?id=16978

File size is 55526 KB for SQLSERVER2008_ASOLEDB10.msi file 64 bit version.

Install the driver on the Cognos BI server and test the connection again.

Connection string:
;LOCAL;M8;SERVER=sr01868;Trusted_Connection=yes;LCID=en

www.cogknowhow.com

 
When working in Excel with Cognos Controller link you get an error message PDF Print E-mail
(1 vote, average 4.00 out of 5)
Product:
Cognos Controller 10
Excel Link
Windows 2003 Server
Citrix Server

Symptom:
When working in Excel with Cognos Controller link you get an error message.

Error message:
Standard Error
Number: 7
Source: mscorlib
Description: Execption of type ‘System.outOfMemoryException’ was thrown.
At System.IO.MemoryStream.set_Capacity(Int32 value)
At System.IO.MemoryStream.EnsureCapacity(Int32 value)
At System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
Xxx


Solution:
The Windows check if there is memory free that the application can use, and at this moment there is not enough memory free on client computer/terminal server, so this error is sent from the Windows Operation system, to not allow the program to access the memory.

In the case of Excel reports, consider to make them smaller with less amount of formulas.
Also ensure the client/Citrix server have enough memory.
At least do you need 8 GB of ram on a Citrix server, which should handle a few Cognos Controller users.

Run the same excel sheet on a computer/server with a lot of memory and see if the problem is gone.

www.cogknowhow.com

 

 

 

 
How to apply fix packs for Cognos PDF Print E-mail
(1 vote, average 5.00 out of 5)

 

Problem:

which steps are required to install fix packs on an existing IBM Cognos installation.

Solution:
Since fix packs involves modified binaries, they need to be linked and working all in conjunction with each other. You cannot have a different versions of binaries working together perfectly.
That's why cmplst.txt file is there in every IBM Cognos installation to make everything work in sync with version.
NOTE: Before you start applying any fix pack make a backup of the repository database (content store) first!

If you have a IBM Cognos deployment working on (default) servlet container like apache tomcat, all you need to do is:

1. Stop IBM Cognos service.
2. Apply fix pack installables.
3. Start IBM Cognos service and you'll be done.


If you are running IBM Cognos on an application server like IBM Websphere or JBoss etc, the steps are little different:

1. Stop IBM Cognos service.
2. Apply fix pack installables.
3. Rebuild the ear/war files.
4. Redeploy the ear/war file.
5. Start IBM Cognos service.


www.cogknowhow.com

 

 
Cannot send mail from inside Cognos Controller client PDF Print E-mail
(1 vote, average 5.00 out of 5)
Written by Roger   

Product:

Cognos Controller 10.1.1
Windows 2008 server

Symptom:
Can not send mail from inside Cognos Controller client

Error message:
Email server reported an error, some or all messages could not be sent. Please check with your local administrator that the email server is operational and that the system configuration is correct (connection details can be found in details and or log file).

java.lang.NullPointerException
com.ibm.cognos.ccr.configproperty.EmailSettings.fromURI(EmailSettings.java:70)
...

Cause:
The value for General Configuration - Server Preferences are not filled in for
variable name: C4_EMAIL_SERVER
variable value: mailrelay.domain.se:25

http://pic.dhe.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.ctrl_ug.10.1.1.doc%2Fc_syparlist.html

Solution:
Start Cognos Controller client
Log in as administrator
Go to Maintain - General Configuration - Server Preferences
Add new variable name C4_EMAIL_SERVER
Add new variable value to your mail server name (FQDN) and include the port number (:25)
Click Save.
All users need to log off Cognos controller to make the change take affect.

Above is for the new dialog boxes in Cognos controller like Group - Command Center.
Where after you have listed the status for a group/company's on the right side have a icon to send notification email.
To get this to work, the user you logged in with to Cognos Controller must have a valid email address added to its user account information in Cognos controller.

To add email address to user in Cognos Controller client, go to
Maintain - Rights - Users dialog
Click on the user in the list on left side, and add a email address on the right side for the user.
The email address must be allowed by the company email server to send email, often a address that exist inside the company.

If the sending users email address is wrong, you get a error message like this:
Unable to proceed, please address errors listed below.
Cannot send without email address for sender (ADM). Please check system configuration.
...


The mail setting inside Maintain - Configuration - General Configuration
tab general 3 is for all the old mail functions in old controller dialogs.
Here you should also specify the mail server at SMTP server line:
mailrelay.company.se
and select the email format you want to use, recommend CSV.

To test this you can go to Transfer - Export Structures.
Mark E-mail and enter an email address to receive the mail on the line at the right.
Mark what to send, for example Country Structure.
Click RUN icon.
Click CLOSE on message that temp file is created.
Enter the message text and click OK to send the email.

You need to logout from Cognos Controller client, to make any changes take affect from the General Configuration dialog.

www.cogknowhow.com

 
Cognos Controller client give an error when running a standard report PDF Print E-mail
Written by Roger   

Product:
IBM Cognos Controller 10.1.1
Windows 2008 R2

Symptom:
When you run a standard report in Cognos Controller client program you get a error.

User Rights and Security Group Reports:
<Message Name="CCLMessage" File="qemsgs" Severity="Error" Nesting="0" ><MessageComponents ID="0x35d88fc3" ><MessageParms><MessageParm Name="CCLMessageParm" Type="string" Value="SQLOLEDB.1:WIN2008:controllerlive:cognos" /></MessageParms></MessageComponents></Message>

Details
RSV-SRV-0042 Spåra bakåt:RSReportService.cpp(722): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(263): QFException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_RequestRSASyncExecutionThread.cpp(808): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(260): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): asynchRunSpecification_RequestRSASyncExecutionThread.cpp(864): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRunSpecification_RequestExecution/RSRenderExecution.cpp(670): QFException: CCL_RETHROW: RSRenderExecution::executeAssembly/RSDocAssemblyDispatch.cpp(291): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSLayoutAssembly.cpp(79): QFException: CCL_RETHROW: RSLayoutAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSReportPagesAssembly.cpp(179): QFException: CCL_RETHROW: RSReportPagesAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSPageSetAssembly.cpp(462): QFException: CCL_RETHROW: RSPageSetAssembly::assembleAssembly/RSAssembly.cpp(662): QFException: CCL_RETHROW: RSAssembly::createListIteratorAssembly/RSAssembly.cpp(717): QFException: CCL_RETHROW: RSAssembly::createListIteratorRSQueryMgr.cpp(1055): QFException: CCL_RETHROW: RSQueryMgr::getListIteratorRSQueryMgr.cpp(1131): QFException: CCL_RETHROW: RSQueryMgr::getResultSetIteratorRSQueryMgr.cpp(1295): QFException: CCL_RETHROW: RSQueryMgr::createIteratorRSQueryMgr.cpp(1569): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgr.cpp(1559): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgrExecutionHandlerImpl.cpp(168): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()RSQueryMgrExecutionHandlerImpl.cpp(160): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()QFSSession.cpp(1147): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1145): QFException: CCL_CAUGHT: QFSSession::ProcessDoRequest()QFSSession.cpp(1102): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1078): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSConnection.cpp(788): QFException: CCL_RETHROW: QFSConnection::ExecuteQFSQuery.cpp(213): QFException: CCL_RETHROW: QFSQuery::Execute v2CoordinationQFSQuery.cpp(2024): QFException: CCL_RETHROW: QECoordinationQFSQuery.cpp(4350): QFException: CCL_RETHROW: CoordinationQFSQuery::CallProviderQFSQuery.cpp(246): QFException: CCL_RETHROW: QFSQuery::EXecute v3Source/RQP_QFSQuery.cpp(492): QFException: CCL_RETHROW: QESource/QE_RsApi.cpp(3604): QFException: CCL_RETHROW: QESource/AQEX_TabularQueryVisitor.cpp(333): QFException: CCL_RETHROW: QESource/QEI_ConnectionFault.cpp(985): QFException: CCL_THROW: QE


Cause:
You have not a data source connection inside Cognos Connection to your Cognos Controller database.

Solution:
Start Cognos Controller Configuration.
Go to Report Server dialog.
Click OK on any information messages.
Click on the green Check icon.
Click on the Repair button to update the Cognos Connection.

Start the Controller Client and test the report again.

You must be logged in to the Windows server with a user account that is System Administrator in Cognos Connection to make the Repair button work.

www.cogknowhow.com

 
«StartPrev123NextEnd»

 

CogKnowHow Newsletter

Newsletter
Please register to the site before you can sign for a list.
No account yet? Register
Banner

Polls

How many users are working on your Cognos environment?