RtlAcquirePebLock in NTdll.dll Error

rbuser

Hello,

I have a new client using one of our applications. It uses Report
Builder with report templates stored to a database table. When ever
they try to print they get an exception (see exception dump below). It
works fine on my test system and other clients systems. Any idea what
is happening here? I seem to remember hearing of a similar error
related to printing some time back for don't recall what the solution
was.

--
David Farrell-Garcia
Whidbey Island Software LLC

Posted with XanaNews 1.16.3.1


date/time : 2004-07-21 15:32
computer name : OFFICE
user name : Action
operating system : Windows XP Service Pack 1 build 2600
system language : English
system up time : 2 days 7 hours
program up time : 12 seconds
physical memory : 145/511 MB (free/total)
free disk space : (C:) 40.17 GB
process id : $374
executable : OrcaCashier30.exe
exec. date/time : 2004-07-21 14:30
version : 3.0.0.490
madExcept version : 2.7b
exception class : EAccessViolation
exception message : Access violation at address D2FF7FFE. Read of
address D2FF7FFE.

main thread ($4b0):
d2ff7ffe +00 ???
77f59b82 +25 ntdll.dll RtlAcquirePebLock
77f59bea +0c ntdll.dll RtlReleasePebLock
00404370 +08 OrcaCashier30.exe System TObject.Free
0088d2fc +c2 OrcaCashier30.exe Sales 5392
TfrmSales.DesignLaserInvoiceActionExecute
008919a0 +a4 OrcaCashier30.exe OrcaCashier30 141 initialization

thread $86c:
7ffe0300 +04 ???
77f5c518 +0a ntdll.dll NtWaitForMultipleObjects
77e75e51 +89 kernel32.dll WaitForMultipleObjectsEx
77e75f93 +12 kernel32.dll WaitForMultipleObjects

thread $430:
7ffe0300 +04 ???
77d44377 +39 user32.dll GetMessageA
00430eb0 +27 OrcaCashier30.exe madExcept ThreadExceptFrame

