| Author |
Message
|
| yadav.neeraj01 |
 Posted: Mon Oct 20, 2014 9:43 pm Post subject: Unable to start Message broker |
 |
|
Apprentice
Joined: 23 Feb 2011
Posts: 49
|
Hi Experts,
i am having a difficulty to start my broker on my 64 bit windows environment.
Below is the command i am using and error ....Please help... 
C:\Program Files\IBM\MQSI\7.0>mqsistart WBRK7_BROKER
BIP2135E: Source character ''f3'' in field ''f3'' cannot be converted to Unicod
from codepage '1208'.
The source character is an invalid code point within the given codepage.
Correct the application that generated the message.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and
ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqb
krs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support
center. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Oct 21, 2014 5:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It sounds like your install didn't complete successfully.
Or you are running on a 64-bit windows platform that isn't supported. |
|
| Back to top |
|
|
| yadav.neeraj01 |
| Posted: Sat Oct 25, 2014 9:46 am Post subject: |
|
|
Apprentice
Joined: 23 Feb 2011
Posts: 49
|
| Yes, i am working on 64 bit....But when i installed this......every component was working fine.....Are you saying that broker do problem with 64 bit sometimes? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 27, 2014 4:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yadav.neeraj01 wrote: |
| But when i installed this......every component was working fine..... |
When was this? How long have you been successfully using this installation? Has the broker been running for this entire period or has the software been installed but unused for a long period?
If it's been working reliably for a long period of time, what has changed recently at an OS or system level e.g. passowrds? Because......
| yadav.neeraj01 wrote: |
| Are you saying that broker do problem with 64 bit sometimes? |
....what I believe my most worthy associate is in fact saying is that broker do problem with 64 bit on platforms and configurations which are not officially supported. So if this is a new install (or reinstall) you could be running an unsupported Windows 64 bit configuration. Or the install (or reinstall) could have failed to complete. Or you've applied a change to Windows that has changed the Windows configuration into an unsupported mode (e.g. bad environment or resource limits).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| yadav.neeraj01 |
| Posted: Thu Nov 20, 2014 1:40 am Post subject: |
|
|
Apprentice
Joined: 23 Feb 2011
Posts: 49
|
When i installed this..every component was working fine.....around after one month suddenly broker stopped working and i was not able to start its service....Now i have created a new broker that is working fine...But again after 1-2 months it has stopped working and i am unable to start its services too..  
To anser the Vitor questions:-
I was using the insatllation software fine till my broker stopped working....No i have been using the broker for daily tasks...its not been unused for long time... And nothing got changed on my system or OS during this time.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 20, 2014 5:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yadav.neeraj01 wrote: |
| nothing got changed on my system or OS during this time.. |
Well something's changed because it's stopped working. Either Windows maintenance has been silently applied or some configuration has been changed.
The broker doesn't have a time limit on how long it works.
Try (as an experiment) using System Restore to revent your system to a past point when the broker worked. If the broker suddenly starts working, check for Windows changes. If it doesn't, look for broker configuration changes in areas System Restore doesn't affect.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 20, 2014 5:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| yadav.neeraj01 wrote: |
| nothing got changed on my system or OS during this time.. |
Well something's changed because it's stopped working. Either Windows maintenance has been silently applied or some configuration has been changed.
The broker doesn't have a time limit on how long it works.
Try (as an experiment) using System Restore to revent your system to a past point when the broker worked. If the broker suddenly starts working, check for Windows changes. If it doesn't, look for broker configuration changes in areas System Restore doesn't affect. |
 sounds like a password change to me... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 20, 2014 11:40 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| fjb_saper wrote: |
sounds like a password change to me... |
Or an expiry 
_________________
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 |
|
|
|
|
