If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Content manager unable to access content store

Started by tejas, 02 Jun 2014 03:04:03 AM

Previous topic - Next topic

tejas

Hello everyone,
The most common error that a newbie face in cognos configuration is that your content manager unable to connect to your content store. This may be because of following reasons.
1.   You are trying to connect by using the credential of user other than the user of the IBM cognos services. If you go to services and future to properties of IBM service u will see the correct user credential in Logon tab, but of course it is encrypted so you need to get correct credential from your administrator.
2.   Another problem that cause this situation is your content store is to able to connect to your sql server. For that you have to make following changes in SQL server configuration  manager:  To assign a TCP/IP port number to the SQL Server Database Engine In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for <instance name>, and then double-click TCP/IP.
In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure. If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.In the IPn Properties area box, in the TCP Port box, type the port number you want this IP address to listen on, and then click OK.In the console pane, click SQL Server Services.  In the details pane, right-click SQL Server (<instance name>) and then click Restart, to stop and restart SQL Server.
3.   Other factors that cause these errors are small things like enabling tcp connection , checking correct ports, enabling the ports, etc.
I hope this may help you to resolve your problem, please leave your comment or suggestion if any.