Results 1 to 10 of 10
  1. #1
    New Lounger
    Join Date
    Sep 2009
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    What does Word do when it starts up? I need to understand this because my own code, which is a set of drivers that encrypt/decrypt files on the fly and monitor registry operations, is interferring with this start up process. As a result of this interferrence, Word displays a 'Windows Installer' dialog when it starts.

    Environment: A VMware VM running XP SP2, Office 2k3, Pointsec (a full disk encryption system) is in effect. Network connects and domains that the laptop from which the VM was originally made are not available and these network request failures likely add to the slowness of the machine's initial response.

    Steps to reproduce:
    1) Start -> Programs -> Microsoft Word
    2) 'Windows Installer' dialog appears. It says, 'Preparing to install...' The user has the option to cancel it.
    3) Wait for a couple of minutes. . . .
    4) Word appears with an empty document.
    5) Word acts normally from this point on.
    6) Further attempts to repeat the process act in the same fashion.

    The fault clearly lies with my own code. I suspect that Word is attempting to do something during its startup that my own device drivers are interferring with. As a result, Word erronously believes that it needs to do some sort of update and that's where the 'Windows Installer' dialog gets called up.

    So, does anyone know the steps that Word takes on start up, what files it must load as part of its initialization? I suspect that my code is failing to decrypt one or more of those early startup files and that is leading Word to believe that it needs to install files that are appropriate for the locale or current document.
    =======
    Richard Lewis Haggard

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    You might use Microsoft's free utility Process Monitor - from the description of the program:
    Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity
    You can set it to filter activity related to a specified process (in this case Winword.exe).

  3. #3
    New Lounger
    Join Date
    Sep 2009
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Sadly, ProcMon terminates shortly after starting on this VM. FileMon runs but I'm not getting anything useful from that.

    Looking in the VM's application Event Log, I see these entries repeated a number of times:

    Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'WordUserData', component '{8ADD2C93-C8B7-11D1-9C67-0000F81F1B38}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\ Word\UserData' does not exist.

    Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'OfficeUserData', component '{4A31E933-6F67-11D2-AAA2-00A0C90F57B0}' failed. The resource 'HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\MS Access Database\' does not exist.


    along with

    Product: Microsoft Office Professional Edition 2003 -- Installation failed.
    Data Bytes -
    {90110409-6000-11D3-8CFE-0150048383C9}

    so I will see if I can convert this GUID into a particular installation package. First look did not reveal any such MSI's on disk. Should they be? Is so, where?



    [quote name='HansV' post='794061' date='19-Sep-2009 12:48']You might use Microsoft's free utility Process Monitor - from the description of the program:
    Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity
    You can set it to filter activity related to a specified process (in this case Winword.exe).[/quote]

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    Either the Office 2003 installation on your VM is munged, or there is a permissions problem if the "missing" registry values do exist but can't be read by Winword.

  5. #5
    New Lounger
    Join Date
    Sep 2009
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I figure the problem is related to interference with installation but I'm a bit short of what that might be. I'm relatively sure that it is not a rights issue (the account I'm using has full admin rights to the VM) but being a little vague on what is actually involved in the install/update process makes it hard to focus on where the real issue is.

    Attempts to open an PRO11.MSI (by double clicking on it) that resides on a network location that the VM has read rights to acts the same as an attempt to open the PRO11.MSI on the local machine. The initial dialog is displayed for a while and then an error box appears, 'Windows Installer' 'This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the applicatino verndor to verify that this is a valid Windows Installer patch package.'

    Are there dependencies that PRO11.MSI attempts to load?

    Going back to the original Setup.exe yields better UI info. It hangs at 'Installation files are being copied to your computer...' 'Current Action: AER_1033.ADM' However, Notepad has no trouble viewing the file so this may be a red herring.

    I'd started setup to write a log and this is as far as it got before the setup became non-responsive:



    c:\setup.log
    Detected Windows Info:
    PlatformId = 2
    MajorVersion = 5
    MinorVersion = 1
    ServicePackLevel = 2
    - - - - - - - - - - - - - - - - - - - - - - -
    Launch Setup
    9/19/2009 9:32:55 PM
    Recognized command line switch lv
    ** Switching to new log file passed on command line. **
    9/19/2009 9:32:55 PM

    Setup path: \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\SETUP.EXE
    Trying to get version of
    \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\SETUP.EXE
    ...succeeded.
    \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\SETUP.EXE is version 11.0.5510.0
    Current version of Setup.exe: 11.0.5510.0
    Searching for .INI file: SETUP.INI
    \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\FILES\SETUP\SETUP.INI
    Settings file located: \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\FILES\SETUP\SETUP.INI
    Reading settings file
    \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\FILES\SETUP\SETUP.INI
    Located: \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\PRO11.MSI
    Package to install: \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\PRO11.MSI
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Product\SkipLangCheck" (Default: 0)
    Value: 0
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Product\CheckUpdates" (Default: 0)
    Value: 0
    Product {90110409-6000-11D3-8CFE-0150048383C9} is installed for the user.
    Read Package Version: 11.0.5614.0
    Read Product Version: 11.0.8173.0
    Media Package Code: {1FFD5289-31ED-4F20-BEE4-91C374B62F4C}
    Installed Package Code: {6102E382-135B-4261-BA67-F6F09B6A6483}
    Checking for Windows Installer....
    C:\WINNT\system32\MSI.DLL
    .. succeeded.
    Checking for any beta version of the product.
    dwNoLtCoExist = 0
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Cache\CDCache" (Default: 0)
    Value: auto
    General properties added: LAUNCHEDFROMSETUP="1" SETUPEXEPATH="\\itadmin02\Images2\Media\Options\Mi crosoft\Microsoft Office 2003\" SETUPEXENAME="SETUP.EXE"

    Writing Task: Main - Microsoft Office 2003
    Path: C:\WINNT\system32\msiexec.exe
    CmdLine: /I "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\PRO11.MSI" LAUNCHEDFROMSETUP="1" SETUPEXEPATH="\\itadmin02\Images2\Media\Options\Mi crosoft\Microsoft Office 2003\" SETUPEXENAME="SETUP.EXE"

    Looking for setup tasks to process.
    9/19/2009 9:32:56 PM WaitForMsiExecDone...
    9/19/2009 9:32:56 PM WaitForMsiExecDone exits
    Verifying install package is available
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Cache\CDCache" (Default: 0)
    Value: auto
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Cache\Purge" (Default: 0)
    Value: 0
    Reading from "\\itadmin02\Images2\Media\Options\Microsoft\Micro soft Office 2003\FILES\SETUP\SETUP.INI": "Cache\DeletableCache" (Default: 0)
    Value: 1
    SetupXml is at: \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\Files\Setup\PRO11.xml

    Parsing Download Info
    Starting to load install configuration
    Download Info:
    Download Code : 90000409-6000-11D3-8CFE-0150048383C9
    Source Path : \\itadmin02\Images2\Media\Options\Microsoft\Micros oft Office 2003\
    Product Code : {90110409-6000-11D3-8CFE-0150048383C9}
    Prod Src Path : PRO11.MSI
    Use Windows Installer : false

    Files to Download:
    File: FILES\WINDOWS\INF\AER_1033.ADM (DW20.ADM_1033)
    File: FILES\PFILES\COMMON\MSSHARED\DW\DW20.EXE (DW20.EXE_0001)
    File: FILES\PFILES\COMMON\MSSHARED\DW\DWDCW20.DLL (DWDCW20.DLL)
    File: FILES\PFILES\COMMON\MSSHARED\DW\1033\DWINTL20.DLL (DWINTL20.DLL_0001_1033)
    File: FILES\PFILES\COMMON\MSSHARED\DW\DWTRIG20.EXE (DWTRIG20.EXE)
    File: FILES\PFILES\MSOFFICE\OFFICE11\OCLEAN.DLL (OCLEAN.DLL_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCORE.OPC (OCLNCORE.OPC_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCUST.OPC (OCLNCUST.OPC_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\1033\OCLNINTL.OPC (OCLNINTL.OPC_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\OFFCLN.EXE (OFFCLN.EXE_1033)
    File: FILES\SETUP\OSE.EXE (OSE.EXE)
    File: PRO11.MSI (PRO11.MSI)
    File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10O.CHM (PSS10O.CHM_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10R.CHM (PSS10R.CHM_1033)
    File: FILES\PFILES\MSOFFICE\OFFICE11\1033\SETUP.CHM (SETUP.CHM_1033)
    File: SKU011.XML (SKU011.XML_0002_1033)
    File: A2561405.CAB (A2561405.CAB)
    File: A3561405.CAB (A3561405.CAB)
    File: A4561405.CAB (A4561405.CAB)
    File: AV561403.CAB (AV561403.CAB)
    File: CC561401.CAB (CC561401.CAB)
    File: CD561401.CAB (CD561401.CAB)
    File: CF561401.CAB (CF561401.CAB)
    File: CL561401.CAB (CL561401.CAB)
    File: CM561401.CAB (CM561401.CAB)
    File: CP561401.CAB (CP561401.CAB)
    File: CR561401.CAB (CR561401.CAB)
    File: CS561401.CAB (CS561401.CAB)
    File: E2561410.CAB (E2561410.CAB)
    File: E3561405.CAB (E3561405.CAB)
    File: E4561410.CAB (E4561410.CAB)
    File: EV561405.CAB (EV561405.CAB)
    File: G3561403.CAB (G3561403.CAB)
    File: GV561403.CAB (GV561403.CAB)
    File: IJ561401.CAB (IJ561401.CAB)
    File: IS561401.CAB (IS561401.CAB)
    File: IU561401.CAB (IU561401.CAB)
    File: L2561403.CAB (L2561403.CAB)
    File: L3561403.CAB (L3561403.CAB)
    File: L4561403.CAB (L4561403.CAB)
    File: L9561403.CAB (L9561403.CAB)
    File: LV561403.CAB (LV561403.CAB)
    File: M2561406.CAB (M2561406.CAB)
    File: M3561404.CAB (M3561404.CAB)
    File: M4561403.CAB (M4561403.CAB)
    File: M9561403.CAB (M9561403.CAB)
    File: MA561403.CAB (MA561403.CAB)
    File: MC561403.CAB (MC561403.CAB)
    File: MG561403.CAB (MG561403.CAB)
    File: MH561401.CAB (MH561401.CAB)
    File: MO561403.CAB (MO561403.CAB)
    File: MT561403.CAB (MT561403.CAB)
    File: O0561401.CAB (O0561401.CAB)
    File: O1561403.CAB (O1561403.CAB)
    File: O9561403.CAB (O9561403.CAB)
    File: P2561401.CAB (P2561401.CAB)
    File: P3561401.CAB (P3561401.CAB)
    File: P4561402.CAB (P4561402.CAB)
    File: PA561401.CAB (PA561401.CAB)
    File: PR103368.CAB (PR103368.CAB)
    File: PR103678.CAB (PR103678.CAB)
    File: PR308246.CAB (PR308246.CAB)
    File: PV561401.CAB (PV561401.CAB)
    File: PW561401.CAB (PW561401.CAB)
    File: Q2561405.CAB (Q2561405.CAB)
    File: Q3561405.CAB (Q3561405.CAB)
    File: Q4561405.CAB (Q4561405.CAB)
    File: QV561405.CAB (QV561405.CAB)
    File: SKU011.CAB (SKU011.CAB)
    File: TR103621.CAB (TR103621.CAB)
    File: TR308222.CAB (TR308222.CAB)
    File: V3561403.CAB (V3561403.CAB)
    File: W2561405.CAB (W2561405.CAB)
    File: W3561405.CAB (W3561405.CAB)
    File: W4561405.CAB (W4561405.CAB)
    File: WV561405.CAB (WV561405.CAB)
    File: X2561401.CAB (X2561401.CAB)
    File: X3561401.CAB (X3561401.CAB)
    File: YA561403.CAB (YA561403.CAB)
    File: YB561408.CAB (YB561408.CAB)
    File: YC561403.CAB (YC561403.CAB)
    File: YH561403.CAB (YH561403.CAB)
    File: YI561401.CAB (YI561401.CAB)
    File: YL561402.CAB (YL561402.CAB)
    File: YM561403.CAB (YM561403.CAB)
    File: YO561403.CAB (YO561403.CAB)
    File: YS561401.CAB (YS561401.CAB)
    File: YT561401.CAB (YT561401.CAB)
    File: ZA561401.CAB (ZA561401.CAB)
    File: ZC561402.CAB (ZC561402.CAB)
    File: ZD561402.CAB (ZD561402.CAB)
    File: ZE561406.CAB (ZE561406.CAB)
    File: ZF561402.CAB (ZF561402.CAB)
    File: ZG561401.CAB (ZG561401.CAB)
    File: ZH561403.CAB (ZH561403.CAB)
    File: ZI561402.CAB (ZI561402.CAB)
    File: ZJ561401.CAB (ZJ561401.CAB)
    File: ZK561401.CAB (ZK561401.CAB)
    File: ZM561401.CAB (ZM561401.CAB)
    File: ZN561401.CAB (ZN561401.CAB)
    File: ZO561401.CAB (ZO561401.CAB)
    File: ZQ561401.CAB (ZQ561401.CAB)
    File: ZR561403.CAB (ZR561403.CAB)
    File: ZS561401.CAB (ZS561401.CAB)
    File: ZT561401.CAB (ZT561401.CAB)
    File: ZU561401.CAB (ZU561401.CAB)
    File: ZV561401.CAB (ZV561401.CAB)
    File: ZY561401.CAB (ZY561401.CAB)
    File: ZZ561401.CAB (ZZ561401.CAB)
    File: FILES\SETUP\SETUP.INI (PRO11.INI)
    File: SETUP.EXE (SETUP.EXE_1033)
    Using Local Cache Drive of already installed product: C:\.
    Found pre-existing download, will use this as default drive for local cache.
    Found enough space on drive "C:\" to cache all feature cabinets.
    (CDCACHE=AUTO) - There is enough space to cache some or all of the image. Drive for this download is C:\
    Already caching file: DW20.ADM_1033
    Already caching file: PSS10R.CHM_1033
    Already caching file: SETUP.CHM_1033
    Already caching file: SKU011.XML_0002_1033


    ==

    [quote name='HansV' post='794079' date='19-Sep-2009 14:46']Either the Office 2003 installation on your VM is munged, or there is a permissions problem if the "missing" registry values do exist but can't be read by Winword.[/quote]

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    I'm afraid this is too technical for me. I hope someone else will be able to help you.

  7. #7
    New Lounger
    Join Date
    Sep 2009
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Thanks anyway. I've appreciated your insights which have given me new avenues to investigate that I'd not thought of on my own.
    ===============
    Richard Lewis Haggard

    [quote name='HansV' post='794083' date='19-Sep-2009 15:47']I'm afraid this is too technical for me. I hope someone else will be able to help you.[/quote]

  8. #8
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,579
    Thanks
    5
    Thanked 1,057 Times in 926 Posts
    [quote name='haggard' post='794261' date='21-Sep-2009 08:42']Thanks anyway. I've appreciated your insights which have given me new avenues to investigate that I'd not thought of on my own.
    ===============
    Richard Lewis Haggard[/quote]

    Did everything work before you started using disk encryption?

    Have you tried disabling the disk encryption?

    Joe
    Joe

  9. #9
    New Lounger
    Join Date
    Sep 2009
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I'm not trying to fix the VM. I'm trying to understand the operations Word is attempting to accomplish and why Word thinks it needs to do them. We already know that there's some sort of unfortunate interaction between Pointsec and ourselves. The first step to fixing the problem is to understand what went wrong.

    [quote name='joeperez' post='794268' date='21-Sep-2009 10:04']Did everything work before you started using disk encryption?

    Have you tried disabling the disk encryption?

    Joe[/quote]

  10. #10
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,579
    Thanks
    5
    Thanked 1,057 Times in 926 Posts
    [quote name='haggard' post='794870' date='25-Sep-2009 08:40']I'm not trying to fix the VM. I'm trying to understand the operations Word is attempting to accomplish and why Word thinks it needs to do them. We already know that there's some sort of unfortunate interaction between Pointsec and ourselves. The first step to fixing the problem is to understand what went wrong.[/quote]

    I saw nothing in your prior posts that would show that Point sec is the culprit. That is why I asked the questions. If the installation worked properly before the disk encryption then you do have a place to look.

    As to ProcMon terminating, is there anything in the Application or System Event Log that is useful? Do you have the most current ProcMon? If you are interested in pursuing the use of Procmon you may want to visit Sysinternals Forums: Process Monitor and see if anyone there can help with the termination issue.

    Joe
    Joe

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •