License determination- Unable to determine currency and UoM

Hi Team,
I created a license in SAP GTS, value and quantity depreciation required. System determining license but not depreciating the value
and giving error " Unable to determine factor for converting from currency USD to currency " . This error i am getting in sales order level. I am assign it
manually and value depreciating but the same error i am getting in Uom in delivery level also. i have done setting of Spot(M) exchage rate for license type. the value also maintained in feeder system side.Which configuraion i am missing, some body can help
Regards,
Ramji

Hi Ramji,
What you're saying doesn't make much sense to me.  The currencies must be different, otherwise you wouldn't be seeing that error.
If you have some knowledge of ABAP, or if you have a developer available, you can debug to hopefully find the cause of the problem, since that error message is only used in 2 places.
Set a break-point in these two places:
In Function Module /SAPSLL/LCLIC_VALUE_CHECK, around line 40
In program /SAPSLL/LLCLIC_INTACTF61, around line 505
Now repeat the transaction, and see what is being passed for conversion (currencies and Exchange Rate Type).  That should give you some clues - perhaps you can share with us?
Regards,
Dave

Similar Messages

  • Unable to determine factor for converting from UoM DR to UoM L

    Hi gurus,
    I ran into an GTS block for inbound delivery which states 'Unable to determine factor for converting from UoM DR to UoM L.'  Actually the PO linked to this inbound delivery was transferred succesfully.
    Per above error log, I checked product master, conversion rate for DR and L was maintained.   Could you shed lights where should I maintain for above error log?
    Thank you,
    Ryan

    Hello Ryan,
    There is one bug recently detected in the contex of IBD transfer, the problem is that the conversion factor isn't taken into account during the interface mapping in ERP side, SAP will provide a Note for this issue. To be more sure that you run into the exact same issue, please check wether cvqdp_flt in item of the inbound delivery is empty(/SAPSLL/CUIT-CVQDP_FLT).
    Thanks,
    Derek

  • ERROR: unable to determine license level

    I have Tuxedo 7.1 for windows NT version, and put Lic.txt file in
    %TUXDIR%\udataobj\
    To make sure, I run License utility 7.1 too.
    ERROR: unable to determine license level
    do you know what's the problem?
    thank,
    Kyoungseop Ko

    Hi, thanks for the reply.  I don't use testing. I had upgraded to kernel 2.6.38.3-1. That caused the problem, so I downgraded to the previous version, 2.6.38.2-1, andthings are OK now.
    Edit: I did pacman -Syu on both systems and after upgrading pacman I let it upgrade the kernel and it seems OK now. I would like to know what happened if anyone can shed some light.
    Last edited by oboedad55 (2011-04-21 02:32:47)

  • The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.

    We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
    The operation failed because:
    Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
    Active Directory Domain Controller \\V-Svr03.mydomain.local.
    The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
    I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
    Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
       Testing server: Default-First-Site\DC1-DEV-OFC
          Starting test: NCSecDesc
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=hookemup,DC=local
             ......................... DC1-DEV-OFC failed test NCSecDesc
    In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
    We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
    Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
    Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.

    Ok... I ran repadmin /showreps /v again and it shows no errors
    C:\>repadmin /showreps /v
    Default-First-Site\DC1-DEV-OFC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
    DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
    ==== INBOUND NEIGHBORS ======================================
    CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381490/OU, 16381490/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114817/OU, 114817/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66047/OU, 66047/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098197/OU, 8098197/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    CN=Schema,CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8097482/OU, 8097482/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 65239/OU, 65239/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114149/OU, 114149/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381373/OU, 16381373/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=ForestDnsZones,DC=mydomain,DC=local
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66295/OU, 66295/PU
            Last attempt @ 2012-10-29 13:57:48 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098367/OU, 8098367/PU
            Last attempt @ 2012-10-29 13:58:13 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 115032/OU, 115032/PU
            Last attempt @ 2012-10-29 13:58:25 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381653/OU, 16381653/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
    DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114871/OU, 114871/PU
            Last attempt @ 2012-10-29 13:54:02 was successful.
    DC=DomainDnsZones,DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=mydomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 16381614/OU, 16381614/PU
            Last attempt @ 2012-10-29 13:56:52 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 66325/OU, 66325/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 8098385/OU, 8098385/PU
            Last attempt @ 2012-10-29 13:58:38 was successful.

  • Unable to determine currency

    Hi all,
    I m getting an error when choosing Income tax infotype. Error message is Unable to determine currency. Pls tell me how to resolve it!
    Thank you!
    Quanglv

    These are some screenshots
    http://i358.photobucket.com/albums/oo30/vquang124/OE00_1.jpg
    http://i358.photobucket.com/albums/oo30/vquang124/OE00_2.jpg
    http://i358.photobucket.com/albums/oo30/vquang124/OE00_3.jpg

  • Unable to Determine the Change Date and Time for records in infotype 2011

    Hi Everyone,
    We need to know on when the clock-in and clock-out records were interfaced to SAP in infotype 2011.
    The change date/time field in infotype 2011 is blank/not populated. Hence, we're unable to determine on when the clock-in records were updated in infotype 2011.
    It is not possible to get the audit logs for infotype 2011 as it is switched off.
    We found this table TEVEN and just the same thing, the field "change on" is blank.
    Kindly help us on how we can determine the change date and time for records in infotype 2011.

    Hi Prasad,
    Here's the scenario.
    On June 3, it was reported that staff's clock-in record on june 1, 7:00AM is missing in infotype 2011.
    However, when I checked infotype 2011, the record is there.
    So, they are now asking me on when this record was updated in infotype 2011 as they are thinking that there might be some delays in sending of the data to SAP.
    The created on and created at in table TEVEN shows the same, june 1, 7:00AM which seems to be not true as on june 3, it was reported to be missing.
    Can you help further on this?

  • Error - unable to determine DB and SAP version

    Hi!
    Getting struct in prepare phase of solution manager 3.2 to 4 upgrade.
    Getting error unable to determine the DB and SAP version.
    during the prepare during the DBCHK
    phase of solution manager getting the error " SEVERE ERROR: unable to
    determine DB and SAP version."
    The following files must be in the path described by
    the environment variable "PATH":
    icuuc30.dll, icudt30.dll, icuin30.dll [nlsui0.c 1489] pid = 2268
    Kindly assist

    dear Elmar,
    Hi!
    The entries are not there in path, but R3trans -d IS SHOWING ONLY following-
    C:\Documents and Settings\smpadm>r3trans.exe -d
    This is r3trans.exe version 6.13 (release 640 - 26.02.07 - 15:37:00).
    r3trans.exe finished (0000).
    And Echo path is - E:\oracle\SMP\102\bin;C:\WINDOWS;C:\WINDOWS\System32;E:\usr\sap\SMP\SYS\exe\run
    Kindly suggest
    sanjay
    Message was edited by:
            Sanjay Birari

  • BCS: unable to determine consolidation area for data basis B1

    Dear gurus,
       I have two consolidation areas B1 and Y1 on the same data basis B1. I want to report the  data of consolidation area Y1. I created a query which had the restrictions on consolidation chart of accounts, fiscal year variant, version, fiscal year, posting period and group currency. But when I opened the query with BEx Analyzer, the error prompted like below:
       Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
       Error reading the data of InfoProvider ZCB_B1V11
       Unable to determine consolidation area for data basis B1
    The row of the query is Item. I found if I activated the hierarchy of Item, this error occured and if deactivated the hierarchy of Item, the error disappeared.
    Please advise. Points will be awarded if helpful.
    Thanks in advance.
    Jin Ming

    Hi Jin Ming,
    Something is wrong with your hierarchy.
    In my case items hierarchy works fine.
    May propose two cases:
    1. Which version of your hierarchy, defaulted 100 or not? If not - wait for trouble.
    2. Hierarchy are global for all consolidation areas. If you hierarcical structures in different cons areas assigned to different special versions, the I'd not exclude some controversies between globality and special version pecularities.
    Hope this helps.

  • Unable to determine consolidation Area for Databasis AF

    Hi All,
    I wanted to check BCS results in BW I found the following errors in running query:
    1. Error reading the data of InfoProvider BCS_C1V11 (Virtual cube)
    2.Unable to determine consolidation Area for Databasis AF
    Can anybody advise, what sould be the probable reasons? I regenerated the consolidation areas, still its same error. Any thoughts, what I should look into.
    Thanks and Regards,
    Ashwin Nagar

    Hi Ashwin,
    You need to specify BCS mandatory fields when doing a listcube from the virtual cube.
    Period
    Year
    Controlling Area
    CS Chart
    CS Version
    BCS Version (or any other custom versions)
    Fiscal Year Variant
    Group Currency
    If you are trying to get consolidated results, make sure cons group is a field for display from the cube.
    Also, if running for a consolidation group, you must enter the cons group you want plus all groups which roll into it.
    For example, if you have
    CG 1
    - CG 2
    - - CG 3
    - CG4
    and you want to get results for CG1, you need to enter CG1, CG2, CG3, CG4.
    This is why List of Totals Records is preferred.
    Hope that helps
    - Chris

  • [SOLVED] Unable to determine major/minor number of root device - USB

    I installed Arch on a USB harddrive of mine from within VirtualBox with the intention of running the installation (via the drive) on a laptop in my house. I passed through the drive through by creating a special vmdk (here - it's for "expert users only". ) and installed Arch on it by booting off the Arch 2011.08.19 iso and following the instructions. I do recall the installer complaining because /sbin/mkinitcpio was missing, so I copied over the one from the host (which is also an up-to-date Arch system). After that, everything worked and I was able to boot the drive within virtualbox.
    Then I went and plugged it in to another laptop in the house and, surprisingly (for me at least), it got past GRUB. My joy was short-lived, because it failed just a bit later:
    :: Running Hook [udev]
    :: Triggering uevents...done.
    ERROR: Unable to determine major/minor number of root device 'Waiting 10 seconds
    for device /dev/disk/by-uuid/[the uuid] ...
    /dev/disk/by-uuid/(the uuid)'.
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [ramfs /]#
    So I googled around for a while and plugged it back in to my computer, booted it up in virtualbox, and added "usb" to the HOOKS array right after udev in /etc/mkinitcpio.conf. Then I rebuilt the initramfs:
    # mkinitcpio -p linux
    So I plugged it back into the laptop, booted it, and got the same error.
    Later, in an attempt to isolate the problem, I removed "sata" from HOOKS, ran the same mkinitcpio command again, and rebooted the VM. I got what looked like the same error as the one above. yay. So I guess the usb hook isn't being loaded or something like that. (I've since added the "sata" hook back and rebuilt the initramfs so I can mess around in the VM )
    I've tried removing autodetect from HOOKS (saw that in some threads) and trying different USB ports on the laptop, but nothing seems to be working. I also checked to see if virtualbox was providing a bogus uuid or something, but the one it's specifying seems to be correct - I looked in my computer's /dev/disk/by-uuid and it matched.
    Info on the drive (first partition is /boot, second is swap (derp!), third is /, and fourth is /home):
    # sudo fdisk -l /dev/sdg
    Disk /dev/sdg: 500.1 GB, 500107861504 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00016b3d
    Device Boot Start End Blocks Id System
    /dev/sdg1 * 63 208844 104391 83 Linux
    /dev/sdg2 208845 4417874 2104515 82 Linux swap / Solaris
    /dev/sdg3 4417875 209230559 102406342+ 83 Linux
    /dev/sdg4 209230560 976768064 383768752+ 83 Linux
    Screengrab of my VirtualBox storage setup (just for giggles):
    My /etc/mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    # Tried this line instead -- didn't work either
    #HOOKS="base udev usb autodetect pata scsi sata filesystems usbinput"
    HOOKS="base udev usb sata filesystems"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    My GRUB menu.lst:
    # Config file for GRUB - The GNU GRand Unified Bootloader
    # /boot/grub/menu.lst
    # DEVICE NAME CONVERSIONS
    # Linux Grub
    # /dev/fd0 (fd0)
    # /dev/sda (hd0)
    # /dev/sdb2 (hd1,1)
    # /dev/sda3 (hd0,2)
    # FRAMEBUFFER RESOLUTION SETTINGS
    # +-------------------------------------------------+
    # | 640x480 800x600 1024x768 1280x1024
    # ----+--------------------------------------------
    # 256 | 0x301=769 0x303=771 0x305=773 0x307=775
    # 32K | 0x310=784 0x313=787 0x316=790 0x319=793
    # 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
    # 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
    # +-------------------------------------------------+
    # for more details and different resolutions see
    # https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution
    # general configuration:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    # boot sections follow
    # each is implicitly numbered from 0 in the order of appearance below
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    # (0) Arch Linux
    title Arch Linux
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
    initrd /initramfs-linux.img
    # (1) Arch Linux
    title Arch Linux Fallback
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
    initrd /initramfs-linux-fallback.img
    # (2) Windows
    #title Windows
    #rootnoverify (hd0,0)
    #makeactive
    #chainloader +1
    Last edited by UncleNinja (2011-12-02 15:33:21)

    UncleNinja wrote:
    skunktrader wrote:https://bugs.archlinux.org/task/27385
    Perfect! Thank you!
    Would it be safe to copy over the version from HEAD into my mkinitcpio?
    EDIT: nevermind, derp derp the package is updated
    EDIT again: Actually, it's not.
    I copied over the init_functions in HEAD into /lib/initcpio/init_functions and rebuilt the initramfs. It worked!
    Thanks guys!
    Last edited by UncleNinja (2011-12-02 15:35:20)

  • SQL Server Agent running SSIS package fails Unable to determine if the owner of job has server access

    I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package.  The website and the instance of SQL Server with the agent and SSIS package are
    on the same windows 2008 r2 server.  When the button is operated no exceptions are raised but the SSIS package did not execute.
    When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
    The job failed.  Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
    ...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
    Could someone show me what I need to do to get this to run?  Thanks tonnes in advance for any help, Roscoe

    This can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
    I suggest you try using the SA account for the job as it does not require to poll the AD.
    Arthur My Blog

  • [SOLVED] ERROR: Unable to determine the file system type of /dev/root:

    :: Running Hook [udev]
    :: Triggering uevents...done
    Root device '804' doesn't exist.
    Creating root device /dev/root with major 8 and minor 4.
    error: /dev/root: No such device or address
    ERROR: Unable to determine the file system type of /dev/root:
    Either it contains no filesystem, an unknown filesystem,
    or more than one valid file system signature was found.
    Try adding
    rootfstype=your_filesystem_type
    to the kernelcommand line.
    You are now being dropped into an emergency shell.
    /bin/sh: can't access tty; job control turned off
    [ramfs /]# [ 1.376738] Refined TSC clocksource calibration: 3013.000 MHz.
    [ 1.376775] Switching to clocksource tsc
    That's what I get when I boot my Arch system. It worked fine for quite a while, but suddenly it ran into an error where the SCSI driver module was corrupt. I fixed it by reinstalling util-linux-ng and kernel26, however, I run into this issue now. http://www.pastie.org/2163181 < Link to /var/log/pacman.log for the month of July, just in case. Yes, I bought a new ATI/AMD Radeon HD 5450 this Saturday, but it seemed to work fine till this broke and it works fine on Ubuntu too, so I suppose we can rule it out.
    Last edited by SgrA (2011-07-05 20:45:36)

    Autodetection failed on your first image, in both your previous kernel installs:
    [2011-07-04 16:14] find: `/sys/devices': No such file or directory
    Which means that sysfs was not mounted. You should be able to boot from the fallback image, which does not use autodetect. Figure out why /sys isn't mounted, as well, and fix that.
    This is also a somewhat crappy bug in mkinitcpio that lets you create an autodetect image that's useless. It'll be fixed in the next version of mkinitcpio that makes it to core.
    Last edited by falconindy (2011-07-04 17:41:19)

  • "Unable to determine destination partition, disk or drive" when Media deployment is used

    We are heavy users of MDT 2013's "media" deployments -- in fact, once we finish testing a new image build on our lab server, media is created and is the sole method we use to deploy new systems due to many limitations.
    We ran into the following issue lately when using USB sticks or hard drives for our deployment media. Deployment of an OS image fails at the "Inject Drivers" stage. The hard disk inside the computer is formatted properly, but the TS fails with
    the error "Unable to determine destination partition, disk or drive".
    I dug into the logs, and it appears that "Inject drivers" does a check for where the \Drivers folder should be placed. The problem is that most USB hard disks and many higher-end USB sticks show up as "hard drives" rather than "removable
    media" when plugged into the machine. Adding another physical disk that appears as a fixed disk with an NTFS partition apparently confuses MDT and you get this error message. I think any "ReadyBoost enabled" USB stick has to show up on the system
    as a fixed disk rather than removable, so if you use these you might have this problem.
    The only workaround is to explicitly specify the disk number and partition number to use when you invoke "Install Operating System." The drivers step must take this information when determining where to put the driver store.
    Is there any other explanation for why this would be happening? We're stuck with media deployment for the foreseeable future, and until Microsoft fixes the problem with handling of split WIM files, we have to use NTFS formatted disks/sticks...this might
    be making it harder for the MDT logic to determine where to put the OS.

    MDT should be smart enough to know that it should Skip USB drives.
    However if you have a USB 3 Hard DIsk (not a USB Flash Disk), that might be the problem
    1. Try using only Flash Drives.
    2. Try plugging the USB Hard Drive into a USB 2.0 port
    3. Additionally try not to use USB Hard Drives that are *Larger* that the internal hard drive.
    If you still have problems, can you copy your Bdd.log file to a public site like OneDrive and share the link?
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Unable to determine the value of component  ''! Workflow error, please help

    Hi All:
        I am getting the error "Unable to determine the value of component  ''" and workflows are not getting processed. I found OSS notes 879100 related to this issue but I am new to workflow and not sure where to start from! Here is the notes description:
    The workflow WS20500025 ('Service Connection Order Processing') encounters an error directly after being started. The following error messages are displayed in the workflow log:
    SWP102: Error at start of an IF branch
    WL821: Work item 000000100012: Object FLOWITEM method EXECUTE cannot be executed
    SWF_RUN535: Error '9' when calling service 'SO_OBJECT_SEND'
    SWF_RUN534: Problems occurred when generating a mail
    WL863: Notification of completion cannot be generated
    SWF_EXP_001073: Unable to determine the value of component 'QUOTATION'
    SWF_EXP_001072: Error in the evaluation of expression '<???>' for item 1
    SWF_RLS_001101: Operator 'GT': The value of the left operand cannot be determined
    SWP085: Error when starting work item 000000100012
    SWP010: Error when evaluating the IF condition for node 0000000075
    Other terms
    Service connection processing, service connection workflow
    Reason and Prerequisites
    This is due to a program error.
    The checks in the workflow Basis have been made stricter. A query of the type 'Quotation.number > 0' now causes an error if the container element 'Quotation' is not set. This is always the case if the workflow is is running without quotation prcessing, for instance.
    Solution
    The error is corrected in the next Support Package.
    If you want to implement the corrections manually in your system, change the condition in step 000075 of workflow WS20500025 as follows:
        &IS-U: Kundenangebot& EX
    and &IS-U: Kundenangebot.Verkaufsbeleg& > 0
    Save and activate the workflow.
    I am new to workflow and not sure where to start from! Could someone please help me with this? Rewards assured.
    Thanks.
    Mithun

    ANy ideas? Please help me if anyone knows the answer.
    Thanks.
    Mithun

  • Unable to determine name of central adapter engine

    We have a central SLD set up. I am now moving some configuration and testing from our dev environment to our qa environment. When I do a cache notification from the Integration Directory I receive a message stating that "Unable to determine the name of the central Adapter Engine from the System Landscape Directory". When I look under the technical system type of Exchange Infrastructure of the system landscape directory I do not see the Adapter Engine of my QA or Production environment. I only see one central adapter engine listed. That of my development environment. It will not let me define another technical system to add these adapter engines because the button New Technical System is grayed out. How do I get these adapter engines defined in the SLD?
    Thanks,
    Jim

    I also had the same problem. But when I opened Integration Directory and Repository from the links, it got added to the Technical system under Exchange Infrastructure. Only Adapter Engine was not getting added.
    But after applying the note 764176. Adapter Engine added to SLD and after refreshing cache now Adapter Engine also got added to RWB components.
    Only one problem now - in Message monitoring, If I select Adapter Engine from the drop down, I get page cannot be displayed. Is it due to the fact that I dont have any adapters configured?? and also no messages available for that matter?? as it is a fresh box..
    Message was edited by: Thilothama v

Maybe you are looking for