Troubleshooting: "Error 534: Error detected by database DLL"

Typically, this error indicates a permissions problem, either within your network or within Bundle-Track.

Where do you encounter the problem? (Please click one of the following.)

• with all reports
• with only one or some specific report(s)
• with only one pay group

No Reports are Working

1. Create a new printer object to print your reports.
2. In Bundle-Track, menu select File >> Printer Setup, and specify the new printer object as the Report Printer.
3. Try opening a Report.

If that works, the problem is not in Bundle-Track but in your network. You may find that this new printer object works for a day or two, but then fails again. This is because your network is identifying its member machines with temporary addresses that expire in a few days. If you experience the pboblem only through Bundle-Track, it is because your other Windows applications are configured to wait for a much longer time for the network to resolve the address mismatch, and Bundle-Track instead times out. To permanently resolve this problem, you need to fix your network configuration. For starters, make sure you are using a TCP/IP network protocol.

If you are still having trouble, try the measures for 'Some Reports Work Fine' below.

Some Reports Work Fine

Test 1 - sysdba access:
Log into Bundle-Track as the System Administrator (sysdba) and try to preview the report.

• If sysdba cannot access the report, it's probably a field mapping problem. Contact LaborMetrix support.
• Otherwise perform Test 2.
   

Test 2 - user permissions:
Confirm that the User encountering the error has permissions to access the report.

• If the User does not have the proper permissions, ask a Bundle-Track Administrator to use Bundle-Track Roles to add the appropriate Role to the User.
   
• If the User does have the proper permissions, contact Bundle-Track support, and let them know about any database scripts you may have run recently.
   

Last measure - grant execute permissions - Version 3.8.40 only:

1. Get ISQL ready to run your commands.
   • If you don't know how, click here to learn, and then return.
      
2. Copy and Paste the following code into ISQL:
   

   GRANT EXECUTE on PROCEDURE RTVPRDRTERPT to PUBLIC;

   
    
3. Click the Lightning Bolt icon to execute and note the result.
   • If the code executes successfully, it will simply disappear from the upper window.
   • If you get an error message, contact Bundle-Track support.
      
4. Exit ISQL and IBConsole.
    

This happens with only one Pay Group

Typically, this indicates that among the worker events you are attempting to report on, at least one event has hours greater than zero, and at least one event has zero hours. Remove any events having zero hours and try again. You can use the query below to locate all current events having zero hours, but remember to remove only those that are in Pay Groups that have other events with non-zero hours (because in those pay groups that have no other events, you'll need at least one event, and you'll generally want that to be a zero-hour event).

select PSD.PaySesDefLab as PayGroup, EM.EmpMasLab as EmployeeCode, EC.WrkDat as WorkDate from PaySesDef PSD, EmpMas EM, EveCur EC where PSD.PaySesDefKey=EM.PaySesDefKey and EM.EmpMasKey=EC.EmpMasKey and EM.HidRec="F" and WrkDat>=(PSD.CurPerDat-PSD.DayPerPer) and WrkDat<=PSD.CurPerDat and TotTim=0 Order by PSD.PaySesDefLab, PSD.CurPerDat, EM.EmpMasLab, EC.WrkDat

We welcome your comments at support@bundle-track.com.

If you would like our live assistance, you may hire us at our professional services rate.