Hi all, could do with some opinions on this.
We are running C8 against a SQL 2000 database.
Recently we have begun to receive error messages intermittently with the following error code whenever we attempt to run or validate reports.
UDA-SQL-0564 [Microsoft OLE DB Provider for SQL Server]Connection failure (SQLSTATE=08S01, SQLERRORCODE=0)
I have serveral other SQL database that exist within the Same SQL instance and I have no issues with these and can quite happily run reports against them.
I can test a connection to all our of my sql databases with success so I'm now stuck as to where to go.
Cognos KB doc 1031255.1 claims that its a network issue, but my infrastructure department claim its Cognos causing the issue.
Any Ideas???? ???
Perhaps you are running out of DB connections or TCPIP ports.
I'm seeing the same issue, did you ever find the cause?
Thanks!
We are seeing the same issue, Please post the root cause or solution if you find any.
Thanks!
Rashid
I have been working on this issue with cognos support for months and we have yet to solve the issue. Our next step will be to increase the emphemeral TCP port range on the cognos server so we'll see. this is a smaller deployment so i don't know how this could be the issue?
I'll let you know if this is indeed the cause.
We have made the changes to the server registry for SYN Attack protection as described in scenario 2 in this Cognos KB doc 1031255.2. We will verify and update if we have any luck resolving this issue.
Rashid
SYN Attack protection is not even listed in our registry...
Had this same error, it was as simple as setting the properties of the SQL Syntax to Pass-Through instead of Native. Hope this helps someone, I tried everything else for about 2 hours until stumbling across my simple error.
I had this error when when we had Content store was taken offline abruptly aand then restored.
Got the Cognos service restarted and that resolved the issue.
If this is a SQL Server issue, you might find something in your SQL Server logs giving more details.... i.e. 'the connection was refused because I ran out of ports'
Quote from: cognosjon on 17 Sep 2007 10:12:18 AM
Hi all, could do with some opinions on this.
We are running C8 against a SQL 2000 database.
Recently we have begun to receive error messages intermittently with the following error code whenever we attempt to run or validate reports.
UDA-SQL-0564 [Microsoft OLE DB Provider for SQL Server]Connection failure (SQLSTATE=08S01, SQLERRORCODE=0)
I have serveral other SQL database that exist within the Same SQL instance and I have no issues with these and can quite happily run reports against them.
I can test a connection to all our of my sql databases with success so I'm now stuck as to where to go.
Cognos KB doc 1031255.1 claims that its a network issue, but my infrastructure department claim its Cognos causing the issue.
Any Ideas???? ???
Look at the SQL Server articles from Microsoft on how to trouble shoot connectivity issues using this topic:
The Connectivity Ring Buffer is on by default, and by default traces all server-initiated connection closures. If you experience an error on the client but see no entry in the ring buffer, this means that the server has seen a connection closure (reset) similar to normal connection closure from the client, or an erratic one coming from outside the server; for instance, from a malfunctioning piece of networking hardware. If this is the case, you should focus on potential networking issues. If you see an entry in the ring buffer, then it will contain information about why the server decided to close this connection, and it will hopefully be enough to facilitate further troubleshooting. For example, if you see that a connection is closed due to invalid information in the TDS packet, you can investigate for faulty network cards, routers and switches which might have corrupted the data. As you will see below, by using a trace flag you can enable
Hello,
Did you solved your problem? because I have the same notification and I don't undersand why I meet this problem.
I need to restart cognos service each 2 hours... thank you for your help!!!
I suggest you go through all of the helpful advice that is already on this thread. At least look at your SQL Server logs. If you have a DBA get him on the case.