Thomas Hauber wrote: > Ever since updating this morning to the latest M$ patches, Ops Console > will no longer connect to our iSeries.
> Has anyone else had this problem?
> Our system is at OS400 V5R3 with the latest CUM applied.
Yes! I'm on V5R4. I already have Supportline involved because I already had a PMR open due to issues with ops console after going to V5R4. (That PMR is 15562,500,00 in case you want to call them about it - but it's really another issue.)
My PC is W2K with service pack 4. Ten updates were downloaded and applied today. I'm kind of at a standstill on it until they call me back. The next step would be to remove the updates and see if that helps. But only 7 of the 10 updates show in Add/Remove programs and I don't know why.
Thomas Hauber wrote: > Ever since updating this morning to the latest M$ patches, Ops Console > will no longer connect to our iSeries.
> Has anyone else had this problem?
> Our system is at OS400 V5R3 with the latest CUM applied.
FYI to anyone monitoring this thread. KB911280 released by Microsoft on 6/13/2006 will break Ops Console. Simply remove it and Ops Console will function again.
Bear in mind that it is a co-requisite with the following other security updates:
Thomas Hauber wrote: > Thomas Hauber wrote: > > Ever since updating this morning to the latest M$ patches, Ops Console > > will no longer connect to our iSeries.
> > Has anyone else had this problem?
> > Our system is at OS400 V5R3 with the latest CUM applied.
> FYI to anyone monitoring this thread. KB911280 released by Microsoft on > 6/13/2006 will break Ops Console. Simply remove it and Ops Console will > function again.
> Bear in mind that it is a co-requisite with the following other security > updates:
> KB917344 > KB917734 > KB917953 > KB918439
When I installed the updates on my W2K PC the client access 5250 connections failed. But after a reboot of the PC I was able to connect again.
Haven't there been issues with the ops console cable and windows in the past? Possibly because client access uses the serial port in ways unlike the majority of PC serial port code. My guess is IBM knew this was coming but it too strapped for resources to provide an alternative.
Thanks for the info. You saved me hours. We checked our ops console machine and sure enough, no connection and the MS update had been installed. We removed it and turned off auto-updates.
Thomas Hauber wrote: > Thomas Hauber wrote: > > Ever since updating this morning to the latest M$ patches, Ops Console > > will no longer connect to our iSeries.
> > Has anyone else had this problem?
> > Our system is at OS400 V5R3 with the latest CUM applied.
> FYI to anyone monitoring this thread. KB911280 released by Microsoft on > 6/13/2006 will break Ops Console. Simply remove it and Ops Console will > function again.
> Bear in mind that it is a co-requisite with the following other security > updates:
> KB917344 > KB917734 > KB917953 > KB918439
> Tom Hauber > IT Manager > Builders Hardware Inc.
Thomas Hauber wrote: > FYI to anyone monitoring this thread. KB911280 released by Microsoft on > 6/13/2006 will break Ops Console. Simply remove it and Ops Console will > function again.
> Bear in mind that it is a co-requisite with the following other security > updates:
> KB917344 > KB917734 > KB917953 > KB918439
> Tom Hauber > IT Manager > Builders Hardware Inc.
TH> FYI to anyone monitoring this thread. KB911280 released by Microsoft TH> on 6/13/2006 will break Ops Console. Simply remove it and Ops Console TH> will function again.
From the "known issues" section of Microsoft's KnowledgeBase article:
"An issue has been confirmed that involves dial-up connections that use a terminal window, or dial-up scripting. This is an older technology that is rarely used by modern dial-up connections. If dial-up scripting is used in a connection, the connection may stop responding. This behavior does not affect any dial-up connections that do not use dial-up scripting. This issue may affect direct-dial connections to a corporate network, to a university network, or to some ISPs (Internet service providers). Microsoft is working to develop and test a revision to this update that will address this issue. If you must use dial-up scripting or terminal window features, do not install security update 911280 (MS06-025) until the revised version is available." -- <URL:http://support.microsoft.com./kb/911280>
>> FYI to anyone monitoring this thread. KB911280 released by Microsoft on >> 6/13/2006 will break Ops Console. Simply remove it and Ops Console will >> function again.
>> Bear in mind that it is a co-requisite with the following other security >> updates:
>> KB917344 >> KB917734 >> KB917953 >> KB918439
>> Tom Hauber >> IT Manager >> Builders Hardware Inc.
> Do you still stand behind this post and if so, what was your > workaround? Was it to apply the patches and then selectively remove > KB911280 afterwards?
> Many thanks in advance,
> Greg
I simply removed the offending M$ patch, ignored the warning about cross compatibility problems (I mean this is only an ops console, nothing else is done on it), rebooted the machine and made sure that this particular patch is ignored.
>> FYI to anyone monitoring this thread. KB911280 released by Microsoft on >> 6/13/2006 will break Ops Console. Simply remove it and Ops Console will >> function again.
>> Bear in mind that it is a co-requisite with the following other security >> updates:
>> KB917344 >> KB917734 >> KB917953 >> KB918439
>> Tom Hauber >> IT Manager >> Builders Hardware Inc.
> Do you still stand behind this post and if so, what was your > workaround? Was it to apply the patches and then selectively remove > KB911280 afterwards?
> Many thanks in advance,
> Greg
Why did this put your M$ and IBM guys at odds? This isn't the first time that a patch has caused a problem and had to be removed.
|
