I wonder the installer of one of the patches had a bug that did that..
Joe _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj Sent: Thursday, September 05, 2013 10:23 PM To: arslist@ARSLIST.ORG Subject: Re: WARNING on Microsoft MS11-030 KB2509553 ** Added by the install On Thursday, September 5, 2013, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > I just checked our 64 bit 7.6.04 system (patch 003) and the image path does not have any quotes on it.. > > > > Any reason how it might have got there? > > > > Joe > > > > ________________________________ > > From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing > Sent: Thursday, September 05, 2013 3:25 PM > To: arslist@ARSLIST.ORG > Subject: Re: WARNING on Microsoft MS11-030 KB2509553 > > > > ** > > Chris, > > Earlier this week, I came across this problem, but it wasn't with the particular MS Patch that you mention. I wanted to send out a note to the community notifying them of the eventual 'fix' that BMC provided to me on this scenario. I had all of the same symptoms, armonitor wouldn't start, no matter how I tried it. When starting it from services, it would try to write to an armonitor.log in the syswow folder, etc. > > > > The eventual fix that BMC came back with was to modify the 'Image Path' of the service to not include " marks. > > > > The install path was > > "C:\Program Files\BMC Software\ARSystem\armonitor.exe" > > > > they just had me take the " out, and everything started up fine. > > > > The best I can come up with regarding the 'reason' for this is that in x64 based systems, MS implements file system redirect to get you to the correct version of the file you are looking for...if you are a 32 bit app, and try to access various folders, you are redirected to the syswow64 folder instead. Based on the 'fix' provided, it seems that at times, MS implements a change in some process that causes the " at the beginning of the image path to be misunderstood and makes c:\windows\syswow64 the 'root' of the process instead of the intended folder, which of course makes it not work because the files don't exist there. > > > > On Wed, Jun 1, 2011 at 12:48 PM, strauss <stra...@unt.edu> wrote: > > Remove Microsoft KB2509553. I have reproduced this on three 7.1 servers, and the only fix is to take the security update back off. On at least one of those, after upgrading it to 7.6.04 and adding the patch back on individually, it no longer stopped the AR service from starting, but BMC Support tells me they have had reports from most supported and older versions. I have had an issue open with Microsoft since mid-April, and they had several others from ARS 7.1 sites, so it is definitely a problem. > > > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
