I have a very old report developed and deployed many years ago (during pilot stage of BOE).
Right now this report does not work in Infoview. Fails with error: Error in File report_name : Database Connector Error
I went to CMC, check connection parameters - everything is fine. Retyped them several times - no luck.
Next, I downloaded report from repository to my workstation, and run it in CR with the same credentials as I use in BOE - not a single problem.
Saved that report back to BOE with a new name, went to CMC set up connector parameters - and again: Database Connector Error.
All other reports on the same server, with the same connection parameters are working fine.
Any ideas how to fix this old report?
No, I do not have CR on the server itself. Usually, to keep editor on server is considered as redundant…
ODBC DSN is the same as in other reports. All connection parameters which I see in CMC are the same. Same DSN, same database, user id, password. But all reports works except for this old one.
Ok, I’ll try that. But right now I do not have access to web-server which hosts BOE, so I am unable to do this…
“Verify database” went smoothly, but no luck in Infoview. Still the same “Database Connector Error”. In CR it still works fine.
Is there any way to ask BOE to show full error stack in Infoline, not just the ‘Connector Error’? I’d like to know what was the exact database server response, it would be much easier to understand the source of the problem.
Can not do this. First of all there is no OLDEB drivers on the server. Second - why report which I made yesterday works fine on BOE with exactly the same connection parameters?
I guess, the only way to fix this nasty problem is to redraw this report from scratch.
The point of OLEDB is that you don’t need drivers on the servers. OLEDB is an embedded connection. The nice thing about using OLEDB is that it makes the report portable because you don’t need drivers installed on each machine capable of running the report.
Sounds like you are having connection issues so trying an alternate connection method could help you determine where the problem is. If you have the same error with OLEDB then there is something else going on.
If Business View, Goto Business view manager and Edit the Dataconnection.(Do it Completely from Scratch). But dont change the Name of the Dataconnection. and Save it. you will be prompted to change the Business View’s. Clicke Yes.
I found this thread while researching the same error message.
With OLEDB you do need drivers on the server, but you don’t need DSNs - the connection info is embedded in the report. The same can be accomplished with an ODBC connection string, but those can be more complicated for report developers to consistently construct (and haven’t reliably worked for us). We encourage the use of OLEDB connections because of the handy wizard(s) and not needing to maintain DSNs on the servers.
We found a solution to our current occurence of the “database connector error” - the report was based on a stored procedure that in turn called two more stored procedures (MS SQL Server). The developer could run the report on her workstation (with her credentials), but when the report was run in BOE with service account credentials, we got the aforementioned error. In troubleshooting, we attempted to run the SP with the service account credentials and got a “execute permission denied error” on one of the underlying SPs - the developer resolved that. We tested in BOE again and got the same error - back to test in the DB we got the same error on the other underlying SP - the parent SP was pointing to the underlying SPs in a different environment (development) where the SA didn’t have permissions. Lessons learned :
the BO error messages can be misleading
be persistent in testing on the DB side with the credentials that will be used to actually run the report
(BOB member since 2006-02-08)
(BOB member since 2008-05-22)
(BOB member since 2008-05-22)