Hi all,
my first post to the forums so I'm hoping this proves a useful place to exchange knowledge!
My problem is that I have a bunch of existing Publish Datastore Containers that I can see in the CAC when looking at the View Publish Containers list. I have tried to choose an existing container to connect to in order as to run a view publish.
As I would expect, I have clicked on the chosen container and clicked OK. - Nothing happens. The container does not appear to connect. I can tell this because the Publish Datastore name should now show the container in the suffix but it is'nt.
Thing is, I can connect to some of the existing containers when trying them randomly - BUT not all of them and more specifically the container I want to connect to. Why is this?
I can also configure a new container but in this instance I want to connect to an existing container.
I wondered about deleting the existing container, then recreating it and connecting to it but suspect that will cause more issues than it will fix, like all the ODBC connected D-Links in Analyst!
Any ideas??
Hi
An issue we had. It may or may not be relevant to you.
We use Cognos Planning 8.1. The default connection string/method used by Contributor is SQLOLEDB. This on the advice of Cognos was changed to SQLNCLI, (native client connectivity) to get round a bug in 8.1. When the connection was set as this we were unable to reconnect/attach publish containers. We would get the model name and then no publish container name. Resetting the Contributor connection string to SQLOLEDB temporarily got round the problem.
Regards
Stuart
Thanks Stuart.
Looks promising given it is an 8.1 environment with SQL database.
I have no direct access to the db and as I am new in my role I have to hunt about for the correct contact but will post an update if this does indeed fix the problem.
I tried "tricking" Cognos by connecting to SQLNCLI but still cannot connect to the container I see available in the list of available View Publsih Containers.
So I tried re-connecting to SQLOLEDB and doing the same. Again no luck!
I tried variants of the above, such as connecting to SQLNCLI and then back to SQLOLEDB and vice versa - no luck.
So I have a container that is clear for all to see but cannot connect to it. What is going on here ???
Sorry to hear this didnt fix it.
tbh I would log a call with Cognos and ask them to help. This sounds like a non normal problem and they have access to internal documents and fixes.
Sorry I can help further
Stuart
thanks for trying!