UWL configuration - strange behavior

Ciao SDN,
i'm trying to configure UWL (again!!).
When i go through
System Admin>System Configuration>Universal Worklist & workflow> Universal Worklist
i got the message: "The specified root item cannot be retrieved from the configuration. Correct the entry before trying again."
This is a very strange behavior, because some time ago i had already configured UWL and all works fine.
Help me...
Luca

Hi Luca,
Please have a look at this thread.
SAP Enterprise Portal : Administration and Development
Regards,
Sumit

Similar Messages

  • IMac mouse problems / strange behavior (impossible to configure mouse preferences)

    I work in a design and communication school, the used hardware is iMac (Intel) whit Lion (OS X 10.7), we have several rooms equipped with these Macs where students light up their data on the server.
    Today, 3 of these Macs had problems with the mouse, including mine.
    Basically the clicks don´t work correctly. We cant close windows, open folders or change some options by clicking, but we can open softwares, scroll.
    In safari if i search something, when I try to click the link i want, safari opens a new tab instead the one i am at, and has other strange behaviors. So I´ve tried to change the mouse settings, and when i make a change, for example: change the scroll button to "buttun 3" the mouse automatically assumes all buttons to dashboard, but not at the configurations window because it says that scrool button still "button 3",  when i use the click or the scroll or any button it just slid me to dashboard or a setting that has nothing to do with my option.
    This is really causing a big problem since we are a school.. I already tried to change the mouse, clean, try another usb ports, search for update or restart but it still doing the same.
    I think it have something to do with an update.. but not sure.. would be really gratefull if someone knows how to solve this.
    As a temporary solution,i disabled all options using only the mouse click, but to do it, i had to plug in my tablet (that works perfectly for the record) and use it instead of mouse (since it was impossible to use it), than went to mouse preferences and disable left click, scroll and side buttons and then restart the Mac (or else it wont work)..
    it will work fine but still a problem cause I use all mouse buttons custom as well as the students...

    I have been experiencing a freezing mouse as well. I updated the mouse drivers but it is still happening. I have been repairing the permissions and noticed something very strange see the mention of a -t. I have been running unix systems since 1984 and have never seen that before....
    Determining correct file permissions.
    Permissions differ on ./Library, should be drwxrwxr-t , they are drwxrwxr-x
    Owner and group corrected on ./Library
    Permissions corrected on ./Library
    Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
    Owner and group corrected on ./private/var/log/secure.log
    Permissions corrected on ./private/var/log/secure.log
    Permissions repair complete
    Permissions differ on ., should be drwxrwxr-t , they are drwxr-xr-x
    Owner and group corrected on .
    Permissions corrected on .
    The privileges have been verified or repaired on the selected volume
    I reported this to Apple and they told me to erase the hard drive reinstall the
    system. I really don't want to have to do that. It seems like something is taking
    control of the machine.....

  • Report FP_TEST_00 - Strange behavior

    Hello Gurus,
    A strange behavior with report FP_TEST_00 occurs:
    SA38 --> FP_TEST_00 --> select a device --> execute --> print preview then and error or popup is show:
    Adobe Reader
    Error initializing the font server module
    Then the SAP GUI is closed, I check the ST22 and no dump is generated and in transaction SM21 only appear:
    DP  Q0  4 Connection to user 551 (ADMIN ), terminal 86 (HUSVP-SAP-BA) lost
    DP  Q0  I Operating system call recv failed (error no. 232 )
    The #1 log entry: *
    Details Page 2 Line 28 System Log: Local Analysis of sapdev                   1
    Time     Type Nr Clt User TCode Grp N Text
    11:37:20 DP                     Q0  4 Connection to user 551 (ADMIN ), terminal 86 (HUSVP-SAP-BA) lost
    Connection to user 551 (ADMIN ), terminal 86 (HUSVP-SAP-BA) lost
    Details
    Recording at local and central time........................ 25.02.2010 11:37:20
    Task...... Process    User...... Terminal Session TCode Program Cl Problem cl         Package
    11092      Dispatcher                                           K  SAP Web AS Problem STSK
    Further details for this message type
    Module nam Line Error text..........              Caller.... Reason/cal
    dpxxdisp   1223 551  ADMIN       86  HUSVP-SAP-BA DpRTmPr    NiBufRe
    Documentation for system log message Q0 4 :
    The SAP Dispatcher (part of the application server) has lost the
    connection to a terminal process.  For example, this happens when the
    terminal program (GUI) terminates without correctly logging off the
    application server.  More detailed information about the error
    context is not available here.
    Technical details
    File Offset RecFm System log type             Grp N variable message data
       21 254340 m     Error (Function,Module,Row) Q0  4 551  ADMIN       86  HUSVP-SAP-BA     DpRTmPrNiBufRedpxxdisp1223
    The #2 Log show: *
    Details Page 2 Line 29 System Log: Local Analysis of sapdev                   1
    Time     Type Nr Clt User TCode Grp N Text
    11:37:20 DP                     Q0  I Operating system call recv failed (error no. 232 )
    Operating system call recv failed (error no. 232 )
    Details
    Recording at local and central time........................ 25.02.2010 11:37:20
    Task...... Process    User...... Terminal Session TCode Program Cl Problem cl         Package
    11092      Dispatcher                                           K  SAP Web AS Problem STSK
    Further details for this message type
    Module nam Line Error text        Caller.... Reason/cal
    nixxi.cp   4435           recv232 NiIRead    recv
    Documentation for system log message Q0 I :
    The specified operating system call was returned with an error.
    For communication calls (receive, send, etc) often the cause of errors
    are network problems.
    It could also be a configuration problem at operating system level.
    (file cannot be opened, no space in the file system etc.).
    Additional specifications for error number 232
    Name for errno number ECONNRESET
    No documentation available for error ECONNRESET
    Technical details
    File Offset RecFm System log type             Grp N variable message data
      21 254520 m     Error (Function,Module,Row) Q0  I           recv232                     NiIReadrecv   nixxi.cp4435
    Edited by: Hernando Polania Cadena on Feb 25, 2010 8:36 PM

    Hello All,
    I applied the solution in page
    http://wiki.sdn.sap.com/wiki/display/PLM/Adobe%209%20-%20SAPGUI%20crash
    Works OK
    Thanks
    Hernando

  • Strange behavior of "Partial message encryption "  in OWSM

    Strange behavior of “Partial message encryption “  in OWSM
    If message format is like this
    <cban:transferFund xmlns:cban="http://cbank.com">
    <cban:arg0>string</cban:arg0>   
    <cban:arg1>string</cban:arg1>   
    </cban:transferFund>
    Then body element configuration in message encryption setting
    Name space  http://cbank.com
    Element arg0
    is working fine
    But my requirement is for below message
    <cban:transferFund xmlns:cban="http://cbank.com"> <!--Optional:-->    <
    <arg0>string</arg0>   
    <arg1>string</arg1 >
    </cban:transferFund>
    For this
    Name space : http://cbank.com
    Element : I tried all possible combination but none is working
    I tried these
    :arg0
    //:arg0
    //cban:arg0
    //cban//arg0
    cban:arg0
    With Regards
    Siddharth

    Had the same problem, could not get it to be consistent. I would say this is a bug, but decided to edit payloads via the database in the end...

  • Strange Behavior connecting to Oracle

    Hi to All,
    On Server Windows 2003 I have installed Oracle 10g R2. On this Server run Toad for Oracle.
    If I run Oracle console, all work fine; running Toad the ORA-12154 error is displayed.
    I have tried to connect to DB with Toad from a client and all works.
    Have someone an idea on this strange behavior ?
    Thank You and Best Regards
    Gaetano

    This may be a problem?NO!
    12154, 00000, "TNS:could not resolve the connect identifier specified"
    // *Cause:  A connection to a database or other service was requested using
    // a connect identifier, and the connect identifier specified could not
    // be resolved into a connect descriptor using one of the naming methods
    // configured. For example, if the type of connect identifier used was a
    // net service name then the net service name could not be found in a
    // naming method repository, or the repository could not be
    // located or reached.
    // *Action:
    //   - If you are using local naming (TNSNAMES.ORA file):
    //      - Make sure that "TNSNAMES" is listed as one of the values of the
    //        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA)
    //      - Verify that a TNSNAMES.ORA file exists and is in the proper
    //        directory and is accessible.
    //      - Check that the net service name used as the connect identifier
    //        exists in the TNSNAMES.ORA file.
    //      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
    //        file.  Look for unmatched parentheses or stray characters. Errors
    //        in a TNSNAMES.ORA file may make it unusable.
    //   - If you are using directory naming:
    //      - Verify that "LDAP" is listed as one of the values of the
    //        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA).
    //      - Verify that the LDAP directory server is up and that it is
    //        accessible.
    //      - Verify that the net service name or database name used as the
    //        connect identifier is configured in the directory.
    //      - Verify that the default context being used is correct by
    //        specifying a fully qualified net service name or a full LDAP DN
    //        as the connect identifier
    //   - If you are using easy connect naming:
    //      - Verify that "EZCONNECT" is listed as one of the values of the
    //        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA).
    //      - Make sure the host, port and service name specified
    //        are correct.
    //      - Try enclosing the connect identifier in quote marks.
    //   See the Oracle Net Services Administrators Guide or the Oracle
    //   operating system specific guide for more information on naming.This error is clear.
    SQL*Net is being asked to resolved TNS_ALIAS & it reports that it can not find the requested name.
    EITHER
    1) the requested name is not correct
    or
    2) SQL*Net is looking in the wrong tnsnames.ora file & still not finding the requested name.
    Good Luck solving your mystery

  • Adding custom navigation rules results in strange behavior

    Hello,
    We'd like to add navigation rules to our application. To avoid post-JHeadstart-generation-steps we created an extra faces-config-custom.xml file which contains the navigation rules. When adding this file to the web.xml and run the aplication we encounter strange behavior
    - Errors are shown in duplicate
    - 'Transaction completed' messages are not shown
    Try adding the underneath faces-config-custom.xml to a standard HR demo project and you will get the same behavior.
    (1) What is the reason of this strange behavior?
    (2) How can we add custom navigation rules, without having to do post creation steps?
    Regards Leon
    [faces-config-custom.xml]
    <?xml version="1.0" encoding="windows-1252" ?>
    <!DOCTYPE faces-config PUBLIC
    "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
    "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config xmlns="http://java.sun.com/JSF/Configuration">
    <navigation-rule>
    <from-view-id>*</from-view-id>
    <navigation-case>
    <from-outcome>BezwaarVerzoeken</from-outcome>
    <to-view-id>/pages/inboeken/BezwaarVerzoeken.jspx</to-view-id>
    </navigation-case>
    <navigation-case>
    <from-outcome>LosseOpdrachten</from-outcome>
    <to-view-id>/pages/inboeken/LosseOpdrachten.jspx</to-view-id>
    </navigation-case>
    </navigation-rule>
    </faces-config>
    [Add faces-config-custom.xml to web.xml]
    <context-param>
    <param-name>javax.faces.CONFIG_FILES</param-name>
    <param-value>/WEB-INF/faces-config-custom.xml,...

    Leon,
    When you perform a drag and drop operation, JDeveloper adds the following lines to the faces-config.xml:
    <lifecycle>
    <phase-listener>
    Oracle.adf.controller.faces.lifecycle.ADFPhaselistener
    </phase-listener>
    </lifecycle>
    However, JHeadstart uses its own subclass of ADFPhaselistener, and defines the lifecycle element in JhsCommon-beans.xml. Due to a bug in ADF, ADF does not look for the lifecycle element in other files than faces-config, and adds its own element in faces-config.xml If you remove these lines, everything works fine again.
    To prevent this from happening again, you can move the following entry from JhsCommon-beans.xml to faces-config.xml:
    <lifecycle> <phase-listener>oracle.jheadstart.controller.jsf.lifecycle.JhsADFPhaseListener</phase-listener>
    </lifecycle>
    And then make a custom template for JhsCommon-beans.vm where you remove this entry.
    Steven Davelaar,
    JHeadstart team.

  • 802.1x "MachineorUser" Auth Mode strange behavior in 2950 & 3750 Switches

    Good Day Support Team around the world,
    Having started recently  tests with 802.1x in a lab environment, I noticed  a strange behavior related to authentication. First let me provide you with the network components I used.
    supplicant:                    domain-joined laptop with Windows XP SP3 802.1x embedded client
    authenticator1:              Cisco 2950-24   
    authenticator2:              Cisco 3750-24
    authentication server:     MS NPS Windows Server 2008
    1.     In the first scenario with 3750 switch when I connect the laptop to relevant port the machine authentication is successful. Then I try to login with a domain account and again the authentication is completed without any problem. Then I log off and user authentication is revoked and the machine authentication is used again without any issue. When I try to login again as local user the authentication fails as expected but the port remains disabled (port blinking amber) regardless the fact that port is configured for Auth-Fail Vlan. When I log off then the machine authentication is used again and the access is granted.
    2.     In the second scenario with 2950 switch as authenticator, I follow the same steps as before and when I try to login as local user the authentication is failed and the port is assigned the Auth-Fail Vlan (as expected based on configuration). However when I log off it seems that the 2950 switch still use the Auth-Fail Vlan for that port and never authenticates again for machine authentication.
    Could you please let me someone know if this is normal ( I suppose no). Please find attached the relevant debug output from the second scenario.
    Thank you!!!

    Hi,
    basically what happens is that the maximum EAP packet size for communication between client and RADIUS server is negotiated. Therefore, in your case the switch notifies NPS that the client is capable of handling packets up to 9000 bytes in size.
    EAP messages, especially those containing the server certificate, are usually bigger than 1500 bytes and arrive at the switch in multiple fragments:
    Mar  6 15:50:11.881: RADIUS(0000002C): Received from id 1645/41
    Mar  6 15:50:11.881: RADIUS/DECODE: EAP-Message fragments, 253+253+253+253+253+253+253+253+20, total 2044 bytes
    Having learned that 2044 bytes is acceptable for the client, the switch forwards the full message in one chunk, but since your client is likely to have set the interface MTU to 1500, the packet is oversized and never reaches its destination.
    And yes, I think changing the System Jumbo MTU to 1500 bytes would lead to the same result. If my memory serves me right, a new setting takes effect only after a reboot, so I'd suggest giving it a go in your lab first.
    Best regards,
    Josef

  • Cropping LR4 occasional strange behavior experienced by others?

    The LR4 cropping process has become unstable during use on several occasions.  The LR4 cropping tool seems to get confused.
    During the cropping process, unwanted changes to position and leveling of the cropped area happen upon exiting.  The cropped image one saw immediately before exiting is not what one sees afterwards. The crop has changed on its own.  During the episode, the response to the mouse is not normal.  One may drag the corner only to have it spring back upon release of the button.
    Exiting LR4 and reentering does not cure the behavior.  One must open image in Develop module,  restore crop defaults, exit, and reenter batch tool to restore normal behavior.  I am not certain as to the exact order of these steps but essentially normalcy was restored during their implementation.
    I have notice that this abnormal behavior seems more likely to occur during sessions when I am making use of the "Previous" button.
    As far as I know, the behavior is not reproducible.  It occurs during some of those late night sessions and I have not documented it well but will do so if we don’t have a cure by next time it occurs.
    My configuration:  
    Lightroom version: 4.2 [850741]
    Operating system: Windows 7 Ultimate Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Physical processor count: 8
    Processor speed: 3.3 GHz
    Built-in memory: 16364.3 MB
    Real memory available to Lightroom: 16364.3 MB
    Real memory used by Lightroom: 1066.6 MB (6.5%)
    Virtual memory used by Lightroom: 1090.4 MB
    Memory cache size: 0.0 MB
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080

    Replacing the Lr preference file may help. The preference file can go "funny" and then causes all kinds of strange behavior of Lr.
    Replacing the preference file takes about 10 minutes, and you don`t need to re-install Lr.
    BTW: Un-installing and re-installing Lr does not replace the preference file.
    See here for instructions o  how to replace the preference file: http://lightroomers.com/replacing-the-lightroom-preference-file/745/
    See  here where to find the preference file: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-4.html

  • WVC54GCA strange behavior

    Hey Guys, I've added my fifth camera. And the rest work great and can access remotely. But my fifth one is a WVC54GCA with audio. And I am getting strange behaviors. For example, when I'm hard wired , I am able to view the video by browsing to the camera. However, when I configure wireless, and not even go wireless, still connected via LAN I can't view the video, it is almost as if the web server in it get hosed, even the graphics change and the Linksys banner is missing and I see this at the top of each menu page:File menu_setup.htm not found. Also another example, is under admin, the buttons for firmware upgarde and factory reset are invisible, I can still tab to them and use them. That's why I think it is a web server issue with itself. I am on rev V1.00R24, my other cam that is behaving correctly is on R22.
    When I go wireless, same problem, I am unable to browse to the camera to view the image, however, I am able to see the picture via the video monitoring utility. I can browse to the camera to 'administer' it but even that doesn't work right either. Especially the basic menu. If I try changing anything, LED, or time or anything, I get a error saying invalid subnet mask. When I didn't change it, plus it is obviously correct since I can browse to it. The cameras address is 192.168.1.122/24 and the gateway is 192.168.1.23, the same mask and DG on all my other cameras.
    I've rebooted the camera and the linksys router and still get the same issue. Has anyone got any ideas? I am barely ok, since I can view the image via the monitor utlity, but it would be nice if the camera work correctly like the other 4. Is their a limit to the number of wireless cam's? I have 5 total now.

    I to have had strange issues with the WVC54GCA.  I have two cameras.  I set them up in my office first for testing.  The final place they will be is at my summer place for monitoring when I'm away.  I had a break-in last year. 
    In the office I had issues primarily with the motion detection email feature.  It simply would not work.  The test messages work just fine every time.  So I know the email config information is correct. I'm not sure if we just did not wait long enough or if it was the scheduled capture we setup, however it seems that until we setup a scheduled capture and deleted it; the motion capture would not work.  So after about 3 hours of testing and cofiguring and resetting we had it capturing pics and video.  BTW we are using a VRV200 at the office.
    Next, took the camera's out to the summer place.  Setup them up from scratch, did a hard reset.  Main issue, same as in the office (using a wrt54g at the summer place) not doing a capture.  Test email works fine,  No capture. Not even after playing the set a scheduled capture trick.  Tried everything I can think of, no luck, no capture.  As you can imagine, if it won't capture, then it is useless for remote monitoring of a summer place.
    I checked for a firmware update for the WVC54GCA, however its brand-d-new, so there is only one version of the firmware and that's the one that came on the camera.
    Any ideas would be welcomed.  I must have a capture solution.  Maybe I just need to buy a more expensive camera.
    Message Edited by EmarioC on 06-07-2008 08:18 AM
    Message Edited by EmarioC on 06-07-2008 08:19 AM

  • Strange behavior after suspend.

    Hi,
    For some time I have a strange behavior of my system after I awake my computer(after suspend). This problem don't disappear after update.
    Ok, so if I suspend my computer, and awake him I can't run any program. Even if i was open some application, this application crashes. I have to restart my machine.
    Somebody had similar problem or know how help?
    I'm using Arch Linux x64, kernel 3.8, openbox. Suspend by "systemctl suspend".

    OK, maybe good idea is paste here my output journal:
    # journalctl --since=today | tac | sed -n '/-- Reboot --/{n;:r;/-- Reboot --/q;p;n;b r}' | tac
    -- Logs begin at Mon 2012-09-10 20:20:07 CEST, end at Thu 2013-03-28 10:17:18 CET. --
    Mar 28 10:10:36 localhost kernel: Freezing user space processes ... (elapsed 0.01 seconds) done.
    Mar 28 10:10:36 localhost systemd[1]: Time has been changed
    Mar 28 10:10:36 localhost systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
    Mar 28 10:10:36 localhost kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
    Mar 28 10:10:36 localhost dhcpcd[1435]: eth1: carrier lost
    Mar 28 10:10:36 localhost kernel: PM: Entering mem sleep
    Mar 28 10:10:36 localhost kernel: Suspending console(s) (use no_console_suspend to debug)
    Mar 28 10:10:36 localhost kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Mar 28 10:10:36 localhost kernel: sd 0:0:0:0: [sda] Stopping disk
    Mar 28 10:10:36 localhost kernel: cfg80211: Calling CRDA for country: PL
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] IRQ 46 Disabled
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Preparing suspend fglrx in kernel.
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Suspending fglrx in kernel completed.
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Power down the ASIC .
    Mar 28 10:10:36 localhost kernel: PM: suspend of devices complete after 1126.292 msecs
    Mar 28 10:10:36 localhost kernel: PM: late suspend of devices complete after 0.263 msecs
    Mar 28 10:10:36 localhost kernel: r8169 0000:09:00.0: System wakeup enabled by ACPI
    Mar 28 10:10:36 localhost kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
    Mar 28 10:10:36 localhost kernel: PM: noirq suspend of devices complete after 52.988 msecs
    Mar 28 10:10:36 localhost kernel: ACPI: Preparing to enter system sleep state S3
    Mar 28 10:10:36 localhost kernel: PM: Saving platform NVS memory
    Mar 28 10:10:36 localhost kernel: Disabling non-boot CPUs ...
    Mar 28 10:10:36 localhost kernel: smpboot: CPU 1 is now offline
    Mar 28 10:10:36 localhost kernel: smpboot: CPU 2 is now offline
    Mar 28 10:10:36 localhost kernel: smpboot: CPU 3 is now offline
    Mar 28 10:10:36 localhost kernel: Extended CMOS year: 2000
    Mar 28 10:10:36 localhost kernel: ACPI: Low-level resume complete
    Mar 28 10:10:36 localhost kernel: PM: Restoring platform NVS memory
    Mar 28 10:10:36 localhost kernel: Extended CMOS year: 2000
    Mar 28 10:10:36 localhost kernel: CPU0: Thermal monitoring handled by SMI
    Mar 28 10:10:36 localhost kernel: Enabling non-boot CPUs ...
    Mar 28 10:10:36 localhost kernel: smpboot: Booting Node 0 Processor 1 APIC 0x4
    Mar 28 10:10:36 localhost kernel: CPU1: Thermal monitoring handled by SMI
    Mar 28 10:10:36 localhost kernel: CPU1 is up
    Mar 28 10:10:36 localhost kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
    Mar 28 10:10:36 localhost kernel: CPU2: Thermal monitoring handled by SMI
    Mar 28 10:10:36 localhost kernel: CPU2 is up
    Mar 28 10:10:36 localhost kernel: smpboot: Booting Node 0 Processor 3 APIC 0x5
    Mar 28 10:10:36 localhost kernel: CPU3: Thermal monitoring handled by SMI
    Mar 28 10:10:36 localhost kernel: CPU3 is up
    Mar 28 10:10:36 localhost kernel: ACPI: Waking up from system sleep state S3
    Mar 28 10:10:36 localhost kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
    Mar 28 10:10:36 localhost kernel: sdhci-pci 0000:07:00.0: MMC controller base frequency changed to 50Mhz.
    Mar 28 10:10:36 localhost kernel: sdhci-pci 0000:07:00.0: proprietary Ricoh MMC controller disabled (via firewire function)
    Mar 28 10:10:36 localhost kernel: sdhci-pci 0000:07:00.0: MMC cards are now supported by standard SDHCI controller
    Mar 28 10:10:36 localhost kernel: PM: noirq resume of devices complete after 133.780 msecs
    Mar 28 10:10:36 localhost kernel: PM: early resume of devices complete after 0.127 msecs
    Mar 28 10:10:36 localhost kernel: ehci-pci 0000:00:1a.0: setting latency timer to 64
    Mar 28 10:10:36 localhost kernel: mei 0000:00:16.0: irq 43 for MSI/MSI-X
    Mar 28 10:10:36 localhost kernel: snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
    Mar 28 10:10:36 localhost kernel: pci 0000:00:1e.0: setting latency timer to 64
    Mar 28 10:10:36 localhost kernel: ehci-pci 0000:00:1d.0: setting latency timer to 64
    Mar 28 10:10:36 localhost kernel: ahci 0000:00:1f.2: setting latency timer to 64
    Mar 28 10:10:36 localhost kernel: snd_hda_intel 0000:02:00.1: irq 45 for MSI/MSI-X
    Mar 28 10:10:36 localhost kernel: r8169 0000:09:00.0: System wakeup disabled by ACPI
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Power up the ASIC
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Preparing resume fglrx in kernel.
    Mar 28 10:10:36 localhost kernel: Extended CMOS year: 2000
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] Resuming fglrx in kernel completed.
    Mar 28 10:10:36 localhost kernel: <6>[fglrx] IRQ 46 Enabled
    Mar 28 10:10:36 localhost kernel: ata5: SATA link down (SStatus 0 SControl 300)
    Mar 28 10:10:36 localhost kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Mar 28 10:10:36 localhost kernel: ata2.00: configured for UDMA/100
    Mar 28 10:10:36 localhost kernel: usb 2-1.3: reset low-speed USB device number 3 using ehci-pci
    Mar 28 10:10:36 localhost kernel: sdhci-pci 0000:07:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 28 10:10:36 localhost kernel: firewire_core 0000:07:00.3: rediscovered device fw0
    Mar 28 10:10:36 localhost kernel: usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
    Mar 28 10:10:36 localhost kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Mar 28 10:10:36 localhost kernel: ata1.00: configured for UDMA/133
    Mar 28 10:10:36 localhost kernel: sd 0:0:0:0: [sda] Starting disk
    Mar 28 10:10:36 localhost kernel: PM: resume of devices complete after 2478.795 msecs
    Mar 28 10:10:36 localhost kernel: PM: Finishing wakeup.
    Mar 28 10:10:36 localhost kernel: Restarting tasks ... done.
    Mar 28 10:10:36 localhost kernel: video LNXVIDEO:00: Restoring backlight state
    Mar 28 10:10:36 localhost slim[806]: Conky: can't open /sys/class/power_supply/BAT0/uevent: No such file or directory
    Mar 28 10:10:36 localhost slim[806]: Conky: can't open /proc/acpi/battery/BAT0/state: No such file or directory
    Mar 28 10:10:36 localhost systemd-sleep[4208]: System resumed.
    Mar 28 10:10:36 localhost dbus-daemon[800]: dbus[800]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
    Mar 28 10:10:36 localhost dbus[800]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
    Mar 28 10:10:36 localhost su[4307]: (to root) root on none
    Mar 28 10:10:36 localhost su[4307]: pam_unix(su:session): session opened for user root by (uid=0)
    Mar 28 10:10:36 localhost systemd[1]: Starting Daemon for power management...
    Mar 28 10:10:36 localhost su[4307]: pam_unix(su:session): session closed for user root
    Mar 28 10:10:36 localhost su[4328]: (to root) root on none
    Mar 28 10:10:36 localhost su[4328]: pam_unix(su:session): session opened for user root by (uid=0)
    Mar 28 10:10:36 localhost su[4328]: pam_unix(su:session): session closed for user root
    Mar 28 10:10:36 localhost systemd[1]: Started Suspend.
    Mar 28 10:10:36 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
    Mar 28 10:10:36 localhost systemd[1]: Stopping Sleep.
    Mar 28 10:10:36 localhost systemd[1]: Stopped target Sleep.
    Mar 28 10:10:36 localhost systemd[1]: Starting Suspend.
    Mar 28 10:10:36 localhost systemd[1]: Reached target Suspend.
    Mar 28 10:10:36 localhost systemd-logind[796]: Operation finished.
    Mar 28 10:10:36 localhost laptop-mode[4441]: Laptop mode
    Mar 28 10:10:36 localhost laptop-mode[4446]: enabled, active [unchanged]
    Mar 28 10:10:36 localhost logger[4463]: ACPI action undefined: ACPI0003:00
    Mar 28 10:10:36 localhost laptop-mode[4501]: Laptop mode
    Mar 28 10:10:36 localhost laptop-mode[4509]: enabled, active [unchanged]
    Mar 28 10:10:36 localhost laptop-mode[4534]: Laptop mode
    Mar 28 10:10:36 localhost laptop-mode[4539]: enabled, active [unchanged]
    Mar 28 10:10:36 localhost laptop-mode[4554]: Laptop mode
    Mar 28 10:10:36 localhost laptop-mode[4557]: enabled, active [unchanged]
    Mar 28 10:10:36 localhost laptop-mode[4562]: Laptop mode
    Mar 28 10:10:36 localhost laptop-mode[4563]: enabled, active [unchanged]
    Mar 28 10:10:36 localhost dbus-daemon[800]: dbus[800]: [system] Successfully activated service 'org.freedesktop.UPower'
    Mar 28 10:10:36 localhost dbus[800]: [system] Successfully activated service 'org.freedesktop.UPower'
    Mar 28 10:10:36 localhost systemd[1]: Started Daemon for power management.
    Mar 28 10:10:37 localhost ntpd[1442]: Deleting interface #3 eth1, 192.168.1.6#123, interface stats: received=135, sent=135, dropped=1, active_time=4197 secs
    Mar 28 10:10:37 localhost ntpd[1442]: 149.156.70.60 interface 192.168.1.6 -> (none)
    Mar 28 10:10:37 localhost ntpd[1442]: 149.156.24.40 interface 192.168.1.6 -> (none)
    Mar 28 10:10:37 localhost ntpd[1442]: 46.250.172.2 interface 192.168.1.6 -> (none)
    Mar 28 10:10:37 localhost ntpd[1442]: peers refreshed
    Mar 28 10:10:38 localhost su[4624]: (to root) root on none
    Mar 28 10:10:38 localhost su[4624]: pam_unix(su:session): session opened for user root by (uid=0)
    Mar 28 10:10:38 localhost laptop-mode[4653]: Laptop mode
    Mar 28 10:10:38 localhost laptop-mode[4654]: enabled, active [unchanged]
    Mar 28 10:10:38 localhost dhcpcd[1435]: eth1: carrier acquired
    Mar 28 10:10:38 localhost dhcpcd[1435]: eth1: sending IPv6 Router Solicitation
    Mar 28 10:10:38 localhost dhcpcd[1435]: eth1: rebinding lease of 192.168.1.6
    Mar 28 10:10:38 localhost dhcpcd[1435]: eth1: acknowledged 192.168.1.6 from 192.168.1.1 `TP-LINK'
    Mar 28 10:10:38 localhost dhcpcd[1435]: eth1: checking for 192.168.1.6
    Mar 28 10:10:38 localhost su[4624]: pam_unix(su:session): session closed for user root
    Mar 28 10:10:38 localhost su[4660]: (to root) root on none
    Mar 28 10:10:38 localhost su[4660]: pam_unix(su:session): session opened for user root by (uid=0)
    Mar 28 10:10:38 localhost su[4660]: pam_unix(su:session): session closed for user root
    Mar 28 10:10:38 localhost kernel: EXT4-fs (sda6): re-mounted. Opts: commit=0
    Mar 28 10:10:38 localhost kernel: EXT4-fs (sda7): re-mounted. Opts: commit=0
    Mar 28 10:10:38 localhost laptop-mode[4694]: Laptop mode
    Mar 28 10:10:38 localhost laptop-mode[4695]: enabled, active [unchanged]
    Mar 28 10:10:38 localhost logger[4698]: ACPI action undefined: ACPI0003:00
    Mar 28 10:10:38 localhost slim[806]: tint2 : invalid option "task_margin",
    Mar 28 10:10:38 localhost slim[806]: upgrade tint2 or correct your config file
    Mar 28 10:10:38 localhost slim[806]: tint2 : nb monitor 1, nb monitor used 1, nb desktop 1
    Mar 28 10:10:38 localhost slim[806]: X Error of failed request: BadWindow (invalid Window parameter)
    Mar 28 10:10:38 localhost slim[806]: Major opcode of failed request: 21 (X_ListProperties)
    Mar 28 10:10:38 localhost slim[806]: Resource id in failed request: 0x18000b0
    Mar 28 10:10:38 localhost slim[806]: Serial number of failed request: 12
    Mar 28 10:10:38 localhost slim[806]: Current serial number in output stream: 12
    Mar 28 10:10:40 localhost slim[806]: you have no weather alerts
    Mar 28 10:10:40 localhost slim[806]: processing complete
    Mar 28 10:10:40 localhost slim[806]: gathering data with curl
    Mar 28 10:10:40 localhost slim[806]: % Total % Received % Xferd Average Speed Time Time Time Current
    Mar 28 10:10:40 localhost slim[806]: Dload Upload Total Spent Left Speed
    Mar 28 10:10:40 localhost slim[806]: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: (nil); Unknown error
    Mar 28 10:10:40 localhost slim[806]: not checking for alerts
    Mar 28 10:10:40 localhost slim[806]: curl attempt timed out, trying again
    Mar 28 10:10:40 localhost slim[806]: % Total % Received % Xferd Average Speed Time Time Time Current
    Mar 28 10:10:40 localhost slim[806]: Dload Upload Total Spent Left Speed
    Mar 28 10:10:40 localhost slim[806]: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: (nil); Unknown error
    Mar 28 10:10:42 localhost dhcpcd[1435]: eth1: sending IPv6 Router Solicitation
    Mar 28 10:10:43 localhost dhcpcd[1435]: eth1: leased 192.168.1.6 for 259200 seconds
    Mar 28 10:10:45 dhcppc4 ntpd[1442]: Listen normally on 6 eth1 192.168.1.6 UDP 123
    Mar 28 10:10:45 dhcppc4 ntpd[1442]: peers refreshed
    Mar 28 10:10:45 dhcppc4 ntpd[1442]: new interface(s) found: waking up resolver
    Mar 28 10:10:45 dhcppc4 slim[806]: Traceback (most recent call last):
    Mar 28 10:10:45 dhcppc4 slim[806]: File "/home/rlk120/.scripts/gmail.py", line 9, in <module>
    Mar 28 10:10:45 dhcppc4 slim[806]: msg=temp.read()
    Mar 28 10:10:45 dhcppc4 slim[806]: File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
    Mar 28 10:10:45 dhcppc4 slim[806]: return codecs.ascii_decode(input, self.errors)[0]
    Mar 28 10:10:45 dhcppc4 slim[806]: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 375: ordinal not in range(128)
    Mar 28 10:10:45 dhcppc4 slim[806]: not checking for alerts
    Mar 28 10:10:45 dhcppc4 slim[806]: curl attempt timed out, trying again
    Mar 28 10:10:45 dhcppc4 slim[806]: % Total % Received % Xferd Average Speed Time Time Time Current
    Mar 28 10:10:45 dhcppc4 slim[806]: Dload Upload Total Spent Left Speed
    Mar 28 10:10:46 dhcppc4 slim[806]: [234B blob data]
    Mar 28 10:10:46 dhcppc4 dhcpcd[1435]: eth1: sending IPv6 Router Solicitation
    Mar 28 10:10:50 dhcppc4 dhcpcd[1435]: eth1: sending IPv6 Router Solicitation
    Mar 28 10:10:50 dhcppc4 dhcpcd[1435]: eth1: no IPv6 Routers available
    Mar 28 10:11:03 dhcppc4 slim[806]: No protocol specified
    Mar 28 10:11:03 dhcppc4 slim[806]: (chromium:4750): Gtk-WARNING **: cannot open display: :0.0
    Mar 28 10:11:31 dhcppc4 systemd-logind[796]: System is rebooting.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Sound Card.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Sound Card.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Daemon for power management...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Authorization Manager...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Graphical Interface.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Graphical Interface.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Multi-User.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Multi-User.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping ACPI event daemon...
    Mar 28 10:11:32 dhcppc4 ntpd[1442]: ntpd exiting on signal 15
    Mar 28 10:11:32 dhcppc4 acpid[793]: exiting
    Mar 28 10:11:32 dhcppc4 dhcpcd[4810]: sending signal 1 to pid 1435
    Mar 28 10:11:32 dhcppc4 dhcpcd[4810]: waiting for pid 1435 to exit
    Mar 28 10:11:32 dhcppc4 dhcpcd[1435]: received SIGHUP, releasing
    Mar 28 10:11:32 dhcppc4 dhcpcd[1435]: eth1: releasing lease of 192.168.1.6
    Mar 28 10:11:32 dhcppc4 dhcpcd[1435]: eth1: removing interface
    Mar 28 10:11:33 dhcppc4 slim[806]: Conky: received SIGHUP or SIGUSR1. reloading the config file.
    Mar 28 10:11:33 dhcppc4 slim[806]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
    Mar 28 10:11:33 dhcppc4 slim[806]: after 200200 requests (200197 known processed) with 0 events remaining.
    Mar 28 10:11:33 dhcppc4 slim[806]: Conky: received SIGHUP or SIGUSR1. reloading the config file.
    Mar 28 10:11:33 dhcppc4 slim[806]: XIO: fatal IO error 4 (Interrupted system call) on X server ":0.0"
    Mar 28 10:11:33 dhcppc4 slim[806]: after 226 requests (226 known processed) with 0 events remaining.
    Mar 28 10:11:33 dhcppc4 slim[806]: real transparency off.... depth: 24
    Mar 28 10:11:33 dhcppc4 slim[806]: xRandr: Found crtc's: 4
    Mar 28 10:11:33 dhcppc4 slim[806]: xRandr: Linking output LVDS with crtc 0
    Mar 28 10:11:33 dhcppc4 slim[806]: real transparency off.... depth: 24
    Mar 28 10:11:33 dhcppc4 slim[806]: xRandr: Found crtc's: 4
    Mar 28 10:11:33 dhcppc4 slim[806]: xRandr: Linking output LVDS with crtc 0
    Mar 28 10:11:33 dhcppc4 slim[806]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
    Mar 28 10:11:33 dhcppc4 slim[806]: after 534585 requests (534585 known processed) with 0 events remaining.
    Mar 28 10:11:33 dhcppc4 slim[806]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
    Mar 28 10:11:33 dhcppc4 slim[806]: after 163909 requests (163909 known processed) with 0 events remaining.
    Mar 28 10:11:33 dhcppc4 slim[806]: you have no weather alerts
    Mar 28 10:11:33 dhcppc4 slim[806]: processing complete
    Mar 28 10:11:33 dhcppc4 kernel: cfg80211: Calling CRDA to update world regulatory domain
    Mar 28 10:11:33 dhcppc4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    Mar 28 10:11:33 dhcppc4 netcfg-daemon[4777]: :: siec_domowa down [done]
    Mar 28 10:11:33 dhcppc4 slim[806]: Server terminated successfully (0). Closing log file.
    Mar 28 10:11:33 dhcppc4 laptop-mode[4865]: Laptop mode
    Mar 28 10:11:33 dhcppc4 laptop-mode[4866]: enabled, active [unchanged]
    Mar 28 10:11:34 dhcppc4 systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped SLiM Simple Login Manager.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Unit slim.service entered failed state
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Permit User Sessions...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Permit User Sessions.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Basic System.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target Basic System.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Daily Cleanup of Temporary Directories.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Sockets.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target Sockets.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping LVM2 metadata daemon socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed LVM2 metadata daemon socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Device-mapper event daemon FIFOs.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed Device-mapper event daemon FIFOs.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Syslog Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed Syslog Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping ACPID Listen Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed ACPID Listen Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping D-Bus System Message Bus Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed D-Bus System Message Bus Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping System Initialization.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target System Initialization.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Load Kernel Modules...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Load Kernel Modules.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Apply Kernel Variables...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Apply Kernel Variables.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Setup Virtual Console...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Setup Virtual Console.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Set Up Additional Binary Formats...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Set Up Additional Binary Formats.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Encrypted Volumes.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Encrypted Volumes.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Swap.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Swap.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Local File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Local File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounting /home...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounting /tmp...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Remote File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Remote File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounted /tmp.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounted /home.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Unmount All Filesystems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Unmount All Filesystems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Remount Root and Kernel File Systems...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Remount Root and Kernel File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Save Random Seed...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Update UTMP about System Shutdown...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Save Random Seed.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Update UTMP about System Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Reboot...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Shutting down.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
    Mar 28 10:11:35 dhcppc4 systemd[1]: Set hardware watchdog to 10min.
    Mar 28 10:11:35 dhcppc4 kernel: watchdog watchdog0: watchdog did not stop!
    Mar 28 10:11:35 dhcppc4 systemd-journal[131]: Journal stopped
    Somebody probably find interesting things in this code.
    And here is some fail slim:
    # journalctl /usr/lib/systemd/systemd --since=today
    -- Logs begin at Mon 2012-09-10 20:20:07 CEST, end at Thu 2013-03-28 10:37:18 CET. --
    Mar 28 10:10:36 localhost systemd[1]: Time has been changed
    Mar 28 10:10:36 localhost systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
    Mar 28 10:10:36 localhost systemd[1]: Starting Daemon for power management...
    Mar 28 10:10:36 localhost systemd[1]: Started Suspend.
    Mar 28 10:10:36 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
    Mar 28 10:10:36 localhost systemd[1]: Stopping Sleep.
    Mar 28 10:10:36 localhost systemd[1]: Stopped target Sleep.
    Mar 28 10:10:36 localhost systemd[1]: Starting Suspend.
    Mar 28 10:10:36 localhost systemd[1]: Reached target Suspend.
    Mar 28 10:10:36 localhost systemd[1]: Started Daemon for power management.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Deactivating swap /dev/sda8...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Sound Card.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Sound Card.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Daemon for power management...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Authorization Manager...
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Graphical Interface.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Graphical Interface.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping Multi-User.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopped target Multi-User.
    Mar 28 10:11:32 dhcppc4 systemd[1]: Stopping ACPI event daemon...
    Mar 28 10:11:34 dhcppc4 systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped SLiM Simple Login Manager.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Unit slim.service entered failed state
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Permit User Sessions...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Permit User Sessions.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Basic System.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target Basic System.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Daily Cleanup of Temporary Directories.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Sockets.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target Sockets.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping LVM2 metadata daemon socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed LVM2 metadata daemon socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Device-mapper event daemon FIFOs.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed Device-mapper event daemon FIFOs.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Syslog Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed Syslog Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping ACPID Listen Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed ACPID Listen Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping D-Bus System Message Bus Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Closed D-Bus System Message Bus Socket.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping System Initialization.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped target System Initialization.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Load Kernel Modules...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Load Kernel Modules.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Apply Kernel Variables...
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopped Apply Kernel Variables.
    Mar 28 10:11:34 dhcppc4 systemd[1]: Stopping Setup Virtual Console...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Setup Virtual Console.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Set Up Additional Binary Formats...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Set Up Additional Binary Formats.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Encrypted Volumes.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Encrypted Volumes.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Swap.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Swap.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Local File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Local File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounting /home...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounting /tmp...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Remote File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Remote File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounted /tmp.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Unmounted /home.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Unmount All Filesystems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Unmount All Filesystems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Remount Root and Kernel File Systems...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Remount Root and Kernel File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Save Random Seed...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Update UTMP about System Shutdown...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Save Random Seed.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Update UTMP about System Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Reboot...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Shutting down.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Unmount All Filesystems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped target Local File Systems (Pre).
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopping Remount Root and Kernel File Systems...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Stopped Remount Root and Kernel File Systems.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Save Random Seed...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Update UTMP about System Shutdown...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Save Random Seed.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Started Update UTMP about System Shutdown.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Reached target Final Step.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Starting Reboot...
    Mar 28 10:11:35 dhcppc4 systemd[1]: Shutting down.
    Mar 28 10:11:35 dhcppc4 systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
    Mar 28 10:11:35 dhcppc4 systemd[1]: Set hardware watchdog to 10min.
    Last edited by xorgx3 (2013-03-28 10:52:08)

  • Outlook strange behavior with error 0x800CCC13 Cannot connect to the network. Verify your network connection or modem

    Hi guys,
    I am having a strange behavior in my environment. We are running Exchange 2010 with Outlook 2007 for client access. Some of these clients needs to access some pop3 accounts from diferent vendors.
    About 2 weeks ago, we start getting error Ox800CCC13 (as described above) when users try to send email through their pop3 accounts in Outlook. This only happens to about 5 out of 100 users. I have removed the pop3 account and readded it. I was able to send
    just one email out then issue was back.
    Next, I tried sending out simple text message with no attachment. No luck. However, I noticed when I remove the signature (10 kb gif image) I was able to send out a few emails. However, issue is back with or without signature.
    For more testing, I added Mozilla Thunderbird client for the pop3 account with no exchange account and so far no error. Emails are sending out fine. I would appreciate any insight please.

    Hi, 
    This problem may occur if the Outlook 2007 client computer does not have a default gateway configured. 
    For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.To
    add this DWORD value yourself, follow these steps.
    Outlook 2007
    1.      
     Click Start, click Run, type regedit in the Open box, and then click OK.
    2.      
     Locate and then click the following subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
    3.      
     On the Edit menu, point to New, and then click DWORD Value.
    4.      
     Type DefConnectOpts, and then press ENTER.
    5.      
     Right-click DefConnectOpts, and then click Modify.
    6.      
     In the Value data box, type 0, and then click OK.
    7.      
     Exit Registry Editor.
    Sincerely
    Harry

  • Report gives strange behavior

    Hi Gurus,
    I am facing strange problem with my oracle report 10GR2 release. Problem is, when user runs a report in early part of the morning from application server, the report runs normally and it generates the PDF file with proper data. But when the same user runs the same report in later part of the day with the same parameters as he gave in the morning, the report doesn't shows any result on generated PDF file.
    At the same time if we run the report query in the data base from sqlplus, it gives the proper output. I have checked the server log and the report trace file also but I didn't found any special and abnormal thing in the log file. I have asked the application DBA also to look into this problem but they are not able to identify the problem.
    The problem occurs only in production database in acceptance and test I am not able to simulate the condition.
    Do any one knows the strange behavior of the report on the application server? If more information is required then please ask.
    Thanks in advance.

    When you say that the PDF is not generated what exactly happens
    a. The report is not generated at all and a blank page is shown up even after a prolonged period of time
    or
    b. Some error is thrown (REP errors)
    Apart from this, what is the value set of maxConnect attribute in reports server configuration file located in <ORACLE_HOME>\reports\conf directory.
    Edited by: Anand on Nov 20, 2010 9:43 AM

  • Strange behavior on my network... Has my home system been compromised?  A disgruntled employee (sysAdmin) could have full access...worried...

    I have been experiencing a lot of strange behavior on my home network ever since a disgruntled employee was let go.  He was a server admin and had root access to my home network - where I run my business.  I am getting a ton of span now, my websites were all infected with xss hacks, and many of my accounts are blacklisted.  I did a clean install and DoD erase pass on my hardware, but I still see a lot of errors and my hosts file and VMs look very odd.  not to mention the extremely odd loops in my ifconfig...  Any help? 
    Here is an output of 'ifconfig'
    (FYI, I am a software dev, so feel free to speak the jargon and ask for specific things)
    (I hid any identifying info with either xx or my:ma:ca:dd:re:ss or something like that)
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        nd6 options=1<PERFORMNUD>
    gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
    stf0: flags=0<> mtu 1280
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
        ether th:is:ad:dr:es:s1
        inet6 fxxx::xx2a:xxff:fxxx:fxxx%en0 prefixlen 64 scopeid 0x4
        inet 10.xx.xx.x netmask 0xffffff00 broadcast 10.xx.xx.xxx
        nd6 options=1<PERFORMNUD>
        media: autoselect (1000baseT <full-duplex,flow-control,energy-efficient-ethernet>)
        status: active
    en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether th:is:ad:dr:es:n1
        inet6 fe80::e2f8:47ff:fe29:6ec2%en1 prefixlen 64 scopeid 0x5
        inet 10.xx.xx.x netmask 0xffffff00 broadcast 10.xx.xx.xxx
        nd6 options=1<PERFORMNUD>
        media: autoselect
        status: active
    fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
        lladdr 70:cd:xx:ff:fe:xx:xx:xx
        nd6 options=1<PERFORMNUD>
        media: autoselect <full-duplex>
        status: inactive
    en2: flags=8922<BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        options=60<TSO4,TSO6>
        ether my:wi:fi:ma:ca:dd
        media: autoselect <full-duplex>
        status: inactive
    bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=63<RXCSUM,TXCSUM,TSO4,TSO6>
        ether th:is:ad:dr:es:mtu
        Configuration:
            id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
            maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
            root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
            ipfilter disabled flags 0x2
        nd6 options=1<PERFORMNUD>
        media: <unknown type>
        status: inactive
    p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
        ether th:is:ad:dr:es:p2p0
        media: autoselect
        status: inactive
    vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:50:56:c0:00:01
        inet 192.168.48.1 netmask 0xffffff00 broadcast 192.168.48.255
    vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:50:56:c0:00:08
        inet 192.168.219.1 netmask 0xffffff00 broadcast 192.168.219.255
    ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1396
        inet my.ded.vpn.xx --> 192.xxx.xxx.xxx netmask 0xffffff00
    nooooooo:~ cearnhart$ ifconfig
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        nd6 options=1<PERFORMNUD>
    gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
    stf0: flags=0<> mtu 1280
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
        ether th:is:ad:dr:es:s1
        inet6 xxx::xxxx:xxff:xxxx:fxx2%en0 prefixlen 64 scopeid 0x4
        inet 10.xx.xx.x netmask 0xffffff00 broadcast 10.x.x.xxx
        nd6 options=1<PERFORMNUD>
        media: autoselect (1000baseT <full-duplex,flow-control,energy-efficient-ethernet>)
        status: active
    en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether th:is:ad:dr:es:n1
        inet6 fxxx::xxf8:47ff:fxx:6xx%en1 prefixlen 64 scopeid 0x5
        inet 10.x.x.x netmask 0xffffff00 broadcast 10.x.x.xxx
        nd6 options=1<PERFORMNUD>
        media: autoselect
        status: active
    fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
        lladdr xx:xx:xx:ff:fe:xx:5f:xx
        nd6 options=1<PERFORMNUD>
        media: autoselect <full-duplex>
        status: inactive
    en2: flags=8922<BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        options=60<TSO4,TSO6>
        ether xx:00:1e:xx:xx:xx
        media: autoselect <full-duplex>
        status: inactive
    bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=63<RXCSUM,TXCSUM,TSO4,TSO6>
        ether th:is:ad:dr:es:mtu
        Configuration:
            id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
            maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
            root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
            ipfilter disabled flags 0x2
        nd6 options=1<PERFORMNUD>
        media: <unknown type>
        status: inactive
    p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
        ether th:is:ad:dr:es:p2p0
        media: autoselect
        status: inactive
    vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:50:56:c0:00:01
        inet 192.168.48.1 netmask 0xffffff00 broadcast 192.168.48.255
    vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:50:56:c0:00:08
        inet 192.168.219.1 netmask 0xffffff00 broadcast 192.168.219.255

    If you know or suspect that a hostile intruder has either had physical access to it, or has been able to log in remotely, then there are some steps you should take to make sure that the computer is safe to use.
    First, depending on the circumstances, computer tampering may be a crime, a civil wrong, or both. If there's any chance that the matter will be the subject of legal action, then you should do nothing at all without consulting a lawyer or the police. The computer would be the principal evidence in such a case, and you don't want to contaminate that evidence.
    Running any kind of "anti-virus" software is pointless. If I broke into a system and wanted to leave a back door, I could do it in a way that would be undetectable by those means—and I don't pretend to any special skill as a hacker. You have to assume that any intruder can do the same. Commercial keylogging software—which has legitimate as well as illegitimate uses—won't be recognized as malware, because it's not malware.
    The only way you can be sure that the computer is not compromised is to erase at least the startup volume and restore it to something like the status quo ante. The easiest approach is to recover the entire system from a backup that predates the attack. Obviously, that's only practical if you know when the attack took place, and it was recent, and you have such a backup. You will lose all changes to data, such as email, that were made after the time of the snapshot. Some of those changes can be restored from a later backup.
    If you don't know when the attack happened, or if it was too long ago for a complete rollback to be feasible, then you should erase and install OS X. If you don't already have at least two complete, independent backups of all data, then you must make them first. One backup is not enough to be safe.
    When you restart after the installation, you'll be prompted to go through the initial setup process for a new computer. That’s when you transfer the data from a backup in Setup Assistant.
    Select only users in the Setup Assistant dialog—not Applications, Other files and folders, or Computer & Network Settings. Don't transfer the Guest account, if it was enabled.
    Reinstall third-party software from original media or fresh downloads—not from a backup, which may be contaminated.
    Unless you were the target of an improbably sophisticated attack, this procedure will leave you with a clean system. If you have reason to think that you were the target of a sophisticated attack, then you need expert help.
    That being done, change all Internet passwords and check all financial accounts for unauthorized transactions. Do this  after the system has been secured, not before.

  • Strange behavior when "trying" to burn a disk.

    At least I think this is strange behavior, following the instructions in the help viewer, topic "Backing up your music to a CD or DVD." One thing for sure, it's not burning a disc and it ain't telling me why.
    I select the playlist and click "Burn Disc"
    Requests a blank disc. I insert one.
    Message "checking media"
    after about a minute, the disc ejects
    Message "checking media" displays another 30 seconds
    No other messages displayed.
    What the ??? Shouldn't it at least display an error message??
    Super-Drive information..... from System Profiler
    MATSHITA DVD-R UJ-845C:
    Firmware Revision: DPP9
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipped/Supported)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -RW, +R, +RW
    Burn Underrun Protection CD: Yes
    Burn Underrun Protection DVD: Yes
    Write Strategies: CD-TAO, CD-SAO, DVD-DAO
    Media: No
    Using Sony DVD+R discs.
    Mac Mini   Mac OS X (10.4.8)  

    Whoops, sorry, this was while burning a playlist.
    I've also tried some Pleomax CD disks (Samsung), with no luck. I've tried burning directly from iTunes, and from Toast 7.
    Of the types I've tried, the Sony DVD's have been the best for me. Haven't tried many types though. Maybe I can get disks one at a time until I find a brand my burner likes.
    Still, isn't it strange that there is NO error message? It just quits?
    Mac Mini   Mac OS X (10.4.8)  

  • Strange Behavior with gMSA in Server 2012 R2

    Greetings,
    I have been doing some testing with gMSA Accounts in a Server 2012 R2 environment (two separate environments, actually), and I have noticed something very strange that occurred in both environments, which does not appear to be occurring in one of our customer's
    self-managed environments.
    We created a Group Managed Service Account using the following article:
    http://blogs.technet.com/b/askpfeplat/archive/2012/12/17/windows-server-2012-group-managed-service-accounts.aspx
    Everything went smoothly, and the account installs/tests successfully on both of the hosts that we are testing on. I am able to set my services to run under the account, and most of them appear to work fine. I am having some issues with a few of my services,
    and I believe that the strange behavior I am seeing may have something to do with this - described below: 
    As soon as I set the service's Log On Account (via the Log On Tab under the Service's Properties), the entirety of the "Log On" tab changes to "greyed out," and I am unable to change the Log On account back via the GUI (Screenshot
    attached).
    I found that I am able to successfully change the account via Command Line using sc.exe, but the Log On tab remains greyed out! So far, I have found nothing to remedy this, but confirmed that it happens for any service I set to use the gMSA as the Logon
    Account, and that it happens in 2 separate test environments, but not in a Customer's production environment - very strange.
    All servers in this environment are running Server 2012 R2, and domain Functional Level is currently Server 2012.
    I have been unable to find any information online about this behavior, so I am hoping someone has seen this before, and can explain why this is happening.
    Nick

    VIvian,
    Yes, we used the Install-AdServiceAccount gMSA command on each host using the gMSA account, and then ran Test-AdServiceAccount gMSA, which returned "True."
    However, one thing I noticed is that if I run Test-ADServiceAccount gMSA as a Local Administrator, it fails with the following:
    PS C:\Users\Administrator> Test-AdServiceAccount gMSA$
    Test-AdServiceAccount : The server has rejected the client credentials.
    At line:1 char:1
    + Test-AdServiceAccount gMSA$
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : SecurityError: (:) [Test-ADServiceAccount], AuthenticationException
        + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.Security.Authentication.AuthenticationException,Microsoft.A
       ctiveDirectory.Management.Commands.TestADServiceAccount
    If I run Test-ADServiceAccount gMSA as Domain Administrator, it returns true:
    PS C:\Users\Administrator.<domainname>> Test-AdServiceAccount gMSA$
    True
    Is this normal?
    Overall, I think the issue I am running into is at the Application Level, and not a problem with the gMSA, as it appears to be working. (Can Start/Stop services without any issues). I will be investigating my issue further with 3rd-party vendors, unless
    you think there is something wrong with my gMSA accounts based on the information I have provided.
    Nick

Maybe you are looking for