Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Editing DB Profiles Crashes InfoMaker

  1. Issue
0
Votes
Undo
  1. Paul Weir
    Paul Weir
  2. InfoMaker
  3. Thursday, 25 May 2023 20:31 PM UTC

We have two servers on which InfoMaker is installed. When I try to edit any of our DB Profiles on one machine I can access any DB Profile and modify it. On the other server doing the exact same thing crashes InfoMaker.

 

So, I think something might be wrong with the profile setup? Is there a way to modify the profile setup without accessing the DP Profiles window? LDAP is the login mode for one server (where IM crashes) and not on the other (where it runs fine). Any other ideas to try?

 

Here are the crash details:

 

Faulting application name: IM190.EXE, version: 19.0.0.2083, time stamp: 0x5d0919c6
Faulting module name: pbODB190.dll, version: 19.0.0.2083, time stamp: 0x5d091b25
Exception code: 0xc0000409
Fault offset: 0x0002955b
Faulting process id: 0x3718
Faulting application start time: 0x01d98f446e632424
Faulting application path: C:\Program Files (x86)\Appeon\InfoMaker 19.0\IM190.EXE
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbODB190.dll
Report Id: 3822203c-5919-495a-b966-a655d68a5f98
Faulting package full name:
Faulting package-relative application ID:

 

Attached are videos of the crash.

 

Thanks as always!

Attachments (2)
2023-05-25_14-55-51.zip
2023-05-25_14-58-10.zip
  1. Crash
  2. Database Profile
  3. InfoMaker
Infomaker Nested Report Failed
Didn't log into Trial version
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 26 May 2023 18:34 PM UTC
  2. InfoMaker
  3. # Permalink
Hi Paul; If the DSN's do not work from their related ODBC Admin utility - then there is no way IM will work either connectivity wise. Depending on how well the ODBC drivers are coded (from the DBMS vendoe), will depend if you get a warning or a crash. As the DBMS connectivity runs as a "sub-task" to the IM IDE and if a sub-task crashes *without catching* the error, the MS-WIndows O/S will just raise the error to the main task (being IM IDE) and thus IM could be closed (penalized) for no fault of it's own. In this case the poorly coded DSN DB driver created a cascading crash that took out IM. HTH Regards ... Chris
Comment
There are no comments made yet.
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 25 May 2023 21:29 PM UTC
  2. InfoMaker
  3. # 1

Hi Paul;

  Can you tell us ...

  1. What version of the MS-Windows O/S(s) are those IM IDE's running on?
  2. Can you connect to the respective DB's from the ODBC Administrator utility for those DSN's being referenced in the DB Profile painter?
  3. Did you install the DSN's as 32 bit as the IM IDE is still 32 bit?

Regards ... Chris

Comment
There are no comments made yet.
Paul Weir
Paul Weir Accepted Answer Pending Moderation
  1. Friday, 26 May 2023 14:23 PM UTC
  2. InfoMaker
  3. # 2

Chris,

 

Both servers are running Windows Server 2019 Standard 64-bit.

 

Here's what I see on each machine's ODBC Data Source Administrator (32-bit) windows:

 

On the machine where InfoMaker does not crash:

 

image

 

image

 

 

On the other machine where InfoMaker is crashing:

 

image

 

Data source name is longer than 32 characters: J12022: J1 Play - Business Office O.

 

image

 

Driver name is an empty string in data source: J12022: J1 Training.

 

image

 

image

 

I'm checking with our server admins about your last question. But it looks like all but that one conversion connection is 32-bit. Is that what it looks like to you also?

 

Again, thank you for your helpfulness as always!!!

 

Paul

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 26 May 2023 16:54 PM UTC
Hi Paul, Seems these are all problems of incorrectly configuring the DSNs. Make sure all the DSN names and configurations inside those DSNs on the problematic server match the server that is working correctly. For example, on the server that works correctly I don't see any DSN names longer than 32 characters or named "12022: J1 Play - Business Office O".
  1. Helpful 1
There are no comments made yet.
Paul Weir
Paul Weir Accepted Answer Pending Moderation
  1. Friday, 26 May 2023 18:35 PM UTC
  2. InfoMaker
  3. # 3

Victory! My server admin said: "I deleted the current "J1 Play" ODBC connection from the RDS server and then re-added the ODBC connection using a REG file that I created to recreate it."

 

Now it works for me. Thank you!!!

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 26 May 2023 19:14 PM UTC
Hi Paul;

That is awesome news .. thanks for letting us know!

Regards ... Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.