Actuate Error

[Anon Anon]

Hi,

I've got the error while trying to start the report from Clarity "Reports and Jobs". Have anyone come across this type of error. If so please advise on what action I should take.

ERROR 2011-05-12 06:15:46,521 [http-80-Processor7] niku.reporting (spalan01:61403426__56e74ec:nmc.executeAvailReport) SOAP Exception : <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns="http://schemas.actuate.com/actuate8">
<ConnectionHandle>u7whmBpUho+tg5MUYUgZxqV+rbtKHLkAq7RmnwSbegyRYEMWxKR8m0pEgUAaXCZHB8OCTIkAq4w2j+egY1xYCBtEJl8Pwbl1UThjBDaOZQnYtpujYrQGv50Do1QhQBnEnkeNA6qEMYj5</ConnectionHandle>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ACTU:ExecuteReportResponse
xmlns="http://schemas.actuate.com/actuate8" xmlns:ACTU="http://schemas.actuate.com/actuate8">
<Status>Failed</Status>
<ErrorDescription>Status No: 1 :
Basic Error: 1011
Module: afc\db.bas
Line: 193

Database Error
3: Database login failed.
6: [SQL State] 08001: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
[SQL State] 08001: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.01000: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
[SQL State] 08001: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.01000: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).IM006: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
</ErrorDescription>
<ConnectionHandle>u7whmBpUho+tg5MUYUgZxqV+rbtKHLkAq7RmnwSbegyRYEMWxKR8m0pEgUAaXCZHB8OCTIkAq4w2j+egY1xYCBtEJl8Pwbl1UThjBDaOZQnYtpujYrQGv50Do1QhQBnEnkeNA6qEMYj5</ConnectionHandle>
</ACTU:ExecuteReportResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

[Anon Anon]

Might be stating the obvious, but that just looks like your Actuate system has not got the right database connection setup!

Have you checked all the settings in the NSA (in the Reporting setup tab).

[Deactivated User]

Is that the only report that gives the error?
Is the ODBC connection OK?

Martti K.

[Anon Anon]

No all the reports give the same type of error.

I checked the ODBC connection they are fine.

[Anon Anon]

Hello,

You need to check two things.

First check the port no
And also niku password.

Thanks,

Arun Mohan

[Anon Anon]

Sorry the adminstrator password

[Anon Anon]

Try reinstalling the reports from NSA. Go to install and upgrade-Reports-reinstall.

Thanks,

Arun Mohan

[Anon Anon]

Hello Sreeram,

Try to create a user in actuate and configure that user in NSA and after that reinstall reports from NSA.

Thanks,

Arun Mohan

[Anon Anon]

If I reinstall the reports , will my predefined reports will get remain as such ? I don't have rights to create a user in DB. Its like this, I'm trying to edit on the existing reports for which I'm currently supporting. So I couldn't connect to db using the report designer tool. I tried through clarity, it threw this error.

[Anon Anon]

Hey you can reinstall the reports in NSA and there is no problem in it. And check whether it is getting installed properly from NSA

[Anon Anon]

I reinstalled ..the logs are as follows

5/12/11 9:03 AM (admin) Installing reports...
5/12/11 9:03 AM (admin) Activating vendor-specific report definitions...
5/12/11 9:03 AM (admin) Reports Installation Complete


When I ran the reports from Clarity, the same error


Thanks

[Anon Anon]

Do you have actuate 8 with you? Try to run the actuate report locally.

Thanks,

Arun

[Anon Anon]

It worked..It was the ODBC problem .thanks for the advise.

Cheers
Sreeram

[Anon Anon]

Hellol!

How do I test if my ODBC within my setup is OK? I'm having just the same issue and I don't know where to look at. Which file do I need to modify? Thanks!!

[Anon Anon]

Hello,

How do you test the ODBC connection??? I'm having the same issue after installing another Oracle Client.....I don't know where to look. Which file?? Please, let me know.

