R
RCW
I guess I've joined the ranks of unhappy Microsoft update
victims. Following install of KB835732 update on W2K
machines, 2 users (myself included) are unable to run
reports from a specific application (Avaya CMS
Supervisor). When I contacted the vendor with confirmation
that the MS patch was the source of the problem, they told
me to check with Microsoft. (Yea, like that will be
effective.)
The appication works fine without the patch, but once the
patch is installed the reports lockup. Our patch is being
pushed by SUS, so as a temporary workaround we have to
cancel install of the patch every time we boot.
After reading these other horror stories, I guess only 1
application malfunction make me feel lucky. Unfortunately
this application is a monitoring tool for our call-
center's phone system. Come on Microsoft - help us out
here!
victims. Following install of KB835732 update on W2K
machines, 2 users (myself included) are unable to run
reports from a specific application (Avaya CMS
Supervisor). When I contacted the vendor with confirmation
that the MS patch was the source of the problem, they told
me to check with Microsoft. (Yea, like that will be
effective.)
The appication works fine without the patch, but once the
patch is installed the reports lockup. Our patch is being
pushed by SUS, so as a temporary workaround we have to
cancel install of the patch every time we boot.
After reading these other horror stories, I guess only 1
application malfunction make me feel lucky. Unfortunately
this application is a monitoring tool for our call-
center's phone system. Come on Microsoft - help us out
here!