ADS error in bi diagnostic and support desk tool

Hi
I have done the configuration for ADS acoording to confign guide.I am getting the error in export check(PDF lib,ADS,...) in bi diagnostic and support desk tool.
ERROR:com.adobe.ProcessingException:the rules specified requires return pdf or render named:node does not exist.
Also when i check with report FP_CHECK_DESTINATION_SERVICE i am getting the same error.
System Error: com.adobe.ProcessingException:the rules specified requires return pdf or render named:node does not exist.
Please help me out.
Regards
Pranav

Hi, Pranav, we have hit this same problem, and the oss note is not supplying the answer, do you remember what the answer was?
Would appreciate the help.
Thanks.
Paul.

Similar Messages

  • BI : Diagnostic and support desk tool

    Hello
    I'm currently using BI7.0 SP9 and the support desk tool version 0.370.
    I have a current red light that i'm not able to solve :
    URLs Prefixes Customized on Both J2EE and ABAP Side
    and the  long text is :
    The URL for ABAP customizing table RSPOR_T_PORTAL: http://cod..airliquide.com:50100 is not compatible with the URL for URL with which you call the WebAS Java: http://cod:50100
    and it told me to apply OSS note 596698 as well as note 654326 for details
    The problem is not solved on this note.
    I would like to know how to chanfe the URL in the abap part whan i call the java part to use the long name and included the domain on it ???
    regards
    François

    Hello
    closed
    we have to use http://hostname.domainName:5XX00 instead of http://hostname:5XX00 to avoid such issue
    François

  • Error in deployed compoents when running diagnostics & support desk tool

    when I run netweaver Business Explorer diagnostics & support desk tool
    I got error in "deployed components".
    the message says:
    "The SCA 'BI-BASE-S' (7.00 SPS 9, patch level #0) is a invalid combination of version/support package with your WebAS ABAP system (7.00 19)"
    the solution says
    "Ensure that both your WebAS Java and your WebAS ABAP have a valid combination of version and support package stack level. Please note that beginning from BI SP 11, the versioning scheme of BI ABAP SPs has changed"
    then I was referred to note 1013369 and 1163789. then which SCA file SPS/patch do I need for ABAP SPS19?
    what do I need to do? and how do I do this? my basis guy need advice.
    George

    Hello George,
    To correct this issue ensure that both your WebAS Java and your WebAS ABAP have a valid combination of version and support package stack level.
    Also you can check the note  1013369 -  SAP NetWeaver 7.0 BI - intermediate Support Packages
    and check the compatibility table.
    I hope that this can help you.
    Kind regards
    Diego Ferrary

  • What is support desk tool?

    Dear SAP Experts,
    What is support desk tool?
    And How can I execute it?
    Thanks and Best Regards,
    Zilla

    Hello Zila,
    Support desk tool is an application that check the configuration of your system and collect informationabout your SAP NetWeaver BI installation.
    There is a note that explains this as well as how to execute it. Please, see 937697.
    I hope this helps you.
    Kind regards,
    Blanca

  • Help button gives error message"windows help and support" can't start

    HP pavilion dv6 laptop, Windows 7 64-bit. Nothing on that website says anything about this type of problem.This happens everytime I try to use the button it doesn't matter what I'm doing.  Anyone have any ideas on how to fix 

    Sorry I posted in the wrong forum

  • [Solved] Error boot after upgrading and util-linux-tools and sysvinit

    Hi all ...
    This morning I did a sudo pacman -Syu to update my laptop which packs sysvinit-tools 2.88-8 and 2.22-6 util-linux packages including ...
    My surprise that I take is that a few hours ago after starting my laptop again I come across a series of error messages which do not allow me log into the laptop. catches of messages are these:
    Picture 1
    Picture 2
    The log of pacman to upgrade is:
    [09.24.2012 9:01] Running 'pacman-Syu'
    [09.24.2012 9:01] synchronizing package lists
    [09.24.2012 9:03] starting full system upgrade
    [09.24.2012 9:21] removed eject (2.1.5-7)
    [09.24.2012 9:22] upgraded coreutils (8.17-3 -> 8.19-1)
    [09.24.2012 9:22] upgraded libmtp (1.1.4-1 -> 1.1.5-1)
    [09.24.2012 9:22] upgraded mlocate (0.25-2 -> 0.26 to 1)
    [09.24.2012 9:22] upgraded procps-ng (3.3.3-3 -> 3.3.3-6)
    [09.24.2012 9:22] upgraded qt (4.8.3-2 -> 4.8.3-3)
    [09.24.2012 9:22] upgraded util-linux (2.21.2-5 -> 2.22-6)
    [09.24.2012 9:22] upgraded sysvinit-tools (2.88-7 -> 2.88-8)
    [09.24.2012 9:22] upgraded transmission-gtk (2.61-3 -> 2.61-4)
    [09.24.2012 9:22] upgraded whois (5.0.18-1 -> 5.0.19-1)
    In making this latest update pacman eject told me that was going to be replaced by util-linux ... before answering affirmatively check the official website of ArchLinux to see if there were any announcement about this change ... I assumed there was none like it was nothing critical and permitted the installation of this patch ....
    At the end of the error message you see in the pictures I show that I can run a command or shortcut systemctl keyboard to enter the "default mode" but I have no way to give commands and keyboard shortcut does not work.
    No I could do to recover the system (other than reinstalling ArchLinux with new. Iso) ...
    Someone has spent the same??? found a solution???
    Greetings and thanks in advance!
    Sorry my bad English!
    Last edited by jesusangelm (2012-09-25 18:12:20)

    in another forum recommended me to downgrade the updated packages to restore the system and use it.
    but installing the updated packages I get this error
    If I try the downgrade util-linux gives me:
    pacman -U /var/cache/pacman/pkg/util-linux-2.21.2-5-x86_64.pkg.tar.xz
    loading packages...
    warning: downgrading package util-linux (2.22-6 => 2.21.2-5)
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): util-linux-2.21.2-5
    Total Installed Size: 7.45 MiB
    Proceed with installation? [Y/n] y
    (1/1) checking package integrity [############################################] 100%
    (1/1) loading package files [############################################] 100%
    (1/1) checking for file conflicts [############################################] 100%
    error: failed to commit transaction (conflicting files)
    util-linux: /bin/dmesg exists in filesystem
    util-linux: /bin/findmnt exists in filesystem
    util-linux: /bin/login exists in filesystem
    util-linux: /bin/lsblk exists in filesystem
    util-linux: /bin/more exists in filesystem
    util-linux: /bin/mount exists in filesystem
    util-linux: /bin/mountpoint exists in filesystem
    util-linux: /bin/umount exists in filesystem
    util-linux: /sbin/agetty exists in filesystem
    util-linux: /sbin/blkid exists in filesystem
    util-linux: /sbin/blockdev exists in filesystem
    util-linux: /sbin/cfdisk exists in filesystem
    util-linux: /sbin/chcpu exists in filesystem
    util-linux: /sbin/ctrlaltdel exists in filesystem
    util-linux: /sbin/fdisk exists in filesystem
    util-linux: /sbin/findfs exists in filesystem
    util-linux: /sbin/fsck exists in filesystem
    util-linux: /sbin/fsck.cramfs exists in filesystem
    util-linux: /sbin/fsck.minix exists in filesystem
    util-linux: /sbin/fsfreeze exists in filesystem
    util-linux: /sbin/fstrim exists in filesystem
    util-linux: /sbin/hwclock exists in filesystem
    util-linux: /sbin/losetup exists in filesystem
    util-linux: /sbin/mkfs exists in filesystem
    util-linux: /sbin/mkfs.bfs exists in filesystem
    util-linux: /sbin/mkfs.cramfs exists in filesystem
    util-linux: /sbin/mkfs.minix exists in filesystem
    util-linux: /sbin/mkswap exists in filesystem
    util-linux: /sbin/pivot_root exists in filesystem
    util-linux: /sbin/raw exists in filesystem
    util-linux: /sbin/sfdisk exists in filesystem
    util-linux: /sbin/swaplabel exists in filesystem
    util-linux: /sbin/swapoff exists in filesystem
    util-linux: /sbin/swapon exists in filesystem
    util-linux: /sbin/switch_root exists in filesystem
    util-linux: /sbin/wipefs exists in filesystem
    util-linux: /usr/bin/cal exists in filesystem
    util-linux: /usr/bin/chfn exists in filesystem
    util-linux: /usr/bin/chrt exists in filesystem
    util-linux: /usr/bin/chsh exists in filesystem
    util-linux: /usr/bin/col exists in filesystem
    util-linux: /usr/bin/colcrt exists in filesystem
    util-linux: /usr/bin/colrm exists in filesystem
    util-linux: /usr/bin/column exists in filesystem
    util-linux: /usr/bin/cytune exists in filesystem
    util-linux: /usr/bin/fallocate exists in filesystem
    util-linux: /usr/bin/flock exists in filesystem
    util-linux: /usr/bin/getopt exists in filesystem
    util-linux: /usr/bin/hexdump exists in filesystem
    util-linux: /usr/bin/i386 exists in filesystem
    util-linux: /usr/bin/ionice exists in filesystem
    util-linux: /usr/bin/ipcmk exists in filesystem
    util-linux: /usr/bin/ipcrm exists in filesystem
    util-linux: /usr/bin/ipcs exists in filesystem
    util-linux: /usr/bin/isosize exists in filesystem
    util-linux: /usr/bin/linux32 exists in filesystem
    util-linux: /usr/bin/linux64 exists in filesystem
    util-linux: /usr/bin/logger exists in filesystem
    util-linux: /usr/bin/look exists in filesystem
    util-linux: /usr/bin/lscpu exists in filesystem
    util-linux: /usr/bin/mcookie exists in filesystem
    util-linux: /usr/bin/namei exists in filesystem
    util-linux: /usr/bin/newgrp exists in filesystem
    util-linux: /usr/bin/pg exists in filesystem
    util-linux: /usr/bin/prlimit exists in filesystem
    util-linux: /usr/bin/rename exists in filesystem
    util-linux: /usr/bin/renice exists in filesystem
    util-linux: /usr/bin/rev exists in filesystem
    util-linux: /usr/bin/script exists in filesystem
    util-linux: /usr/bin/scriptreplay exists in filesystem
    util-linux: /usr/bin/setarch exists in filesystem
    util-linux: /usr/bin/setsid exists in filesystem
    util-linux: /usr/bin/setterm exists in filesystem
    util-linux: /usr/bin/tailf exists in filesystem
    util-linux: /usr/bin/taskset exists in filesystem
    util-linux: /usr/bin/ul exists in filesystem
    util-linux: /usr/bin/unshare exists in filesystem
    util-linux: /usr/bin/uuidgen exists in filesystem
    util-linux: /usr/bin/whereis exists in filesystem
    util-linux: /usr/bin/write exists in filesystem
    util-linux: /usr/bin/x86_64 exists in filesystem
    util-linux: /usr/include/blkid/blkid.h exists in filesystem
    util-linux: /usr/include/libmount/libmount.h exists in filesystem
    util-linux: /usr/include/uuid/uuid.h exists in filesystem
    util-linux: /usr/lib/libblkid.a exists in filesystem
    util-linux: /usr/lib/libblkid.so exists in filesystem
    util-linux: /usr/lib/libblkid.so.1 exists in filesystem
    util-linux: /usr/lib/libblkid.so.1.1.0 exists in filesystem
    util-linux: /usr/lib/libmount.a exists in filesystem
    util-linux: /usr/lib/libmount.so exists in filesystem
    util-linux: /usr/lib/libmount.so.1 exists in filesystem
    util-linux: /usr/lib/libmount.so.1.1.0 exists in filesystem
    util-linux: /usr/lib/libuuid.a exists in filesystem
    util-linux: /usr/lib/libuuid.so exists in filesystem
    util-linux: /usr/lib/libuuid.so.1 exists in filesystem
    util-linux: /usr/lib/libuuid.so.1.3.0 exists in filesystem
    util-linux: /usr/lib/pkgconfig/blkid.pc exists in filesystem
    util-linux: /usr/lib/pkgconfig/mount.pc exists in filesystem
    util-linux: /usr/lib/pkgconfig/uuid.pc exists in filesystem
    util-linux: /usr/sbin/addpart exists in filesystem
    util-linux: /usr/sbin/delpart exists in filesystem
    util-linux: /usr/sbin/fdformat exists in filesystem
    util-linux: /usr/sbin/ldattach exists in filesystem
    util-linux: /usr/sbin/partx exists in filesystem
    util-linux: /usr/sbin/readprofile exists in filesystem
    util-linux: /usr/sbin/rtcwake exists in filesystem
    util-linux: /usr/sbin/tunelp exists in filesystem
    util-linux: /usr/sbin/uuidd exists in filesystem
    util-linux: /usr/sbin/vigr exists in filesystem
    util-linux: /usr/sbin/vipw exists in filesystem
    util-linux: /usr/share/getopt/getopt-parse.bash exists in filesystem
    util-linux: /usr/share/getopt/getopt-parse.tcsh exists in filesystem
    util-linux: /usr/share/locale/ca/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/cs/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/da/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/de/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/es/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/et/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/eu/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/fi/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/fr/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/gl/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/hu/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/id/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/it/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/ja/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/nl/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/pl/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/pt_BR/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/ru/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/sl/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/sv/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/tr/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/uk/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/vi/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/zh_CN/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/locale/zh_TW/LC_MESSAGES/util-linux.mo exists in filesystem
    util-linux: /usr/share/man/man1/cal.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/chrt.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/col.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/colcrt.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/colrm.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/column.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/dmesg.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/fallocate.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/flock.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/getopt.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/hexdump.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/ionice.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/ipcmk.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/ipcrm.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/ipcs.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/logger.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/look.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/lscpu.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/mcookie.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/more.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/mountpoint.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/namei.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/pg.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/prlimit.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/rename.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/renice.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/rev.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/script.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/scriptreplay.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/setsid.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/setterm.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/tailf.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/taskset.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/ul.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/unshare.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/uuidgen.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/whereis.1.gz exists in filesystem
    util-linux: /usr/share/man/man1/write.1.gz exists in filesystem
    util-linux: /usr/share/man/man3/libblkid.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_clear.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_compare.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_copy.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_generate.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_generate_random.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_generate_time.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_generate_time_safe.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_is_null.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_parse.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_time.3.gz exists in filesystem
    util-linux: /usr/share/man/man3/uuid_unparse.3.gz exists in filesystem
    util-linux: /usr/share/man/man5/fstab.5.gz exists in filesystem
    util-linux: /usr/share/man/man8/addpart.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/agetty.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/blkid.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/blockdev.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/cfdisk.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/chcpu.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/ctrlaltdel.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/cytune.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/delpart.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fdformat.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fdisk.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/findfs.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/findmnt.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fsck.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fsck.minix.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fsfreeze.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/fstrim.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/hwclock.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/i386.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/isosize.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/ldattach.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/linux32.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/linux64.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/losetup.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/lsblk.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/mkfs.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/mkfs.bfs.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/mkfs.minix.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/mkswap.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/mount.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/partx.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/pivot_root.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/raw.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/readprofile.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/rtcwake.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/setarch.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/sfdisk.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/swaplabel.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/swapoff.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/swapon.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/switch_root.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/tunelp.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/umount.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/uuidd.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/wipefs.8.gz exists in filesystem
    util-linux: /usr/share/man/man8/x86_64.8.gz exists in filesystem
    Errors occurred, no packages were upgraded.
    If I try the downgrade sysvinit-tool gives me:
    pacman -U /var/cache/pacman/pkg/sysvinit-tools-2.88-7-x86_64.pkg.tar.xz
    loading packages...
    warning: downgrading package sysvinit-tools (2.88-8 => 2.88-7)
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): sysvinit-tools-2.88-7
    Total Installed Size: 0.17 MiB
    Proceed with installation? [Y/n] y
    (1/1) checking package integrity [############################################] 100%
    (1/1) loading package files [############################################] 100%
    (1/1) checking for file conflicts [############################################] 100%
    error: failed to commit transaction (conflicting files)
    sysvinit-tools: /bin/pidof exists in filesystem
    sysvinit-tools: /sbin/bootlogd exists in filesystem
    sysvinit-tools: /sbin/fstab-decode exists in filesystem
    sysvinit-tools: /sbin/killall5 exists in filesystem
    sysvinit-tools: /sbin/sulogin exists in filesystem
    sysvinit-tools: /usr/bin/last exists in filesystem
    sysvinit-tools: /usr/bin/lastb exists in filesystem
    sysvinit-tools: /usr/bin/mesg exists in filesystem
    sysvinit-tools: /usr/bin/utmpdump exists in filesystem
    sysvinit-tools: /usr/bin/wall exists in filesystem
    sysvinit-tools: /usr/include/initreq.h exists in filesystem
    sysvinit-tools: /usr/share/man/man1/last.1.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man1/lastb.1.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man1/mesg.1.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man1/utmpdump.1.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man1/wall.1.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man8/bootlogd.8.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man8/fstab-decode.8.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man8/killall5.8.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man8/pidof.8.gz exists in filesystem
    sysvinit-tools: /usr/share/man/man8/sulogin.8.gz exists in filesystem
    Errors occurred, no packages were upgraded.
    If I try the downgrade eject gives me:
    pacman -U /var/cache/pacman/pkg/eject-2.1.5-7-x86_64.pkg.tar.xz
    loading packages...
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): eject-2.1.5-7
    Total Installed Size: 0.14 MiB
    Proceed with installation? [Y/n] y
    (1/1) checking package integrity [############################################] 100%
    (1/1) loading package files [############################################] 100%
    (1/1) checking for file conflicts [############################################] 100%
    error: failed to commit transaction (conflicting files)
    eject: /usr/bin/eject exists in filesystem
    eject: /usr/share/man/man1/eject.1.gz exists in filesystem
    Errors occurred, no packages were upgraded.

  • Error in BI Mastersystem and WebAS ABAP Settings

    Hi Team,
    We are facing below issues, and we ran the support desk tool.
    When im running support desk tool, i'm receiving the below error and able to enter the credentials to get the configuration checks.
    Here im facing few errors.
    RFC connection using properties in Portal System Landscape to ABAP backend has failed. Reason:
    com.sap.mw.jco.JCO$Exception:Issuer of SSO ticket is not authorized
    You can enter the connection properties manually (button OK) or proceed to the check message result screen (button CANCEL)
    1. BI Mastersystem
    RED
    RFC to ABAP was done via entering connection properties manually.
    Enter connection properties in Portal Systemlandscape for the property category 'Connector' (Systemlandscape/SAP_BW)
    Here i've verified all the connctor settings in portal, but the connection is failing as below
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    2. WebAS ABAP Settings
    RED
    Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018)
    Check Connector Connection of System Object in Portal System Landscape
    RED
    Combination of System ID of J2EE 'BWP' and UME property login.ticket_client '000' is missing in Access Control List (ACL) of ABAP system
    Add 'BWP/000' to Access Control List (ACL) with transaction STRUSTSSO2
    RED
    Combination of System ID of J2EE 'BWP' and client 000 is missing in Access Control List (ACL) of ABAP system
    Add system 'BWP' with client 000 to Access Control List (ACL) with transaction STRUSTSSO2. This is required for transport of Web Templates. See note 945055 for details.
    Display note 945055
    Here i've added certificated into ACL with 000 client, still the issue exists
    Could you please help me on this.
    Regards
    Nani

    Hi Nani,
    Can you please refer the following SAP Note and check whether it helps you:
    2002823 - User-Specific Broadcaster setting cancels with SSO error.
    Can you please refer the following SAP KBA Notes:
    1575891 - After executing a Broadcast setting you receive the Java error: call FM RSRD_X_PRODUCE_PROXY to ProgId 'abc' on host 'xyz' with SSO not authorized
    1769367 - Issuer of SSO ticket is not authorized
    And, please refer the following SAP Notes:
    1083421 - SSO2 Wizard
    945055 - Transporting Web templates in SAP NetWeaver 2004s
    1573365 - Sporadic communication error in BEx Web 7.X
    Also, please note the following:
    "With SAP NetWeaver 7.1, the Visual Administrator (VA) is replaced by
    the SAP NetWeaver Administrator, that is, all relevant functions of
    the VA are available in the SAP NetWeaver Administrator.
    The VA is no longer delivered as of SAP NetWeaver 7.1.  "
    And, please refer the Error Message "RFC to ABAP was done via entering connection properties manually" of Section 'Case2: BI Master System' mentioned in the following SAP KBA Note:
    2113395 - Supportdesk Tool RED signal checking trouble shooting guide
    And, please refer the Error12 and Error13 of Section 'Case16: WebAS ABAP Settings' mentioned in the following SAP KBA Note:
    2113395 - Supportdesk Tool RED signal checking trouble shooting guide
    Thanks & Regards,
    Sapna

  • Production and support

    HI,
      Iam new to this forum.
    in production and support what we will do daily activities as a bw consultant.what will be the errors occur.can any one have document please send me.
    points will be assigned.
    Thanku
    Message was edited by: Ron Silberstein

    D PAVANI,
    There are lots of errors occur in production and support like
    1.timestamp error:replicate the ds
    2.rfc failure error: check through sm59
    2.ods data is not acivated error: manulaay activate it
    4.ale remote is locked error: check with basis
    6.sid is not matched:check master data before loading t data
    7.sid number range error.: schduler menu set number ranger
    8.short dump: chek it in st22
    9.cache problem.: restart the load,refresh the catch
    regards
    nain

  • Error 513, no message was created in support desk system BCOS005

    Hi All,
    After completing the ITSM config on Solution Manager 7.1, I am stuck with the following error when creating message from any of the satellite system, or from SM itself.
    "Because of error 513, no message was created in support desk system"
    Message no. BCOS005
    Error logs from SLG1:
    "No message created from SAP message 00xxxxxx 000xxxxx 2013 due to missing IBase"
    Transaction: SOLMAN_INCIDENT_UPD
    Program:AI_CRM_IM_UPDATE_FROM_SAP
    I have already checked various threads and suggested notes including 1522809 / 1741109, but unable to fix the issue.
    RFC's between both the systems are working fine. The entry for BCOS_CUST on SM is maintained as
    OSS_MSG   W    NONE    CUST   6.2    1.0
    The number range for SLF1 is maintained as 01 in TCode DNO_CUST01
    I suspect this to be related to IBASE or Number range, but seem to have the correct values maintained as mentioned in above notes. Would appreciate your valuable inputs on this.
    Thanks,
    Varun

    Hi Vivek,
    Tried updating the parameter, but no luck
    "Because of error 513, no message was created in support desk system"
    Message no. BCOS005
    Should be something to do with BCOS, can't figure out though.
    Any further thoughts?
    Regards,
    Varun

  • Error 513, no message was created in Support Desk System

    After implementing QAS in sp's 15, when the user wants to create a message from QAS solution manager, get the following error "Because of error 513, no message was created in Support Desk System"
    has been revised rfc connections and have no problem because when the user is done with NetWeaver - works perfect basis.
    Nor is it because of permissions users have the same roles that were assigned in the other systems DEV and PRD, and when they have no problems sending messages.
    I have reviewed the table BCOS_CUST "and is fine. As in other systems.
    I am grateful if someone can help me.
    Regards

    Dear Leonor,
    This forum is related to Public Sector Funds Management (budget) issues.
    I believe the best for you is to open this thread in the Basis forum. There you will find the experts to help you.
    Best Regards,
    Vanessa.

  • Error while creating change request via solman support desk message

    I have configured CHARM and my change req. is working for urgent correction, I have tested the entire workflow.
    however when i try to create a new change req. via support desk message --> create a change request open
    I get following error
    An action was terminated due to an exceptional situation.
    Message no. SOCM_ACTION_LOG 090
    Diagnosis
    An exception has been triggered in PPF action processing.
    System Response
    Action processing has been terminated. The status of the transaction is still incorrect.
    Procedure
    You cannot execute the action until the cause of the error has been removed.
    The error messages will be kept until the transaction is next checked for subsequent analysis.
    Procedure for System Administration
    If necessary, analyze other messages in the application log for the incorrect transaction. To analyze the termination, you can activate the breakpoints in the checkpoint group socm_exception.
    Additional Information:
    Exception CX_SOCM_PRECONDITION_VIOLATED occurred (program:
    CL_HF_HELPER==================CP, include:
    CL_HF_HELPER==================CM00A, line: 29).
    pls help

    Hi Yunus,
    Your probably have changed the transaction type SLFN to a the customer namespace Z or Y. If this is the case you MUST also "Define Mapping Rules for Copy Control".
    Goto SPRO -> SAP Solution Manager -> Scenario-Specific Settings -> Change Management -> Change Request Management -> Extended Configuration -> Change Transaction -> Change Transaction Types -> Copy Control for Change Request Management ->  Define Mapping Rules for Copy Control.
    Once at this point in the IMG make a copy of SLFN -> ZLFN. This will resolve your problem.
    Kind regards,
    Latief

  • An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003.

    I received the above error reinstalling SQL Server 2008.  I have tried all suggestions.  This error also appears when I install any version of SQL Server.
    I have also installed;
    Microsoft® .NET Framework Version 2.0.50727.4927
    Microsoft® .NET Framework Version 4.0.31106.0
    Microsoft® .NET Framework Version 3.0.6920.50
    Microsoft Visual C++ 2005 Redistributable (x64) 8.0.59192
    Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
    Microsoft Visual C++ 2010 x64 Redistributable 10.0.40219
    Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219
    Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
    Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -2068052081
      Exit facility code:            1212
      Exit error code:               1935
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Start time:                    2014-02-23 19:17:20
      End time:                      2014-02-23 19:21:35
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SqlSupport_KatmaiRTM_Cpu64_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
    Machine Properties:
      Machine name:                  OHPC
      Machine processor count:       2
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         H:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           OHPC\Robert
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SystemConfigurationCheck_Report.htm
    SFC/ Scannow
    2014-02-23 19:08:22, Info                  CSI    0000016f [SR] Verifying 100 (0x0000000000000064) components
    2014-02-23 19:08:22, Info                  CSI    00000170 [SR] Beginning Verify and Repair transaction
    2014-02-23 19:08:23, Info                  CSI    00000172 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:23, Info                  CSI    00000174 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:26, Info                  CSI    00000176 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:26, Info                  CSI    00000177 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
    2014-02-23 19:08:26, Info                  CSI    00000179 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
    source file in store is also corrupted
    2014-02-23 19:08:27, Info                  CSI    0000017c [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:27, Info                  CSI    0000017d [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
    2014-02-23 19:08:27, Info                  CSI    00000180 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
    source file in store is also corrupted
    2014-02-23 19:08:27, Info                  CSI    00000182 [SR] Verify complete
    2014-02-23 19:12:33, Info                  CSI    00000326 [SR] Verifying 100 (0x0000000000000064) components
    2014-02-23 19:12:33, Info                  CSI    00000327 [SR] Beginning Verify and Repair transaction
    2014-02-23 19:12:33, Info                  CSI    00000329 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:12:35, Info                  CSI    0000032b [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:12:35, Info                  CSI    0000032c [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
    2014-02-23 19:12:35, Info                  CSI    0000032f [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
    source file in store is also corrupted
    2014-02-23 19:12:36, Info                  CSI    00000331 [SR] Verify complete
    2014-02-23 19:13:14, Info                  CSI    0000035d [SR] Repairing 3 components
    2014-02-23 19:13:14, Info                  CSI    0000035e [SR] Beginning Verify and Repair transaction
    2014-02-23 19:13:14, Info                  CSI    00000360 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000362 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000364 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000366 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000367 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
    2014-02-23 19:13:15, Info                  CSI    0000036a [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    0000036c [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:15, Info                  CSI    0000036d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
    2014-02-23 19:13:15, Info                  CSI    0000036f [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    00000371 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:15, Info                  CSI    00000372 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
    2014-02-23 19:13:15, Info                  CSI    00000375 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    00000377 [SR] Repair complete
    2014-02-23 19:13:15, Info                  CSI    00000378 [SR] Committing transaction
    2014-02-23 19:13:15, Info                  CSI    0000037c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction 
    have been successfully repaired

    Summary:
    Attempted proposed solution.  Error still appears.
    This is installed:
    Microsoft Visual C++ 2005 ATL Update kb973923 - x86 8.0.50727.4053
    Microsoft Visual C++ 2005 Redistributable               8.0.56336
    Microsoft Visual C++ 2005 Redistributable (x64)         8.0.59192
    Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
    Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
    Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
    Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
    Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
    I reinstalled:
    vcredist_x64 Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) .exe
    vcredist_x86 Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).exe
    Results:
    Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable (x64). Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft
    Corporation. Reconfiguration success or error status: 0.
    Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable. Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft Corporation.
    Reconfiguration success or error status: 0.
    I installed SQLServer2008R2_SP1
    Same error message came up;
    SqlSupport_KatmaiRTM_Cpu64_1.log
    MSI (s) (64:94) [23:03:43:910]: Source for file 'pfbafgaq.dll' is uncompressed, at 'H:\SQLServer2008R2_SP1\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\'.
    MSI (s) (64:94) [23:03:43:926]: Executing op: SetTargetFolder(Folder=C:\Windows\winsxs\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.1833_none_8a17faaf2edd3e00\)
    MSI (s) (64:94) [23:03:43:926]: Executing op: SetSourceFolder(Folder=1\Windows\winsxs\nvdlei3o.taa\)
    MSI (s) (64:94) [23:03:43:926]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.1833,ProductCode={B40EE88B-400A-4266-A17B-
    E3DE64E94431},ProductVersion=10.1.2731,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:941]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:972]: Executing op: AssemblyCopy(SourceName=uvdlei3o.taa|
    ATL80.dll,SourceCabKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,DestName=ATL80.dll,Attributes=0,FileSize=113152,PerTick=65536,,VerifyMedia=1,ElevateFlags=4,,,,ComponentId=
    {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E},,,,AssemblyMode=0,)
    MSI (s) (64:94) [23:03:43:972]: Assembly Error:The system cannot find the path specified.
    MSI (s) (64:94) [23:03:43:972]: Note: 1: 1935 2: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E} 3: 0x80070003 4: IAssemblyCache 5: CreateAssemblyCacheItem 6:
    Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"
    MSI (s) (64:94) [23:03:43:972]: Assembly Error (sxs): Please look into Component Based Servicing Log located at -169675656ndir\logs\cbs\cbs.log to get more diagnostic information.
    MSI (s) (64:94) [23:03:49:882]: Product: Microsoft SQL Server 2008 Setup Support Files  -- Error 1935. An error occurred during the installation of assembly
    'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
    HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
    Error 1935. An error occurred during the installation of assembly
    'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
    HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
    MSI (s) (64:94) [23:03:49:882]: User policy value 'DisableRollback' is 0
    Thanks, Ted U

  • Getting error message 14 when restoring Iphone 3gs,ran diagnostic and can't find iphone.Tried everything...please help!e

    I tried to update Iphone 3gs to ios 5 with Itunes. first try,It did sync,posted my name under devices(iphone). Tried to restore,keep recieving error message 14. I ran the diagnostic and it kept saying under Port, it does'nt not find Iphone. Tried EVERYTHING! From uninstalling, youtube, google, DFU and downloading some of the so called help links and files. It also keep saying my phone is in restored mode and on the phone it shows a usb plug pointing to itunes and a cd. Trying to fix problem from home and not be charge a fee just to talk to Apple representative. Please help !!!

    http://support.apple.com/kb/TS3694#error3194
    Apple does not support downgrading, so that is probably why you are getting error 3194. As you have to hack the phone to downgrade all bets are off now. As some of the help links and files direct you to jailbreak your phone if you followed any of those you now have bigger problems.

  • Error with Both Designer and Deski

    Hi all
    Recently we had upgraded our Business objects XIR2 to XIR3.1. i am getting an error which i am trying to run the "integrity check" on a universe, and the error is Microsoft visual c++ runtime library-----> run time error! c:\programfiles\business objects\...  this application has requested the runtime to terminate it in an unusal way. please conatct app support team for more info. if i click ok on that dialouge box it another window appers saying that "Business Objects has encountered a problem and needs to close. we are sorry for inconvenience." and the program crashes it closes the designer.
    all other universes are working good. i dont know i am getting an error for this.
    and even the deski report related with it is also not working gives an error "abnormal program termination" and it crashs the deski and it closes.
    thanks in advance

    Do anybody can help me out in this
    thanks in advance

  • Unable to load ITUNES onto PC HP, windows 7 Home Version.  Error message reads "Application Application Support not found".  "Unistall and reload".  I have done that 4 times on Explorer and Firefox without success.  Help??

    Unable to load ITUNES onto PC HP, windows 7 Home Version.  Error message reads "Application Application Support not found".  "Uninstall and reload".  I have done that 4 times on Explorer and Firefox without success.  Help??

    I had gotten a similar problem, except with "provider services", i believe, but i solved it by copying sqlite3.dll from E:\Program Files\Common Files\Apple\Apple Application Support to E:\Program Files\Common Files\Apple\Mobile Device Support. doing that solved my first problem, but now i have been getting the error described in this topic (unable to load dataclass info... etc.). i tried reinstalling itunes (i already had 9.1.1, and thats what i reinstalled) by using the method described on apples site (using the "remove programs" tool in the control panel) and then downloading and installing itunes. when i opened it again, i still got the same error, and just now i got an error saying "the instruction at "0x00aadb6b" referenced memory at "0x00000008". the memory could not be read" it gave me the option to cancel and debug, or to press ok and terminate the program. I tried pressing cancel, and the popup went away but nothing else happened. a minute later the popup was back, so i pressed ok and itunes quit. Upon opening Itunes again, i got the very same error. sorry for the long post, but its really been bugging me. thanks for any help you might give, and if you need anymore info, feel free to contact me.

Maybe you are looking for