Duplicates NOT detected

I have a few guesses as to why this is happening and need a fix if you can offer one. I am trying to import only the photos that are not already in my Aperture library from a folder. I use the "do not import duplicates" check box yet Aperture still thinks that all the photos are new, even though I can clearly find a couple of them in the library. I don't want to go through all 3,000 and would like Aperture to know which ones are already in the library.
The difference between the photos from what I can tell is that the files have different creation and modification dates. Apparently, Aperture copied these photos in before when I last moved some of them in and the ones that were copied did not retain their created/modified dates.
I tried using Tidy Up!, but it doesn't detect the duplicates either.
Filenames, type, size, are the same.
First, what can I do to just import the photos I don't already have?
Second, how can I make sure that when Aperture imports, it retains the creation and modification date?
Thanks for your help.

I've been hammering Tidy Up to help with a lot of dupes and found that although it is not easy to specify settings, one you have it, the app is fast and accurate. The interface suffers from translation and logic issues, IMHO.
And, the developer is extremely responsive. Try emailing Guissepe and see if he can offer help.

Similar Messages

  • Bug: Duplicates not detected when importing photos older than year 2001

    If you import photos taken before 1st of January 2001 00:00:00, duplicates will not be detected even if you select the "Ignore duplicates" option on import. The files will be imported twice into the same location with a "-2" postfix added to their name.
    Technical details (to help developers):
    To detect duplicates, Lightroom uses a so called import hash (AgLibraryFile.importHash in the database) that has the following form:
         <capture_time><original_filename><file_size>,
    where:
    <capture_time> - interval in seconds between 1st Jan, 2001 00:00:00 and capture time recorded in Exif,
    <original_filename> - name of source file before import,
    <file_size> - file size in bytes.
    The problem here is the <capture_time> part, since it gets negative for files older than 2001, since 1st Jan 2001 is sort of  considered the beginning of time (called "epoch" in computing). Lightroom seems to get confused on negative timestamps.

    I will report this bug.  Thanks!

  • PSE9 on Mac - Duplicates Not Detected on Import

    When I use PSE9 on a Mac, the Organizer doesn't seem to recognize files that are already in its catalog and will reimport them. E.g., import a bunch of photos from an SD card then perform the action again - I find that PSE9 will import the photos each time even the files are already in the catalog. PSE9 on the PC behave as I would expect (and want) and will refuse to import the duplicates. Has anyone else seen this? Any way around it?
    thanks

    Tried importing from folder but not an issue. Will check from sd card also but have never heard of any such issue. You can try resetting the preferences. More info is also at link http://forums.adobe.com/thread/801014. Also try importing in new catalog and then check. Just reset all the settings to default. It pops up a dialog box if we try to import already existing files in catalog.
    -Garry

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • External monitor not detected on Thinkpad W530 intel-virtual-output

    I'm having problems with connecting my ThinkPad W530 to external monitors since a few months. I'm using NVIDIA Optimus and bumblebee/optirun since the VGA and Mini DisplayPort connectors are only wired to the NVIDIA card om this laptop. For a long time I have executed:
    $ optirun true
    $ intel-virtual-output
    Then I have started the Screens GUI tool in Gnome to setup the placement of the external screen but now the external screen is not present in the GUI tool and xrandr gives me:
    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
    LVDS1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
    1920x1080 60.00*+ 50.00
    1400x1050 59.98
    1280x1024 60.02
    1280x960 60.00
    1024x768 60.00
    800x600 60.32 56.25
    640x480 59.94
    VGA1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)
    If I select "Discrete mode" and select startup screen as VGA in the BIOS the BIOS and the Grub screens shows on the external monitor but the screen locks on the screen that shows that the system is booting with the linux-ck kernel. This has never worked for me in Arch Linux so that is no surprise. In Ubuntu everything everything worked fine the last time I tried.
    How can I debug this? Why is the external screen not detected any more?

    Thanks, I am not sure exactly how to read the logs but I cannot find anything that is obviously wrong
    Below is my log with an external screen connected via Mini DisplayPort and after running:
    $ optirun true
    $ intel-virtual-output
    a few times, no more logs seem to be added when I connect/disconnect the monitor or when I run the above two commands more times.
    ╰─➤ cat /var/log/Xorg.0.log 1 ↵
    [ 2.616]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 2.616] X Protocol Version 11, Revision 0
    [ 2.616] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 2.616] Current Operating System: Linux ethuil 3.13.9-1-ck #1 SMP PREEMPT Fri Apr 4 15:50:10 EDT 2014 x86_64
    [ 2.616] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-ck root=UUID=25086a9b-a542-4018-9f71-4f492f09be91 rw quiet rcutree.rcu_idle_gp_delay=1
    [ 2.616] Build Date: 09 January 2014 08:47:24AM
    [ 2.616]
    [ 2.616] Current version of pixman: 0.32.4
    [ 2.616] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2.616] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2.616] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 14 22:09:08 2014
    [ 2.624] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2.624] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 2.627] (==) No Layout section. Using the first Screen section.
    [ 2.627] (==) No screen section available. Using defaults.
    [ 2.627] (**) |-->Screen "Default Screen Section" (0)
    [ 2.627] (**) | |-->Monitor "<default monitor>"
    [ 2.628] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2.628] (==) Automatically adding devices
    [ 2.628] (==) Automatically enabling devices
    [ 2.628] (==) Automatically adding GPU devices
    [ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2.638] Entry deleted from font path.
    [ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2.638] Entry deleted from font path.
    [ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2.638] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 2.638] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2.638] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2.638] (II) Loader magic: 0x804c80
    [ 2.638] (II) Module ABI versions:
    [ 2.638] X.Org ANSI C Emulation: 0.4
    [ 2.638] X.Org Video Driver: 15.0
    [ 2.638] X.Org XInput driver : 20.0
    [ 2.638] X.Org Server Extension : 8.0
    [ 2.639] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 3.588] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21f5 rev 9, Mem @ 0xf1400000/4194304, 0xe0000000/268435456, I/O @ 0x00006000/64
    [ 3.588] (--) PCI: (0:1:0:0) 10de:0ffb:17aa:21f5 rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
    [ 3.588] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 3.589] Initializing built-in extension Generic Event Extension
    [ 3.589] Initializing built-in extension SHAPE
    [ 3.589] Initializing built-in extension MIT-SHM
    [ 3.589] Initializing built-in extension XInputExtension
    [ 3.589] Initializing built-in extension XTEST
    [ 3.589] Initializing built-in extension BIG-REQUESTS
    [ 3.589] Initializing built-in extension SYNC
    [ 3.589] Initializing built-in extension XKEYBOARD
    [ 3.589] Initializing built-in extension XC-MISC
    [ 3.589] Initializing built-in extension SECURITY
    [ 3.589] Initializing built-in extension XINERAMA
    [ 3.589] Initializing built-in extension XFIXES
    [ 3.589] Initializing built-in extension RENDER
    [ 3.589] Initializing built-in extension RANDR
    [ 3.589] Initializing built-in extension COMPOSITE
    [ 3.589] Initializing built-in extension DAMAGE
    [ 3.589] Initializing built-in extension MIT-SCREEN-SAVER
    [ 3.589] Initializing built-in extension DOUBLE-BUFFER
    [ 3.589] Initializing built-in extension RECORD
    [ 3.589] Initializing built-in extension DPMS
    [ 3.589] Initializing built-in extension Present
    [ 3.590] Initializing built-in extension DRI3
    [ 3.590] Initializing built-in extension X-Resource
    [ 3.590] Initializing built-in extension XVideo
    [ 3.590] Initializing built-in extension XVideo-MotionCompensation
    [ 3.590] Initializing built-in extension XFree86-VidModeExtension
    [ 3.590] Initializing built-in extension XFree86-DGA
    [ 3.590] Initializing built-in extension XFree86-DRI
    [ 3.590] Initializing built-in extension DRI2
    [ 3.590] (II) "glx" will be loaded by default.
    [ 3.590] (II) LoadModule: "dri2"
    [ 3.590] (II) Module "dri2" already built-in
    [ 3.590] (II) LoadModule: "glamoregl"
    [ 3.593] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 3.615] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 3.615] compiled for 1.15.0, module version = 0.6.0
    [ 3.615] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 3.615] (II) LoadModule: "glx"
    [ 3.617] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 3.618] (II) Module glx: vendor="X.Org Foundation"
    [ 3.618] compiled for 1.15.0, module version = 1.0.0
    [ 3.618] ABI class: X.Org Server Extension, version 8.0
    [ 3.618] (==) AIGLX enabled
    [ 3.618] Loading extension GLX
    [ 3.618] (==) Matched intel as autoconfigured driver 0
    [ 3.618] (==) Matched intel as autoconfigured driver 1
    [ 3.618] (==) Matched modesetting as autoconfigured driver 2
    [ 3.618] (==) Matched fbdev as autoconfigured driver 3
    [ 3.618] (==) Matched vesa as autoconfigured driver 4
    [ 3.618] (==) Assigned the driver to the xf86ConfigLayout
    [ 3.618] (II) LoadModule: "intel"
    [ 3.618] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 3.623] (II) Module intel: vendor="X.Org Foundation"
    [ 3.623] compiled for 1.15.0, module version = 2.99.911
    [ 3.623] Module class: X.Org Video Driver
    [ 3.623] ABI class: X.Org Video Driver, version 15.0
    [ 3.623] (II) LoadModule: "modesetting"
    [ 3.624] (WW) Warning, couldn't open module modesetting
    [ 3.624] (II) UnloadModule: "modesetting"
    [ 3.624] (II) Unloading modesetting
    [ 3.624] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 3.624] (II) LoadModule: "fbdev"
    [ 3.624] (WW) Warning, couldn't open module fbdev
    [ 3.624] (II) UnloadModule: "fbdev"
    [ 3.624] (II) Unloading fbdev
    [ 3.624] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 3.624] (II) LoadModule: "vesa"
    [ 3.624] (WW) Warning, couldn't open module vesa
    [ 3.624] (II) UnloadModule: "vesa"
    [ 3.624] (II) Unloading vesa
    [ 3.624] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 3.624] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
    [ 3.624] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
    [ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
    [ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
    [ 3.624] (++) using VT number 1
    [ 3.625] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000
    [ 3.625] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 3.625] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 3.625] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 3.625] (==) intel(0): RGB weight 888
    [ 3.625] (==) intel(0): Default visual is TrueColor
    [ 3.625] (**) intel(0): Framebuffer tiled
    [ 3.625] (**) intel(0): Pixmaps tiled
    [ 3.625] (**) intel(0): "Tear free" disabled
    [ 3.625] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 3.625] (II) intel(0): Output LVDS1 has no monitor section
    [ 3.625] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
    [ 3.625] (II) intel(0): Output VGA1 has no monitor section
    [ 3.625] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 3.625] (--) intel(0): Output LVDS1 using initial mode 1920x1080 on pipe 0
    [ 3.625] (==) intel(0): DPI set to (96, 96)
    [ 3.625] (II) Loading sub module "dri2"
    [ 3.625] (II) LoadModule: "dri2"
    [ 3.625] (II) Module "dri2" already built-in
    [ 3.625] (==) Depth 24 pixmap format is 32 bpp
    [ 3.627] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend
    [ 3.627] (==) intel(0): Backing store enabled
    [ 3.627] (==) intel(0): Silken mouse enabled
    [ 3.628] (II) intel(0): HW Cursor enabled
    [ 3.628] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 3.628] (==) intel(0): DPMS enabled
    [ 3.628] (II) intel(0): [DRI2] Setup complete
    [ 3.628] (II) intel(0): [DRI2] DRI driver: i965
    [ 3.628] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 3.628] (II) intel(0): direct rendering: DRI2 Enabled
    [ 3.628] (==) intel(0): hotplug detection: "enabled"
    [ 3.628] (--) RandR disabled
    [ 3.650] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 3.650] (II) AIGLX: enabled GLX_ARB_create_context
    [ 3.650] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 3.650] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 3.650] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 3.650] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 3.650] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 3.650] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 3.650] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 3.650] (II) AIGLX: Loaded and initialized i965
    [ 3.650] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 3.652] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 3.665] (II) intel(0): Setting screen physical size to 508 x 285
    [ 3.732] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 3.732] (**) Power Button: Applying InputClass "system-keyboard"
    [ 3.732] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 3.732] (II) LoadModule: "evdev"
    [ 3.732] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 3.734] (II) Module evdev: vendor="X.Org Foundation"
    [ 3.734] compiled for 1.15.0, module version = 2.8.2
    [ 3.734] Module class: X.Org XInput Driver
    [ 3.734] ABI class: X.Org XInput driver, version 20.0
    [ 3.734] (II) Using input driver 'evdev' for 'Power Button'
    [ 3.734] (**) Power Button: always reports core events
    [ 3.734] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 3.734] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 3.734] (--) evdev: Power Button: Found keys
    [ 3.734] (II) evdev: Power Button: Configuring as keyboard
    [ 3.734] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
    [ 3.734] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 3.734] (**) Option "xkb_rules" "evdev"
    [ 3.734] (**) Option "xkb_model" "pc104"
    [ 3.734] (**) Option "xkb_layout" "se"
    [ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    [ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.754] (**) Video Bus: always reports core events
    [ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event13"
    [ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.754] (--) evdev: Video Bus: Found keys
    [ 3.754] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
    [ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 3.754] (**) Option "xkb_rules" "evdev"
    [ 3.754] (**) Option "xkb_model" "pc104"
    [ 3.754] (**) Option "xkb_layout" "se"
    [ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
    [ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.754] (**) Video Bus: always reports core events
    [ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event14"
    [ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.754] (--) evdev: Video Bus: Found keys
    [ 3.754] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
    [ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 3.754] (**) Option "xkb_rules" "evdev"
    [ 3.754] (**) Option "xkb_model" "pc104"
    [ 3.754] (**) Option "xkb_layout" "se"
    [ 3.755] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 3.755] (II) No input driver specified, ignoring this device.
    [ 3.755] (II) This device may have been added with another device file.
    [ 3.755] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 3.755] (**) Sleep Button: Applying InputClass "system-keyboard"
    [ 3.755] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 3.755] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 3.755] (**) Sleep Button: always reports core events
    [ 3.755] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 3.755] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 3.755] (--) evdev: Sleep Button: Found keys
    [ 3.755] (II) evdev: Sleep Button: Configuring as keyboard
    [ 3.755] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event2"
    [ 3.755] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 3.755] (**) Option "xkb_rules" "evdev"
    [ 3.755] (**) Option "xkb_model" "pc104"
    [ 3.755] (**) Option "xkb_layout" "se"
    [ 3.755] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 3.755] (II) config/udev: Adding input device Integrated Camera (/dev/input/event6)
    [ 3.756] (**) Integrated Camera: Applying InputClass "system-keyboard"
    [ 3.756] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 3.756] (II) Using input driver 'evdev' for 'Integrated Camera'
    [ 3.756] (**) Integrated Camera: always reports core events
    [ 3.756] (**) evdev: Integrated Camera: Device: "/dev/input/event6"
    [ 3.756] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb2eb
    [ 3.756] (--) evdev: Integrated Camera: Found keys
    [ 3.756] (II) evdev: Integrated Camera: Configuring as keyboard
    [ 3.756] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input8/event6"
    [ 3.756] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 3.756] (**) Option "xkb_rules" "evdev"
    [ 3.756] (**) Option "xkb_model" "pc104"
    [ 3.756] (**) Option "xkb_layout" "se"
    [ 3.756] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event10)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event9)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.757] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event8)
    [ 3.757] (II) No input driver specified, ignoring this device.
    [ 3.757] (II) This device may have been added with another device file.
    [ 3.757] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
    [ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 3.757] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 3.757] (**) AT Translated Set 2 keyboard: always reports core events
    [ 3.757] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 3.757] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 3.757] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 3.757] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 3.757] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 3.757] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    [ 3.757] (**) Option "xkb_rules" "evdev"
    [ 3.757] (**) Option "xkb_model" "pc104"
    [ 3.757] (**) Option "xkb_layout" "se"
    [ 3.757] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 3.757] (II) LoadModule: "synaptics"
    [ 3.757] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 3.758] (II) Module synaptics: vendor="X.Org Foundation"
    [ 3.758] compiled for 1.15.0, module version = 1.7.4
    [ 3.758] Module class: X.Org XInput Driver
    [ 3.758] ABI class: X.Org XInput driver, version 20.0
    [ 3.758] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 3.758] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.758] (**) Option "Device" "/dev/input/event12"
    [ 3.783] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 3.783] (**) Option "TapButton1" "1"
    [ 3.783] (**) Option "TapButton2" "2"
    [ 3.783] (**) Option "TapButton3" "3"
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.783] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.793] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
    [ 3.793] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 3.793] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.793] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 3.794] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 3.794] (II) No input driver specified, ignoring this device.
    [ 3.794] (II) This device may have been added with another device file.
    [ 3.794] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event4)
    [ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "system-keyboard"
    [ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    [ 3.794] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
    [ 3.794] (**) ThinkPad Extra Buttons: always reports core events
    [ 3.794] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event4"
    [ 3.794] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
    [ 3.794] (--) evdev: ThinkPad Extra Buttons: Found keys
    [ 3.795] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
    [ 3.795] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input5/event4"
    [ 3.795] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
    [ 3.795] (**) Option "xkb_rules" "evdev"
    [ 3.795] (**) Option "xkb_model" "pc104"
    [ 3.795] (**) Option "xkb_layout" "se"
    [ 3.799] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
    [ 3.824] (II) UnloadModule: "synaptics"
    [ 3.824] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 3.824] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.824] (**) Option "Device" "/dev/input/event12"
    [ 3.844] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 3.844] (**) Option "TapButton1" "1"
    [ 3.844] (**) Option "TapButton2" "2"
    [ 3.844] (**) Option "TapButton3" "3"
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.844] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.854] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
    [ 3.854] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 3.854] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.854] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 /dev/dri/card0
    [ 3.855] xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    [ 3.855] failed to find screen to remove
    [ 3.855] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (null)
    [ 3.855] (II) config/udev: removing device Video Bus
    [ 3.863] (II) evdev: Video Bus: Close
    [ 3.863] (II) UnloadModule: "evdev"
    [ 3.863] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    [ 3.863] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.863] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.863] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.863] (**) Video Bus: always reports core events
    [ 3.863] (**) evdev: Video Bus: Device: "/dev/input/event13"
    [ 3.863] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.863] (--) evdev: Video Bus: Found keys
    [ 3.863] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.863] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
    [ 3.863] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 3.863] (**) Option "xkb_rules" "evdev"
    [ 3.863] (**) Option "xkb_model" "pc104"
    [ 3.863] (**) Option "xkb_layout" "se"
    [ 3.863] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (null)
    [ 3.863] (II) config/udev: removing device Video Bus
    [ 3.870] (II) evdev: Video Bus: Close
    [ 3.870] (II) UnloadModule: "evdev"
    [ 3.870] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
    [ 3.870] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.870] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.870] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.870] (**) Video Bus: always reports core events
    [ 3.870] (**) evdev: Video Bus: Device: "/dev/input/event14"
    [ 3.870] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.870] (--) evdev: Video Bus: Found keys
    [ 3.870] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.870] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
    [ 3.870] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 3.870] (**) Option "xkb_rules" "evdev"
    [ 3.870] (**) Option "xkb_model" "pc104"
    [ 3.870] (**) Option "xkb_layout" "se"
    [ 4.540] (II) intel(0): EDID vendor "LEN", prod id 16562
    [ 4.540] (II) intel(0): Printing DDC gathered Modelines:
    [ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 139.00 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (67.8 kHz eP)
    [ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 115.83 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (56.5 kHz e)
    [ 7.358] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event15)
    [ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
    [ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "Trackpoint Wheel Emulation"
    [ 7.358] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
    [ 7.358] (**) TPPS/2 IBM TrackPoint: always reports core events
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event15"
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
    [ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
    [ 7.358] (**) Option "Emulate3Buttons" "false"
    [ 7.358] (**) Option "EmulateWheel" "true"
    [ 7.358] (**) Option "EmulateWheelButton" "2"
    [ 7.358] (**) Option "YAxisMapping" "4 5"
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
    [ 7.358] (**) Option "XAxisMapping" "6 7"
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: XAxisMapping: buttons 6 and 7
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 7.358] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input14/event15"
    [ 7.358] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 14)
    [ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
    [ 7.359] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
    [ 7.359] (II) No input driver specified, ignoring this device.
    [ 7.359] (II) This device may have been added with another device file.
    [ 20245.335] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21030.923] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21196.939] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21209.255] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 24416.533] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 26177.657] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none

  • Dimension processing error: "duplicate id detected"

    Hi All,
    Im facing an issue where when i try to process a dimension, i get an error message ."error while processing dimensions"
    "duplicate id detected" .The reason for this is there are two identical id's with in the same dimension. "pu" & "PU".
    Im not able to root cause, how BPC allowed processing of these identical dimensions in the first place. But becoz of this, whene ever i try to add a new dimension member and process the same, i get the above mentioned error.
    Have you ever encountered this error in your applications.
    If so, what is the way out?
    Also, Is there a solution ,which does not involve deleting & re-creating the dimensions.
    Thanks in advance,
    sridhar

    Hi Sridhar,
    Best way is delete both the line and process it. The wild fact in BPC is that if if you have used ABC as dimension member in cost center, you can not have same name as dimension member in profit center as well.
    Is it not wild? So best way is delete the dimension member..but if you have posted some transaction data u have to delete the transaction data first..

  • [svn:fx-trunk] 21141: Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors .

    Revision: 21141
    Revision: 21141
    Author:   [email protected]
    Date:     2011-04-26 06:40:39 -0700 (Tue, 26 Apr 2011)
    Log Message:
    Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: When a logout was followed by an immediate login, sometimes the server would throw duplicate session detected errors. This was because when logout happened, a fire-and-forget disconnect message was sent to the server that established a new session, and if the subsequent login happened before disconnect ACK returned from the server, that would establish another session and hence the error. The fix is to insert a slight delay between disconnect and ResultEvent dispatching. This way, disconnect has a chance to return before a login is performed.
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

    You've got an  incompatible Logitech driver and java was incompletely uninstalled.
    You may have a problem with the Wacom driver.
    I don't know if fixing those things will help.
    There also a few window server errors, but I don't know if they are causal.
    If you can note the time of the hangs, that might help narrow it down in the logs.

  • Nexus 5548 - %ARP-3-DUP_SRCIP_PROBE: Duplicate address Detected

    Hello.
    Looking for some assistance on the following please, I'll try to include a lot of detail:
    I noticed we're receiving repeating messages on a pair of Nexus 5548UP switches, regarding duplicate IP's, and the IP's in question are the mgmt0 of each respective Nexus switch; which are connected to each other and uplinked to two 3750X switches which are also linked to each other (not as a stack, with optics).
    Here is a sample of the syslog message:  %ARP-3-DUP_SRCIP_PROBE:  arp [####]  Duplicate address Detected. Probe  packet received from zzzz.zzzz.zzzz on mgmt0 with destination set to our local ip, xxx.xxx.xxx.xxx
    And in ascii art, here is a diagram:  SW1&2 are 3750X (running 15.x code) and NX1&2 are Nexus 5548UP (running 6.x code)
    SW1---SW2
    |           |
    NX1---NX2
    Pretty basic box/"ring", just in case the diagram doesn't format well, with rapid spanning-tree in effect.  The Nexus are Layer2 only, and the 3750X's are Layer 2 & 3 /w HSRP on a few SVI's in them.  All vlans can pass over the connecting trunks.  And on the Nexus, the management interface (mgmt0) is connected to 3750X (NX1 to SW1 and NX2 to SW2); e.g. management is done over this vrf interface, versus it flowing through a trunk interface to a SVI on the Nexus.
    I know these messages to be erroneous as far an being actual duplicate IP's on the network, and have seen a few posts that indicate a command ("no ip arp gratuitous hsrp duplicate") typically referencing a Nexus 7000 setup has helped, but obviously as described that's not involved here.  Note: Placing that command on the mgmt0 interface of the two nexus had no positive effect.  The messages didn't start showing until after HSRP was enabled on the applicable 3750X SVI's - so seems a likely correlation.
    Essentially looking to clear this up (ideally) or suppress the messages since they're false.  Any ideas?
    Thanks!

    For those encountering this same issue, here is some information that may lead you to a resolve.
    I decided to open a TAC case to get some direct assistance, and I was directed to the 3750X's and a new feature in the 15.x code, "ip device tracking".  I was directed to remove that without specific details / steps on how to best do it (e.g. "no ip device tracking" does not remove it from the global config, as of 15.2(1)E anyway and is the most current at the time of this posting), and that didn't take, giving the message: % IP device tracking is disabled at the interface level by removing the relevant configs.  However, after doing some research on the command, I can across some similar posts on 15.x code and duplicate IP messages.... Here's two posts I referenced:
    https://supportforums.cisco.com/thread/2244042
    https://supportforums.cisco.com/thread/2239656
    I opted for the "no macro auto monitor" command in the 3750X's in global config, as mentioned in the above post(s) - This did stop the messages from occurring in the Nexus switches.  IMPORTANT NOTE:  I noticed that it did appear to bounce all the switch ports however, which could impact production - Be advised!
    I cannot speak to if the interface level command 'nmsp attach suppress' is a better route to go, which is also referenced in the posts (first one primarily) - I went the other route to not have all the extra config line entries.  I have asked Cisco what the true impact of the "no macro auto monitor" command is, and am waiting a response - Ideally there's little to none, probably depending on if you want to make use of device tracking or not... in my case, I suspect I don't have a need for this and thus there's no impact - I shall see.
    It would be ideal if code is released to disable this service / feature in the future more gracefully and/or code changes are done to remedy this issue so you can have the feature enabled (or not).  I akin this much like the "vstack" service that was introduced around 12.2(55/58)SE IOS that couldn't be disabled & left an open TCP port (not good for security scans), then with 12.2(58)SE2 they allowed it to be disabled (e.g. "no vstack" in global config).
    Hopefully these details prove of value.
    Regards.
    NOTE:  Since it doesn't seem you can"answer" your own posts, which seems silly; please note I consider this item resolved / answered.

  • Exchange 2013 - Duplicate Message Detection

    Hi,
    I am trying to resend an email from my spam firewall but it is not reaching the user. The duplication detection on the server is not allowing me to resend. If I go back older than a month I was able to successfully resend from the spam firewall. 
    How do I temporally disable the duplicate message detection on Exchange 2013 server?
    I found this from someone else for 2013 but I did not have this path in my registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server_Name>\Public-<GUID>
    Thank you

    Hi,
    After some search, I think we can adjust the expiration time of duplicate message detection. And the minimum value is 1 hour, so we don't need to wait several days.
    The registry setting is:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\<Private/Public-Guid>\Track Duplicates
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\<Private/Public-Guid>\Background Cleanup
    please refer to these articles:
    http://msexchangeguru.com/2013/04/22/transport/
    http://technet.microsoft.com/en-us/library/dd577073(v=exchg.80).aspx

  • OPA is not detecting subversion client.

    Hi All,
    The OPA help says that if the command line client version is installed then OPA automatically detects the subversion. However, the OPA on my machine is not detecting it and hence it is not available in File | Source Control menu options.
    Both OPA and Subversion client are installed on same drive and on same Folder i.e. Program files.
    I there any other prerequisite?
    Kindly help me resolve this.

    Duplicate of thread OPA and Subversion

  • Disable duplicate message detection

    Hi Folks
    there is a way to disable duplicate message detection feature?
    I need to deliver emails with same MessageID and Date.
    Thanks in advance
    Luca

    Hi Luca,
    We can create the Disable All Duplicate Detection registry entry to disable duplicate detection on a Mailbox server. It enables any message to be delivered to a recipient with a duplicate message ID. It is recommend that you make
    this change only on Mailbox servers that contain Journal mailboxes and no other mailboxes.
    The ParametersPrivate subkey in registry to disable duplicate detection for mailboxes:
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSExchangeIS/ParametersPrivate
    If the ParametersPrivate registry subkey does not exist, follow these steps:
    a. On the Edit menu, point to New, and then click Key.
    b. Type ParametersPrivate, and then press ENTER.
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. Type Disable All Duplicate Detection, and then press ENTER.
    5. On the Edit menu, click Modify.
    6. Type 1, and then click OK.
    For more information about it, please refer to:
    http://support.microsoft.com/kb/975990/en-us
    Regards,
    Winnie Liang
    TechNet Community Support

  • Windows 10 elitepad in Dock can not detect VGA monitor

    Windows 10 will not detect my external monitor.  I loaded Winbdow 10 on elitepad 1000 about 2 days ago.  This is the first time I've tried to use my extenal monitor.  My elitpad is in the elitpad docking station.  The tablet id also in the expansion Jacket.  Under windows 81.  I was able to duplicate my tablet display on to the external monitor over the VGA jack in the dock.  Now tablet can  not detect the VGA monitor.      The monitor is an HP2065 using the HP provided VGA to DVI cable.   I've tried rebooting with the monitor diconnected and then adding plugin it in .  I've run the detect monitor several times.   Any one got a solution.  The new HP support page does not even list tablet as an option for display support. Thank you 

                Ok, thats the procedure I was talking about earlier. I did that bios default factory reset just now. First the version 6 and earlier. It didn't work so I tried version 7 and later and that didn't work. I then tried version 6 and earlier again only this time pushed F10 more rapidly and got right in right when I got to the F5 and enter portion. Then I pushed F10 again to save the change and enter again to close. The PC didn't boot up the next screen like the test said it would. So I did it all again and spent some time reading what was on the bios pages but  accidently pushed ESC as the bios menu suggested instead of enter to close out   . No boot up screen again. I did another hard shutdown and then unplugged the cord for 5 minutes and this time the PC stayed off when I plugged it back in. The bios are set to default but I cannot get it to start again in safe mode or boot up. So if the power supply is working properly, and the monitor worked in safe mode, then the video card must be good. right?
              So I'm editing from the night before, its Monday morning here in Wi. and I'm sorry to say that after leaving the PC unplugged all night that when I plugged it back in this morning, the dumb thing started again without pushing the  start button.  So the only thing doing a recovery on the bios accomplished was to prove that my the video card can run the monitor in safe mode which is a good thing I guess. Hope someone has an idea as to what else I can try.-------thanks

  • IPod Touch, not detected in Windows or iTunes...

    First of all, hello to everyone...
    i want to say that i read a lot EVERYWHERE about my issue and still i couldnt find a solution...
    the problem is easy, i have a 3rd gen ipod touch, OS 4.2.1 now fully working... but, it's not detected in windows or itunes, as simple as that, and as u all have read in lots of other posts...
    my ipod is now working because i took it to an apple store and they charged it in a MAC and they had no problem at all. the MAC detected the ipod, with all its content and my ipod's name...
    but when i took it home -this has been hapenning since maybe... 5 MONTHS!-, i plug it in my PC and nothing happens...
    ok, first of all, my spec... win vista home premium 64 bits, last version of itunes...
    i tried ALL the solutions provided in APPLE official support page, and nothing happens... that means:
    1- completely uninstall itunes and then reinstalling it... i ALSO FORMATED my entire hard drive twice!!!!
    2- tried all USB ports and even an entirely different PC and nothing happened
    3- bought 3 different IPOD to USB cables and nothing happened
    4- tried setting ipod to restore, that way itunes SOMETIMES detected the ipod but i coulnt restore because of different error codes, so i had to take it several times to apple store to "unblock" it...
    the only way it works -detection and charge- is with MAC computers or dock systems such as an iHome my gf has thats the way im charging it now, but otherwise it wont work...
    i would really appreciate any help, since idont know what else to do!!
    thx in advance!!

    HI I was having some other problems getting my itouch to restore because it was not being recognized in itunes and kept erroring out. Now it has finally restored after I updated all kinds of drivers and removed and reinstalled itunes and apple software a million times,(yes this is all after installing itunes 8.1 and paying for an itouch upgrade as well) Now itunes says it cannot do anything with the ipod because it is getting an invalid response from the device. So it won't put anything back on my itouch or even show that I have plugged it in. I emailed tech support, If I find anything out I'll let you know, will you do the same for me?

  • Fax not detected,C​omm error, fax run test is all PASS,

    Hi Good Day! Im Using a HP color Laserjet Pro MFP M177fw. The Problem is sending fax messages. I do all the updates you need to installed. but the problem with my hp fax machine is still there specially i still receive a fax not detected issue,comm.error, but when i run the fax test run..the result is all PASS. especially the active tel.line,correcrt port on fax machine,tel line current test,dial tone..all the question and are PASS. The firmware is updated like..20140914. Please help me for this kind of problem. Thank You!

    Hi @ali_al , I can help you with the fax not being able to send faxes.
    Check these settings on the printer:
    Confirm the fax number:
    Go to setup, fax setup, advanced setup, confirm fax #.
    Turn off error correction:
    Go to setup, service, fax service, error correction and turn if off.
    Set the fax speed to medium:
    Go to setup, fax setup, advanced setup, fax speed and select medium.
    Turn off the private receive:
    Go to setup, fax setup, advanced setup, private receive. Turn it off.
    Test the fax.
    I have provided a document with some steps to try to see if that will resolve the issue.
    Cannot Send or Receive Faxes.
    Please provide the following information so I can assist you better.
    What type of connection do you have? (Analogue, DSL, Cable Modem)
    Are you using the 2 wire phone cable?
    Do you have distinctive ring set up on the line?
    Is there any voice mail set up?
    Do you have a answering machine? (Where is it connected to?)
    Where is the fax cable connected to? (modem, wall jack)
    Is there a phone also connected the printer?
    Have a nice day!
    Thank You.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • DVD-Audio and "can not detect sound blaster card" with Audigy2 Va

    I recently purchased an "Audigy2 Value" card from an eBay user, because I recently purchased some DVD-Audio discs. I downloaded the Audigy2 drivers from the website, and the Creative MediaSource player. 5. Surround sound worked fine for me, though sometimes the driver would reset to the default 2/2. sound and I would have to re-select 5. sound, which was annoying.
    Then I was completely unable to get the MediaSource player to recognise my DVD-Audio discs, and the EAX functionality of the player would never work. The EAX logo never appeared in the player. When I tried installing the MediaSource player from an install disc, I got the message "can not detect sound blaster card". Then I discovered the world of EEPROM problems.
    I followed advice from some other threads, including using ScanPCI to get information on the card, which yielded the following result.
    When installed on my machine (Asus A7A266 motherboard) the ScanPCI reads:
    Vendor 02h Creative Labs
    Device 0008h Unknown
    Command 0005h (I/O Access, BusMaster)
    Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
    Revision 00h, Header Type 00h, Bus Latency 20h
    Self test 00h (Self test not supported)
    PCI Class Multimedia, type Audio
    Subsystem ID 0002h Unknown
    Subsystem Vendor 02h Creative Labs
    Address 0 is an I/O Port : 0000A800h
    System IRQ 5, INT# A
    New Capabilities List Information :
    Power Management Capabilities
    Supports power state D2
    Supports power state D
    Current Power State : D0 (Device fully-operational, no power saving)
    On another machine (specs unknown, it's a "house pc") I got this (with 3 entries!):
    Vendor 02h Creative Labs
    Device 0002h EMU0K Audio Chipset (SB Li've!)
    Command 0004h (BusMaster)
    Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
    Revision 04h, Header Type 80h, Bus Latency 20h
    Self test 00h (Self test not supported)
    PCI Class Multimedia, type Audio
    Subsystem ID 002002h CT4850 SBLi've! Value
    Subsystem Vendor 02h Creative Labs
    Address 0 is an I/O Port : 00009000h
    New Capabilities List Information :
    Power Management Capabilities
    Current Power State : D0 (Device fully-operational, no power saving)
    Vendor 02h Creative Labs
    Device 7002h PCI Gameport Joystick
    Command 0004h (BusMaster)
    Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
    Revision 0h, Header Type 80h, Bus Latency 20h
    Self test 00h (Self test not supported)
    PCI Class Input, type Other
    Subsystem ID 002002h PCI Gameport Joystick
    Subsystem Vendor 02h Creative Labs
    Address 0 is an I/O Port : 00008800h
    New Capabilities List Information :
    Power Management Capabilities
    Current Power State : D0 (Device fully-operational, no power saving)
    Vendor 02h Creative Labs
    Device 0008h Unknown
    Command 0004h (BusMaster)
    Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
    Revision 00h, Header Type 00h, Bus Latency 20h
    Self test 00h (Self test not supported)
    PCI Class Multimedia, type Audio
    Subsystem ID 0002h PCI Gameport Joystick (Guess Only!)
    Subsystem Vendor 02h Creative Labs
    Address 0 is an I/O Port : 00008400h
    New Capabilities List Information :
    Power Management Capabilities
    Supports power state D2
    Supports power state D
    Current Power State : D0 (Device fully-operational, no power saving)
    (Just a note: above you can clearly see that it does not say I have an Audigy, it thinks it is a SBLi've. Is this normal? The card IS an Audigy 2, it says so on the card.)
    So, I put the card back on my own PC, thinking this has fixed my EEPROM, but I get the same as before. Subsystem ID 0002h. And of course the install software will not detect the card.
    I realise that I could go back to using the web drivers, but this still leaves me with MediaSource not recognising the card and not enabling DVD-Audio or EAX, which is why I bought the card in the first place!
    I have heard that the VIA chipset is possibly to blame for the EEPROM problems on the Audigy cards, and certainly it seems like it is not permanent, since it gave different information on the other PC. So now I am seriously considering getting a new motherboard.
    Do other motherboards cause this same problem? I don't want to buy another board and get the same trouble. All I want is to be able to install my MediaSource and have it recognise my card so I can listen to my DVD-Audio discs.
    Cheers,
    Russ.

    Figured out my problem. Installing the drivers from the web to begin with was a bad idea. They just did not work properly with the card.
    The "card not found" problem has gone as well, after installing it in another PC. I am also using the proper install disc now, as the other one I was using turned out to not be for the Audigy 2 value after all, but was an Audigy 2 install disc. That easily explains the "Card not found" error. The differing results from the ScanPCI program are still bizarre, though.
    Thanks to all of the people on the forum who posted information in other threads to help me deal with this issue. For now I am sticking with the original drivers from the disc and I am not upgrading.

Maybe you are looking for

  • Why is my thunderbird acting very slow and keeps giving me (not responding)

    I have just purchased a brand new HP all in one touch screen computer for work, which has windows 8 installed on it. We all use firefox as a browser as well as thunderbird for an email. My firefox seems to be working just fine however my thunderbird

  • Video on 2nd Monitor distorted and half sized

    My superintendent has a X300 series laptop that he got when they first came out. We are running Windows XP Pro with SP3 on it. He has always connected a 2nd larger LCD screen on the vga output connector when in his office which has been working great

  • Coverflow Display Issue

    I'm using coverflow on a network drive (1gb link) of pictures. Finder has loaded all the thumbnails/previews and everything looks ok. However when you scroll to the next picture, you get a brief flash of the blank ? icon, before the picture shows. Ve

  • Full screen from embedded video

    I would like to watch a live stream that is embedded on a webpage. Is there a way to get it to play full screen in Quicktime? If it wasn't live I know I could just save it and then run it on QT stand-alone, but what about if it's live? Thanks

  • Lost permission to my external drive after : Debugger called : panic

    Hi, I run Snow Leopard. Yesterday, I installed a RAID array using an external disk. The result was that the external disk was connected but, it did not seem to work. I have many external disk and many partition on my boot disk. They are all protected