Author |
Message
|
isaw |
Posted: Wed May 09, 2007 5:38 am Post subject: Runtime error: DataFlowEngine.exe |
|
|
Apprentice
Joined: 09 May 2007 Posts: 45
|
Hey guys,
I'm new here and have googled for help on this and 'searched' these forums but couldn't find a reference to my issue.
Basically, something has "broken" in my WMB setup on my WinXp machine. As soon as I try to deploy a *.bar file, I get the message that it was deployed, but nothing in the event logs and it never actually gets deployed.
And then I get an error Window popup with the title, "Microsoft Visual C++ Runtime Library" and with a message of, "Runtime Error! Program: C:\Program Files\IBM\MQSI\6.0\bin\DataFlowEngine.exe -- This application has requested the Runtime to terminate it in an unusal way. Please contact the app support team for more information".
Looking in the WinXP event viewer I see no red X's under app, security or system.
I have followed some steps I found in these forums on removing the broker, cleaning the registry of the entry and recreating the broker. I have also removed and recreated the config manager as well and even gone so far as to remove the broker database and have it recreated when I recreate the broker.
I still have the same issue -- nothing gets deployed when I request deployment, i have to cancel deployments in order to re-deploy so it's recognized that i have tried to deploy but it's not finished. And this window keeps popping up about the DataFlowEngine.exe error every few seconds.
It's almost as tho the requests arent hitting the ConfigMgr queue and not getting put onto the appropriate channels.
I'm quite new to WMB and WMQ so apologies if this is a common issue and there's a thread on how to resolve it. Please you could point me to it if one exists. Otherwise, any help you guys could provide or advice to try I would greatly appreciate it.
Thanks! |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 09, 2007 5:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Sounds like the Broker is continually crashing.
I'd re-install, and try again.
After making sure your Broker service user is still valid and has all necessary group memberships. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
isaw |
Posted: Wed May 09, 2007 5:43 am Post subject: |
|
|
Apprentice
Joined: 09 May 2007 Posts: 45
|
jefflowrey wrote: |
Sounds like the Broker is continually crashing.
I'd re-install, and try again.
After making sure your Broker service user is still valid and has all necessary group memberships. |
Heh, that's what I was hoping *not* to hear!
As far as I can tell, the Broker service user is valid and has not been removed from the groups it's needs.
Looks like an un-inst/re-inst... gyah.. there goes 2 days of my life! Again!
EDIT: Sorry Jeff - did you mean re-inst of the whole package of WM* or just the Broker side of it? |
|
Back to top |
|
 |
mqmatt |
Posted: Wed May 09, 2007 5:55 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 09, 2007 6:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Just Broker runtime. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed May 09, 2007 2:39 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Quote: |
And then I get an error Window popup with the title, "Microsoft Visual C++ Runtime Library" and with a message of, "Runtime Error! Program: C:\Program Files\IBM\MQSI\6.0\bin\DataFlowEngine.exe -- This application has requested the Runtime to terminate it in an unusal way. Please contact the app support team for more information". |
I seem to remember such an error.
If you have the FileExtender installed make sure you have the Fixpack for it otherwise this error will prevent your setup from working...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
isaw |
Posted: Thu May 10, 2007 7:24 am Post subject: |
|
|
Apprentice
Joined: 09 May 2007 Posts: 45
|
fjb_saper wrote: |
I seem to remember such an error.
If you have the FileExtender installed make sure you have the Fixpack for it otherwise this error will prevent your setup from working...
Enjoy  |
Ahhh.. Oddly enough, this just happened after I installed the FileExtender package. I can't remember whether I added the fix pack or not.
Hmm. I just read this after I started the uninstall. Ok -- I'll keep this in mind and try it again.
thanks! |
|
Back to top |
|
 |
isaw |
Posted: Fri May 11, 2007 1:41 am Post subject: |
|
|
Apprentice
Joined: 09 May 2007 Posts: 45
|
Just as an update....
Ok. Removed FileExtender and Broker and reinst'd Broker, patched it up and presto -- no more DataFlowEngine.exe error!
Obviously I screwed up on the File Extender install and missed the fix pack for it. From what I have been told, the version I installed from our network drive was a "trial version" anywaze
Thanks guys for the help and advice!  |
|
Back to top |
|
 |
Gralgrathor |
Posted: Wed Jul 29, 2009 4:54 am Post subject: DataFlowEngine fails after MBFE install |
|
|
Master
Joined: 23 Jul 2009 Posts: 297
|
Hi, I have a similar problem - let me recap... |
|
Back to top |
|
 |
