Windows Installer on Windows 2008R2 Terminal Server

Home Forums Virtualization Terminal Services Windows Installer on Windows 2008R2 Terminal Server

This topic contains 4 replies, has 3 voices, and was last updated by Avatar Robert R. 9 years, 1 month ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Avatar
    Robert R.
    Participant
    #153321

    environment: psterm.dev.CO.TLD Windows 2008 R2 with Remote Desktop configured as Remote Desktop Server

    When attempting to install PeopleSoft on a Windows 2008 R2 terminal server, from the administrator command line, and setting change user /install , I get the following error messages:

    Workstation Configuration Error
    Error Copying File
    c:peoplesoftpt849SETUPPSODBC12420437.cpx
    to
    C:Windowssystem3212520437.cpx
    Access is denied.
    Please correct before installing workstation.

    and

    Workstation Configuration Error
    Error Copying File
    c:peoplesoftpt849SETUPPSODBC12520850.cpx
    to
    C:Windowssystem3212520850.cpx
    Access is denied.
    Please correct before installing workstation.

    and then a “Workstation Installation Complete” message, even though the application has not actually been installed.

    [IMG]http://forums.petri.com/attachment.php?attachmentid=4602&stc=1&d=1297383933[/IMG]

    I can copy the two files manually to C:WindowsSystem32

    In the event log, there is a

    Log Name: Application
    Source: MsiInstaller
    Date: 2/10/2011 4:34:38 PM
    Event ID: 1000
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: psterm.dev.CO.TLD
    Description:
    Windows Installer proxy information not correctly registered
    Event Xml:

    1000
    2
    0
    0x80000000000000

    1232
    Application
    psterm.dev.CO.TLD



    Windows Installer proxy information not correctly registered
    (NULL)
    (NULL)
    (NULL)
    (NULL)


    A search for Windows Installer proxy information not correctly registered” led me to the appropriate Tech Net page.

    Following Microsoft’s directions, I changed the value of

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesMSIServerImagePath

    from C:UsersrobertrAppDataLocalTempIXP000.TMPMsiExec.exe /V

    to C:WindowsSystem32MsiExec.exe /V

    rebooted the server into Safe Mode, and registered the service

    msiexec /regserver

    and rebooted back into normal mode.

    The path to the service in both the registry and Windows Installer service properties is now correct.

    [IMG]http://forums.petri.com/attachment.php?attachmentid=4600&stc=1&d=1297383933[/IMG]

    When I again attempted to run the PeopleSoft installation batch file, I got the same error message.

    Both the executable path in the Windows Installer service and the value of ImagePath in the registry were changed back to C:Users[username *]AppDataLocalTempIXP000.TMPMsiExec.exe /V

    * In the attached screen shots , I was logged in as the local administrator after rebooting back into normal mode.

    Why does the Windows Installer service keep reverting back to it’s previous setting of C:Users[username]AppDataLocalTempIXP000.TMPMsiExec.exe /V , in both the registry and the properties of the service, every time I try to run this installation?

    Avatar
    Ossian
    Moderator
    #183817

    Re: Windows Installer on Windows 2008R2 Terminal Server

    I would speak to PeopleSoft about this one — you will probably not be the first to install it on a TS.
    Moving the thread to the TS forum as well.

    Avatar
    Robert R.
    Participant
    #353171

    Re: Windows Installer on Windows 2008R2 Terminal Server

    PS

    In the System log there is another Windows Installer error (see below).

    Per Microsoft’s instructions, I unchecked the “Allow service to interact with desktop” box, but the results are the same.

    Log Name: System
    Source: Service Control Manager
    Date: 2/11/2011 8:57:36 AM
    Event ID: 7030
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: psterm.dev.CO.TLD
    Description:
    The Windows Installer service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
    Event Xml:

    7030
    0
    2
    0
    0
    0x8080000000000000

    4289

    System
    psterm.dev.CO.TLD

    Windows Installer

    Avatar
    yuval14
    Member
    #174546

    Re: Windows Installer on Windows 2008R2 Terminal Server

    Hi,

    I would advise to use Ossian recommendation and contact Peoplesoft support staff.

    Avatar
    Robert R.
    Participant
    #353172

    Re: Windows Installer on Windows 2008R2 Terminal Server

    To test whether this was a PeoleSoft problem or a Windows Installer problem, I attempted to install Office 2010 Professional, 32-bit edition, as a terminal service application.

    I got the following error (both from the Office installation wizard and in the event log):

    Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

    The Windows Installer settings in the service and registry were not altered, but there was definitely something wrong with the Windows Installer.

    After changing the registry value for HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesMSIServerWOW64 from 1 (the default) to 0, I was able to install Office without any problem.

    At this point, the Windows Installer was working correctly.

    An attempt to re-install PeopleSoft resulted in the same problems as above (failure, changing of Windows Installer settings), and changed the value of WOW64 from 0 back to 1.

    Since I was able to install other applications correctly (Office, and the Oracle 10g client without any problems beforehand), this definitely appears to be a PeopleSoft problem, and not a Windows problem.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.