on 02-25-2014 3:37 AM
please note - i'm not the developer of the app but trying to determine two things purpose behind dll and why the app crashes out.
If any one in the community has historical information from when a client cuts and paste text between word 2003 document and the PB app
the PB app crashes out on PBVM120.dll (version 121.0.7000) - generating a .net runtime 2.0 error stamp is always the same 4bb8260d but the fault address typically changes but hovers in the 0x001a???? location
any help or direction would be greatly appreciated. - Thank you
may contact me at richard.vanderwal@sympatico.ca
Hi Richard;
Can you tell us ...
1) PB.Net or PB Classic?
2) Version of MS-Windows?
3) Version of MS-Word?
4) If your PB Classic - is your application a Win32 or Winform deployment
5) If your app is Win32 is it p-code or m-code compiled?
Note: If you application crashes at the same point each time ... add "/pbdebug' to the command-line that starts your application.exe to start a low level trace. That may give us some more information around your error.
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Crashes like that are hard to pin down, and I've never found the debug info useful at all.
Things to look for:
- Are all the PB*.DLL files in the same folder?
- Is this the ONLY location for them on the computer? Do a full search.
- Are they all from the same version/build?
Sometimes, a failed patch install can leave older versions of those DLLs in other folders, and if they're from different builds, then the entire app can become unstable.
-Paul Horan-
SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.