Error: Database Connector Error: ' [Database Vendor Code: 9

dsweise · Forum Member Joined: 03 Dec 2007 Posts: 1

We need some help and I'm hoping someone here can shed some light on an issue we are having.

We are running BO XI Release 2 as our Enterprise server and are connecting to it from Remedy AR System - Web Client to run "canned" reports against our Oracle Database. All of the reports have run in the past. We have cloned our environment and are now trying to connect the clone and run the reports.

Some of them run and others give the error:
Database Connector Error: ' [Database Vendor Code: 9055 ]' Failed to retrieve data from the database.

This is after the parameter screen appears and it is generating the report in the Windows\Temp directory on the BO Server.

We have Tomcat installed and running as well as IIS on the server.

We are using an Oracle ODBC driver to connect to the database. We have verified this several times.

Any help or guidance would be greatly appreciated.

dsweise

Pagoon · Forum Member Joined: 04 Dec 2007 Posts: 2

I'm also receiving this error, and haven't found a solution.

I'm creating a new report using Crystal Reports Pro v11. I've set up a parameter to query the assigned_group field for filtering purposes. When the report runs, I receive the 9055 error. I also have some reports that have "broke" with this same scenerio. There were two changes made during the time this error occurred. We switched from sql 2000 to sql 2005 server, and I upgraded my CP client through a routine patch. Our Remedy 7.01 server hasn't been upgraded to the latest patch.

Faudge · Forum Member Joined: 14 Jan 2008 Posts: 1

Hi,

We had the same Error with Crystal Reports XI.

We solved it, with 2 actions :

- add the form, which uses for the report, on an application,
=> I'm not sure that it is necessary ...

- check rights on the form (Public hidden for the form) and rights on all fields
=> on my case, I add Change permission to Public group on Field of Id 1

and it works

Cédric

Sorry for my english, i hope it's understandable...

Pagoon · Forum Member Joined: 04 Dec 2007 Posts: 2

Thanks for the response. I tried your suggestion, and this didn't work for me. I have a feeling it's a setting on the ARSystem server or the SQL DB. The only work around I've found is to use non-dynamic field selections in the report.

dwmac · Forum Member Joined: 19 Feb 2008 Posts: 1

Another datapoint for this discussion:
ARS 7.1.01 on 2003 Server
MS-SQL2005 on 2003 Server, separate platform
Crystal Pro XI
Following transactions conducted with user tool:

On XP client--'tickets for date range'-type reports work CORRECTLY.
On Vista client--same reports generate the subject ERROR.

Additional data for these observations :
-same Remedy loginID
- same AR Server
- ODBC driver for AR Server is same on both clients

SQL ODBC driver is 2000.85.1117.00 on XP (working)
and 6.00.6000.16386 on Vista (error)

So--at least by my observation--we may have an OS/driver issue.

Don McClure
University of North Texas

sbaumann · Forum Member Joined: 15 Mar 2008 Posts: 1

I just ran into this same error at a client. The reports run fine in the User tool, but not on the web. We discovered that if you allow unqualified queries, the reports work on the web. We have escalated to BMC and it turns out they were already aware of this and are working on a fix.