Unable to demote MDC

Hello, I have a XSAN environment (1 MDC and 3 Workstation). I temporary installed the MDC on a MacBook Pro and now I have to change it with a XServer. I can not recover the license because I can not downgrade a client (the choise is disable).
Any idea?
Help will be welcome...

Can you describe exaclty what you want to acheive? If you install xsan on a macbook pro, it will never function as an MDC as a macbook pro has no fibre connection. You can upgrade a client to a controller, switch the macbook pro off, connect your xserve and enter the licence from the macbook pro, and set your xserve to be a controller. Then change your current controller back to a client. It is quite a dangerous thing running with only one mdc though. If you loose that, you loose your data!

Similar Messages

  • Unable to demote a domain controller

    Hi Everone,
    My primary DC is windows Server 2012 R2 and ADC is windows Server 2008 x64
    I am trying to demote  Windows Server 2008 x64 and i am facing issues.
    when i demote2008 I am getting Error : A Domain Controller could not be contacted for the domain(mydomain.com) that contains
    an account for this computers.Make the computer a member of a workgroup then rejoin the domain before retrying the prmotion.
    The specified domain either doesnot exist or could not be contacted
    When i browse my \\windows2012dc i cannot see sysvol and netlogon shared folders.
    on window2012dc C:\windows\sysvol\mydomain and mydomain folder is empty.(no issues with replication in sites and services and no issues with connectivity or gateway )
    please guide me because i dont want forceful demote.

    I would first recommend taking backups of both DCs before proceeding with any changes.
    Before trying a forced demotion, you can try the following:
    Make sure that both DCs have a single NIC card enabled and only one IP address in use
    Make both DCs point to the other as primary DNS server, their private IP addresses as secondary DNS server and 127.0.0.1 as third one. Once done, run
    ipconfig /registerdns and restart netlogon service
    Disable any security filtering between both DCs and temporary disable security software you use
    If this does not help then you need to proceed with a forced demotion.
    You can then proceed like the following (First, Use dcdiag to check that the Windows Server 2012 R2 DC has no problems apart of the SYSVOL folder and the replication with the other DC):
    Shutdown the DC running Windows Server 2008 (Do not bring it online again without re-installing it later)
    Seize all FSMO roles to your Windows Server 2012 R2 DC if it is not already the current FSMO holder: http://support.microsoft.com/KB/255504
    Do a metadata cleanup to remove the data of the old Windows Server 2008 DC: Use
    dssite.msc to remove its NTDS settings and object over there then use
    dsa.msc to remove its AD account
    Rebuild your SYSVOL tree: http://support.microsoft.com/kb/315457
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Get Active Directory User Last Logon
    Create an Active Directory test domain similar to the production one
    Management of test accounts in an Active Directory production domain - Part I
    Management of test accounts in an Active Directory production domain - Part II
    Management of test accounts in an Active Directory production domain - Part III
    Reset Active Directory user password

  • Unable to demote server

    Migrated Server 2012 essentials to new hardware. Trying to demote the old server - when going through the Active Directory Domain Services configuration wizard the demotion fails with this error:
    The operation failed because:
    Managing the network session with NEWSERVER.DOMAIN.Local failed
    "the target account name is incorrect"
    Getting a Security-Kerberos error 4 in the system log and SRMSVC errors 12317, 12339 and 12344 errors in the application log. Any ideas where to start? Thanks!
    Jack
    Jack - IT Portfolio

    Hi,
    Thanks for your post.
    Before you demote the Source Server from the role of the AD DS domain controller to the role of a domain member server, ensure that Group Policy settings are applied to all client computers.
    The Source Server and the Destination Server must be connected to the network while the Group Policy changes are updated on the client computers.
    https://technet.microsoft.com/en-us/library/78d4325f-e587-4c19-ba21-d34b603768fa#BKMK_DemoteTheSourceServer
    For further investigation, could you please search in the "DCPromoUI.log" (in '%systemroot%\debug\' folder ) for errors in that demotion attemption?
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Unable to remove an mdc?

    I have a 3rd MDC that I'd like to downgrade to a client, then remove the software, then add back as a metadata controller. It doesn't allow me the option thru the gui.
    suggestions?
    thanks!

    this machine is not used to manage users, and it's not a primary mdc, it's not hosting any volumes.
    is there some other 'primary' setting or such that i wouldn't see easily?
    (i didn't set up this san).
    thanks.

  • Unable to extract Customer Master data from MDC

    Hello,
    We creating an MDM-XI-ERP2005 Customer scenario. We want to work with all bussiness scenarios (not customizing scenario).
    First I'm trying to extract Customer Master Data from EP 2005 using MDM_CLNT_EXTR.
    I have created a New Variant which properties are:
    Variant: CUSTOMER_TOTAL
    Description: Send all customer data to MDM
    Extraction Object: CUSTOMER_EXTRACT.
    Target System: PI7.
    But, the display jobs shows the following error: Could not determine recipients for message type MDMRECEIPT. Job cancelled after system exception.
    We need to focus the problem. We have done the following ALE configuration.
    SALE transaction:
    In Basic Settings -> Logical Systems -> Define Logical System we have add the following logical systems:
                  EUS100
                  MDM: Master Data Management
                  PI7: Process Integration 7.0
    WE21:
    Transactional RFC -> PI7, IDOC record types SAP Release 4.x
    RFC destination: SAPSLDAPI
    BD64
    New Model -> PFMC
    Add message type: Model iview: PFMC
                                 Sender: EUS100
                                  Receiver: PI7
                                 Message Type: DEBMDM
    WE20 transaction shows:
    Partner profiles -> Partner Type LS (logical system)
                        PI7: Outbound parmtrs. DEBMDM, SYNCH.
    Any idea will be very helpful,
    Thanks in advance
    Marta.
    Edited by: Marta Sánchez on Jul 9, 2008 12:34 PM

    Sorry because I made a mistake in my previous message. ALE seems to be correctly configured. I'll try to update correctly my current situation:
    In WE02 I can see al IDOCs that I'm trying to send to XI. All them have the IDoc Status = 3 (Data Passed to Port OK) instead of 12 Status Dispatch OK :(. So, It seems an tRFC error.
    SM58 shows me more trails: "Basic type 'DEBMDM06' is unknown"
    before that I have done the following steps at SAP ERP:
        1. WE21: I have created a PI7 port with 700PI70CLNT RFC.
        2. SM59: I have checked successfully 700PI70CLNT RFC connection.
        3. WE20: I have created a PI7 Partner Type LS with the following inbound and outbound parameters: DEBMDM and MDMRECEIPT.
        4. BD64: I have created a Distribution Model with DEBMDM and MDMRECEIPT message types.
    and at SAP PI:
         5.IDX: Port: SAPEUS. Client: 111. RFC Destination: PI7.
         6. technical and business system for sender SAP system(System Landscape Directory)...
    - Maybe some of the previous steps is not correct....
    - Is RFC Destination = PI7 is correct in step #5?
    - Is also necessary to configure more steps in PI system like RFC destinations or Transactional port?
    - I have read that is neccessary to check that the option "transfer idoc immediately" in we20. How?
    Please any idea will be very helpful.......
    Thank you!
    Best regards,
    Marta.

  • Unable to add Addtional DC In Existing Domain

    Hello Team,
    I've three sites configured for replication,there are 3 domain controllers in each site, i demoted one domain controller and now i again i am promoting it as DC but unable to do so .. i gives me error saying could not retrieve domain controllers , system cannot
    find file specified..
    event id 1202 , source : DFSR
    what does that mean.?
    what should i do ?

    Hello Team,
    I've three sites configured for replication,there are 3 domain controllers in each site, i demoted one domain controller and now i again i am promoting it as DC but unable to do so .. i gives me error saying could not retrieve domain controllers , system cannot
    find file specified..
    event id 1202 , source : DFSR
    what does that mean.?
    what should i do ?
    I would recommend that you refer to the IP setting recommendations I shared here: http://www.ahmedmalek.com/web/fr/articles.asp?artid=23
    Also, make sure that the required ports are opened and not filtered.
    You can also use dcdiag and repadmin to make sure that your DCs and AD replication are in a healthy state.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • 10.6.2 Server Xsan 2.2.1 and SNFS 3.1.2 MDC

    I'm trying to connect an Xserve running 10.6.2 and Xsan 2.2.1 to a Linux MDC running StorNext 3.1.2, but Xsan can't connect to the fsmpm. I receive the following entries in system.log:
    Feb 25 17:52:49 engOSX106Svr xsand[1186]: Synchronizing with fsmpm.
    Feb 25 17:52:49 engOSX106Svr sandboxd[1191]: portmap(1190) deny network-outbound /private/var/tmp/launchd/sock
    Feb 25 17:54:49 engOSX106Svr xsand[1186]: Failed to synchronize with fsmpm (error 2).
    Feb 25 17:54:49 engOSX106Svr fsmpm[1189]: NSS: Name Server '192.168.171.1' (192.168.171.1) heartbeat lost, unable to send message.
    Feb 25 17:54:55 engOSX106Svr xsand[1186]: fsm shutdown after 0 seconds
    Feb 25 17:54:55 engOSX106Svr com.apple.launchd[1] (com.apple.xsan[1186]): Exited with exit code: 1
    I am able to ping the MDC (192.168.171.1) and the OS X firewall is disabled. Other Linux and Windows cvfs clients are able to connect.
    Can anyone provide me some insight into this problem? My hunch is some sort of port filtering but I can't figure out what service might be blocking the traffic.
    Thanks,
    Kevin Wright.

    Here is my config.plist with the code and Company X'd out.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>computers</key>
    <array/>
    <key>metadataNetwork</key>
    <string>192.168.171.0/24</string>
    <key>role</key>
    <string>CLIENT</string>
    <key>serialNumbers</key>
    <array>
    <dict>
    <key>license</key>
    <string>XSAN-XXX-XXX-X-XXX-XXX-XXX-XXX-XXX-XXX-X</string>
    <key>organization</key>
    <string>XXXXXXXXXXX</string>
    <key>registeredTo</key>
    <string>ProductionIT</string>
    </dict>
    </array>
    </dict>
    </plist>
    I was afraid of 10.6.2 Server... We'd like to stick with Snow Leopard, does 10.6.0 or .1 handle Xsan better?

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

    Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs.  I had a similar problem which I solved by removing some old migration batches, now I have a problem
    with the Microsoft Exchange Mailbox Replication service.
    The event logged is:
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
    domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
    configured incorrectly DNS server.
    The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring.  When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
    How can I stop these events occurring and is it likely to be causing something else not to work correctly.
    We are running Exchange 2013 CU1

    No, that didn't work.  Here are more details:
    Source: MSExchange ADAccess (EventID: 2130)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
    incorrectly DNS server.
    Source: MSExchange ADAccess (EventID: 2119)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
     The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
     Common causes of this error include the following:
     - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
    at set intervals. This computer is configured to use DNS servers with following IP addresses:
    10.59.100.7
    10.59.100.8
    fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
     - One or more of the following zones do not include delegation to its child zone:
    admin.riddlesdown.local
    riddlesdown.local
    local
    . (the root zone)
    Source: MSExchange Mailbox Replication Service (EventID: 1121)
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Something is cause the Exchange server to go looking for our old domain, but what and why?

  • HT2506 Hello I'm unable to open any pdf's with preview window opens up with message file couldn't be opened because you don't have permission to view it (none of the pdf's have any security thanks if you can assist

    Hello this week I'm unable to open any pdf's with preview, when I select to open a window opens up with message "file couldn't be opened because you don't have permission to view it" none of the pdf's have any security thanks if you can assist

    Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • DC Demoted, now issues siezing roles. AD Broken.

    Hello,
    I've taken ownership of yet another troubled network. This time, the issue is that the server 2012 domain controller was expereincing hardware failure. I set up another Server 2012 machine, managed to add it to the forest, and then demoted the old DC using
    dcpromo.
    That was a few months ago. Now it appears that I am experiencing some issues with the new domain controller. I noticed issues when I was having trouble logging in. My password no longer works, but I managed to get into the DC using a colleagues' password. Upon
    launching Active Directory Users & Computers, I get "Naming information cannot be located because: The specified domain either does not exist or could not be contacted."
    Then, I realised that when I go to \\DC2, I don't see any netlogon or sysvol shares. So as I was diagnosing it, I went to check which server holds all the FSMO roles. It looks like DC1 (the old DC which was decomissioned) still held all the roles! I'm not sure
    why demotion process didn't shift the roles from the old failing DC to the new DC. So, I went sieze all the roles using ntdsutil. Everything was going smoothly until I went to seize the schema master role using the "sieze schema master" -- at this
    point I got an error stating:
    Win32 error returned is 0x2098(Insufficient access rights to perform the operati
    on.)
    Depending on the error code this may indicate a connection,
    ldap, or role transfer error.
    Transfer of schema FSMO failed, proceeding with seizure ...
    ldap_modify of SD failed with 0x32(50 (Insufficient Rights).
    Ldap extended error message is 00000005: SecErr: DSID-031521E1, problem 4003 (IN
    SUFF_ACCESS_RIGHTS), data 0
    Win32 error returned is 0x5(Access is denied.)
    So naturally I google it, and it appears the issue here is that the account I am using to do the role siezing has insufficient permissions (i.e. not member of Enterprise Admins/Schema Admins) to conduct this role siezure. However, I have successfully siezed
    the Naming Master, PDC, RID, and Infrastructure roles.
    Now I am stuck in a chicken and egg situation --  I can't give the account I'm using the correct group permissions beause AD is broken; I can't fix AD because I don't have the permissions.
    How can I fix this? Any insight appreciated. I'd like to avoid rebuilding the DC if possible.

    Hi,
    Alright -- I thought the root issue was that I couldn't sieze the roles. After further research it appears there are 2 issues.
    1. Netlogon/Sysvol are missing (All the steps I can find on the internet pertaining to restoring Netlogon/Sysvol require the use of FRS, however on my system teh FRS service is set to 'disabled' -- I understand FRS was only used in server 2003 and earlier,
    everything after that uses DFS?)
    2. There are remnants of the old DC still left behind. Here is the output of dcdiag /E:
    3. I can't launch ADUC, Sites & Services or anything like that to fix anything.
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    Home Server = DC2
    * Identified AD Forest.
    Ldap search capability attribute search failed on server DC1, return value = 81
    Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\DC1
    Starting test: Connectivity
    The host 0478fe4a-28c5-4151-894a-06c5b32bf1a0._msdcs.mydomain.com.au could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc.
    Neither the the server name (DC1.mydomain.com.au) nor the Guid DNS name (0478fe4a-28c5-4151-894a-06c5b32bf1a0._msdcs.mydomain.com.au) could be resolved by DNS. Check that the server is
    up and is registered correctly with the DNS server.
    Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
    ......................... DC1 failed test Connectivity
    Testing server: Default-First-Site-Name\DC2
    Starting test: Connectivity
    ......................... DC2 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\DC1
    Skipping all tests, because server DC1 is not responding to directory service requests.
    Testing server: Default-First-Site-Name\DC2
    Starting test: Advertising
    Fatal Error:DsGetDcName (DC2) call failed, error 1355
    The Locator could not find the server.
    ......................... DC2 failed test Advertising
    Starting test: FrsEvent
    ......................... DC2 passed test FrsEvent
    Starting test: DFSREvent
    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 failed test DFSREvent
    Starting test: SysVolCheck
    ......................... DC2 passed test SysVolCheck
    Starting test: KccEvent
    An error event occurred. EventID: 0xC0000466
    Time Generated: 06/12/2014 08:57:14
    Event String: Active Directory Domain Services was unable to establish a connection with the global catalog.
    An error event occurred. EventID: 0xC0000827
    Time Generated: 06/12/2014 08:57:21
    Event String:
    Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Act
    ive Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between
    domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
    A warning event occurred. EventID: 0x8000082C
    Time Generated: 06/12/2014 08:58:14
    Event String:
    ......................... DC2 failed test KccEvent
    Starting test: KnowsOfRoleHolders
    [DC1] DsBindWithSpnEx() failed with error 1722,
    The RPC server is unavailable..
    Warning: DC1 is the Schema Owner, but is not responding to DS RPC Bind.
    Warning: DC1 is the Schema Owner, but is not responding to LDAP Bind.
    ......................... DC2 failed 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
    [Replications Check,DC2] A recent replication attempt failed:
    From DC1 to DC2
    Naming Context: DC=ForestDnsZones,DC=mydomain,DC=com,DC=au
    The replication generated an error (1256):
    The remote system is not available. For information about network troubleshooting, see Windows Help.
    The failure occurred at 2014-06-12 08:57:21.
    The last success occurred at 2013-11-14 00:56:59.
    5057 failures have occurred since the last success.
    [Replications Check,DC2] A recent replication attempt failed:
    From DC1 to DC2
    Naming Context: DC=DomainDnsZones,DC=mydomain,DC=com,DC=au
    The replication generated an error (1256):
    The remote system is not available. For information about network troubleshooting, see Windows Help.
    The failure occurred at 2014-06-12 08:57:21.
    The last success occurred at 2013-11-14 01:10:06.
    5057 failures have occurred since the last success.
    [Replications Check,DC2] A recent replication attempt failed:
    From DC1 to DC2
    Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=au
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    The failure occurred at 2014-06-12 08:57:33.
    The last success occurred at 2013-11-14 00:49:16.
    5054 failures have occurred since the last success.
    The guid-based DNS name 0478fe4a-28c5-4151-894a-06c5b32bf1a0._msdcs.mydomain.com.au
    is not registered on one or more DNS servers.
    [Replications Check,DC2] A recent replication attempt failed:
    From DC1 to DC2
    Naming Context: CN=Configuration,DC=mydomain,DC=com,DC=au
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    The failure occurred at 2014-06-12 08:57:27.
    The last success occurred at 2013-11-14 00:56:53.
    5054 failures have occurred since the last success.
    The guid-based DNS name 0478fe4a-28c5-4151-894a-06c5b32bf1a0._msdcs.mydomain.com.au
    is not registered on one or more DNS servers.
    [Replications Check,DC2] A recent replication attempt failed:
    From DC1 to DC2
    Naming Context: DC=mydomain,DC=com,DC=au
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    The failure occurred at 2014-06-12 08:57:21.
    The last success occurred at 2013-11-14 01:34:40.
    5056 failures have occurred since the last success.
    The guid-based DNS name 0478fe4a-28c5-4151-894a-06c5b32bf1a0._msdcs.mydomain.com.au
    is not registered on one or more DNS servers.
    ......................... DC2 failed test Replications
    Starting test: RidManager
    ......................... DC2 passed test RidManager
    Starting test: Services
    ......................... DC2 passed test Services
    Starting test: SystemLog
    An error event occurred. EventID: 0xC00038D6
    Time Generated: 06/12/2014 08:47:34
    Event String:
    The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data
    A warning event occurred. EventID: 0xC000042B
    Time Generated: 06/12/2014 08:50:30
    Event String:
    The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or
    could not be contacted.
    ......................... DC2 failed 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 : mydomain
    Starting test: CheckSDRefDom
    ......................... mydomain passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... mydomain passed test CrossRefValidation
    Running enterprise tests on : mydomain.com.au
    Starting test: LocatorCheck
    Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
    A Global Catalog Server could not be located - All GC's are down.
    Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
    A Good Time Server could not be located.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
    A KDC could not be located - All the KDCs are down.
    ......................... mydomain.com.au failed test LocatorCheck
    Starting test: Intersite
    ......................... mydomain.com.au passed test Intersite
    and the result of repadmin /showreps:
    C:\Windows\system32>repadmin /showreps
    Default-First-Site-Name\DC2
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: 219d0225-9342-49c5-a00d-e233b042e075
    DSA invocationID: 3587d588-d03b-47e1-81ce-88d14d99a052
    ==== INBOUND NEIGHBORS ======================================
    DC=mydomain,DC=com,DC=au
    Default-First-Site-Name\DC1 via RPC
    DSA object GUID: 0478fe4a-28c5-4151-894a-06c5b32bf1a0
    Last attempt @ 2014-06-12 08:57:21 failed, result 8524 (0x214c):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    5056 consecutive failure(s).
    Last success @ 2013-11-14 01:34:40.
    CN=Configuration,DC=mydomain,DC=com,DC=au
    Default-First-Site-Name\DC1 via RPC
    DSA object GUID: 0478fe4a-28c5-4151-894a-06c5b32bf1a0
    Last attempt @ 2014-06-12 08:57:27 failed, result 8524 (0x214c):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    5054 consecutive failure(s).
    Last success @ 2013-11-14 00:56:53.
    CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=au
    Default-First-Site-Name\DC1 via RPC
    DSA object GUID: 0478fe4a-28c5-4151-894a-06c5b32bf1a0
    Last attempt @ 2014-06-12 08:57:33 failed, result 8524 (0x214c):
    The DSA operation is unable to proceed because of a DNS lookup failure.
    5054 consecutive failure(s).
    Last success @ 2013-11-14 00:49:16.
    DC=DomainDnsZones,DC=mydomain,DC=com,DC=au
    Default-First-Site-Name\DC1 via RPC
    DSA object GUID: 0478fe4a-28c5-4151-894a-06c5b32bf1a0
    Last attempt @ 2014-06-12 08:57:21 failed, result 1256 (0x4e8):
    The remote system is not available. For information about network troubleshooting, see Windows Help.
    5057 consecutive failure(s).
    Last success @ 2013-11-14 01:10:06.
    DC=ForestDnsZones,DC=mydomain,DC=com,DC=au
    Default-First-Site-Name\DC1 via RPC
    DSA object GUID: 0478fe4a-28c5-4151-894a-06c5b32bf1a0
    Last attempt @ 2014-06-12 08:57:21 failed, result 1256 (0x4e8):
    The remote system is not available. For information about network troubleshooting, see Windows Help.
    5057 consecutive failure(s).
    Last success @ 2013-11-14 00:56:59.
    Source: Default-First-Site-Name\DC1
    ******* 5057 CONSECUTIVE FAILURES since 2013-11-14 01:34:40
    Last error: 1256 (0x4e8):
    The remote system is not available. For information about network troubleshooting, see Windows Help.
    DC1 is long gone -- since 2013-11-14 as shown on the last lines of the above output of repadmin. How can I remove all remnants of this old DC?
    I have tried to follow steps in this KB article http://support.microsoft.com/kb/315457/en-gb but the FRS service will not start on my server at all (probably as I'm using DFS). Are there special steps needed to be taken on a server if the SYSVOL/NETLOGON folders
    are using DFS rather than FRS? That article appears to be for Win server 2003 and not 2012.

  • Unable to store log data into database through JDBCAppender of Log4j

    I am able to store the log data into the file as well as to display that on console. But unable to store the same into the database. I am not getting any error or warning while execution. The code of log.properties is as below : -
    log4j.rootLogger=ERROR, C, FILE
    log4j.logger.org.firebird=ERROR, C
    log4j.logger.org.firebirdsql=ERROR, C
    log4j.logger.org.apache.joran=ERROR, C
    log4j.logger.org.apache.log4j.joran.action=ERROR, C
    log4j.appender.FILE=org.apache.log4j.FileAppender
    log4j.appender.FILE.file=/log.txt
    log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
    log4j.appender.FILE.layout.ConversionPattern=[%d{MMM dd HH:mm:ss}] %-5p (%F:%L) - %m%n
    log4j.logger.org.apache.log4j.jdbcplus.examples=DEBUG, JDBC
    # console appender
    log4j.appender.C=org.apache.log4j.ConsoleAppender
    log4j.appender.C.layout=org.apache.log4j.PatternLayout
    log4j.appender.C.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n
    # JDBC appender using custom handlers, 2a)
    log4j.appender.JDBC=org.apache.log4j.jdbcplus.JDBCAppender
    log4j.appender.JDBC.connector=org.apache.log4j.jdbcplus.examples.MySqlConnectionHandler
    log4j.appender.JDBC.sqlhandler=org.apache.log4j.jdbcplus.examples.SqlHandler
    log4j.appender.JDBC.dbclass=com.mysql.jdbc.Driver
    log4j.appender.JDBC2.url=jdbc:mysql:172.22.15.131/3306:plugins?
    log4j.appender.JDBC2.username=user18
    log4j.appender.JDBC2.password=user18
    log4j.appender.JDBC.buffer=1
    log4j.appender.JDBC.commit=true
    log4j.appender.JDBC.sql=INSERT INTO logtest (id, prio, iprio, cat, thread, msg, layout_msg, throwable, ndc, mdc, mdc2, info,
    addon, the_date, the_time, the_timestamp, created_by) VALUES (@INC@, '@PRIO@', @IPRIO@, '@CAT@', '@THREAD@', '@MSG@',
    '@LAYOUT:1@', '@THROWABLE@', '@NDC@', '@MDC:MyMDC@', '@MDC:MyMDC2@', 'info timestamp: @TIMESTAMP@', '@LAYOUT@', cast
    ('@LAYOUT:3@' as date), cast ('@LAYOUT:4@' as time), cast ('@LAYOUT:3@ @LAYOUT:4@' as timestamp), 'me')
    log4j.appender.JDBC.layout=org.apache.log4j.PatternLayout
    log4j.appender.JDBC.layout.ConversionPattern=%m
    Please help me out.. As I got stuck...

    Hi,
    This might help
    http://avdeo.com/2008/05/21/uploading-excel-sheet-using-oracle-application-express-apex/
    I think heading about that blog post is wrong. It is solution to import CSV.
    But you can convert your Excels easilly to CSV.
    I think import pure Excel is quite hard, and I have not seen any solutions.
    See this post also
    Importing Excel spreadsheet into Oracle via Apex
    Br,Jari

  • Unable to Delete a Satellite Server

    I have a satellite server (server class machine)11.1.x . That i want to get ride off. I removed it as a satellite server and it is no longer showing as a Satellite in the Server Hierarchy. I Ithen try to delete the server, I get unable to delete the object error in ZCC when I try
    Tried using zman sd /devicepath but am getting the device has associations or dependencies. Delete those first.
    I cannot see any kind of dependencies or association anywhere. I have looked at at the Locations made sure it is not in any. There are no policies or bundles associated with the device.
    Any suggestions?
    Paul Lamontagne
    Lamtech Consulting Inc.

    Originally Posted by Paul Lamontagne
    The device was on and was comminication as I see the last contact time.
    I tried to removed the ZAA and it did a local uninstall only....
    So now it no longer communicates to the zone, and i cannot delete it out of
    ZCC and i tried to install the 11.2.4 agent and now get a missing libxxx.so
    file
    This is in a lab as well, but I hate not being able to "clean it up before I
    install 11.3.1..
    Paul
    >>> On 08/09/2014 at 7:18 AM, in message
    <NfgPv.6120$[email protected] m>, nop1983<[email protected]>
    wrote:
    > PaulLamontagne wrote:
    >
    >>
    >> I have a satellite server (server class machine)11.1.x . That i want
    >> to get ride off. I removed it as a satellite server and it is no
    >> longer showing as a Satellite in the Server Hierarchy. I Ithen try to
    >> delete the server, I get unable to delete the object error in ZCC
    >> when I try
    >>
    >> Tried using zman sd /devicepath but am getting the device has
    >> associations or dependencies. Delete those first.
    >>
    >> I cannot see any kind of dependencies or association anywhere. I have
    >>
    I could've sworn someone else ran into something similar with this, but I don't recall what the solution (if any) was.
    I thought that for a satellite server that it was acceptable to delete it if you could only do a removal only
    Maybe you can reinstall the agent on the machine and then see if it'll reconnect and let you demote it?

  • Unable to view list of added devices in LMS

    Dear All ,
         Iam working on Cisco LMS 3.2.1.Everything was working fine before but since last 2-3 days we are unable to view the list of added devices under device management tab.We are able to see the added groups only.Because of this issue we are unable to get the logs from the added devices.
    Can anybody help in resolving this issue.....???
    Regards ,
    Divya A M

    We tried the suggested steps and could successfully reset the Casuser Password.But couldnot perform unregistering and registering Apache service.We ended up getting the following errors.
    1.)
    C:\Documents and Settings\Administrator>pdreg -u Apache(no output)
    2.)
    E:\lms\MDC\Apache\bin>pdreg -r Apache -epdcmd: option requires an argument -- eERROR: no such command, or option error.Usage:    pdcmd options...Where -b msg    broadcast message to all daemons -k daemon    kill daemon -K    stop system -H    start system -l    list daemon registry -R daemon    start daemon -i daemon    show daemon status briefly -I    show all daemons status briefly -s daemon    show daemon status -S    show all daemons status -G    show daemon statistics -r daemon -e path -d depends -f arguments [-w ] [-n] [-q] [-t code]    register daemon (-w -- timeout for ready file notification)                    (-n -- no autostart)                    (-q -- no INFO messages)                    (-t {0|p|n} -- expected transient exit code                         where                            0 = expected exit code is 0                            p = expected exit code is >=0                            n = expected exit code is < 0 ) -u daemon [-q]    unregister daemon (-q -- no INFO messages) -v    show version number
    3.)
    E:\lms\MDC\Apache\bin>Apache.exe" -f "-d'Apache.exe" -f "-d' is not recognized as an internal or external command,operable program or batch file.
    4.)
    E:\lms\MDC>Apache -D SSL" -d TomcatMonitor(OS 10048)Only one usage of each socket address (protocol/network address/port)is normally permitted.  : make_sock: could not bind to address 0.0.0.0:443no listening sockets available, shutting downUnable to open logs
    Regards  ,
    Divya

  • Mac Pro - Unable to install SL on disks in Bays 3 & 4

    After a debacle this morning, I reinstalled SL tonight after re-cloning the target disk from my Leopard boot drive. Booting from the DVD, I note that all 4 internal SATA drives have a GUID partition, and three boot Leopard just fine. The last 2 drive bays are not available for a SL install though - they had been a RAD volume, but I demoted both drives to get rid of the RAID. Each drive booted Leopard fine, but could not be used for the installation. Is thee some reason why I could not select them as the install target? There do seem to be issues with SL and RAID volumes in Mac Pro's, but once the drives wee demoted, I've have thought that would be irrelevant. Thanks for any ideas!

    I'd already done that, being unable to think of anything else. I guess RAID is unreliable for now in SL.

  • Unable update Mac to 10.8.5   itune error 103 !!!

    Some one guide tired of try to update my mac to 10.8.5 ..... all the time showing unexpected error occurred !!!!!  
    itune error 103 !!! how can i fix these issue ??

    Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

Maybe you are looking for