Database DLL problem and/or looping logon

[lyanch]

Hello all,

This is a problem that I am currently working on with Crystal Support but was hoping someone here might have some insight.

I am trying to publish some new reports going to a different database. The database is Oracle 9i and I have the same problem with all of them.

The reports run fine from the server logging on as the same user that the services run under.

When I try to open the reports from eportfolio I get the following error:

Error detected on database DLL. [On Page Server: COAPPS1.pageserver]

Sometimes I will get the following error first (it only happens the first time I try to run a report, but sometimes I only get the previous error)

Error in File D:\Program
Files\Segate\Software\WCS\Data\COAPPS1.pageserver\temp\procReportTemp\mgrT
emp\ps_96127e365ced443f.rpt:
Unable to connect: incorrect log on parameters. [On Page Server:
COAPPS1.pageserver]

I have verified the database, etc. And am currently testing with a single table report that brings back 7 records for one field (to eliminate any "complicated" report issues).

When I shut down the pageserver, and start it as an application instead of a service, I get the looping logon problem. Hey... I though running it as an app was supposed to help you get RID of the looping login problem!

I currently run reports off of several Sybase and SQL databases with no problems. The first time this has cropped up is with Oracle.

One note, we also have some Enterprise logon issues because of the server being a BDC. I don't think this has anything to do with it... but you just never know.

Any ideas?

Thanks in advance

Lisa

 

[synapsevampire]

I just had this problem today, which was caused because of a new Oracle 9i client install, without having thoroughly nuked the old 8i client beforehand.

If this matches your scenario, I semi-resolved by:

First I renamed the old orahome80 folder under the Oracle folder to orahome80 old.

This made the reports start working.

I decided to reinstall and clean up...killing the c:\oracle directory, I then searched for oracle in the registry and obliterated anything that even *might* have had anything to do with an Oracle client.

Everything is happy and running smoothly.

Hopefully yours is something simple like this, it's a very annoying, and useless error message...

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[lyanch]

Thanks for the suggestion... I had the server admin do exactly this today (per your suggestions). No such luck. I am beginning to suspect this has something to do with our general problems due to the Enterprise server also being a BDC. I am going to have the guys that are working on that problem check this one as well.

Lisa

 

[synapsevampire]

I doubt that it hs anything to do with it also being a BDC, more likely it's because it also functions as a Oracle 8 client for another application or if there is a residual or current oracle 8 file in the path or registry that 9i might try to use. Someone else had a similar problem and they resolved by finding some old 8 files in the Windows or System folder.

But...I'm sure there are other culprit.

I 've had CE 8.5 running on 9i now for a few days without a hiccup, so it can work...

Good luck.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com