modules:
00400000 OrcaCashier30.exe 3.0.0.490 C:\Program Files\Whidbey
Island Software\Orca 3.0
015e0000 odbc32.DLL 3.520.9042.0 C:\WINDOWS\System32
10000000 asOEHook.dll 2004.1.3.7
C:\PROGRA~1\COMMON~1\SYMANT~1\ANTISPAM
1a400000 URLMON.DLL 6.0.2800.1400 C:\WINDOWS\system32
1f850000 odbcint.dll 3.520.7713.0 C:\WINDOWS\System32
30000000 IMGHOOK.DLL 6.2.0.0 C:\Program Files\Iomega\Tools
4bde0000 IDAPI32.DLL 5.2.0.2 C:\Program Files\Common
Files\Borland Shared\BDE
4c9e0000 IDR20009.DLL 5.2.0.2 C:\Program Files\Common
Files\Borland Shared\BDE
4cde0000 IDPDX32.DLL 5.2.0.2 C:\Program Files\Common
Files\Borland Shared\BDE
4dde0000 IDDBAS32.DLL 5.2.0.2 C:\Program Files\Common
Files\Borland Shared\BDE
4e8e0000 BANTAM.DLL 1.0.0.8 C:\Program Files\Common
Files\Borland Shared\BDE
58000000 IPHook32.dll 5.5.100.92 C:\Program Files\Verizon
Online\Visual IP InSight
5ad70000 uxtheme.dll 6.0.2800.1106 C:\WINDOWS\System32
5b0a0000 umdmxfrm.dll 5.1.2600.0 C:\WINDOWS\System32
5cd70000 serwvdrv.dll 5.1.2600.0 C:\WINDOWS\System32
5edd0000 olepro32.dll 5.0.5014.0 C:\WINDOWS\System32
63000000 wininet.dll 6.0.2800.1405 C:\WINDOWS\system32
70a70000 SHLWAPI.dll 6.0.2800.1514 C:\WINDOWS\system32
71950000 comctl32.dll 6.0.2800.1515
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df
_6.0.2600.1515_x-ww_7bb98b8a
71aa0000 WS2HELP.dll 5.1.2600.0 C:\WINDOWS\System32
71ab0000 WS2_32.dll 5.1.2600.1240 C:\WINDOWS\System32
71ad0000 wsock32.dll 5.1.2600.0 C:\WINDOWS\System32
71b20000 mpr.dll 5.1.2600.0 C:\WINDOWS\system32
71bf0000 SAMLIB.dll 5.1.2600.1106 C:\WINDOWS\System32
71c10000 ntlanman.dll 5.1.2600.1106 C:\WINDOWS\System32
71c20000 NETAPI32.dll 5.1.2600.1562 C:\WINDOWS\System32
71c80000 NETRAP.dll 5.1.2600.0 C:\WINDOWS\System32
71c90000 NETUI1.dll 5.1.2600.0 C:\WINDOWS\System32
71cd0000 NETUI0.dll 5.1.2600.0 C:\WINDOWS\System32
72d10000 msacm32.drv 5.1.2600.0 C:\WINDOWS\System32
72d20000 wdmaud.drv 5.1.2600.0 C:\WINDOWS\System32
73000000 winspool.drv 5.1.2600.1106 C:\WINDOWS\System32
73dc0000 LZ32.DLL 5.1.2600.0 C:\WINDOWS\system32
74d30000 oledlg.dll 5.1.2600.0 C:\WINDOWS\System32
74e30000 RICHED20.DLL 5.30.23.1211 C:\WINDOWS\System32
75f60000 drprov.dll 5.1.2600.0 C:\WINDOWS\System32
75f70000 davclnt.dll 5.1.2600.0 C:\WINDOWS\System32
762a0000 MSASN1.dll 5.1.2600.1362 C:\WINDOWS\system32
762c0000 CRYPT32.dll 5.131.2600.1123 C:\WINDOWS\system32
76390000 imm32.dll 5.1.2600.1106 C:\WINDOWS\System32
763b0000 comdlg32.dll 6.0.2800.1106 C:\WINDOWS\system32
76b40000 winmm.dll 5.1.2600.1106 C:\WINDOWS\System32
76f90000 Secur32.dll 5.1.2600.1106 C:\WINDOWS\System32
77120000 oleaut32.dll 3.50.5016.0 C:\WINDOWS\system32
771b0000 OLE32.DLL 5.1.2600.1362 C:\WINDOWS\system32
773d0000 shell32.dll 6.0.2800.1556 C:\WINDOWS\system32
77bd0000 midimap.dll 5.1.2600.0 C:\WINDOWS\System32
77be0000 MSACM32.dll 5.1.2600.0 C:\WINDOWS\System32
77c00000 version.dll 5.1.2600.0 C:\WINDOWS\system32
77c10000 MSVCRT.DLL 7.0.2600.1106 C:\WINDOWS\system32
77d40000 user32.dll 5.1.2600.1255 C:\WINDOWS\system32
77dd0000 ADVAPI32.dll 5.1.2600.1106 C:\WINDOWS\system32
77e60000 kernel32.dll 5.1.2600.1106 C:\WINDOWS\system32
77f50000 ntdll.dll 5.1.2600.1217 C:\WINDOWS\System32
78000000 RPCRT4.dll 5.1.2600.1361 C:\WINDOWS\system32
7c000000 MSVCR70.dll 7.0.9466.0 C:\WINDOWS\System32
7e090000 GDI32.dll 5.1.2600.1346 C:\WINDOWS\system32

nicocizik

Hi David,

This is not a known issue with ReportBuilder. Does this exception occure
every time your user tries to print? Are they able to print to another
printer successfully? Are they able to print from another computer
successfully, using your application? Be sure they are using the latest
printer and video drivers for their hardware.

--

rbuser

Nico Cizik (Digital Metaphors) wrote:


Hi Nico. Sorry, I found the problem and should have posted the results
here. It appears that the template that I shipped to the customer did
not match the application after we updated the application. We sent
new database tables and the problem went away. We did not change
anything on purpose but only opened the report designer at design time.
There was a error about an inherited property, we realized our mistake
and closed the designer, thinking nothing else about it, but when we
compiled the app and shipped it to the customer as an update is when we
got the error. After failing to find a solution we just shipped our
copies of the report templated tables and it worked perfectly. I hope
that storing templates in database tables is not going to prove to be a
fragile thing for us regarding updates..


--
David Farrell-Garcia
Whidbey Island Software LLC

Posted with XanaNews 1.16.3.1

nicocizik

Hi David,

Updating your application is generally very easy when storing templates on a
database. The only difficulty you might encounter is if you decide to
change your database and connectivity type for an upgrade. Then you will
need to individually open each template file and save it back down with new
datasettings and new datamodules. It is on our to-do list to improve this
process.

--