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

Unable to connect with FM to SQL server

Started by sschurin, 26 Oct 2009 08:41:47 AM

Previous topic - Next topic

sschurin

Hi all,

I have created a data source in Framework manager for a SQL server DB. I have used 'OLE DB' as type.
In the wizard I have chosen to use as 'Signon'  "An external namespace" because I want to connect with my Active Directory NT user.
While testing the connection, I get the message 'Succesfull', but after I close the wizard and I want to use my data source, I am surprised with the message:

QE-DEF-0314 An error occurred while calling the content store for the database: 'ANVA MI' information.
CCL-RCI-0002 The Soap server returned a Soap fault.
The error messages from WASP engine:
CM-REQ-4222 You do not have the permissions to access this data source.

Can anyone help me to resolve this issue?

Thanks in advance,
Steffen

NaviGator

Hello sschurin,

What about your SQL Server, Can you login using SQL authontication and Windows authntication ?

I think all your NT users have to be defined as logins in SQL server in order to be able to use them.

Thanks ..
Never Stop Learning ..

sschurin

Hi,

Thanks for your reply.

Yes, I have tested this and with 'SQL Server Management Studio', using Windows Authentication, I am able to connect succesfully.

I hope you have some more hints.

Regards, Steffen

NaviGator

As I told you .. All The users in your NT namespace, have to be defined as logins in SQL Server.
Never Stop Learning ..

sschurin

My NT-account is defined as login in SQL server; when I define the data source, the connection is succesfull (I use my NT-account to test the connection). But after closing the wizard, when I want to select tables from SQL server, I get the error-message...

sschurin

Problem solved!

It seems that my local Cognos FM installation was not correct because this problem did not occur on other PC's here..
I copied a few .ini files from the other PC's to my PC and now I have access to the tables.