Skip to main content

[archive] Visual C Error

  • April 8, 2008
  • 3 replies
  • 0 views

[Migrated content. Thread originally posted on 07 April 2008]

Hello everyone,
I've got a couple of W2003 servers with an Acu722 Thin Client solution on 'em that started showing this popup message:
"Application Popup: Microsoft Visual C Runtime Library : Runtime Error!

Program: C:\\Acucorp\\Acucbl722\\AcuGT\\bin\\wrun32.exe


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
"
Local Support team suggested to activate Abend logging with ACU_DUMP 1 and have more infos but 2 day ago a popup was shown and no dump was generated.
A big problem is that with those popup active all the system slows down and applications must be restarted.
Has anyone have experienced such a behaviour?
TiA Gio.

3 replies

[Migrated content. Thread originally posted on 07 April 2008]

Hello everyone,
I've got a couple of W2003 servers with an Acu722 Thin Client solution on 'em that started showing this popup message:
"Application Popup: Microsoft Visual C Runtime Library : Runtime Error!

Program: C:\\Acucorp\\Acucbl722\\AcuGT\\bin\\wrun32.exe


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
"
Local Support team suggested to activate Abend logging with ACU_DUMP 1 and have more infos but 2 day ago a popup was shown and no dump was generated.
A big problem is that with those popup active all the system slows down and applications must be restarted.
Has anyone have experienced such a behaviour?
TiA Gio.
I've experienced these before (with beta products mostly). We see them every once in a while and have never seen them enough where we could learn anything about it. I've always assumed that it's a memory corruption of some sort or some really illegal code. I hope you get more information from others because I know my comments aren't very useful...

[Migrated content. Thread originally posted on 07 April 2008]

Hello everyone,
I've got a couple of W2003 servers with an Acu722 Thin Client solution on 'em that started showing this popup message:
"Application Popup: Microsoft Visual C Runtime Library : Runtime Error!

Program: C:\\Acucorp\\Acucbl722\\AcuGT\\bin\\wrun32.exe


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
"
Local Support team suggested to activate Abend logging with ACU_DUMP 1 and have more infos but 2 day ago a popup was shown and no dump was generated.
A big problem is that with those popup active all the system slows down and applications must be restarted.
Has anyone have experienced such a behaviour?
TiA Gio.
I've experienced these before (with beta products mostly). We see them every once in a while and have never seen them enough where we could learn anything about it. I've always assumed that it's a memory corruption of some sort or some really illegal code. I hope you get more information from others because I know my comments aren't very useful...

[Migrated content. Thread originally posted on 07 April 2008]

Hello everyone,
I've got a couple of W2003 servers with an Acu722 Thin Client solution on 'em that started showing this popup message:
"Application Popup: Microsoft Visual C Runtime Library : Runtime Error!

Program: C:\\Acucorp\\Acucbl722\\AcuGT\\bin\\wrun32.exe


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
"
Local Support team suggested to activate Abend logging with ACU_DUMP 1 and have more infos but 2 day ago a popup was shown and no dump was generated.
A big problem is that with those popup active all the system slows down and applications must be restarted.
Has anyone have experienced such a behaviour?
TiA Gio.
Hi Rob,
happy to hear that I'm not the only one with this clue. I confirm that abend dump doesen't catch the runtime error. I tried to activate DrWatson32 logging, hoping to get some more details. Due to it's random appearance I can't decide to put on a standard Wrun32 trace file at level 9 it'll generate an an overall slow down of performance for all users...
MSDN forums reports that error due mainly to a "bad hanfling of application's error routine" but no more info's.
Howevere thanks!
bye Gio