Another JIWA 6.5 crash on Windows 2008 R2

Discussions relating to breakout scripting, .NET and COM programming with Jiwa objects.

Another JIWA 6.5 crash on Windows 2008 R2

Postby ted.nsw » Mon Jul 13, 2015 10:47 am

Dear JIWA support,

I've got another 2 problems.
When I exit from JIWA I have another crash.
It says,

Problem signature:
Problem Event Name: APPCRASH
Application Name: Jiwa.exe
Application Version: 6.5.558.12
Application Timestamp: 48bb8b8b
Fault Module Name: StackHash_f7dd
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 55636317
Exception Code: c0000374
Exception Offset: 000cea5f
OS Version: 6.1.7601.2.1.0.18.10
Locale ID: 3081
Additional Information 1: f7dd
Additional Information 2: f7dd9aa05faa1a79f51de71ef0824e22
Additional Information 3: ec00
Additional Information 4: ec00090dab611a3512a5465d3d645b51

This happens to all Terminal Server users including Admin console.

My second problem is related to Crystal Report.
When I print an invoice, I have

Error : Failed to open the connection.
Detail: [Database Vendor Code: 4060 ]
Module: clsJiwaPrintReport.SetTableLocations.

Thanks in advance again.

Ted Ahn
ted.nsw
Occasional Contributor
Occasional Contributor
 
Posts: 10
Joined: Wed Jul 01, 2015 6:15 pm

Re: Another JIWA 6.5 crash on Windows 2008 R2

Postby Mike.Sheen » Thu Jul 16, 2015 9:48 am

ted.nsw wrote:When I exit from JIWA I have another crash.


I think this is a known problem - Can you verify if you only get the crash on exit after you have printed a report? I find I can often get that crash on exit after printing a report, but not when not having printed a report. If that is the problem, then unfortunately that is related to a third-party component (Crystal Reports) and beyond our control.

ted.nsw wrote:My second problem is related to Crystal Report.
When I print an invoice, I have

Error : Failed to open the connection.
Detail: [Database Vendor Code: 4060 ]
Module: clsJiwaPrintReport.SetTableLocations.


It's difficult to say what is causing this. Does the standard Jiwa invoice report exhibit the same problem? If not, then your invoice report may simply need to have the connection type reset using the Crystal reports designer (I believe I have experienced this when the .NET native SQL client is used rather than OLEDB).

Mike
Mike Sheen
Chief Software Engineer
Jiwa Financials

If I do answer your question to your satisfaction, please mark it as the post solving the topic so others with the same issue can readily identify the solution
User avatar
Mike.Sheen
Overflow Error
Overflow Error
 
Posts: 2444
Joined: Tue Feb 12, 2008 11:12 am
Location: Perth, Republic of Western Australia
Topics Solved: 756

Re: Another JIWA 6.5 crash on Windows 2008 R2

Postby ted.nsw » Fri Jul 17, 2015 12:20 pm

Thanks for your reply.
First, I fixed the Crystal Report connection problem[4060], by restarting the server.

But I'm still having that crash at Jiwa exit. As you said, it looks like relating to Crystal Report 2008.
Because, Crystal reports installation window keeps coming up when we start JIWA.
So I simply blocked it by using gpedit.msc
Please inform me when you find a solution for it.

Regards,

Ted Ahn
ted.nsw
Occasional Contributor
Occasional Contributor
 
Posts: 10
Joined: Wed Jul 01, 2015 6:15 pm

Re: Another JIWA 6.5 crash on Windows 2008 R2

Postby Scott.Pearce » Fri Jul 17, 2015 12:52 pm

ted.nsw wrote:Because, Crystal reports installation window keeps coming up when we start JIWA.


If the user is made local admin, then they log in to Jiwa, Crystal will be able to jump in and install/repair whatever it was trying to install/repair. After that, Crystal will be happy and you can remove local admin rights.
Scott Pearce
Senior Analyst/Programmer
Jiwa Financials
User avatar
Scott.Pearce
Senpai
Senpai
 
Posts: 742
Joined: Tue Feb 12, 2008 11:27 am
Location: New South Wales, Australia
Topics Solved: 221


Return to Technical / Programming

Who is online

Users browsing this forum: No registered users and 2 guests