| Author |
Message
|
| jpeela |
 Posted: Thu Mar 29, 2007 3:46 am Post subject: |
 |
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi HubertKleinmanns,
The event logs are as shown in at the begenning
The TCP/IP responder program could not be started.
An attempt was made to start an instance of the responder program, but the program was rejected.
The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the responder program later). The reason code was 0
and
Channel negotiation failed.
Channel '' between this machine and the remote machine could not be established due to a negotiation failure.
Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.
And nothing more than these two errors.
And now we have re installed with MQparms.exe changing the language in the inin file to english.But this displays the lang in english only for installation and the logs are still written in japanese only.So where should we change that parameter for making everything in english.
Awaiting your reply,
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
 |
| HubertKleinmanns |
| Posted: Thu Mar 29, 2007 4:54 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
jpeela,
what you described are not the NT event logs. You described an error file of MQ!
I meant the Windows NT Event log or also known as Event Viewer. You find it in the Start menu under Settings and Control Panel.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 29, 2007 5:13 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi HubertKleinmanns,
I have copied those from the event viewer > application logs
do you require something from security and sysytem logs
from event viewer >system logs these are the errors
The machine wide Šù’è ‹N“®‚ƃAƒNƒeƒBƒu‰» security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
would this help out.
awaiting your reply,
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Mar 29, 2007 5:27 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
yes,
any created FDC will cause a corresponding entry in the application part of the NT event log, but should have a look into the system event log, which could have some entries at nearly the same time.
In the past I had a similar problem at a customers side, and the reason (in this situation) was a "disk full" error (shown in the system log) which lead to a "MQ error" in the application log or in the filesystem under "%MQ_INSTALL_PATH%\errors".
So what I was asking for was: Is there any NT system error which may cause, that MQ is not able to write to a log or Q file? The system error should have been appeared short time before the MQ error.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 29, 2007 5:40 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi HubertKleinmanns,
Ya I have checked the System logs , and there I found nothing more than these.Only this same error is appering all along.
And Coming to the disks they are having enough space of about 17 gb.
So no Idea what is happening around.And today we have reinstalled and still the same thing and this time even the channel from the other side is not able to ping, and when I checked for the telnet it was unable to connect on the specified port.So should be some network issue.But no firewall is existing either.and we are able to ping the sender from this sourse side.
Some where some ports must have been blocjed.Cannot confirm.
awaiting your reply.
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Mar 29, 2007 5:48 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Then I first would suggest, to upgrade to the latest CSD level (CSD-13).
If the problem persists, raise a PMR at IBM.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2007 6:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| HubertKleinmanns wrote: |
| Then I first would suggest, to upgrade to the latest CSD level (CSD-13). |
If the problem persists, raise a PMR at IBM.[/quote]
That's 2 votes for the upgrade. It's so much easier on the current platform. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Mar 29, 2007 6:31 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| Vitor wrote: |
| HubertKleinmanns wrote: |
Then I first would suggest, to upgrade to the latest CSD level (CSD-13).
If the problem persists, raise a PMR at IBM. |
That's 2 votes for the upgrade. It's so much easier on the current platform. |
Upgrading the software is (mostly) a good idea, but nevertheless I am always interested, why a problem occured.
I also had a lok into the README to CSD-13 and looked for the stringXC381010 - and did not found it. So it maybe, that this proble, won't be fixed.
But then jpeela has a supported version  .
(I guess, if we would make a voting, we would find a lot more, than two votes for upgrade  )
_________________
Regards
Hubert |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2007 6:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| HubertKleinmanns wrote: |
But then jpeela has a supported version .
|
No question of that. It's why I said current.
| HubertKleinmanns wrote: |
(I guess, if we would make a voting, we would find a lot more, than two votes for upgrade ) |
It'd be an interesting exercise, given the number of people who post questions about back version.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 29, 2007 9:02 pm Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi Vitor , HubertKleinmanns,
Presently we are in a hurry we cannot wait till we raise a PMR get new version and do the implementation then.
We had a change of plan, because we did not have approval for the latest CSD , we had to chose another server and continue with that.I 'll be back with some more if any.
Anyways thanks for all your suggessions and advises.
But still need your help yet.
And please let me know this one thing.I have even browsed for this in the infocenter which did not help.
How do we set the language to english on servers which defaults to their local languages like japanese chinese etc.
awaiting your reply,
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Mar 29, 2007 10:45 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| jpeela wrote: |
Hi Vitor , HubertKleinmanns,
Presently we are in a hurry we cannot wait till we raise a PMR get new version and do the implementation then.
We had a change of plan, because we did not have approval for the latest CSD , we had to chose another server and continue with that.I 'll be back with some more if any... |
That's the problem: Administrators, who do not permanently check and upgrade their versions and patch levels (for MQ as well as for operating systems or any other software - e. g. virus scanners) will always get trouble and come into hurry  (I'm quite sure, Vitor will agree ).
Nevertheless, I think, installing the CSD and raising a PMR will be much faster, than solving your problem manually  (To be more precisely: I am sure )
_________________
Regards
Hubert |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2007 11:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| HubertKleinmanns wrote: |
| jpeela wrote: |
Hi Vitor , HubertKleinmanns,
Presently we are in a hurry we cannot wait till we raise a PMR get new version and do the implementation then.
We had a change of plan, because we did not have approval for the latest CSD , we had to chose another server and continue with that.I 'll be back with some more if any... |
That's the problem: Administrators, who do not permanently check and upgrade their versions and patch levels (for MQ as well as for operating systems or any other software - e. g. virus scanners) will always get trouble and come into hurry (I'm quite sure, Vitor will agree ).
Nevertheless, I think, installing the CSD and raising a PMR will be much faster, than solving your problem manually (To be more precisely: I am sure ) |
If I agreed any more, I'd be an echo..... 
Especially with the last point!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 29, 2007 11:18 pm Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi Vitor , HubertKleinmanns,
Ya we would go for that parallelly,and installing CSD13 and look if works out, but as you said it may not work then we would raise the PMR.
Thanks & regards
_________________
Jogi |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2007 11:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jpeela wrote: |
| Ya we would go for that parallelly,and installing CSD13 and look if works out, but as you said it may not work then we would raise the PMR. |
It is a win/win. If the upgrade works out, fine. If it doesn't and you raise a PMR, the first thing they'll ask is "what level are you on", followed in short order by "it's fixed in the latest version" if you're still on CSD 7!
Hence you win again by saving time & saying "we're on the latest version".
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
