Progress DB reports won't schedule

[dukeslater]

From archived thread 782-1164845:

"paulmarr (Instructor) 13 Dec 05 18:04
Hi everyone,

Perhaps someone could point me in the right direction. We are using CR v10 and CE10.

We have created reports against a Progress Database using the MERANT 3.60 32-BIT Progress SQL92 v9.1D ODBC driver that is installed with the client app to this database.

The reports run fine in Crystal Reports - but when I publish to CE10 they return the error "The database logon information is either incorrect or incomplete....".

I can verify that the logon information in the CMC is correct and I have also successfully ran the reports on the report server that hosts CE10.

Where else can I look? What else might be occurring? It has stumped me.

Thanks in advance for any words of wisdom.

cheers

paulmarr"

Was there any resolution found for this issue? I'm having the same problem with BOE XI, reports run fine within CR on the server but won't schedule properly. Other ODBC based reports (not Progress) schedule fine.

Thanks,

John

 

[synapsevampire]

How does "I'm having the same problem with BOE XI, reports run fine within CR on the server but won't schedule properly" differ from scheduling the reports, can you be specific about how you ran them?

Does not scheduling properly mean that they return an error, provide the wrong data, or?

Can you just run them in BOE XI, is it only when scheduled?

The first thought is always that the database settigns aren't correct, but I need to know specifically what isn't working means.

-k

 

[Turkbear]

Hi,
Is the ODBC DSN on the server a System,User or File one?

Does the Job Server run under an account that has full access rights to both the datasource and the ODBC DSNs?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[dukeslater]

Job and page servers run under domain admin account; others run under local system account.

What I mean is that I can refresh data against the Progress system dsn within Crystal Reports on the Enterprise server with no problem. If I schedule them via the CMC or Infoview it fails with "The database logon information is either incorrect or incomplete....". If I run ODBC tracing I get the additional, but not very useful, message: "Specified driver could not be loaded due to system error 126". I've rebuilt the ODBC layer so there are no dll conflicts.

Let me know what else I need to include.

Thanks.

 

[Turkbear]

Hi,
That seems to indicate a permissions issue:
That you can run them from the server means that your account can do it..
That you cannot run them from the CMC, means that one or more or the Crystal server accounts cannot.

Try using your account or a domain admin account on all the servers - except the CMS maybe..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[mwake]

I have the exact same problem. We are using Merant 3.70 32 Bit Progress drivers and I get the same error messages you are getting. Please post the solution to this problem if you figure it out!!

Thanks,

Mark

 

[dukeslater]

Steps tried so far:

Verified that the database password is stored within the report object in Crystal Server.
Verified that the reports will process properly within the Crystal Reports designer on the Crystal Server.
Verified that the job and page servers are running under a domain account with adequate permissions.
Rebuilt the ODBC layer and verified that there are no duplicate dll’s.
Ran SQLConn and got connectivity.
Ran ODBC tracing and found the “…error 126” message. I did not see any evidence in the trace log of a username/password being passed to the database.
BO knowledge base article c2005338 deals with the error 126 message. I modified the system path variable to include the DTS/bin directory.
I opened a ticket with Progress support for the general problem, and specifically to get a listing of all dependent dll’s that might not be in a defined system path.
I opened a ticket with BO for the general problem.

I'm definitely open to suggestions and I'll definitely be interested in what paulmarr did to solve the problem, if he actually did solve it. mwake, I'll be sure to post any solution here and you do the same...

Thanks.

 

[ryber2]

Not sure if this applies to your problems or not, but it seems to me. I was having nearly identical problems with ASP as SQL with the MERANT 3.6 driver. In my case the ODBC drivers were pointing to a mapped network drive. I could run pages locally, and run querys locally but not off the server (remotely) and would get the error 126. I copied the /prgs61d/bin folder into the local drive, then edited the registry for the drivers to look at that location. It seems the user permissions are not passed to mapped directories. All of my programs are now working perfectly. Probably not the most elegant solution, but it worked for me.

 

[paulmarr]

Sorry Dukeslater

Had a hard time finding your thread - we solved the problem by creating a MS-SQL database with the same db structure and using a pseudo ETL process - filled the SQL database with the data from the Progress database. This happens nightly and the MS-SQL database works superbly.

I would now run away as fast as I could any product that uses the Progress database!

Cheers
paulmarr