on 01-25-2017 10:09 AM
Hi Folks,
When we are closing our application then we are getting below error and application is getting closed -
a_app.exe has stopped working
A problem caused the program to stop working correctly. Please close the program.
While checking event viewer in windows getting below details -
Faulting application name: a_app.exe, version: 1.0.0.1, time stamp: 0x56c16dec
Faulting module name: PBSHR126.dll, version: 12.6.0.4091, time stamp: 0x56c16def
Exception code: 0x80000003
Fault offset: 0x00117d0e
Faulting process id: 0x47f4
Faulting application start time: 0x01d2766a68718eb2
Faulting application path: D:\Users\a_app.exe
Faulting module path: C:\Program Files (x86)\Sybase\Shared\PowerBuilder\PBSHR126.dll
Report Id: c3d2e955-e25d-11e6-8106-005056b51f8e
Faulting package full name:
Faulting package-relative application ID:
We have PB12.6 B4091.
any pointers will be helpful.
Hi All,
Is above issue already resolved ? If yes please submit your answer as I'm getting same issues for different dll's
error -
Faulting application name: app.exe, version: 1.0.0.1, time stamp: 0x6308a94fFaulting package full name:
Thanks.
Vijay Jha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijay jha,
Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time please note that:
You are adding a comment to an old post that is not likely to get an answer.
I suggest starting a new question and following these guidelines:
I recommend that you familiarize yourself with: https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members.
For example, you can:
- outline what steps you took to find answers (and why they weren't helpful)
- share screenshots of what you've seen/done
- make sure you've applied the appropriate tags
- use a more descriptive subject line
The more details you provide, the more likely it is that members will be able to respond. Feel free to also take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html
Should you wish, you can revise your question by selecting Actions, then Edit.
By adding a picture to your profile you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html
Regards,
Dedi
The crash you are encountering is unrelated to the crash in pbshr126.dll. Your crash occurs in a control for RTF. Assuming that this is for the RTF support built into SAP PowerBuilder, you should ensure that you are using 12.6 Build 4280 (12.6 SP00 PL16) as that is the last update for SAP PowerBuilder. If this is with Appeon PowerBuilder, you should work with Appeon. If the issue is with an independent use of that RTF software, you will need to work with its vendor.
Hi Devang;
Can you tell us ...
1) Any recent changes to PB - ie: new EBF applied?
2) Recent changes to your PB application?
3) Are the PB run-time DLL's matching your PB IDE build?
4) What O/S are you using?
5) Does this happen on more than one PC?
6) How long has this issue been happening?
7) Does the application call external DLL's?
etc
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We tried with that and in that case, application is not getting crashed.
Few more details -
PB Classic
Executable build with P Code & 32 bit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try to run exe with /pbdebug parameter and see the generated DBG file. Often you can see at last lines what code causes the problem.
One possible reason is an infinite call loop (like if you want to call the ancestor event or function and forgot to specify "super::")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.