Enterprise - error detected by database dll

[mchoss]

Crystal 8.5 developer
Crystal Enterprise 8
SQL Server 2000
Windows 2000 server

I have a report with a number of left outer joins and 2 subreports. It works fine through Crystal against a database on my development machine. It also works fine through an external Enterprise web server here in the office. However, when i publish the report on our client's web server, this report gives the following:

"Error encountered by Crystal Pageserver - Error detected by database DLL. [On Pageserver: 'servername' pageserver]"

The Pageserver log file has the following:

"Timestamp (Process ID, Thread ID), (Event Type, Category, Event ID), Information:
17:54:15 (5296, 5308), (1, 1, 33009), Info: assert failure (Y:\backend\jobserver\dlls\procreport\src\pagerequrl.cpp706). (0 : ).
Call Stack Dump: Not available"

Note: I have dialled up to the site and set the database location to 'their' database, and verified this location. This previews correctly through Crystal.

Any ideas?

PS - I am connecting directly to the database as i cannot get outer joins to work through the SQL odbc driver [the error presented states categorically that outer joins won't work]. Does any one know how to remedy this.

----------------------------------------------------------

if any one is interested the sql is:

SELECT DISTINCT
I_DETAILS.incno, I_DETAILS.incdate, I_DETAILS.stn, I_DETAILS.risk, I_DETAILS.location, I_DETAILS.comments, I_DETAILS.ss_life_risk, I_DETAILS.time_mobilisation, I_DETAILS.time_arrival, I_DETAILS.time_stop, I_DETAILS.time_last_return, I_DETAILS.time_failed, I_DETAILS.map_east, I_DETAILS.map_north, I_DETAILS.created_dt,
L_MAIN_TYPES.descr,
L_SUBTYPES.descr,
L_SS_TYPE.descr,
L_SS_SUBTYPE.descr,
L_CAUSE.descr,
L_EXTING_METHOD.descr,
L_CALL_METHOD.descr,
F_CLOSURE.incno, F_CLOSURE.room_of_orig, F_CLOSURE.reason, F_CLOSURE.other_reason, F_CLOSURE.fire_spread_info, F_CLOSURE.violence_crew, F_CLOSURE.violence_assailants, F_CLOSURE.violence_sex, F_CLOSURE.violence_physical, F_CLOSURE.violence_verbal, F_CLOSURE.violence_abuse, F_CLOSURE.container_skip, F_CLOSURE.container_refuse_bin, F_CLOSURE.container_wheelie_bin, F_CLOSURE.container_recycling_container, F_CLOSURE.container_quantity, F_CLOSURE.container_refuse, F_CLOSURE.container_open_ground, F_CLOSURE.container_fly_tipping, F_CLOSURE.container_household_waste, F_CLOSURE.container_other_quantity, F_CLOSURE.vehicle_make, F_CLOSURE.vehicle_model, F_CLOSURE.vehicle_reg, F_CLOSURE.vehicle_year, F_CLOSURE.vehicle_other_info, F_CLOSURE.fs_children, F_CLOSURE.fs_youth, F_CLOSURE.fs_adult, F_CLOSURE.fs_pensionable_age, F_CLOSURE.fs_oven, F_CLOSURE.fs_grill, F_CLOSURE.fs_ring, F_CLOSURE.fs_microwave, F_CLOSURE.fs_pan, F_CLOSURE.fs_frying_pan, F_CLOSURE.fs_chip_pan, F_CLOSURE.fs_fire_plan, F_CLOSURE.fs_plan_carried_out, F_CLOSURE.fs_plan_appropriate, F_CLOSURE.smoke_fitted, F_CLOSURE.smoke_mains, F_CLOSURE.smoke_battery, F_CLOSURE.smoke_working, F_CLOSURE.smoke_operate, F_CLOSURE.smoke_sited_suitable, F_CLOSURE.smoke_further_info, F_CLOSURE.smoke_attempt, F_CLOSURE.smoke_details, F_CLOSURE.brig_cas, F_CLOSURE.brig_res, F_CLOSURE.brig_fatal, F_CLOSURE.civ_cas, F_CLOSURE.civ_res, F_CLOSURE.civ_fatal, F_CLOSURE.signedoff_by, F_CLOSURE.numsmokedet, F_CLOSURE.numheatdet, F_CLOSURE.numfloors, F_CLOSURE.officerincharge,
L_UNWANTED.descr,
L_FA_TYPES.descr,
L_FS_PRIOR_FF.descr,
L_FS_OCCDETS.descr,
L_FAIL_OVERIDE.descr,
L_AFFECTED_AFA.descr,
L_UNWANTED_AFA.descr,
L_ALLEGED_EVENTS.descr,
L_FS_ROOM_OF_ORIG.descr
FROM
INCIDENT.dbo.I_DETAILS I_DETAILS,
INCIDENT.dbo.L_MAIN_TYPES L_MAIN_TYPES,
INCIDENT.dbo.L_SUBTYPES L_SUBTYPES,
INCIDENT.dbo.L_SS_TYPE L_SS_TYPE,
INCIDENT.dbo.L_SS_SUBTYPE L_SS_SUBTYPE,
INCIDENT.dbo.L_CAUSE L_CAUSE,
INCIDENT.dbo.L_EXTING_METHOD L_EXTING_METHOD,
INCIDENT.dbo.L_CALL_METHOD L_CALL_METHOD,
INCIDENT.dbo.F_CLOSURE F_CLOSURE,
INCIDENT.dbo.L_UNWANTED L_UNWANTED,
INCIDENT.dbo.L_FA_TYPES L_FA_TYPES,
INCIDENT.dbo.L_FS_PRIOR_FF L_FS_PRIOR_FF,
INCIDENT.dbo.L_FS_OCCDETS L_FS_OCCDETS,
INCIDENT.dbo.L_FAIL_OVERIDE L_FAIL_OVERIDE,
INCIDENT.dbo.L_AFFECTED_AFA L_AFFECTED_AFA,
INCIDENT.dbo.L_UNWANTED_AFA L_UNWANTED_AFA,
INCIDENT.dbo.L_ALLEGED_EVENTS L_ALLEGED_EVENTS,
INCIDENT.dbo.L_FS_ROOM_OF_ORIG L_FS_ROOM_OF_ORIG
WHERE
F_CLOSURE.incno = I_DETAILS.incno AND
I_DETAILS.main_type *= L_MAIN_TYPES.type AND
I_DETAILS.subtype *= L_SUBTYPES.code AND
I_DETAILS.ss_type *= L_SS_TYPE.code AND
I_DETAILS.ss_subtype *= L_SS_SUBTYPE.ss_code AND
I_DETAILS.cause *= L_CAUSE.code AND
I_DETAILS.exting_method *= L_EXTING_METHOD.code AND
I_DETAILS.call_method *= L_CALL_METHOD.code AND
F_CLOSURE.fail_overide *= L_FAIL_OVERIDE.code AND
F_CLOSURE.fs_details *= L_FS_OCCDETS.code AND
F_CLOSURE.fs_alleged_event *= L_ALLEGED_EVENTS.code AND
F_CLOSURE.fs_room_of_origin *= L_FS_ROOM_OF_ORIG.code AND
F_CLOSURE.fs_prior_ff *= L_FS_PRIOR_FF.code AND
F_CLOSURE.afa_building *= L_UNWANTED_AFA.code AND
F_CLOSURE.afa_affected *= L_AFFECTED_AFA.code AND
I_DETAILS.fa_app_code *= L_FA_TYPES.code AND
I_DETAILS.unwanted_code *= L_UNWANTED.code

 

[lyanch]

This is probably a permissions issue on the server. The "user" the page service runs on (usually a server admin account) must have all the access necessary to view the report.

To test, log onto the server using the same user the pageservice runs under. Open and run the report on the server. If you are having problems with permissions, you will probably get much better error messages that will point you in the right direction. My guess is that either the page service is running under localhost (not a good idea) or the user account that is using it can't find the ODBC or other connection you are using.

Lisa

 

[mchoss]

Hey Lisa,

Not entirely sure which users we are talking about here. Using the Crystal Enterprise Management Console, you can see that there is only really one account set up: 'Administrator' and this is in the Administrators group. How do i find out which user the Page service is running under?

In the Crystal Configuration Manager the service has the SystemAccount box checked and is running under the 'LocalSystem' account.

When logging on to the site via the eportfolio link, the 'Administrator' login is being used.

Basically, within the Enterprise system there seems to be only one user, and it is this user i am logging on with.

[Unfortunately i cannot 'open' the report directly on the server, if you mean through Crystal itself, as the client will not load crystal on to their production interface server]

 

[lyanch]

From the server, open the "Crystal Configuration Manager". This is a local to the server app and not a web based app.


Right click on the pageservice and select properties. There is a section that shows the user to log on as. In CE8 you can use local host, but things can get funky (like permissions to databases sometimes don't work right). I ran mine under an admin account.

If that user (or local host) does not have permission to use the connection (assuming ODBC) then the report will not run correctly. It is also possible that the ODBC is not set up correctly.

I didn't want to put CR on my production server either.. I ended up doing it anyway, it made troubleshooting so much simpler.


Lisa

 

[rknorc]

What if all of your other reports work fine.

Let me throw another kink in this.

I have a report that runs fine through the designer, but on the Web I get the error "Error detected by database DLL. [On PageServer: Servername.pageserver]".

However, when I click OK, the error dialog goes away and I can click through the pages of the reprt and see the data as if nothing ever happened. The only thing is, the nav shows 0 of 0+. As I click through it says 1 of 1+; 2 of 2+; etc.

Any ideas?

 

[mchoss]

If found that to avoid any problems i had to either use an external connection [ODBC] for all object/table references, or connect the report in design mode directly to the databases that the reports would be run against.

 

[rknorc]

We've done both and we still get that error.

This report uses sub-reports. Has anyone had issues with that?

Does anyone know what this error means?

Thanks - Rick

 

[mchoss]

The report i was running uses subreports and i also thought this might be causing an issue - but as i say, once i connected to the live database, and reset all table locations from within the report designer (inc all sub-report references) that seemed to sort my problems out.

The error seemed to be just some generic 'connection/retrieval' error thrown by crystal, i have had it a number of times for different underlying reasons. If you find a way to get better fault descriptions i would be more than happy to know as well!