FTPS failing with Error: ...FTPEx: 'AUTH TLS': command not understood !!

Hi,
I am trying to send a file over FTPS (FTP using SSL/TLS) .
But it fails with the following error in RWB - Communication Channel monitoring:
Error when getting an FTP connection from connection pool: com.sap.aii.af.lib.util.concurrent.ResourcePoolException:
Unable to create new pooled resource: FTPEx: 'AUTH TLS': command not understood
I running NW711_05 and my FTP Connection Parameters are as follows:
Server: OurServerName
Port: 21
Data Connection: Passive {even tried Active but got the same error}
Timeout: 20
Connection Security: FTPS (FTP Using SSL/TLS) for control connection
X Use X.509 Certificate for Client Authentication
Keystore: service_ssl
X.509 Certificate and Private Key: ssl-credentials
Do I need to do any specific configuration/settings on the receiving FTP-server side?
Kind regards,
Joe

Hi Rajesh,
Thx for your speedy response! I started out by deselecting the certificate checkbox and changing the port no from 21 to 990, this of course generated a different error message:
Unable to create new pooled resource: ConnectException: Connection refused
which I believe is because connection is not configured for port 990.
Anyone else has any suggestions as to how to proceed?
Regards,
Joe

Similar Messages

  • VS 2013 Build tools installation fails with error "Signature or catalog could not be verified"

    VS 2013 ultimate - Build tools installation fails with error "Signature or catalog could not be verified" for MSBuild assemblies. Any idea what could be the problem?
    Thanks
    NM

    Hello,
    Do you mean you are trying to use this tool:
    https://www.microsoft.com/en-us/download/details.aspx?id=40760
    Can you navigate to your %temp% folder and filter by date to see the log of the Build tool?
    I want to know which assemblies failed to be verified.
    By the way, since MSBuild is embed in Visual Studio why you want to install this again? Do you have any error about this Build Tool when you install Visual Studio 2013 Ultimate?
    “Signature or catalog could not be verified” is always related to corrupt source
    , please double check you have a healthy network and then try the web installer again.
    Best regards,
    Barry
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Loadlibrary failed with error 126 the specified module could not be found

    Hello i get this error message at random when am using oracle sql developer, sometimes it comes right after startup, and some times after 5 mins.
    the error closes down the program
    please help

    Searching the web for "loadlibrary failed with error 126 java" seems to point to issues with OpenGL and certain video drivers and/or environments with multiple monitors. Here are several discussions...
    https://netbeans.org/bugzilla/show_bug.cgi?id=243153
    Error "LoadLibrary failed with error 126: The module could not - Microsoft Community
    [SOLVED] Issue with Technic Launcher: Load Library failed with Error 126 - Technic Launcher - Technic Forums
    So it seems this issue is not specific to SQL Developer. The last discussion includes a video link in its last post saying that ".dll" is searched for rather than "atioglxx.dll" on 32-bit systems or "atio6axx.dll" on 64-bit system (in the C:\Windows\system32 folder), so a workaround is to copy one of those to ".dll".

  • Trying to assign Security Baseline fails with error 24001

    We are trying to assign the Sample Security baseline updates to a cluster group in VMM.
    We have followed the steps here
    http://technet.microsoft.com/en-us/library/gg675110.aspx
    But the job to assign the baseline fails with the following:-
    Error 24001
    Update server operation failed with error: The specified item could not be found in the database.
    We are running VMM 2012R2 V 3.2.7510.0 on Windows Server 2012R2

    Remove wsus from VMM and add it again.
    This will fix the problem. Otherwise I Think cleaning SQL of missing update fixes the problem.

  • Time Machine. Backup failed with error code: 21

    Hi,
    I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
    After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
    However, TM is still not working. The console messages have the following:
    Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
    Network volume mounted at /Volume/Volume11
    Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
    Backup failed with error: 21
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Has anybody else seen this error or better yet, got a fix for it?

    James,
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
    *Mount Point Conflict (TMDisk-1)*
    NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
    First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
    When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
    Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
    *”The Backup Disk Image Could Not Be Mounted”*
    The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
    +Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
    +Backup failed with error: 21+
    More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
    Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    For more information, see an article on this here:
    [http://discussions.apple.com/thread.jspa?threadID=1715977]
    Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    Let me know if any of this helps.
    Cheers!

  • Open command fails with error -10810

    Switching from 10.4 to 10.5.3 I can no longer launch applications from the command line using the open command. For example:
    some bloke's macbook$ open TextEdit.app
    LSOpenFromURLSpec() failed with error -10810.
    Seems to be some kind of permissions issue since it does work if I sudo open. Anyone know how to fix this?

    It's interesting, yogh's post above might be the reason it's failing for you.
    Based on that post, I removed execute permissions from the TextEdit binary in /Applications/TextEdit.app/Contents/MacOS, then tried to use open to run the application. Here's what I get:
    % open -a TextEdit
    LSOpenFromURLSpec() failed with error -10810.
    Now, it may be that the above error is generic and could be generated by several things, but as yogh suggested it may be something to check...

  • Dehydration failed with error: Use introspectWLS12 command to introspect domains

    Hello Experts,
    I am trying to Introspect my Oracle weblogic server Locally to configure appliances on my assembly in Virtual Assembly Builder using command
    # ./abctl introspectWLS -wlsHome /home/punit/Oracle/Infra/wlserver -domainRoot /home/punit/Oracle/Infra/user_projects/domains/base_domain -adminUser weblogic
    but it is getting failed with error:
    Use introspectWLS12 command to introspect domains based on WLS 12.1.2 and younger..
    Error:  OAB-7105: Introspection failed.
    Caused by: Dehydrate job failed.
    Caused by:  OAB-50008: Use introspectWLS12 command to introspect domains based on WLS 12.1.2 and younger.
    later I replaced introspectWLS with introspectWLS12  but its throwing   Usage error: Command not found: introspectWLS12.
    Can somebody help me in finding the exact command for version 12.1.2 to by-pass this..
    FYI: I am using fmw_Infra_121200_OVAB.jar binnary  bundled with JRF & FM Components on my OEL-6.0 platform
    Thanks in Advance
    Punit

    Hi,
    Thanks for your reply.
    This icon you provided means "the DHCP server connected but current user does not have the administrative credentials to manage the server."
    That's why "0x80070005. Access is denied" is received.
    DHCP console icons reference
    http://technet.microsoft.com/en-us/library/cc784812(WS.10).aspx
    So, you need to make sure the current user have the administrative credentials to configure DHCP server. Usually members of the DHCP Administrators
    group can view and modify any data at the DHCP server. DHCP Administrators can create and delete scopes, add reservations, change option values, create superscopes, or perform any other activity needed to administer the DHCP server, including export or import
    of the DHCP server configuration and database. DHCP Administrators perform these tasks using the Netsh commands for DHCP or the DHCP console. For more information, see
    DHCP tools.
    DHCP groups
    http://technet.microsoft.com/en-us/library/cc737716(WS.10).aspx
    Hope this helps.
    Thanks,
    Robbin Meng
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked
    post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Check_ntlm_password:  Authentication for user ['name'] - ['name'] FAILED with error NT_STATUS_LOGON_FAILURE

    Hi,
    We are running a Mountain Lion Server with Open Directory / LDAPv3, as far as I can tell.  My responsibility is to get my CentOS 6.3 box running Samba v. 3.5.10-125.el6 to authenticate users against the ML / OD box.  I can ssh to the CentOS box OK and I can get Guest access to the Samba share to go OK too.  Also, the OD passwords on the LDAP server are set to 'Open Directory' so I guess that means that they are encrypted and the Samba server is set to send encrypted passwords.  But when a user tries to properly authenticate using either say via a Mac client Finder [Command-K], or smbclient, the Samba server will generate this message:
    check_ntlm_password:  Authentication for user ['name'] -> ['name'] FAILED with error NT_STATUS_LOGON_FAILURE
    (I am blanking out the user name on purpose).
    Of course there is more to the story, but those are the basics.
    Here are the relevant parts of my smb.conf.  FWIW, the CentOS / Samba box is called Jupiter.
    Thank you,
    NickZ
    [smb.conf]
    [global]
              display charset = UTF-8
              realm = SATURN.MCLEAN.HARVARD.EDU
              netbios aliases = ANL
              server string = Welcome To The Jupiter Samba Server Version 3.5.10-125.el6
              interfaces = lo, em1
              security = SERVER
              update encrypted = Yes
              password server = saturn.mclean.harvard.edu
              smb passwd file = /var/lib/samba/private/secrets.tdb
              passdb backend = ldapsam:ldap://saturn.mclean.harvard.edu
              passwd program = /usr/bin/passwd %u
              unix password sync = Yes
              lanman auth = Yes
              client NTLMv2 auth = Yes
              client use spnego principal = Yes
              kerberos method = system keytab
              log level = 2
              syslog = 3
              log file = /var/log/samba/log.%m
              max log size = 50
              name resolve order = host lmhosts wins bcast
              server signing = auto
              preferred master = Auto
              ldap admin dn = uid=DirAdmin,cn=users,dc=saturn,dc=mclean,dc=harvard,dc=edu
              ldap group suffix = cn=groups
              ldap passwd sync = yes
              ldap suffix = dc=saturn,dc=mclean,dc=harvard,dc=edu
              ldap ssl = no
              ldap user suffix = cn=users
              usershare allow guests = Yes
              idmap backend = ldap:ldap://saturn.mclean.harvard.edu
              idmap uid = 10000-20000
              idmap gid = 30000-40000
              cups options = raw
    [homes]
              comment = Home Directories
              read only = No
    [printers]
              comment = All Printers
              path = /var/spool/samba
              printable = Yes
              browseable = No
    [anl]
              comment = Main ANL Share
              path = /anl
              read only = No
              guest ok = Yes
              hide dot files = No

    Turns out a printer driver installed on an XP (even W2K(?)) was (apparently?) flooding the OS X SMB server to the point of collapse. Uninstalling the "HP Tools" part of the driver cleared it up. The printer is an HP LJ1300. I had downloaded the full driver from HP.com. I don't know if any/all these conditions need to be matched, but: the printer was on the network using an HP print server JetDirect EX Plus, and the computer(s) in question were connecting directly to it (not via a print server). It's been too long ago, but there were always several errors in the System Log (Win XP Event Viewer) that correlated with the errors on the OS X server.
    Proud to say that since that day (10+ months ago) I've not seen it happen again. whew.

  • Windows 7 update fails with error 8000FFFF

    I've got a Windows 7 x64 installation that I've had for around three months.  Everything has been fine and working up until a few weeks ago.  When I run Windows Update it finds updates and allows me to select them, but when I run the install it fails with error 8000FFFF.  Update used to work, but then suddenly quit.
    I've dug through tons of forum and web sites regarding this specific error, but they all of their solutions do nothing to fix my problem.  In frustration I decided to put in a spare hard drive and install Windows 7 from scratch.  I did that and the first thing I tried to do after logging in was updates and it failed for the same reason (8000FFF).
    I have the same situation with a Windows Storage Server 2008 x64 that I have as well.  It has been runing for about six months or more and updates were working fine.  Then update started failing for the same or some other reason about the same time.  On this machine I can start the update and see it report a percentage downloading the update.  It gets to about 5 or 6 percent and then fails.
    Is there some possible networking issue at play in my situation?  I have earlier Windows versions (XP, XP64, Svr 2003 and Svr 2003 R2) and updates work fine on those.  I know those are using a different mechanism, but I do not notice any other kind of networking issues from my house to the Internet.  I have not changed anything or any settings in my firewall at all.  Is there some specific protocol, port or something that has to work prefectly in order for the new Windows update to work? 
    All of my machines are pretty much Intel based.  Win7 box is a Core2Duo on an EVGA 680i motherboard.  The servers are Intel Xeons with Intel motherboards, chipsets and nics.
    Thanks for any advice and help

    Wow, suddenly I have the same bizarre error at 11% of downloading, then error #8000FFFF.
    Fix IT, registry keys and SoftwareDistribution folder cleaning, uninstalling previous updates, manual downloading of appropriate updates and attempt do install it and creating/deleting user profiles - don't work at all.
    Any new ideas?
    Thanks,
    Win7 x64 SP1
    Package KB2633873 failed to be changed to the Installed state.
    Status: 0x8e5e0408.Windows update "Security Update for Windows (KB2633873)" could not be installed because of error 2388526088 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\Wiewior\Downloads\Windows6.1-KB2633873-x64.msu"       
    Package KB2645640 failed to be changed to the Installed state. Status: 0x8e5e0408.
    Windows update "Security Update for Windows (KB2645640)" could not be installed because of error 2388526088 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\Wiewior\Downloads\Windows6.1-KB2645640-x64.msu"       

  • CcmSetup failed with error code 0x80004005 - windows 8.1

    using sccm 2012 r2, trying to push to a windows 8.1 client i get:
    <![LOG[==========[ ccmsetup started in process 7416 ]==========]LOG]!><time="16:05:28.041+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X64]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="util.cpp:1837">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9272" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\WINDOWS\ccmsetup\]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:727">
    <![LOG[In ServiceMain]LOG]!><time="16:05:28.044+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:3365">
    <![LOG[Running on 'Microsoft Windows 8.1 Pro' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="16:05:28.085+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="16:05:28.086+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8617">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8632">
    <![LOG[CCMHTTPSSTATE:    224]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8650">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8668">
    <![LOG[FSP:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8720">
    <![LOG[CCMFIRSTCERT:    1]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8778">
    <![LOG[Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4539">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4540">
    <![LOG[MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4541">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="consto" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="16:05:28.088+00"
    date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4542">
    <![LOG[Source List:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4550">
    <![LOG[                  \\TA-SRV-SC.constoplc.local\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4557">
    <![LOG[                  \\TA-SRV-SC.constoPLC.LOCAL\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4566">
    <![LOG[MPs:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4569">
    <![LOG[                  TA-SRV-SC.constoplc.local]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:4584">
    <![LOG[MapNLMCostDataToCCMCost() returning Cost 0x1]LOG]!><time="16:05:28.091+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmutillib.cpp:5479">
    <![LOG[No version of the client is currently detected.]LOG]!><time="16:05:28.093+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:2748">
    <![LOG[Folder 'Microsoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="16:05:28.094+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="wintask.cpp:622">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:9281">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:1995">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='328' will not be sent.]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="16:05:28.119+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:10879">
    any ideas why its failing?

    Hi,
    I've seen the same error on a customer where we had Windows Intune Client (SCCM) installed previously. Did you try it on a newly deployed computer? If you had Intune or another CCM client on it previously make sure you clean it up. Here is a well formulated
    instruction:
    http://douwevanderuit.wordpress.com/2014/01/30/removing-windows-intune-client/
    Usually when deploying to many clients we use a startup script, there is a great one that Jason Sandys made in the link below.
    http://blog.configmgrftw.com/configmgr-client-startup-script/
    There should be no problems deploying SCCM 2012 R2 clients on Windows 8.1 unless there is something wrong with either the setup or the client computer.
    All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

  • FAILED with error NT_STATUS_NO_SUCH_USER

    Setup:
    OS X Server 10.3.9. PDC. ALL clients are a combination of XP and W2K. No macs (sadly).
    Situation:
    Over the last 3 years I've been plagued with this problem. Symptoms include new authentications are not granted access, but existing connections suffer no degradation of service. The simple solution has been to simply go into Server Admin and "Restart Service" on the Windows service. Done and done. However, this can happen anywhere from once a week to (up to) 3 times a day. Even on weekends when (likely) no one is in the building, though some users may not log out of their workstations - let alone shut down.
    Troubleshooting:
    1) I set the smbd logs to 1 (debug) and at the point of degrading, I only see this:
    ***** Begin: I changed nothing; I left out nothing ***********************
    [2008/04/14 10:54:09, 1] authods.c:opendirectory_authuser(208)
    User "bvolz" authenticated successfully with "dsAuthMethodStandard:dsAuthSMBNTKey"
    [2008/04/14 10:54:09, 2] authods.c:opendirectory_smb_pwd_checkntlmv1(424)
    opendirectorysmb_pwd_checkntlmv1: [-14071]opendirectoryuser_sessionkey
    [2008/04/14 10:54:09, 2] /SourceCache/samba/samba-60.5/samba/source/auth/auth.c:checkntlmpassword(305)
    checkntlmpassword: authentication for user [bvolz] -> [bvolz] -> [bvolz] succeeded
    [2008/04/14 10:54:10, 1] /SourceCache/samba/samba-60.5/samba/source/smbd/service.c:close_cnum(841)
    volzsql (192.168.0.3) closed connection to service Shared
    [2008/04/14 10:54:11, 0] pdbods.c:getrecords(1015)
    dsGetRecordEntry error (-14085)odssam_getsampwnam: [-14085]getsam_recordattributes dsRecTypeStandard:Users no account for 'jpiper'!
    [2008/04/14 10:54:11, 2] /SourceCache/samba/samba-60.5/samba/source/auth/auth.c:checkntlmpassword(312)
    checkntlmpassword: Authentication for user [jpiper] -> [jpiper] FAILED with error NTSTATUS_NO_SUCHUSER
    ***** End: I changed nothing; I left out nothing ***********************
    2) Recently, I tried to change the default allowed connections per KB Article: http://docs.info.apple.com/article.html?artnum=107899 but that actually only seemed to exacerbate the problem. Today I removed the directories that were added in Netinfo Manager from the KB.
    3) I also looked at the nmbd.log and frequently see this, which is equally as troubling:
    [2008/04/14 10:44:29, 2] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdbrowsesync.c:sync_withdmb(154)
    syncwithdmb:
    Initiating sync with domain master browser VOLZSERVER<20> at IP 65.16.245.50 for workgroup VOLZINC
    [2008/04/14 10:44:29, 2] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdbrowsesync.c:announce_local_master_browser_to_domain_masterbrowser(110)
    announcelocal_master_browser_to_domain_masterbrowser:
    We are both a domain and a local master browser for workgroup VOLZINC. Do not announce to ourselves.
    [2008/04/14 10:44:29, 2] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdbrowsesync.c:sync_withdmb(154)
    syncwithdmb:
    Initiating sync with domain master browser VOLZSERVER<20> at IP 65.16.245.50 for workgroup VOLZINC
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:46:57, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:05, 0] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdpackets.c:process_browsepacket(1050)
    processbrowsepacket: Discarding datagram from IP 65.16.245.54. Source name VOLZSERVER<00> is one of our names !
    [2008/04/14 10:59:27, 2] /SourceCache/samba/samba-60.5/samba/source/nmbd/nmbdbrowsesync.c:announce_local_master_browser_to_domain_masterbrowser(110)
    announcelocal_master_browser_to_domain_masterbrowser:
    We are both a domain and a local master browser for workgroup VOLZINC. Do not announce to ourselves.
    This type of activity in the log is repeated over and over and over again.
    Question:
    How do I make it stop? Ok, to be fair, I've searched for the last few years for a solution and I'm not sure why samba is continuing to 'break.' Is there someone here that can enlighten me or poke me in the right direction to why this could be happening? I know little to nothing about samba. I DO know networking, and this could be the issue. The server was handed to me by the previous admin and so to rebuild (the easy solution) isn't so easy because the previous admin didn't document anything he did to build it, like NAT forwarding and such, which, if I don't put back into it, will cause MANY headaches. So, eventually I WILL rebuild from scratch (the time may be nigh), and I think it may fix a misconfiguration, but I fear it will be difficult. This is our production server with no test environment (other than using SuperDuper! to image the drive and play with it over a weekend or something).
    Plea:
    For help.
    Edit: How do I suppress the wiki markup? It's butchering the posted log excerpts. <nowiki></nowiki> doesn't seem to work.

    Turns out a printer driver installed on an XP (even W2K(?)) was (apparently?) flooding the OS X SMB server to the point of collapse. Uninstalling the "HP Tools" part of the driver cleared it up. The printer is an HP LJ1300. I had downloaded the full driver from HP.com. I don't know if any/all these conditions need to be matched, but: the printer was on the network using an HP print server JetDirect EX Plus, and the computer(s) in question were connecting directly to it (not via a print server). It's been too long ago, but there were always several errors in the System Log (Win XP Event Viewer) that correlated with the errors on the OS X server.
    Proud to say that since that day (10+ months ago) I've not seen it happen again. whew.

  • 703: Subdaemon connect to data store failed with error TT9999

    All,
    I'm getting the following error whilst trying to connect to a TimesTen DB:
    connect "DSN=my_cachedb";
    703: Subdaemon connect to data store failed with error TT9999
    In the tterrors.log:
    16:39:24.71 Warn: : 2568: 3596 ------------------: subdaemon process exited
    16:39:24.71 Warn: : 2568: 3596 exited while connected to data store '/u01/ttdata/datastores/my_cachedb' shm 33554529 count=1
    16:39:24.71 Warn: : 2568: daRecovery: subdaemon 3596, managing data store, failed: invalidate (failcode=202)
    16:39:24.71 Warn: : 2568: Invalidating the data store (failcode 202, recovery for 3596)
    16:39:24.72 Err : : 2568: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc -2 err1 703 err2 9999
    16:39:24.72 Warn: : 2568: 3619 Subdaemon reports creation failure
    16:39:24.72 Err : : 2568: TT14000: TimesTen daemon internal error: Deleting 3619/0x1558650/'/u01/ttdata/datastores/my_cachedb' - from association table - not found
    16:39:24.72 Err : : 2568: TT14004: TimesTen daemon creation failed: Could not del from dbByPid internal table
    16:39:24.81 Warn: : 2568: child process 3596 terminated with signal 11
    16:39:25.09 Err : : 2568: TT14000: TimesTen daemon internal error: daRecovery for 3619: No such data store '/u01/ttdata/datastores/my_cachedb'
    I've checked and the datastore does exist and is owned by the timesten UNIX user.
    ttversion:
    TimesTen Release 11.2.2.2.0 (64 bit Linux/x86_64) (tt1122:53396) 2011-12-23T09:26:28Z
    Instance admin: timesten
    Instance home directory: /home/timesten/TimesTen/tt1122
    Group owner: timesten
    Daemon home directory: /home/timesten/TimesTen/tt1122/info
    PL/SQL enabled.
    Datastore definition from sys.odbc.ini:
    [my_cachedb]
    Driver=/home/timesten/TimesTen/tt1122/lib/libtten.so
    DataStore=/u01/ttdata/datastores/my_cachedb
    LogDir=/u01/ttdata/logs
    PermSize=40
    TempSize=32
    DatabaseCharacterSet=AL32UTF8
    OracleNetServiceName=testdb
    Kernel parameters from sysctl -a:
    kernel.shmmax = 68719476736
    kernel.shmall = 4294967296
    Memory / SWAP:
    MemTotal: 2050784 kB
    SWAP: /dev/mapper/VolGroup00-LogVol01 partition 4095992
    I'm new to TimesTen and I'm planning on evaluationg it to see if it could solve an issue we're having. Any suggestions would be much appreciated.
    Thanks,
    Ian.

    Hi Ian,
    Can you please answer the following / provide the following information:
    1. What are your kernel parameters relating to semaphores set to? Is anything else on the mahcine using significant numbers of semaphores?
    2. Please provide the output of the following shell commands:
    ls -ld /u01
    ls -ld /u01/ttdata
    ls -ld /u01/ttdata/datastores
    ls -ld /u01/ttdata/logs
    3. Please provide an excerpt of the detailed message log (ttmesg.log) between around 16:38 and 16:40 (i.e. from a little while before the problem until after the problem).
    Thanks,
    Chris

  • [DC2] An net use or LsaPolicy operation failed with error 67 - Moving AD from 2003R2 to Server 2012

    Hello, i hope someone can help me with this tricky situation.
    The plan is to move AD from 2003R2 name "DC" to a server 2012 "DC2"
    I have made all the adjustments and transferred all the role to the new 2012 server, and both are now GC servers.
    The problem is "transferring" the netlogon share.
    in DCDIAg on the new server i get:
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = DC2
       * Identified AD Forest. 
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\DC2
          Starting test: Connectivity
             ......................... DC2 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\DC2
          Starting test: Advertising
             ......................... DC2 passed test Advertising
          Starting test: FrsEvent
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems. 
             ......................... DC2 passed test FrsEvent
          Starting test: DFSREvent
             ......................... DC2 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... DC2 passed test SysVolCheck
          Starting test: KccEvent
             ......................... DC2 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... DC2 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... DC2 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... DC2 passed test NCSecDesc
          Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\DC2\netlogon)
             [DC2] An net use or LsaPolicy operation failed with error 67,
             The network name cannot be found..
             ......................... DC2 failed test NetLogons
          Starting test: ObjectsReplicated
             ......................... DC2 passed test ObjectsReplicated
          Starting test: Replications
             ......................... DC2 passed test Replications
          Starting test: RidManager
             ......................... DC2 passed test RidManager
          Starting test: Services
                NtFrs Service is stopped on [DC2]
             ......................... DC2 failed test Services
          Starting test: SystemLog
             ......................... DC2 passed test SystemLog
          Starting test: VerifyReferences
             ......................... DC2 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : dom1
          Starting test: CheckSDRefDom
             ......................... domain passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... domain passed test CrossRefValidation
       Running enterprise tests on : domain.xxxxx.no
          Starting test: LocatorCheck
             ......................... domain.xxxxx.no passed test LocatorCheck
          Starting test: Intersite
             ......................... domain.xxxx.no passed test Intersite
    I have as a last option the burflags issue, i tried this with the option D2, but i think i have done it wrong, because the netlogon share is gone on the old DC. i took a backup of the files and folders before
    i did this. http://support.microsoft.com/kb/290762/en-us But i am a little confused on which server i am going to set the D4 value on now? COuld someone help? Best regards Aksel

    Hello Dirk
    And thank you for your answer, in regards of the KB, do i have to follow the steps regarding:
    Global vs. replica set specific reinitialization
    You can locate the replica set specific
    BurFlags
    registry key by determining the GUID for the replica set that you want to configure. To determine which GUID
    corresponds to which replica set and configure a restore, follow these steps:
    Click Start, and then click Run.
    In the Open box, type cmd and then press ENTER.
    In the Command box, type net stop ntfrs.
    Click Start, and then click Run.
    In the Open box, type regedit and then press ENTER.
    To determine the GUID that represents the replica set that you want to configure, follow these steps:
    Locate the following key in the registry:
    KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets
    Below the Replica Sets subkey, there are one or more subkeys that are identified by a GUID. In the left pane, click the GUID, and then in the right
    pane note the Data that is listed for the Replica Set Root value. This file system path will indicate which replica set is represented by this GUID.
    Repeat step 4 for each GUID that is listed below the Replica Sets 
    And so on?
    I have only thos 2 DC's in the network...

  • [ForumFAQ]How to troubleshoot error "SSPI handshake failed with error code 0x80090324"

    Understanding the problem:
    When connect to SQL Server with Windows authentication, you may receive the following message in the SQL Server error log:
    SSPI handshake failed with error code 0x80090324, state 14 while establishing a connection with integrated security; the connection has been closed.
    Security Support Provider Interface (SSPI) is a set of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. SQL Server supports Kerberos indirectly through the Windows Security Support
    Provider Interface (SSPI) when SQL Server is using Windows Authentication.
    "SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos Authentication. There are many reason for SSPI Handshake error to appear in SQL Server error log.
    Troubleshot the problem:
    Download and install the Windows error code lookup tool Err.exe to view error descriptions for Windows Error Codes.
    The error code 0x80090324 (SEC_E_TIME_SKEW) means "clock on client and server machines are skewed". In most case, this is a Kerberos issue. Kerberos is using a timestamp to protect against replay attacks. The maximum time skew that can be tolerated
    between a ticket's timestamp and the current time at the KDC is 5 minutes by default.
    Also check the Windows Event Log of client machine, domain controller and the SQL Server machine for existence of W32time error messages.
    The solution:
    Make sure the clock of client server, domain controller and the server running SQL Server are within five minutes of each other. Or Resynchronize the clock by run w32tm /resync on client machine and SQL Server machine.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This error can happen due to Active Directory configuration issue or Network related issues. Assuming they are fine,
    another reason could be related to fail Kerberos Authentication to connect to SQL Server.
    In Windows 2003 and above, the default method of establishing a connection is Kerberos but if it fails, then connection may be established using NTLM. An error may be registered on SQL Server error log due to Kerberos failure.
    To confirm if you have any database connection using Kerberos authentication, run this on your SQL Server
    SELECT distinct auth_scheme FROM sys.dm_exec_connections
    If you only see NTLM and SQL then, there is no Kerberos connection.
    To use Kerberos, the client and SQL Server must be in the same domain or trusted domains and a Service Principal Name (SPN) must be registered with Active Directory for SQL Server service account.
    You can check if the service account already has SPN, by running this on the SQL Server
    setspn -l <domain\sqlserviceaccount>
    If you don't see anything starting with MSSQLSvc\ then the account is not setup with SPN.
    You can manually register SPN as a Domain Administrator using these commands.
    To      create an SPN for the NetBIOS name of the SQL Server use the following      command:
    setspn –A MSSQLSvc/<SQL Server computer name>:1433      <Domain\Account>
    To      create an SPN for the FQDN of the SQL Server use the following command:
    setspn      -A MSSQLSvc/<SQL Server FQDN>:1433 <Domain\Account>
    If SQL Server service account is granted "Validated write to service principal name" privilege in Active Directory, SQL Server database engine will register itself when it starts and unregisters at shutdown. If you Domain Administrators do not permit this setting
    then you should manually register the SPN and the SSPI error will go away.
    Also the SQL Server service account must be granted "Account is trusted for delegation" privilege in Active Directory. If your SQL Server connects to other SQL Server using Linked Server then the server must also be granted "Trust this computer for delegation
    to any service" privilege.
    For a named instance, you can use the FQDN of the named instance instead of SQL Server FQDN and use the port number.
    For a clustered server, you should use the FQDN of the SQL Server virtual name. In this case you will need two entries, one with port name and one without such as
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN> <Domain\Account>
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN>:1433 <Domain\Account>
    Kerberos authentication works when SQL Server, Service Account and Windows account accessing the SQL Server are in same windows domain. If anyone these are in different domain, there must be bidirectional trust established between the domains, otherwise it
    does not work.

  • NAConnectToServerSync failed with error

    Hi all,
    since i upgraded to ML on my MBA the automatic (hourly, daily,...) Backups on my TimeCapsule doesn't work. When i start a manuall backup Time Machine (i have choosen my TC to be the only backup-destination, no rotating backups with another disk) works fine and the backup is done without any errors.
    But the next time when an automatic backup should be taken, it occurs with the error "Backup Disk is not available", in the System Log it looks like this:
    com.apple.backupd:  NAConnectToServerSync failed with error:  2 for url afp://<myuser>; AUTH=[email protected]/HDD;AUTH=SRP@TC
    com.apple.backupd:  Backup failed with error: 19

    Well, I was hoping for a networking guru to leap in with a magical answer. 
    Even asked one directly; no help.
    So, all I can suggest is the usual "grab bag" -- hopefully one will do it:
    • Re-select the TC via TM Preferences.
    • If that doesn't help, do a "full reset" of Time Machine, per #A4 in Time Machine - Troubleshooting.
    • Reset the TC.  I think a "hard reset" is what you want.  See http://support.apple.com/kb/ht3728
    • If stil no help, power your Mac and Time Capsule down.  Leave them off for several minutes.  Power the TC back up first.  Wait several minutes, then power up your Mac.

Maybe you are looking for