Installation Server Compilation 1 to Compliation 2 ??

Is there a way to add the new 'Automatic Workstation Update Service' which is part of NW2004s Compilation 2 to an existing Compilation 1 server?
I don't want to do a full installation server update since Compilation 2 has SAPGui 7.10 at patch level 7 and our production environment is not ready to move to that yet.
Thanks!
Bob H

Five years later...  did you ever figure this out?

Similar Messages

  • Applying BW 3.50 patch 3 for sapgui 7.10 to a installation server

    Hi All
    Im applying a few patches to a 7.10 installation server, everything works fine , except for when applying the BW 3.50 patch 3 for 7.10 GUI to the server .. well applying the patch actually works , but afterwards instead of having only 2 products to choose from on the first hierarchy level (Business Explorer and SAP GUI for Windows 7.10), there is suddenly 6 products instead (SAPGUI for windows 7.10, Engineering client viewer, bw 3.5 addon, kw addon, tweak gui and business explorer).
    The real question is .. before applying the patches, I had a package called "complete" which included both available products, after applying 3.50 bw patch, the original package still contains the same two products, but is that adequate ?? or should a new package be created that includes ALL products available after the patch ?
    Or .... is the original package completely patched ??
    I have never before seen a patch apply additional products to the installation server ....
    /Kim

    Hi Kim Sonny,
    nice to hear from you ....
    Ok, please check the note
    #1131768  and
    #1155445 !
    I recommend you to set up a new installation server with the new compilation 3 CD of
    sapgui 710 ! And for this please look into the note #1266552
    Best Regards,
    Sven
    from primary support gsc austria ....

  • Installation Server and Windows 7 - Admin Rights Issue

    Here is a good one.  Completely reproducible error when granting Local Admin Rights by the LSH Service.
    For those with SAPGui Installation Server (SAPGui 7.20 Patch 6 or above) ... try this on a Windows 7 SP1 front end when you are NOT logged on with local admin rights.
      1) Open the Windows RUN dialog
      2) Type path to your installation server\setup\nwsapsetup.exe
      3) You should find the install wizard starts (granting local admin rights) as expected.
    NOW TRY THIS
      1) Type path to your installation server\setup\nwsapsetup.exe /uninstall
      2) You will find that you get a dialog about can't grant admin rights. Un-install will abort.
    This only appears to happen with the /uninstall switch!  Using /product= for example it will still grant admin rights.
    BIZZARE ...
    I've opened a Customer Support Message (Friday) priority - MEDIUM  have not heard back from SAP Support yet.
    Bob

    Jude,
    Thanks, it looks like that note has been getting a lot of update activity lately because the newly released Patch 8 has nwsapsetup.exe as version:  8.6.1.62   and that version also has the issue with the /nnnnnn switches. 
    I do have to say however, that this issue with nwsapsetup.exe and admin rights (requiring SapSetup.exe_Patch) first appeared with the release of Patch 6 for the Gui.  It was fixed for WinXP (I had a customer support message opened on this).  So why didn't anyone also test on Win7?
    Who is QA-ing these software releases? 
    Patch 8 had the same problem. 
    The change log for SapSetup.exe_Patch, is up to 8.1.6.70 now. 
    How are we in large enterprises to feel comfortable deploying any of this?
    End of rant ....
    Bob
    P.S. I really appreciate your presence here ... the tech assigned to my formal Support Message on the matter still has not gotten back advising of the updated release of SapSetup.exe_Patch. 
    Message: 0000746888
    Edited by: Bob Held on Sep 16, 2011 10:30 PM

  • Front End Installation Server - Administrator rights on client PC's

    We are using a third party repackaging tool to deploy sapgui to our workstations.  This has proven to be problematic in the past and are now considering the SAP Front End Installation server approach.
    After reveiwing the installation guide we are wondering about how packages are deployed to workstations.  Our users do not have administrator priveleges on thier workstations, so is it still possible to deploy packages from the installation server (either where they "pull" it down, or it is pushed down to them).
    This factor is one reason we are still using the third party repackaging tool because packages can be deployed under a "system" account (via a cleint agent on each PC) - in lieu of each user having administrator privelges on their workstations.
    If the SAP Installation server requires users to have these elevated priveleges it won't be an option for us.  Does anyone else have any experience with the Installation server and users who do not have administrator priveleges?
    Any feedback, directions, or links to additional resources would be greatly appreciated and happily rewarded with positive feedback and reward points
    thanks,
    jeff henke

    Hi Jeff. Try to download the SAPGUI 710 instguid. Go to http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000614745& in left press on 
    "SAP GUI for Windows" -->  7.10, download this file. In this Guide you can read about :
    Local security handling (LSH) lets users on the network deploy SAP front-end components on
    their front ends using NetWeaver SAPSetup without requiring administrative privileges on
    each front end. Regards.

  • SAPGUI 7.10 patch application to installation server.

    I set up SAPGUI 7.10 Installation server on windows. For 6.40,
    when applying frontend patches, we use to follow the below procedure:
    1) Log into service.sap.com.Click on Downloads.2) Click on support
    packages and patch 3) Click on entry by application group.4) Click on
    SAP Frontend Components 5) Click on SAPGUI for windows 6) Click on
    SAPGUI for windows 6.40 7) Click on win32 and download following
    patches BW 3.5 addon patch, sapgui for windows 6.40 patch and sapsetup
    for sapgui 6.40. 8) Once all the required patches are downloaded, next
    step is to create gui package using those patches. 9)Click on
    SAPADMIN.exe, click on apply patch and the patches are applied in the
    following order Setup patch, gui patch, BW patch. 10) Click on Browse
    and go to the folder where the above patches are located and select the
    patch that should be added to the package and click on open. 11) Then
    click on install.12) Then you can check the version of installed
    patches by click on View--> Server Monitor.
    I would like to know, what is the equivalent procedure for SAPGUI 7.10
    and where can I find document about it?

    Try this guide:
    http://www.id.uzh.ch/dl/sw/sap/SAPGUI/SAP_FE_Instguide_710.pdf

  • Installation Server Corruption when applying  a Patch

    I have setup a installation server with 7.10 gui.  I have twice tried to apply a patch, the first time bw350gui710_1 patch, the second time was the gui710_4 patch.  Both times my installation server was corrupted to the point where I had to delete it and rebuild it. 
    When I called NWSAPSETUPADMIN I got a System Invalid Cast Exception and it showed that I had no components on my installation server.

    Tried a few more times and it worked.

  • Cannot find the installer"server/Linux 64/DisK.. Erron on Informatica 8.6.1

    Hi Friends,
    I am trying to install Power Centre Informatica 8.6.1 (64 bit) on RHEL 5.4 (64 bit) and while invoking the installer i am getting the following error:
    cannot find the installer "server/Linux 64/Disk1/Instdata/VM/install.bin
    Please let me know the fix.
    Regards,
    DB

    Hi,
    This is the data mining forum so we don't have anything to offer for Informatica installation issues.
    I am not sure what forum to recommend given Informatica is not an Oracle product.
    You could try the data base general forum:
    General Database Discussions
    Thanks, Mark

  • 7.10 installation server, load balancing and multiple installation servers

    Hi
    In the 7.10 GUI installation server, there is no Load balancing option anamore, also there seems to be no option to easily clone the installation server from within the nwsapsetupadmin.exe program.
    If having MANY users at one location, and needing more than one installation server to accomodate the frontend installations, do you need to do this "manually" now ? grouping users and and the logon script directing different user groups to different sapgui installation servers ?
    what about creating multiple installation servers easily, is it possible to simply copy the installation server directory (c:\sapinst f.ex.) to another file server, share the directory and configure the DS and IS services (if needed) ??
    will configured packages and "on end install" scripts and such be copied too to the new installation server ?
    I need to easily create installation servers in 15 countries, this is the reason for my question...

    Hi Kim Sonny,
    hope you're doing fine
    Regarding your question:
    The "Load Balancing" was more a fail-over service and wasn't intended to use for several locations like in your case.
    So the easiest way to do this is to setup one installation server and copy the files to the other servers. On the new Installation servers you only have to setup the service again and that's it.
    Cheers,
    Martin

  • No update of Business Explorer 3.50 and SCM via Installation Server 6.40

    Dear all
    We use SAP Installation Server 6.40 to deploy SAP Front End 6.40 and updates. For new installations, target systems will get the latest version of SAP GUI 6.40 (PL 27), Business Explorer 3.50 (PL 13) and Supply Chain Management add-on (PL 6).
    On existing installations only SAP GUI will be patched resp. updated. Business Explorer 3.50 and Supply Chain Management add-on will not be patched by Installation Server. We have checked this by local installation of patch (patch level 13, your present patch level 4). What is going wrong? Has anyone a hint how I can solve this problem?
    Thanks
    PK

    Hi. I'm think first you need to chek this :
    Viewing the Log
    Use
    You can check the installation by viewing the log file sapsetup.log. The log file can be found in:
    • C:\WINDOWS\ under Windows XP
    • C:\WINNT\ under Windows 2000
    The most recent log has no number. The older logs are numbered. The higher the number, the older the log. Each time new log is generated, each of the log numbers is incremented by 1.
    Procedure
    1. Run saplogvw.exe from the server, to start the SAPSetup Log Viewer.
    2. Enter the path and filename of the log file.
    3. Choose Finish.
    The log file is displayed. Errors are colored red. Warnings are colored blue.
    Also run this in command line
    sapsetup.exe /check
    Regards.
    Edited by: Sergo Beradze on Apr 2, 2008 9:44 PM

  • Remote installation option for SAPsetup installation server  removed.

    Hi all,
    I have been using SAPsetup Installation Server for distributing SAPGUI 6.4. Many options with this version, remote installation and Load Balancing to name a couple right within SAPADMIN. I have put the latest version 7.10 on a test server and those options are no longer available. Also I don't even see and upgrade option, am I missing something? Is it possible to use the old installation server to push out the new SAPGUI, if so how?
    Thanks,
    Jeff

    Hello Jeff,
    the installation software for SAPGUI 7.10is completely new and you can't distribute a SAPGUI 7.10 with an Installation Serrver installed with the SAPGUI 6.40 CD.
    Regards, Martin

  • SAPGUI Installation Server Script - Commands Reference

    Hi
    I've been using SAPGUI Installation server for some time and it works fine, but now I would like to add some more functions to it. I've read the documentation about commands you can use in pre/post install and uninstall scripts but there aren't too many of them. What I would like is a list of all commands that can be used in such scripts.
    Hope to get some help
    Best Regards,
    Paweł

    Hello
    you find in the setup folder of the Sapgui cd the file named
    Installation Server Help.chm
    There is a chapter named
    Package Event Scripting Samples
    That's all
    Best Regards, Sven

  • Installing Solaris 11 on SunFIre T1000 With Automated Installer Server Fail

    h4. Hi
    h4. A few days i am try to intall solaris 11 11/11 on our server Sunfire T1000
    h4. we first upgrade the firmware of the server to
    sc> showhost
    Sun-Fire-T1000 System Firmware 6.7.12 2011/07/06 20:03
    Host flash versions:
    OBP 4.30.4.d 2011/07/06 14:27
    Hypervisor 1.7.3.c 2010/07/09 15:14
    POST 4.30.4.b 2010/07/09 14:25
    h4. And after we install Solaris 11 x86 on a laptop, in that we configure an AIS (Automated installer Server)
    installadm list
    Service Name Alias Of Status Arch Image Path
    default-sparc s11-sparc on Sparc /install/images/s11-sparc
    s11-sparc - on Sparc /install/images/s11-sparc
    h4. We are using the default installations with a DHCP server in the Laptop
    installadm list -m -p
    Service Name Manifest Status
    default-sparc orig_default Default
    s11-sparc orig_default Default
    h4. By the other side, in the sparc server (T1000) we use OBP for a WAN Boot Installation
    boot net:dhcp - installl
    2012-08-08 20:33:44,911 InstallationLogger DEBUG Starting Automated Installation
    2012-08-08 20:33:44,913 InstallationLogger INFO Using XML Manifest: /system/volatile/ai.xml
    2012-08-08 20:33:44,965 InstallationLogger INFO Using profile specification: /system/volatile/profile
    2012-08-08 20:33:45,018 InstallationLogger INFO Using service list file: /var/run/service_list
    2012-08-08 20:33:45,070 InstallationLogger INFO Starting installation.
    2012-08-08 20:33:45,122 InstallationLogger DEBUG Registering Manifest Parser Checkpoint
    2012-08-08 20:33:45,124 InstallationLogger DEBUG Engine registering:
    2012-08-08 20:33:45,126 InstallationLogger DEBUG name: manifest-parser
    2012-08-08 20:33:45,128 InstallationLogger DEBUG module_path: solaris_install.manifest.parser
    2012-08-08 20:33:45,129 InstallationLogger DEBUG checkpoint_class_name: ManifestParser
    2012-08-08 20:33:45,131 InstallationLogger DEBUG args: None
    2012-08-08 20:33:45,133 InstallationLogger DEBUG kwargs: {'call_xinclude': True, 'manifest': '/system/volatile/ai.xml', 'validate_from_docinfo': True}
    2012-08-08 20:33:45,135 InstallationLogger DEBUG insert_before: None
    2012-08-08 20:33:45,136 InstallationLogger DEBUG log_level: None
    2012-08-08 20:33:45,138 InstallationLogger DEBUG =============================
    2012-08-08 20:33:45,142 InstallationLogger DEBUG Current checkpoint list:
    2012-08-08 20:33:45,144 InstallationLogger DEBUG      manifest-parser
    2012-08-08 20:33:45,146 InstallationLogger DEBUG Executing Manifest Parser Checkpoint
    2012-08-08 20:33:45,148 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
    2012-08-08 20:33:45,150 InstallationLogger DEBUG Executing Engine Checkpoints...+
    2012-08-08 20:33:45,152 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
    2012-08-08 20:33:45,154 InstallationLogger DEBUG Engine will be executing following checkpoints:+
    2012-08-08 20:33:45,155 InstallationLogger DEBUG      manifest-parser
    2012-08-08 20:33:45,157 InstallationLogger DEBUG Spawning InstallEngine execution thread
    2012-08-08 20:33:45,160 InstallationLogger DEBUG Loading manifest-parser checkpoint
    2012-08-08 20:33:45,213 InstallationLogger.manifest-parser DEBUG Initializing ManifestParser (manifest=/system/volatile/ai.xml, Validate_from_docinfo=True, dtd_file=None, load_defaults=True, call_xinclude=True)
    2012-08-08 20:33:45,273 InstallationLogger DEBUG manifest-parser: prog est-1, prog ratio-0.95, total_ratio-1.00
    2012-08-08 20:33:45,275 InstallationLogger DEBUG Last checkpoint, manifest-parser: prog ratio 0.95
    2012-08-08 20:33:45,279 InstallationLogger DEBUG Snapshotting DOC to /var/run/install_engine/engine.MYk67H/.data_cache.manifest-parser
    2012-08-08 20:33:45,286 InstallationLogger DEBUG Executing manifest-parser checkpoint
    2012-08-08 20:33:45,288 InstallationLogger.manifest-parser DEBUG ManifestParser.execute(dry_run=False) called
    2012-08-08 20:33:45,290 InstallationLogger.manifest-parser DEBUG ManifestParser.parse(doc=-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)
         -> [persistent] (DataObjectCacheChild: persistent)
              -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)
         -> [volatile] (DataObjectCacheChild: volatile)
              -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)) called
    2012-08-08 20:33:45,292 InstallationLogger.manifest-parser DEBUG loading manifest (dtd_validation=True)
    2012-08-08 20:33:45,872 InstallationLogger.manifest-parser DEBUG Parsed XML document:
    <!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
    <auto_install>
    <ai_instance name="orig_default" auto_reboot="false">
    <target>
    <logical noswap="false" nodump="false">
    <zpool name="rpool" is_root="true" action="create">
    <filesystem name="export" mountpoint="/export" action="create" in_be="false"/>
    <filesystem name="export/home" action="create" in_be="false"/>
    <be name="solaris"/>
    </zpool>
    </logical>
    </target>
    <software type="IPS">
    <destination>
    <image action="create" index="false">
    <!-- Specify locales to install -->
    <facet set="false">facet.locale.*</facet>
    <facet set="true">facet.locale.en</facet>
    <facet set="true">facet.locale.en_US</facet>
    <facet set="true">facet.locale.es</facet>
    <facet set="true">facet.locale.es_ES</facet>
    </image>
    </destination>
    <source>
    <publisher name="solaris">
    <origin name="http://pkg.oracle.com/solaris/release"/>
    </publisher>
    </source>
    h4. When the installation precess is in this part
    13% target-selection completed.
    17% ai-configuration completed.
    19% target-instantiation completed.
    19% Beginning IPS transfer
    Creating IPS image
    Installing packages from:
    solaris
    origin: http://pkg.example.com/solaris/
    h4. in the install_log file show us this errors:
    2012-08-08 20:51:39,653 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/doctools ...
    2012-08-08 20:51:43,156 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/core-os ...
    2012-08-08 20:52:03,704 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/less ...
    2012-08-08 20:52:03,788 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/management/rad/module/rad-smf ...
    2012-08-08 20:52:03,835 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/library ...
    2012-08-08 20:52:30,609 InstallationLogger.generated-transfer-1184-1 DEBUG Cleaning up
    2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
    Traceback (most recent call last):
    File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
    checkpoint.execute(dry_run)
    File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 359, in execute
    self._transfer()
    File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 639, in _transfer
    self.api_inst.prepare()
    File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021, in prepare
    self._img.imageplan.preexecute()
    File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 2827, in preexecute
    p.download()
    File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 406, in download
    mfile.wait_files()
    File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 2857, in wait_files
    self._transport._get_files(self)
    File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 432, in wrapper
    return f(instance, fargs, *f_kwargs)
    File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1736, in getfiles
    self._get_files_list(mfile, filelist)
    File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1685, in getfiles_list
    raise tfailurex
    TransportFailures: 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
    2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
    3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
    4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
    5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
    6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
    7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
    8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
    2012-08-08 20:52:30,731 InstallationLogger DEBUG Checkpoints Completed: DOC:+
    -> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)+
         -> [persistent] (DataObjectCacheChild: persistent)+
              -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)+
              -> [Engine-DOC-Root-Node] (<solaris_install.engine.EngineData object at 0xecc930>)+
                   -> [manifest-parser] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee10d0>)+
                   -> [target-discovery] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1230>)+
                   -> [target-selection] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee12f0>)+
                   -> [ai-configuration] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1410>)+
                   -> [var-shared-dataset] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1c30>)+
                   -> [target-instantiation] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1750>)+
              -> [discovered] (<solaris_install.target.Target object at 0xee1330>)+
                   -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=False)+
                        -> [0] (Slice: name=0; action=preserve, force=False, is_swap=False, tag=2, flag=0, in_use={'used_by': ['exported_zpool'], 'used_name': ['rpool']}; size=148.99gb; start_sector=4768)+
                        -> [2] (Slice: name=2; action=preserve, force=False, is_swap=False, tag=5, flag=1; size=148.99gb; start_sector=0)+
                   -> [logical] (Logical: noswap=True; nodump=True)+
              -> [desired] (<solaris_install.target.Target object at 0xede3f0>)+
                   -> [logical] (Logical: noswap=False; nodump=False)+
                        -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=['c2t0d0s0'])+
                             -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                             -> [export/home] (Filesystem: name=export/home; action=create)+
                             -> [solaris] (BE: name=solaris; mountpoint=/a)+
                             -> [vdev] (Vdev: name=vdev; redundancy=none)+
                             -> [swap] (Zvol: name=swap; action=create; use=swap; size=1024m)+
                             -> [dump] (Zvol: name=dump; action=create; use=dump; size=512m)+
                             -> [var] (Filesystem: name=var; action=create; mountpoint=/var)+
                   -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=True)+
                        -> [0] (Slice: name=0; action=create, force=True, is_swap=False, tag=2, flag=0; in_zpool=rpool; in_vdev=vdev; size=148.99gb; start_sector=4768)+
         -> [volatile] (DataObjectCacheChild: volatile)+
              -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)+
              -> [orig_default] (ai_instance: name='orig_default' auto_reboot=False; http_proxy='None')+
                   -> [target] (<solaris_install.target.Target object at 0xee1d30>)+
                        -> [logical] (Logical: noswap=False; nodump=False)+
                             -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=[None])+
                                  -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                                  -> [export/home] (Filesystem: name=export/home; action=create)+
                                  -> [solaris] (BE: name=solaris)+
                   -> [generated-transfer-1184-1] (<solaris_install.transfer.info.Software object at 0xee1f30>)+
                        -> [transfer] (<solaris_install.transfer.info.IPSSpec object at 0xecc050>)+
                        -> [destination] (<solaris_install.transfer.info.Destination object at 0xecc0b0>)+
                             -> [image] (<solaris_install.transfer.info.Image object at 0xecc130>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc150>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc1b0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc210>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc270>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc2d0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc330>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc390>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc3f0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc450>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc4b0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc510>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc570>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc5d0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc630>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc690>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc6f0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc750>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc7b0>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc810>)+
                                  -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc870>)+
                                  -> [img_type] (<solaris_install.transfer.info.ImType object at 0xee1b70>)+
                        -> [source] (<solaris_install.transfer.info.Source object at 0xecc8b0>)+
                             -> [publisher] (<solaris_install.transfer.info.Publisher object at 0xecc8f0>)+
                                  -> [origin] (<solaris_install.transfer.info.Origin object at 0xecc910>)+
              -> [transfer-zpool-cache] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee18f0>)+
              -> [transfer-ai-files] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee15b0>)+
    2012-08-08 20:52:30,747 InstallationLogger DEBUG Checkpoints Completed: DOC (xml_format):
    <root>
    <target name="discovered">
    <disk whole_disk="false">
    <disk_name name="c2t0d0" name_type="ctd"/>
    <disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>
    <disk_keyword key="boot_disk"/>
    <slice name="0" action="preserve" force="false" is_swap="false">
    <size val="312456576secs" start_sector="4768"/>
    </slice>
    <slice name="2" action="preserve" force="false" is_swap="false">
    <size val="312461344secs" start_sector="0"/>
    </slice>
    </disk>
    <logical noswap="true" nodump="true"/>+
    </target>+
    <target name="desired">+
    <logical noswap="false" nodump="false">+
    <zpool name="rpool" action="create" is_root="true">+
    <filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
    <filesystem name="export/home" action="create" in_be="false"/>+
    <be name="solaris"/>+
    <vdev name="vdev" redundancy="none"/>+
    <zvol name="swap" action="create" use="swap">+
    <size val="1024m"/>+
    </zvol>+
    <zvol name="dump" action="create" use="dump">+
    <size val="512m"/>+
    </zvol>+
    <filesystem name="var" action="create" mountpoint="/var" in_be="true"/>+
    </zpool>+
    </logical>+
    <disk whole_disk="false">+
    <disk_name name="c2t0d0" name_type="ctd"/>+
    <disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>+
    <disk_keyword key="boot_disk"/>+
    <slice name="0" action="create" force="true" is_swap="false" in_zpool="rpool" in_vdev="vdev">+
    <size val="312456576secs" start_sector="4768"/>+
    </slice>+
    </disk>+
    </target>+
    <ai_instance auto_reboot="false" name="orig_default">+
    <target>+
    <logical noswap="false" nodump="false">+
    <zpool name="rpool" action="create" is_root="true">+
    <filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
    <filesystem name="export/home" action="create" in_be="false"/>+
    <be name="solaris"/>+
    </zpool>+
    </logical>+
    </target>+
    <software name="generated-transfer-1184-1" type="IPS">+
    <software_data>+
    <name>pkg:/entire@latest</name>+
    <name>pkg:/group/system/solaris-large-server</name>+
    </software_data>
    <destination>
    <image img_root="/a" action="create" index="False">
    <facet set="false">facet.locale.*</facet>
    <facet set="true">facet.locale.en</facet>
    <facet set="true">facet.locale.en_US</facet>
    <facet set="true">facet.locale.es</facet>
    <facet set="true">facet.locale.es_ES</facet>
    </image>
    </destination>
    <source>
    <publisher name="solaris">
    <origin name="http://pkg.oracle.com/solaris/release"/>
    </publisher>
    </source>
    </software>
    </ai_instance>
    </root>
    2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
    2012-08-08 20:52:30,803 InstallationLogger ERROR
    2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
    2012-08-08 20:52:30,907 InstallationLogger ERROR
    2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
    2012-08-08 20:52:31,012 InstallationLogger ERROR
    2012-08-08 20:52:31,064 InstallationLogger ERROR 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
    2012-08-08 20:52:31,117 InstallationLogger ERROR 2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
    2012-08-08 20:52:31,169 InstallationLogger ERROR 3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
    2012-08-08 20:52:31,222 InstallationLogger ERROR 4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
    2012-08-08 20:52:31,274 InstallationLogger ERROR 5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
    2012-08-08 20:52:31,326 InstallationLogger ERROR 6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
    2012-08-08 20:52:31,379 InstallationLogger ERROR 7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
    2012-08-08 20:52:31,431 InstallationLogger ERROR 8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
    2012-08-08 20:52:31,484 InstallationLogger ERROR
    2012-08-08 20:52:31,536 InstallationLogger INFO Automated Installation Failed. See install log at /system/volatile/install_log
    2012-08-08 20:52:31,588 InstallationLogger DEBUG Shutting down Progress Handler
    h4. Is something about:
    2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
    Traceback (most recent call last):
    File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
    checkpoint.execute(dry_run)
    2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
    2012-08-08 20:52:30,803 InstallationLogger ERROR
    2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
    2012-08-08 20:52:30,907 InstallationLogger ERROR
    2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
    h4. Somebody knows about this error?

    The chash failures indicate that either the repository you're using has corrupt content for those files, or the files are being corrupted on download. The latter is more likely, usually a result of badly-behaved http proxies.

  • Can't apply patch level 14 to installation server

    I'm trying to apply patch level 14 to the installation server using the nwsapsetupadmin tool.  I have installed previous patches with no problem, and I have just installed the Business Explorer patch with no problem.  But patch 14 for SAP GUI 7.10 fails.
    I click Patch Server.
    I select the patch. (gui710_14-10002995.exe)
    It extracts and validates the patch.
    I click Next to apply the patch.
    I see a splash screen and a black cmd window appears for a split second.
    Then nothing.  Here I should see a progress bar while the patch installs.
    Any ideas?
    Thanks.
    Tom

    Hello ALL...
    for the reason you must have a look in the NWSAPSETUPADMIN.log...
    Or you open an OSS MESSAGE in BC-FES-INS  and  attach there the log files from
    your installation server.
    Then i can have al ook at this and can support you.
    A possible reason is that the patch is already installed on the server...
    Or an exception is raised in the .NET framework...
    All is possible, but it is very hard to analyse without the logfiles.
    Best Regards, Sven

  • How to repair a 7.20 Installation Server ?

    hello all,
    i set up an 7.20 SAP Installation Server with PL4. It worked fine last month, no changes were made, but now, if i start NWSapSetupAdmin.exe nothing happens. What possibilities do i have to repair the server or to see which part causes trouble?
    Thanks in advance
    Alexander

    Hello,
    Check log file 'NwSapSetupAdmin.log' in folder C:\Program Files\SAP\SapSetup\LOGs. If log file is not created, check Windows Event Viewer (System events).
    Hope that helps.
    Regards,
    Martin

  • ECL Viewer on 2 different locations in the SAPGui Installation server

    I've installed the SP 13 of the SAPGui Installation Server.  Can anyone explain me why the ECL Viewer is installed 2 times in the SAPGui Installation server.  One time as a separate product and one as a General Add-On in the SAPGui 7.1 Product.  Doesn't this give any conflicts?  We are getting a dump for several transactions.  Is this due to this?
    Next to that I can't delete the ECL Viewer in the General add-on.
    Thanks for helping.

    Hm, you can check this from t-code SM04 (if one server) or SM51 and after on all servers.
    SM04 --> Change layout (CTRL+F8) --> Gui version add in Displayed Columns , after you will see all GUIs.
    SM51 --> select server --> User (CtrlShiftF7) after as  above.
    If you install the package on some PC, before installin sapsetup checks are this GUI installed or not(are the present package installed,are all components from package installed), and if it are installed finished installation.
    Regards.

Maybe you are looking for