[SOLVED] mkinitcpio error during kernel 2.6.37-6 package upgrade

After upgrading to kernel26-2.6.37-6-x86_64, I failed after reboot (couldn't mount root and got dropped to the "you're on your own" prompt). Fortunately, the fallback kernel worked. I didn't look into it at the time (it was late), and I noticed a new kernel package the next day, so I updated again thinking maybe it was a bug that got fixed. Nope. Same problem after reboot, but I paid a little more attention this time and saw the errors below:
sudo pacman -U kernel26-2.6.37.1-1-x86_64.pkg.tar.xz
...snip...
checking package integrity...
(1/1) checking for file conflicts [######################] 100%
(1/1) upgrading kernel26 [######################] 100%
>>> Updating module dependencies. Please wait ...
...snip...
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
...snip...
:: Generating module dependencies
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/drivers/ata/pata_acpi.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/lib/libcrc32c.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/crypto/crc32c.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/arch/x86/crypto/crc32c-intel.ko.gz: Exec format error
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
Since my root partition is btrfs, I require the libcrc32c module on load, and it looks like mkinitcpio couldn't manage to get it (and a few other modules) into my initrd. So I ran:
sudo /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
again by hand, and it worked without errors. (Yeah, I'm a sudo person, in case you were wondering.)
Here are the relevant /etc/mkinitcpio.conf lines:
MODULES="dm_mod dm_mirror btrfs crc32c libcrc32c"
HOOKS="base udev autodetect pata scsi sata dmraid lvm2 filesystems"
I don't know squat about mkinitcpio and why it would work fine when run by hand but choke when run via pacman. Anyone have any ideas?
Last edited by archix (2011-02-21 18:35:46)

According to Ryan Hill's comment on http://bugs.gentoo.org/show_bug.cgi?id=353907#c16 which is sending us to http://lwn.net/Articles/429345/  - it looks like ext4 is also impacted by this bug, not only compressed btrfs!
Chris Mason from Oracle (funny, "magical" coincidence ;P ) said he's got a patch for btrfs and hes testing it. Hope to see it soon...
Edit: ahhh here it is http://www.mail-archive.com/linux-btrfs … 08577.html
Edit2: patches were merged with today's (26.02.2011) mainline kernel snapshot: 2.6.38-rc6-git6
it seems to work fine for me, so i guess it's [SOLVED] now
Last edited by Vi0L0 (2011-02-26 15:51:46)

Similar Messages

  • [SOLVED] DHCP error during install due to multiple net cards

    Hello all,
    At the "Setup Network" option during the installation, I choose eth0. Then it asks if I want to use DHCP. I select 'Yes' but get
    Failed to run dhcpcd. See /dev/tty7 for details
    while polling for DHCP. So I press Alt+F7 and the details are
    eth0: dhcpcd 4.0.10 starting
    eth0: waiting for carrier
    eth0: timed out
    When I try to manually set it up (ie select 'No' when asked if I want to use DHCP), it asks for the following: IP address, submask, broadcast, Gateway (optional), DNS Server. Then it says "Network is configured" but I still can't download the packages.
    I have a Realtek RTL8139 Family PCI Fast Ethernet NIC card (not wireless) to a Linksys Router. I've set up DHCP on it for 5 users (only two being used). By the way I have WinXP on the same computer which accesses the network fine, and net access also worked during other distros' installation.
    Any clues? Thanks.
    Last edited by AMA (2009-05-11 13:17:53)

    ralvez wrote:OK. You  have an IP address, so that rules out a problem with your Nic card.
    Sorry I was maybe a little bit unclear on my previous post, but I'm pretty sure that I don't have an IP address during installation. I would like to add some precisions. Here are my observations:
    When I type ifconfig immediately after login (as root), it shows
    lo Link encap:Local loopback
    inet addr:127.0.0.1 Mask 255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Then when I run /arch/setup, Configure Network, answer 'Yes' to DHCP, and after the error message (the one on 1st post), ifconfig gives this (which clearly shows that I do NOT have an IP)
    eth0 Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    lo Link encap:Local loopback
    inet addr:127.0.0.1 Mask 255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Finally, when I answer 'No' to the DHCP question, and after I've entered my IP/Broadcast/Subnet Mask/DNS addresses, the result of ifconfig is the one on the previous post, that is
    eth0 Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
    inet addr:172.30.201.6 Bcast:172.30.201.255 Mask 255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    lo Link encap:Local loopback
    inet addr:127.0.0.1 Mask 255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    NB: I have entered the same addresses that I use normally (ie with Windows, the ones I see in cmd->ipconfig /all), but I could have entered whatever addresses I wanted. And I still don't have net access during install (ping does not return anything).
    Can you explain what are you doing to install Linux? Do you try to run the CD from within Windows or are you placing the CD in the CD bay and re-booting the machine and the CD fails?
    Of course I am booting the cd at startup (not within windows)! And the CD does not fail, or at least does not seem. Everything runs fine except the DHCP thing. So the problem is not the CD, but my computer. I'm finding a way to get DHCP working during the installation.

  • [solved] davtools - errors during compilation

    Most of the logs are here:
    http://www.archlinux.pastebin.com/671575
    Anyone has advices?

    Hm, i have a similar strange problem when I try to compile davtools:
    The first and maybe most important error is:
    make -C src/cdavl
    make[1]: Entering directory `/tmp/qpkg/src/davl-1.2.0/src/cdavl'
    make[1]: `cdavl' is up to date.
    make[1]: Leaving directory `/tmp/qpkg/src/davl-1.2.0/src/cdavl'
    make -C src/gdavl
    make[1]: Entering directory `/tmp/qpkg/src/davl-1.2.0/src/gdavl'
    gcc -DGTK2 -Wall -g -O `pkg-config --cflags --libs gtk+-2.0`  -o gdavl gdavl.c if.c
    /bin/sh: pkg-config: command not found
    The rest is similar to Mac1ek's errors:
    http://pastebin.com/673096
    I have already reinstalled libxrender... but i wasnt able to find a package with pkg-config...

  • Errors during Solaris 11/11 to 11.1 upgrade

    Hi,
    I originally resurrected a thread from 2012 and attempted to hijack it away for my own question. However, a kind forum moderator split it away to let it stand on its own since I wasn't trying to help that original post but was only concerned about my own system.
    Here's my post:
    #Am also trying to upgrade our local AI 11/11 server to 11.1 but finding similar errors. First I've updated our local 11/11 repo with SRU 13.4 and then updated the AI server's BE from this successfully
    root@sol11:~# beadm list
    BE                   Active Mountpoint Space  Policy Created         
    sol-11-1111-sru13_04 NR     /          39.91G static 2013-01-21 11:18
    solaris              -      -          7.50M  static 2011-12-09 09:15
    root@sol11:~# pkg list entire
    NAME (PUBLISHER)                                  VERSION                    IFO
    entire (solaris)                                  0.5.11-0.175.0.13.0.4.0    i--#Then trying to follow http://www.oracle.com/technetwork/articles/servers-storage-admin/howto-update-11dot1-ips-1866781.html
    root@sol11:~# pkg update --accept
    WARNING: pkg(5) appears to be out of date, and should be updated before
    running update.  Please update pkg(5) by executing 'pkg install
    pkg:/package/pkg' as a privileged user and then retry the update.
    root@sol11:~# pkg update pkg:/package/pkg
                Packages to remove:  1  
           Create boot environment: No
    Create backup boot environment: No
    PHASE                                        ACTIONS
    Removal Phase                                  13/13
    PHASE                                          ITEMS
    Package State Update Phase                       1/1
    Package Cache Update Phase                       1/1
    Image State Update Phase                         2/2 # DWL entire 11.1 ISO file from 11.jan 2013 and copied repo onto AI server and switched publisher to this repo:
    root@sol11:~# pkg publisher
    PUBLISHER                             TYPE     STATUS   URI
    local-solaris                                          
    solaris                               origin   online   file:///export/sol11.1_ipsrepo/
    root@sol11:~# pkg update --be-name s11.1ga --accept
    Creating Plan \                     
    pkg update: No solution was found to satisfy constraints
    Plan Creation: Package solver has not found a solution to update to latest available versions.
    This may indicate an overly constrained set of packages are installed.
    latest incorporations:
      pkg://solaris/consolidation/admin/[email protected],5.11-0.175.1.0.0.5.0:20111212T232623Z
      pkg://solaris/consolidation/l10n/[email protected],5.11-0.175.1.0.0.23.1134:20120820T154803Z
      pkg://solaris/consolidation/userland/[email protected],5.11-0.175.1.0.0.24.0:20120904T170613Z
      pkg://solaris/[email protected],5.11-0.175.1.0.0.24.2:20120919T190135Z
      pkg://solaris/consolidation/install/[email protected],5.11-0.175.1.0.0.24.1736:20120912T193249Z
      pkg://solaris/consolidation/sunpro/[email protected],5.11-0.175.1.0.0.19.0:20120625T151735Z
      pkg://solaris/consolidation/gfx/[email protected],5.11-0.175.1.0.0.5.0:20111212T232623Z
      pkg://solaris/consolidation/sfw/[email protected],5.11-0.175.1.0.0.5.0:20111212T232623Z
      pkg://solaris/consolidation/ips/[email protected],5.11-0.175.1.0.0.24.0:20120904T180327Z
      pkg://solaris/consolidation/ldoms/[email protected],5.11-0.175.1.0.0.21.1:20120723T182124Z
      pkg://solaris/consolidation/vpanels/[email protected],5.11-0.175.1.0.0.17.0:20120529T220223Z
      pkg://solaris/consolidation/dbtg/[email protected],5.11-0.175.1.0.0.15.0:20120501T214422Z
      pkg://solaris/consolidation/X/[email protected],5.11-0.175.1.0.0.24.1317:20120904T175757Z
      pkg://solaris/consolidation/man/[email protected],5.11-0.175.1.0.0.21.0:20120723T163455Z
      pkg://solaris/consolidation/desktop/[email protected],5.11-0.175.1.0.0.24.2:20120919T183843Z
      pkg://solaris/consolidation/nspg/[email protected],5.11-0.175.1.0.0.5.0:20111212T232623Z
      pkg://solaris/consolidation/sic_team/[email protected],5.11-0.175.1.0.0.5.0:20111212T230120Z
      pkg://solaris/consolidation/SunVTS/[email protected],5.11-0.175.1.0.0.14.0:20120416T200729Z
      pkg://solaris/consolidation/solaris_re/[email protected],5.11-0.175.1.0.0.24.3:20120919T185316Z
      pkg://solaris/consolidation/smcc/[email protected],5.11-0.175.1.0.0.5.0:20111212T232623Z
      pkg://solaris/consolidation/cns/[email protected],5.11-0.175.1.0.0.23.0:20120820T162238Z
      pkg://solaris/consolidation/cacao/[email protected],5.11-0.175.1.0.0.11.0:20120305T152551Z
      pkg://solaris/consolidation/osnet/[email protected],5.11-0.175.1.0.0.24.2:20120919T184141Z
      pkg://solaris/consolidation/desktop/[email protected],5.11-0.175.1.0.0.22.0:20120806T171142Z
    The following indicates why the system cannot update to the latest version:
      No suitable version of required package pkg://solaris/consolidation/userland/[email protected],5.11-0.175.1.0.0.24.0:20120904T170613Z found:
        Reject:  pkg://solaris/consolidation/userland/[email protected],5.11-0.175.1.0.0.24.0:20120904T170613Z
        Reason:  A version for 'incorporate' dependency on pkg:/network/dns/[email protected],5.11-0.175.1.0.0.24.0 cannot be found*# Why and how to resolve this issue?*
    *#TIA*
    #Just in case you ask:
    root@sol11:~# pkg info entire
    Name: entire
    Summary: entire incorporation including Support Repository Update (Oracle Solaris 11 11/11 SRU 13.4).
    Description: This package constrains system package versions to the same
    build. WARNING: Proper system update and correct package
    selection depend on the presence of this incorporation.
    Removing this package will result in an unsupported system. For
    more information see https://support.oracle.com/CSP/main/article
    ?cmd=show&type=NOT&doctype=REFERENCE&id=1372094.1.
    Category: Meta Packages/Incorporations
    State: Installed
    Publisher: solaris
    Version: 0.5.11 (Oracle Solaris 11 SRU 13.4)
    Build Release: 5.11
    Branch: 0.175.0.13.0.4.0
    Packaging Date: November 6, 2012 07:46:23 PM
    Size: 5.45 kB
    FMRI: pkg://solaris/[email protected],5.11-0.175.0.13.0.4.0:20121106T194623Z
    root@sol11:~# pkg info consolidation/osnet/osnet-incorporation
    Name: consolidation/osnet/osnet-incorporation
    Summary: OS/Net consolidation incorporation
    Description: This incorporation constrains packages from the OS/Net
    consolidation.
    Category: Meta Packages/Incorporations
    State: Installed
    Publisher: solaris
    Version: 0.5.11
    Build Release: 5.11
    Branch: 0.175.0.13.0.4.1
    Packaging Date: November 6, 2012 07:31:22 PM
    Size: 17.15 kB
    FMRI: pkg://solaris/consolidation/osnet/[email protected],5.11-0.175.0.13.0.4.1:20121106T193122Z

    Yes also indicated previously, only I found that I also needed to remove two more packages before upgrading successfully, see below.
    Thanks for your reply!
    Removing installadm pkg along made it possible to upgrade from 11/11-SRU13-4 to 11.1...
    root@sol11:~# pkg uninstall pkg:/service/network/dhcp/isc-dhcp pkg://solaris/install/installadm
    Packages to remove: 2
    Create boot environment: No
    Create backup boot environment: No
    Services to change: 3
    PHASE ACTIONS
    Removal Phase 166/166
    PHASE ITEMS
    Package State Update Phase 2/2
    Package Cache Update Phase 2/2
    Image State Update Phase 2/2
    The following unexpected or editable files and directories were
    salvaged while executing the requested package operation; they
    have been moved to the displayed location in the image:
    var/db/isc-dhcp/dhcpd4.leases~ -> /var/pkg/lost+found/var/db/isc-dhcp/dhcpd4.leases~-20130122T143604Z
    var/db/isc-dhcp/dhcpd4.leases -> /var/pkg/lost+found/var/db/isc-dhcp/dhcpd4.leases-20130122T143604Z
    root@sol11:~# pkg update be-name s11.1ga accept
    Package: pkg://solaris/consolidation/osnet/[email protected],5.11-0.175.1.0.0.24.2:20120919T184141Z
    License: usr/src/pkg/license_files/lic_OTN
    Packages to remove: 10
    Packages to install: 40
    Packages to update: 415
    Mediators to change: 2
    Create boot environment: Yes
    Create backup boot environment: No
    DOWNLOAD PKGS FILES XFER (MB)
    Completed 465/465 24964/24964 445.9/445.9
    PHASE ACTIONS
    Removal Phase 9898/9898
    Install Phase 18235/18235
    Update Phase 14665/14665
    PHASE ITEMS
    Package State Update Phase 878/878
    Package Cache Update Phase 424/424
    Image State Update Phase 2/2
    A clone of sol-11-1111-sru13_04 exists and has been updated and activated.
    On the next boot the Boot Environment s11.1ga will be
    mounted on '/'. Reboot when ready to switch to this updated BE.
    NOTE: Please review release notes posted at:
    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=1372094.1
    # reinstall earlier removed pkg
    root@sol11:~# pkg install pkg:/service/network/dhcp/isc-dhcp pkg://solaris/install/installadm pkg://solaris/network/dns/bind pkg://solaris/service/network/dns/bind
    Packages to install: 4
    Create boot environment: No
    Create backup boot environment: No
    Services to change: 3
    DOWNLOAD PKGS FILES XFER (MB) SPEED
    Completed 4/4 128/128 4.5/4.5 0B/s
    PHASE ITEMS
    Installing new actions 286/286
    Updating package state database Done
    Updating image state Done
    Creating fast lookup database Done
    root@sol11:~# pkg list entire
    NAME (PUBLISHER) VERSION IFO
    entire (solaris) 0.5.11-0.175.1.0.0.24.2 i--

  • Error during AddOn Creation using Xcelius AddOn Packager ver 2.1

    Hi,
    I get the following error when I try to build my add on usng the addon manager. Does anyone has a solution for this?
    Regards,
    bala.
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    Exception Text **************
    System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
       at Packager.Util.OpenArchive(String filename, Int32 mode)
       at Packager.Package.generateXLX(String filename)
       at Packager.MainForm.buildToolStripButton_Click(Object sender, EventArgs e)
       at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
       at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ToolStrip.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    Packager
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files%20(x86)/Business%20Objects/Xcelsius/SDK/Packager.exe
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Hi,
    I get the following error when I try to build my add on usng the addon manager. Does anyone has a solution for this?
    Regards,
    bala.
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    Exception Text **************
    System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
       at Packager.Util.OpenArchive(String filename, Int32 mode)
       at Packager.Package.generateXLX(String filename)
       at Packager.MainForm.buildToolStripButton_Click(Object sender, EventArgs e)
       at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
       at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ToolStrip.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    Packager
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files%20(x86)/Business%20Objects/Xcelsius/SDK/Packager.exe
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

  • Error during execution in background: No Test Package Selected

    We have created a test package and tried to run both in foreground (Goto -> Automatic Test -> Execute) and background (Goto -> Automatic Test -> Execute in background). We are pretty confident that the test case included in the package works well.
    Foreground run is successful. However, when we try to run using background mode, we get the error "No Test Package Selected." What could be the possible issue for this?

    Unsigned applets are not allowed to access the file system...
    http://java.sun.com/developer/technicalArticles/Security/Signed/

  • Process Chain error during info package execution

    I'm trying to load master data into 0CURTYPE using process chain.
    I have created a start process and included the info package and corresponding DTP in the chain to load master data into the info object.
    On scheduling the process chain I get an error during the execution of the info package
    "Could not find code page for receiving system
    For the logical destination Q4900CL010, you want to determine the code page in which the data is sent with RFC. However, this is not currently possibe, and the IDoc cannot yet be dispatched."
    Is it relatred to some setting whihc I have missed out?
    Any help on this please?
    Thanks,

    Hi, this is a issue related to idocs in the source....
    U can contact ur BASIS team to solve this...
    From their end they have to chk the unprocessed/errored idocs in BD87...
    this issue belongs to source...
    They have to run a report:RBDAGAIN  to process the errore idoc's in the source which are in STATUS:'02'.
    This is a solution for temporarilrly basis...
    if this occurs regularly they have to change the settings in SM59..
    refer exact note for this: 784381
    rgds,

  • Error: no kernel source files found

    Trying install avira- it need's Dazuko. Installing Dazuko (yaourt -S dazuko):
    error: no kernel source files found
    Help please
    Last edited by litemotiv (2010-08-25 11:30:31)

    The package build points to a directory that doesn't exist:
    kernel source in /lib/modules/2.6.34-ARCH/source... no
    kernel build source in /lib/modules/2.6.34-ARCH/build... no
    kernel build source in /usr/src/linux... no
    kernel source in /usr/src/linux... no
    error: no kernel source files found
    This package hasn't been updated for almost 2½ years, you will have to report this to the package maintainer: http://aur.archlinux.org/packages.php?ID=3779

  • Detect some error during PININST_BB​V. [SOLVED]

    I have a HP 2000-2b16NR that needed a new HDD. I ordered and just received the Recovery DVD's for this model from HP and after 5 times running the HP recovery I get this error message.
    ChkErrBB.CMD : Detect some error during PININST_BBV.
    ChkErrBB.CMD : Check c:\system.sav\logs\BurnBootWarn.log
    ChkErrBB.CMD : or, check c:\system.sav\logs\BurnBootMerge.log
    I've already tried defaulting the BIOS like suggested in another thread for this error with no joy.  I even pulled the CMOS Battery and removed the Main Batt/Power as well.
    Searched the HDD for these two log files BurnBootWarn.log  and BurnBootMerge.log and they do not exist in c:\system.sav\logs. However did find this one in there BurnBootMergeBBV1.log.
    Replacement HDD is a HGST Travelstar H2IK500854SP 500GB / 5400RPM / 8MB Cache
    I suspect that one of the DVD's is bad or HP's Recovery Process is utter cr@p!
    RESOLVED: Seems the Supplemental Disk is bad.  Ran recovery skipping the Supplemental Disk and all is fine.
    This question was solved.
    View Solution.

    Thanks! That worked great.

  • During upgrade I've had ERROR FATAL: kernel too old

    I'm using a recompiled kernel 2.6, today I've upgraded my archlinux (like all days), but during it, I've had an error:
    FATAL: kernel too old
    Rebooting my computer, now I can't login on my archlinux, infact I've kernel panic (using default kernel). If instead I use my recompiled kernel, I can login, but wifi device is not more known, kde doesn't start more, nvidia drivers doesn't work. So it's impossible to login.
    I've the same problem on another computer where I've archlinux with a recompiled kernel 2.6
    Anyone has had the same problem or can show me a resolution ?
    Please, I don't want reinstall completely Archlinux, infact I've it from 2 years and half on one computer, and from 1 year and half in the other.
    Thanks.

    Or prolly wiser would be to install the latest arch kernel...

  • [Solved] 'New' error messages during init after updating initscripts

    After updating to the latest initscripts, I got some error messages during init that I hadn't seen before.  They occurred during one of the UDev steps, and were caused by an attempt to load an IDE module despite the controller being disabled.  The controller shows up in Windows devmgr too, so I guess it's a failing of the mobo or BIOS.
    In any case, I downgraded and found that the errors were nothing new.  I'm just curious if the appearance of the errors during init was by design or a happy accident.
    Last edited by alphaniner (2011-08-01 17:07:30)

    alphaniner wrote:
    karol wrote:If you have the new (i.e. current) initscripts, you should be fine:
    http://projects.archlinux.org/initscrip … 328fbaf2e7
    http://projects.archlinux.org/initscrip … 42dfeca8c2
    I had never noticed the file before yesterday, actually. And I'm up-to-date, yet it's still full of 'em.
    You need to reboot.
    After you do, run
    tail /var/log/boot
    Mine isn't perfect, but I've already sent an e-mail to the dev (it's a matter of just a sed oneliner)
    [karol@black ~]$ tail /var/log/boot
    Tue Aug 2 05:03:01 2011: :: Setting Hostname: black ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Setting Locale: pl_PL.UTF-8 ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Setting Consoles to UTF-8 mode ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Loading Keyboard Map: pl ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: :: Loading Console Font: Lat2-Terminus16 ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: :: Saving dmesg Log ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: INIT: Entering runlevel: 3
    Tue Aug 2 05:03:02 2011: :: Starting Syslog-NG ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:03 2011: :: Starting D-BUS system messagebus ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:04 2011: :: Starting acpid ^[[171G [BKGD] :: Starting gpm ^[[171G [BKGD^[[0;1

  • [SOLVED] Error during boot, need help to identify

    I've noticed recently that I'm getting an error during (taken from dmesg)
    [    7.982440] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
    [    7.982865] DRM: Fill_in_dev failed.
    can anyone tell me where this is coming from and how to fix it maybe? I have a Intel i7-2600K (Ivy Bridge generation) with a Nvidia GTX 580 card using the propriatary driver.
    Last edited by fettouhi (2014-11-20 21:28:04)

    BTW, if your processor really is an i7-2600k, that would make it a Sandy Bridge (2nd gen) processor, not an Ivy Bridge (3rd gen and starts with a '3').  Unless this is just a typo, knowing this might help you debug things in the future, as there are unfortunately bugs that affect some 2nd but not 3rd gen procssors, and vice-versa.

  • [SOLVED] Error during update of LUKS header on device ./file

    dd if=/dev/zero of=./file bs=1M count=200
    cryptsetup luksFormat -s 512 -c aes-xts-plain64 -h sha512 ./file
    WARNING!
    ========
    This will overwrite data on ./file irrevocably.
    Are you sure? (Type uppercase yes): YES
    Enter LUKS passphrase:
    Verify passphrase:
    Error during update of LUKS header on device ./file.
    This only happens on my 1TB HDD (GPT, xfs filesystem).  I have 2 SSDs that do not throw the error. 
    I tested using a flash drive formatted as GPT and using xfs filesystem and it worked.
    Ideas?
    Last edited by not_sure (2013-03-01 02:50:32)

    Hmm... I didn't know you could do that. Are you sure it can? https://wiki.archlinux.org/index.php/Di … ison_table
    I thought dm-crypt basically did block level encryption.
    I guess this is a "virtual partition"? Maybe https://www.linux.com/community/blogs/1 … nux/280174 helps? It seems to mount it as loopback prior to encryption?
    Last edited by cfr (2013-03-01 01:07:16)

  • Error during application of stack

    Hi all,
    I am applying the stack using JSPM.
    I got an error
    An error occured during execution of JSPM_PROCESS Phase.
    java.lang.StringIndexOutOfBoundsException: String index out of range: -9
    Provide me solution to solve this error.

    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\NW7\DVEBMGS01\j2ee\JSPM\log\log_20071231170532\JSPM_PROCESS_1_01.LOG]/>
    <!PATTERN[JSPM_PROCESS_1_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC1A1C5000000000001401AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#JSPM/JSPMPhases/JSPM_PROCESS#
    #1.5#C000AC1A1C5000000000001501AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.jspm.phases.PhaseTypeJSPM#
    #1.5#C000AC1A1C5000000000001601AB28FE0004429371744A78#1199100937915#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#Java###Starting Initialize dialog...##
    #1.5#C000AC1A1C5000000000001C01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#Java###Initializing JSPM data model...##
    #1.5#C000AC1A1C5000000000001D01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#Java###Detected profile directory .#1#C:
    usr
    sap
    NW7
    SYS
    profile#
    #1.5#C000AC1A1C5000000000001E01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    config
    DBINFO.XML#
    #1.5#C000AC1A1C5000000000001F01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#3#com.sap.sdt.dmt.main.DMT#
    #1.5#C000AC1A1C5000000000002001AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2#  #C:
    j2sdk1.4.2_13
    jre
    bin
    java.exe -cp .;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    sdt_dmt.jar;C:/sapdb/programs/runtime/jar/sapdbc.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    jddi.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    opensqlsta.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    tc_sec_secstorefs.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    frame.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    exception.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    logging.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    jperflib.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    util.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    tc_sec_secstorefs.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    exception.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    logging.jar;C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    lib
    opensqlsta.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    engine
    iaik_jce.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    engine
    info
    IAIKSecurityFS.list;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    iaik_jce.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    iaik_jsse.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    iaik_smime.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    iaik_ssl.jar;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    info
    IAIKSecurityFS.list;
    CP-CHN-3F-029
    sapmnt
    NW7
    SYS
    global
    security
    lib
    tools
    w3c_http.jar com.sap.sdt.dmt.main.DMT -rootdir=C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM -descriptor=cp-chn-3f-029_NW7 -logfile=DMT_01.LOG dbinfo C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    config
    DBINFO.XML#
    #1.5#C000AC1A1C5000000000002101AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    log
    log_20071231170532
    DMT_01.LOG_01.OUT#
    #1.5#C000AC1A1C5000000000002201AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#3#
    #1.5#C000AC1A1C5000000000002301AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#3#java.exe#
    #1.5#C000AC1A1C5000000000002401AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#3#java.exe#0#
    #1.5#C000AC1A1C5000000000002501AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
    #1.5#C000AC1A1C5000000000002601AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#C:
    usr
    sap
    NW7
    SYS
    profile
    DEFAULT.PFL#
    #1.5#C000AC1A1C5000000000002701AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#SCS00#C:
    usr
    sap
    NW7
    SYS
    profile
    NW7_SCS00_CP-CHN-3F-029#C:
    usr
    sap
    NW7
    SYS
    profile
    START_SCS00_CP-CHN-3F-029#CP-CHN-3F-029#
    #1.5#C000AC1A1C5000000000002801AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#DVEBMGS01#C:
    usr
    sap
    NW7
    SYS
    profile
    NW7_DVEBMGS01_CP-CHN-3F-029#C:
    usr
    sap
    NW7
    SYS
    profile
    START_DVEBMGS01_CP-CHN-3F-029#CP-CHN-3F-029#
    #1.5#C000AC1A1C5000000000002901AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#Java###SCS is local, so this is not a High Availability system.##
    #1.5#C000AC1A1C5000000000002A01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#4#sappfpar#
    #1.5#C000AC1A1C5000000000002B01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EPS_ROOT#
    #1.5#C000AC1A1C5000000000002C01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_01.out#
    #1.5#C000AC1A1C5000000000002D01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#4#
    #1.5#C000AC1A1C5000000000002E01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#4#sappfpar#
    #1.5#C000AC1A1C5000000000002F01AB28FE0004429371ED3398#1199100945839#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#4#sappfpar#0#
    #1.5#C000AC1A1C5000000000003001AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#5#sappfpar#
    #1.5#C000AC1A1C5000000000003101AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 SAPSYSTEM#
    #1.5#C000AC1A1C5000000000003201AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_20.out#
    #1.5#C000AC1A1C5000000000003301AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#5#
    #1.5#C000AC1A1C5000000000003401AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#5#sappfpar#
    #1.5#C000AC1A1C5000000000003501AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#5#sappfpar#0#
    #1.5#C000AC1A1C5000000000003601AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#6#sappfpar#
    #1.5#C000AC1A1C5000000000003701AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 INSTANCE_NAME#
    #1.5#C000AC1A1C5000000000003801AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_21.out#
    #1.5#C000AC1A1C5000000000003901AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#6#
    #1.5#C000AC1A1C5000000000003A01AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#6#sappfpar#
    #1.5#C000AC1A1C5000000000003B01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#6#sappfpar#0#
    #1.5#C000AC1A1C5000000000003C01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#7#sappfpar#
    #1.5#C000AC1A1C5000000000003D01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EXECUTABLE#
    #1.5#C000AC1A1C5000000000003E01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_22.out#
    #1.5#C000AC1A1C5000000000003F01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#7#
    #1.5#C000AC1A1C5000000000004001AB28FE00044293723C22A0#1199100951012#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#7#sappfpar#
    #1.5#C000AC1A1C5000000000004101AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#7#sappfpar#0#
    #1.5#C000AC1A1C5000000000004201AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#8#sappfpar#
    #1.5#C000AC1A1C5000000000004301AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_CT_RUN#
    #1.5#C000AC1A1C5000000000004401AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_23.out#
    #1.5#C000AC1A1C5000000000004501AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#8#
    #1.5#C000AC1A1C5000000000004601AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#8#sappfpar#
    #1.5#C000AC1A1C5000000000004701AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#8#sappfpar#0#
    #1.5#C000AC1A1C5000000000004801AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#9#sappfpar#
    #1.5#C000AC1A1C5000000000004901AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 jstartup/vm/home#
    #1.5#C000AC1A1C5000000000004A01AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_24.out#
    #1.5#C000AC1A1C5000000000004B01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#9#
    #1.5#C000AC1A1C5000000000004C01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#9#sappfpar#
    #1.5#C000AC1A1C5000000000004D01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#9#sappfpar#0#
    #1.5#C000AC1A1C5000000000004E01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#10#sappfpar#
    #1.5#C000AC1A1C5000000000004F01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 SAPSYSTEM#
    #1.5#C000AC1A1C5000000000005001AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_01.out#
    #1.5#C000AC1A1C5000000000005101AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#10#
    #1.5#C000AC1A1C5000000000005201AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#10#sappfpar#
    #1.5#C000AC1A1C5000000000005301AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#10#sappfpar#0#
    #1.5#C000AC1A1C5000000000005401AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#11#sappfpar#
    #1.5#C000AC1A1C5000000000005501AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 INSTANCE_NAME#
    #1.5#C000AC1A1C5000000000005601AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_25.out#
    #1.5#C000AC1A1C5000000000005701AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#11#
    #1.5#C000AC1A1C5000000000005801AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#11#sappfpar#
    #1.5#C000AC1A1C5000000000005901AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#11#sappfpar#0#
    #1.5#C000AC1A1C5000000000005A01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#12#sappfpar#
    #1.5#C000AC1A1C5000000000005B01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_EXECUTABLE#
    #1.5#C000AC1A1C5000000000005C01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_26.out#
    #1.5#C000AC1A1C5000000000005D01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#12#
    #1.5#C000AC1A1C5000000000005E01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#12#sappfpar#
    #1.5#C000AC1A1C5000000000005F01AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#12#sappfpar#0#
    #1.5#C000AC1A1C5000000000006001AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#13#sappfpar#
    #1.5#C000AC1A1C5000000000006101AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_CT_RUN#
    #1.5#C000AC1A1C5000000000006201AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_27.out#
    #1.5#C000AC1A1C5000000000006301AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#13#
    #1.5#C000AC1A1C5000000000006401AB28FE00044293733F1F68#1199100967985#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#13#sappfpar#
    #1.5#C000AC1A1C5000000000006501AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#13#sappfpar#0#
    #1.5#C000AC1A1C5000000000006601AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#14#sappfpar#
    #1.5#C000AC1A1C5000000000006701AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2#  #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 rdisp/msserv_internal#
    #1.5#C000AC1A1C5000000000006801AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2#  #C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    tmp
    Sappfpar_28.out#
    #1.5#C000AC1A1C5000000000006901AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#14#
    #1.5#C000AC1A1C5000000000006A01AB28FE00044293736A4648#1199100970813#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#14#sappfpar#
    #1.5#C000AC1A1C5000000000006B01AB28FE0004429373953678#1199100973627#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#14#sappfpar#0#
    #1.5#C000AC1A1C5000000000006C01AB28FE00044293739B6868#1199100974033#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#Java###JSPM data model has been initialized.##
    #1.5#C000AC1A1C5000000000006D01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#Java###Initialize dialog has been processed.##
    #1.5#C000AC1A1C5000000000006E01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#Java###Starting dialog...#1#LogIn#
    #1.5#C000AC1A1C5000000000007701AB28FE00044293754DE6E0#1199101002508#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#Java###Dialog has been confirmed by the user.#1#LogIn#
    #1.5#C000AC1A1C5000000000007801AB28FE00044293754EDCF8#1199101002571#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#Java###Checking connectivity for SDM server on host , port ...#2#CP-CHN-3F-029#50118#
    #1.5#C000AC1A1C5000000000007901AB28FE0004429375703FD8#1199101004759#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#Java###Connection to SDM server on host , port is valid.#2#CP-CHN-3F-029#50118#
    #1.5#C000AC1A1C5000000000007A01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#Java###Detecting kernel exchange directory of the J2EE Engine...##
    #1.5#C000AC1A1C5000000000007B01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#Java###You can find additional information in log file $.#1#C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    log
    log_20071231170532
    KERNEL_DETECTION_01.LOG#
    #1.5#C000AC1A1C5000000000008901AB28FE0004429375A0AA60#1199101007932#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#Java###Parameter DIR_CT_RUN from with value will be used as target directory for unicode kernel update.#2#NW7_DVEBMGS01_CP-CHN-3F-029#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
    #1.5#C000AC1A1C5000000000008A01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcd#
    #1.5#C000AC1A1C5000000000008B01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
    #1.5#C000AC1A1C5000000000008C01AB28FE0004429375A3FDF0#1199101008150#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
    #1.5#C000AC1A1C5000000000008D01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcdcontent#
    #1.5#C000AC1A1C5000000000008E01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
    #1.5#C000AC1A1C5000000000008F01AB28FE0004429375A7CE80#1199101008400#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
    #1.5#C000AC1A1C5000000000009001AB28FE0004429375AAEB60#1199101008604#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#Java###Parsing of file and extracting the relative deployment data model has finished.#1#C:/usr/sap/NW7/DVEBMGS01/j2ee/JSPM/config/dodf.xml#
    #1.5#C000AC1A1C5000000000009101AB28FE0004429375AE7D70#1199101008838#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#Java###Receiving information about deployed J2EE Engine components...##
    #1.5#C000AC1A1C5000000000009201AB28FE0004429375B19668#1199101009041#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#Java###A valid SQL data source for is obtained.#1#jdbc/pool/NW7#
    #1.5#C000AC1A1C5000000000009301AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#Java###API to the system component version tables has been obtained.##
    #1.5#C000AC1A1C5000000000009401AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#Java###System component version tables will be synchronized with SDM repository.##
    #1.5#C000AC1A1C5000000000009501AB28FE0004429375D2BEB0#1199101011214#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113651.log#
    #1.5#C000AC1A1C5000000000009601AB28FE000442937BD618E8#1199101112097#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113832.log#
    #1.5#C000AC1A1C5000000000009701AB28FE000442937BD65768#1199101112113#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#Java###Access to SDM repository has been obtained. Start to read SDM repository content.##
    #1.5#C000AC1A1C5000000000009801AB28FE000442937BD9E978#1199101112347#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#Java###Data about components deployed on the engine is obtained from SDM repository.##
    #1.5#C000AC1A1C5000000000009901AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#JLOGVIEW#sap.com#
    #1.5#C000AC1A1C5000000000009A01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C5000000000009B01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C5000000000009C01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C5000000000009D01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C5000000000009E01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C5000000000009F01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C500000000000A001AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C500000000000A101AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
    #1.5#C000AC1A1C500000000000A201AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#Java###Data from SDM repository has been read.##
    #1.5#C000AC1A1C500000000000A301AB28FE000442937C8D7A38#1199101124115#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#Java###Information about deployed J2EE Engine components has been received.##
    #1.5#C000AC1A1C500000000000A401AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#Java###Retrieving SDM version by parsing ...#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/version.txt#
    #1.5#C000AC1A1C500000000000A501AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#Java###SDM version with release , SP level , patch level found in .#5#SAP_JAVASL#7.00#06#0#C:/usr/sap/NW7/DVEBMGS01/SDM/program#
    #1.5#C000AC1A1C500000000000A601AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#Java###Looking for system kernel(s) under directory .#1#C:
    usr
    sap
    NW7
    SYS
    exe#
    #1.5#C000AC1A1C500000000000A701AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#Java###Central instance kernel directory is .#1#C:
    usr
    sap
    NW7
    SYS
    exe
    uc
    NTI386#
    #1.5#C000AC1A1C500000000000A801AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#Java###Starting searching for kernel version in directory ...#1#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
    #1.5#C000AC1A1C500000000000A901AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#Java###You can find additional information in log file .#1#C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    log
    log_20071231170532
    KERNEL_DETECTION_02.LOG#
    #1.5#C000AC1A1C500000000000B701AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#Java###Kernel with release , SP level , patch level found in .#5#SAP KERNEL UNICODE WINDOWS_I386#7.00#52#0#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
    #1.5#C000AC1A1C500000000000B801AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#Java###SCS kernel directory is .#1#C:
    usr
    sap
    NW7
    SYS
    exe
    uc
    NTI386#
    #1.5#C000AC1A1C500000000000B901AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#Java###Login dialog has been processed.##
    #1.5#C000AC1A1C500000000000BA01AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#Java###Starting dialog...#1#SelectPackageType#
    #1.5#C000AC1A1C500000000000CE01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#Java###The user has chosen for Inbox granulation.#1#Support Package Stack#
    #1.5#C000AC1A1C500000000000CF01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#Java###Dialog : the user has chosen the Next dialog button.#1#SelectPackageType#
    #1.5#C000AC1A1C500000000000D001AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#Java### dialog has been processed.#1#SelectPackageType#
    #1.5#C000AC1A1C500000000000D101AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#Java###Starting scanning Inbox for deployable J2EE Engine components...#1#
    CP-CHN-3F-029
    sapmnt
    trans
    EPS
    in#
    #1.5#C000AC1A1C500000000000D201AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#Java###You can find additional information in log file $.#1#C:
    usr
    sap
    NW7
    DVEBMGS01
    j2ee
    JSPM
    log
    log_20071231170532
    SCAN_INBOX_01.LOG#
    #1.5#C000AC1A1C500000000000D301AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#Java###Scanning of Inbox for deployable J2EE Engine components has finished.##
    #1.5#C000AC1A1C500000000000D401AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#Java###Starting searching for stack definition files in the Inbox...##
    #1.5#C000AC1A1C500000000000D501AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC1A1C500000000000D601AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#Java###java.lang.StringIndexOutOfBoundsException: String index out of range: -9##
    #1.5#C000AC1A1C500000000000D701AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_PROCESS#
    #1.5#C000AC1A1C500000000000D801AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#c

  • [SOLVED] mkinitcpio silently fails to build initramfs image

    I faced this annoying problem where mkinitcpio kept generating 20-byte initramfs images (for normal and fallback).
    The first symptom was being unable to boot. Kept getting error messages about junk in the initramfs image. I suspected a corrupted file. Used chroot, tried reinstalling the linux package, regenerating using mkinitcpio - didn't solve the problem.
    Then, I checked the /boot directory and found that the initramfs images were 20 bytes! mkinitcpio was generating 20-byte images (essentially empty images). It had done so on the last kernel upgrade.
    I was able to copy initramfs images from another Arch installation (same architecture, same kernel version) and boot Arch. I was unable to figure out why mkinitcpio was doing so. I tried reinstalling a few core packages (the build tools, grep etc.) but they didn't help.
    I gave up and tried the brute force method of reinstalling all packages. It was then that pacman complained about conflicting files for libarchive - libarchive! I remembered that there had been a forced shutdown at some time when packages were being updated. libarchive.so was corrupted/missing and had to be copied from another system (pacman wouldn't function without it). I hadn't reinstalled libarchive then. I did so now, and voila! mkinitcpio worked properly again.
    TLDR - If mkinicpio is not generating images properly, some tool it depends on (or mkinitcpio) is failing silently/is missing/is corrupt. Reinstall those things.

    I feel silly!
    pactree -u mkinitcpio
    would have given me the list of packages I needed to reinstall.

Maybe you are looking for

  • Report generation: Using only bottom border cell in Excel

    I'm trying to write a report to Excel. for each 2 rows I want the cells to have a bottom border. With the VI " Excel set Cell Color and Border VI" I have 2 options, using inside border and outside border. Outside border seems to be the top and bottom

  • Problems with background job

    Hi, I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice. - First it is executed synchronously when the job is created - Then it

  • My usb port doent work after I plug in my xbox rock candy controller

    Hello So recently I've gotten the blue screen of death on my computer for some reason on this horide laptop and then it shuts down. Afterwards when I turn on the computer the usb port were responsive for a short while before they stop working. The so

  • How to use AbstractTableModel in JTable

    hi i want how to use AbstractTableModel in Jtable plz give code

  • CSCIO.open_rpt

    Where I can find more information on how to use CSCIO.open_rpt and cscio.write_rpt in PL/SQL Package. When Package is call Oralce Application. Thanks Bob