sreeram.babu wrote:

It worked..It was the ODBC problem .thanks for the advise.

Cheers
Sreeram

[Deactivated User]

If you are using oracle with actuate you are not using ODBC but Actuate direct connection drivers to Oracle.
When you installed new Oracle client does that support the same version as Actuate Oracle connection drivers?
Did you make the client set up the same way as it was before.
Can you access Oracle with any tool from the server where Actuate is installed?

Marttti K.

[Anon Anon]

When you installed new Oracle client does that support the same version as Actuate Oracle connection drivers?
A: No, it doesn't support the connection drivers....that's why I want to use the older one (version 10). Our DBA installed Oracle client version 11.

Did you make the client set up the same way as it was before.
A: I believe our DBA set it up the same way....

Can you access Oracle with any tool from the server where Actuate is installed?
A: Are you referring a SQLPLUS?....

another_martink wrote:

If you are using oracle with actuate you are not using ODBC but Actuate direct connection drivers to Oracle.
When you installed new Oracle client does that support the same version as Actuate Oracle connection drivers?
Did you make the client set up the same way as it was before.
Can you access Oracle with any tool from the server where Actuate is installed?

Marttti K.

[Deactivated User]

When looking at my iServer 9 the highest Oracle driver is acorcl90.dll which is for Oracle 9
If your s is the same then you Oracle Client has to be downward compatible with Oracle 9 so that the rapports should work without problems.

The tnsnames.ora should specify your Oracle for Actuate.
If you can access it with SQLPlus from the server where Actuate is the the connection is OK, but the version compatibility may not be if you can't run reports.


Martti K.

[Anon Anon]

Thanks another_martink,

Our reports were running fine, the problem began when we tried to install a higher oracle client version from 9 to 10...

Our last resort is to extract a current working environment image and apply it to this new environment to override anything the installation of the newer oracle client did.

We think this will solve the issue to apply an untouched version......

javascript:;:sad

[Deactivated User]

I hear what you are saying.

My understanding is that the Actuate reports have version specific connection to Oracle.
That is specific to the Oracle client. There is slightly more leeway with the backend database.
A couple of direct connectors to Oracle come with Actuate and the reports normally use those.

If there is no match with the versions connector support and the Oracle client then there is the option to modify the report design files (.rod) and to generate new report executables (.rox) from them and to deploy them over the existing ones.

That is if you do not want to move to BO (on the outset that your Clarity version support BO)

Martti K.

[Anon Anon]

We tried modifying a report in Actuate Designer and compiled it a new one. We installed it and test it out and the same error....

we've spent to many days dealing with this and without any clue, at all.

the big issue here is that we are dealing with this old, old, old version.
Actuate 8
Clarity 8.1
Database 9i

..but it was required to upgrade our database to 11g....but certain errors appears from Clarity..so we decided to upgrade the Oracle Client from 9 to at least 10G.......

BO is not supported for our Clarity version......we need to upgrade rushhhhh.

Thanks a lot for your attention and help!! I really appreciate it!

:grin:

[Deactivated User]

If you can connect with If you can access it with SQLPlus then the connection is OK.
If you have eRDpro then that is good.

If you want to try further

May I suggest that you create an ODBC data source to Oracle and confirm that it works.
Then create the simplest report you can using that ODBC data source and see if that displays data when run in eRDpro and from the Actuate management console.
If it does then that is an option.
I take that now the reports don't work in eRDpro or from the MActuate Management console either.

Martti K.

[Anon Anon]

I tried to connect to http://vmtestcty1.7-11t.com:8000/ , it didn't work.

Please see the screen shot , Do I need to change anything or check anything

thanks

Sreeram

[Deactivated User]

As proposed before login into Actuate and run the reports there.
Is the Administrator the actuate user you created or is that the user ID to run the Actuate service?
Does the ODBC connect pass the test?

Martti K.