Gralgrathor |
Posted: Wed Jul 29, 2009 4:55 am Post subject: DataFlowEngine in WMB6.0 fails after MBFE5.0 install |
|
|
Master
Joined: 23 Jul 2009 Posts: 297
|
Here we go:
Hello,
The problem seems related to the problem detailed in this thread:
http://www.mqseries.net/phpBB/viewtopic.php?t=21616&view=next&sid=d0508c18e56394ba5714caa47be5b292
but the solutions presented did not work for me.
I have a WMQ 5.3 install, topped off with a WMB 6.0 runtime install, running on WXP. It was running like a charm, until I decided to install the MB File Extender - 5.0.0 with fixpack 5.0.0.4. Now, after starting a broker, I get the message:
Quote: |
Runtime Error!
Program C:\Program Files\IBM\MQSI\6.0\bin\DataFlowEngine.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information. |
I already stopped and removed everything, cleaned the registry and filesystem of the last traces of the broker install and reinstalled everything in order, but the result remains the same.
After installing, this is what happens if I set up a config mgr, a broker and attempt to start them:
Code: |
MQSISTART DEFAULTCONFIGMGR |
results in an application event:
Quote: |
( DEFAULTCONFIGMGR ) The WebSphere Message Brokers service has started at version '6000'; process ID 4512.
The WebSphere Message Brokers service executable has been started.
No user action required |
Then I
Code: |
MQSISTART DEFAULTBROKER |
resulting in the runtime error I described above, and a number of application events:
Quote: |
( DEFAULTBROKER ) The WebSphere Message Brokers service has started at version '6000'; process ID 5228.
The WebSphere Message Brokers service executable has been started.
No user action required |
Quote: |
( DEFAULTBROKER ) The WebSphere Message Brokers service has started at version '6000'; process ID 5228.
The WebSphere Message Brokers service executable has been started.
No user action required |
Quote: |
( DEFAULTBROKER.$SYS_mqsi ) Execution Group started: process '5888'; thread '5872'; additional information: brokerName ''DEFAULTBROKER''; executionGroupUUID ''82a6e590-12b3-11d3-81a2-00203506a68e''; executionGroupLabel ''$SYS_mqsi''; defaultExecutionGroup 'true'; queueManagerName ''DEFAULTQM''; trusted 'false'; dataSourceName ''DEFLTDB''; userId ''X45840D''; migrationNeeded 'false'; brokerUUID ''9c7b53c6-2201-0000-0080-bc65647850e4''; filePath ''C:\Program Files\IBM\MQSI\6.0''; workPath ''C:\Profiles\All Users\Application Data\IBM\MQSI''; ICU Converter Path ''''.
The execution Group has started using process '5888' and thread '5872' and will now start processing messages.
No user action required. |
Quote: |
( DEFAULTBROKER.$SYS_mqsi ) Publish/Subscribe subscriptions recovery started.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker. |
Quote: |
( DEFAULTBROKER.$SYS_mqsi ) Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required. |
Starting up the broker itself results in no error messages, but it doesn't run either, and there's that pesky Runtime error popup. I can find no relevant logging in the application-data folders or anywhere else.
When I
Code: |
MQSISTOP DEFAULTBROKER |
I get several error messages in the application event log, all reading the same:
Quote: |
( DEFAULTBROKER ) Execution Group '$SYS_mqsi' failed to return an internal configuration 'Start' message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow for large and complex deployments. Resolve any problems described in the system log. This 'internal configuration' operation will be retried automatically, if you continue to see this message you should investigate the reason for the Execution Groups failure to respond. |
I could not readily find any solution using google or mqseries.net. I hope somebody will recognize the problem and know a solution.
Thanks in advance,
Gr. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jul 29, 2009 5:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Replace your MQ v5.3 with MQ v6.0.2.6.
Replace your Broker version 6.0.0.0 with Broker version 6.0.0.9, or 6.1.0.4 would be even better. |
|
Back to top |
|
 |
fschofer |
Posted: Wed Jul 29, 2009 5:23 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
Hi,
on my AIX box the MBFE placed an extra script into
/var/mqsi/common/profiles which is called by the mqsiprofile.
Probably something similar is done under Windows by mqsiprofile.cmd
Have you removed this script too ?
Greetings
Frank |
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Jul 29, 2009 6:14 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
If you READ the MBFE documentation you will see that you have to 'enable' the Queue Manager to use MBFE. By This I mean, create some Queues for the MBFE Code to use.
There is a script that you have to run before starting the broker. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Gralgrathor |
Posted: Wed Aug 19, 2009 1:22 am Post subject: |
|
|
Master
Joined: 23 Jul 2009 Posts: 297
|
smdavies99 wrote: |
If you READ the MBFE documentation |
[grin] I did prepare the QM's I use for the MBFE. Apparently though the order in which one installs components is of some importance. I started out with a clean slate, and stuff works (more or less; I'm still having some problems, likely unrelated to this issue) now. Thanks! |
|
Back to top |
|
 |
|