IPAM upgrade fails on server 2012 R2

IPAM was installed and running on Server 2012.  Server was then upgraded to 2012 R2.  IPAM console presents "Update IPAM 6.2.01 to 6.3.0.1".   Update then fails with "Failed to convert Schema. Please see the details.
The given key was not present in the dictionary."
Windows event  errors show "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Could not find a login matching the name provided. [CLIENT: <named pipe>]"
The IPAM Admin log shows "The IPAM database schema conversion from version 6.2.0.1 to version 6.3.0.1 failed with error: The given key was not present in the dictionary.. Your IPAM installation might not work properly."
Any ideas?

Hi,
Thank you for your question. 
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best regards,
Susie

Similar Messages

  • IPAM Upgrade Failed - Windows Server 2012 R2

    Why previous discussion was locked?
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/324f812f-80b5-4822-aadc-cf92d9f11949/ipam-upgrade-failed-windows-server-2012-r2?forum=windowsserverpreview
    IPAM Upgrade Failed - Windows Server 2012 R2
    Hi All,
    I'm experiencing some problems with the upgrade procedure of an IPAM service hosted on a Windows Server 2012 R2 instance which originally was deployed on a non-R2 version. I've recently done in-place upgrade of the W2K12 OS to W2K12R2 which went absolutely
    fine, however when I'm trying to upgrade the IPAM service itself (from v6.2.0.1 to v6.3.0.1), I'm receiving an error message right after the database schema update procedure.
    Received error message:
    Failed to convert Schema. Please see the details.
    The given key was not present in the dictionary.
    Please restart the Wizard to update the IPAM server.
    Tried to restart the wizard several times, but it ends up with the same result.
    Also I noticed that the event log shows some authentication problems with the WID DB service:
    Connecting to IPAM database failed with,
        Number: 18456
        ErrorCode: -2146232060
        Level: 14
        State: 1
        Message: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
    For database,
        Database Type: WindowsInternalDatabase
        Database Authentication Type: WindowsAuthentication
        Database Name: IPAM
        Database Path: C:\Windows\System32\ipam\Database
        Database Server:
        Database Server Port: 0
        Username:
    The original IPAM deployment was pretty much a standard one by the official MS guides so there were no custom actions applied at any point in time. Right now I can access neither the IPAM features nor the previously made inventory, because server manager wouldn't
    let me do so until the upgrade is complete. For the time being this upgrade failure seems to be a bug.
    Kindly ask you to help me out with this issue.
    Thanks in advance.

    Hi, event id 60002 in admin log:
    Connecting to IPAM database failed with,
    Number: 18456
    ErrorCode: -2146232060
    Level: 14
    State: 1
    Message: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
    For database,
    Database Type: WindowsInternalDatabase
    Database Authentication Type: WindowsAuthentication
    Database Name: IPAM
    Database Path: C:\Windows\System32\ipam\Database
    Database Server:
    Database Server Port: 0
    Username:
    and event id 10459:
    The IPAM database schema conversion from version 6.2.0.1 to version 6.3.0.1 failed with error: The given key was not present in the dictionary.. Your IPAM installation might not work properly.
    10x

  • Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1

    We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1.  Upgrade was successful.  Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
    Studio are unable to log in via Windows Authentication. 
    The error they receive is listed below:
    Connect not connect to XXXXXXX
    Login Failed.  The login is from an untrusted domain and cannot be used with Windows Authentication. 
    (Microsoft SQL Server, Error: 18452)
    If we switch to Mixed authentication, users can log in via SQL Server Authentication.
    Our security policy prohibits SQL Authentication. 
    Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?
    Thanks.
    DJ

    Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
    Extended Protection is?
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Windows Server 2012 Essentials upgrade to Windows Server 2012 Standard

    I've just upgraded a Windows Server 2012 Essentials to Standard via the Powershell command. The server restarted and is now Standard version. However I've noticed in the services that one particular service fails. 
    silsvc <Failed to Read Description. Error Code: 2 > 
    C:\Windows\system32\silsvc.exe
    It is set to automatic.
    I guess this is part of the essentials license and hasn't been removed. I would like to keep the Essentials Features however on a VM I replicated the same problem but when I removed Essentials features this service also got removed.
    Is it ok to just disable this service? because I want to keep the Essentials features. Is it going to cause any issues?

    Hello,
    What is the procedure to migrate to standard essentials without losing programs?
    Can you help me?
    actually I have windows server 2012 essentials and I want to upgrade to standard

  • Upgrade from Windows Server 2012 Active Directory to Windows Server 2012 R2 Active Directory

    We are currently running Windows Server 2012 Active Directory and would like to upgrade to Windows Server 2012 R2 AD. Is it OK to just do an in-place upgrade, or is it advisable to build new domain controllers on R2? Are there any guides or articles anyone
    can recommend?

    Hi Ginandtonic,
    To upgrade DC(Domain Controller) from windows server 2012 to windows server 2012 r2, please refer to these articles:
    Upgrade from windows Server 2012 to 2012 R2                                 
    Upgrade Active Directory from 2012 to 2012 R2
    I hope this helps.
    Best Regards,
    Anna

  • In-place upgrade of Windows Server 2012 RDS to R2 fails

    Hi All
    I have a Server 2012 Standard RDS virtual machine (vmware) on which I have tried doing an in-place upgrade to 2012 R2 but it constantly fails.
    It sits at the "Collecting files, settings and applications" process for quite a while - always on 0% and then says: Installing Windows was Canceled "Setup can't continue. Restart the computer and restart Setup. When prompted, try getting
    the latest updates."
    I have tried combinations of all the settings during setup to look for updates, not look for updates, etc., rebooted several times, even disabled the RDS services and still the same result.
    As a test, I tried doing an in-place upgrade on the base OS installation that was used to create this VM and it works perfectly. The only difference between the servers is that the live has RDS role installed.
    Is there any Microsoft documentation on the 2012 RDS in-place upgrade process to R2?
    Can anyone offer any suggestion as to why the in-place upgrade might be failing with the RDS role installed?
    Thanks heaps

    As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.
    It seems that the RDS role may be preventing the upgrade?
    Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.
    if you really think the RDS is preventing the upgrade, how about stopping the RDS service then do an in place upgrade.
    check how it goes.. :)
    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

    Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
    Given:
    1) Operating System Windows 2012 R2
    2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource.  The two VMS are called APPS08 and APPS09.  They are our development environment that is setup similar to our production environment.
    Problem:  When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance.  I then moved onto upgrading on the node that was running the instance.  As soon as the install attempt to failover the running instance
    an install error occurred that it could not failover.  After many install attempts I consistently received the error
    The SQL Server Failover cluster instance name 'Dev01'
    already exists as a cluster resource.  Opening Failover cluster manager there is no record of a DEV01.
    New Strategy:  Create a SQLCluster called DEV07.  At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists.  Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.  
    We do not see anything out of the ordinary.
    Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

    Hi PSCSQLDBA,
    As your description, you want to upgrade the default instance in SQL Server cluster.
    >> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
    This error could occur when there is a previously used instance name which may not be removed completely.
    To work around the issue, please use one of the ways below.
    1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
    For more information about the process, please refer to the article:
    http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
    2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
    For more information about the process, please refer to the article:
    http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
    >> 'Resource for instance 'MSSQLSERVER' should not exist'
    This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
    Regards,
    Michelle Li

  • SCSM 2012 R2 - In-Place Upgrade to Windows Server 2012 R2

    Hello,
    is an in-place upgrade of the underlying OS from Windows Server 2012 to Windows Server 2012 R2 supported by SCSM 2012R2. I know of some products where it is supported, some where it isn't (e.g. Exchange) but I haven't found any information on SCSM (Management,
    DW, SQL, DWSQL).
    Thank you in advance.
    Regards
    Sascha

    i would never recommend upgrading the OS on any production environment, especially you have any virtualization and can stand up the new OS on the same hardware. 
    that being said, i don't see any obvious reason this would fail, but i don't thing it would be obviously supported either. 

  • Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

    My Current Setup: 
    I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
    VM1: Configured to boot from an ISO file and runs Clonezilla server. 
    VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk. 
    These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server. 
    For the past few months I have been using this setup for two purposes:
    1. To clone physical machines to the Clonezilla virtual server (as a backup).
    2. To restore those image to the second VM if I find that need to get access to the files on the original image.. 
    This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works... 
    Now my problem:
    I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
    PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot). 
    Are Gen 2 VMs unable to pull down images from anything other than a WDS Server? 

    Hi J,
    >>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
    If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.”  In addition, make sure not to set the client to the domain in the unattend file and do not prestage
    the computer in AD. "
    It is quoted from following thread :
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
    Best Regards
    Elton Ji
    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.

  • Windows Update fails on Server 2012 R2 Virtual Machine

    I have set up a virtual network with two virtual machines. The first VM is Server 2008 R2 and is set up as a domain controller. The second VM is Server 2012 R2, and has been joined to the domain.  The DC (TestVM1) is also set up as a DNS server. 
    From TestVM2 (Server 2012 R2), I am able to log in using a domain login, and I am able to browse to a public website.
    I was able to run Windows Updates from TestVM1, but when I attempt to run Windows Updates from TestVM2, it fails.
    The Windows Update client shows "Error(s) found:" and "Code 8024402F". 
    Errors in WindowsUpdate.log include
    2014-10-17 18:26:14:235  800 950 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
    2014-10-17 18:26:26:238  800 950 Misc WARNING: Send failed with hr = 80072ee7.
    2014-10-17 18:26:26:238  800 950 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-10-17 18:26:26:238  800 950 Misc WARNING: Send request failed, hr:0x80072ee7
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://v4.download.windowsupdate.com/c/msdownload/update/others/2014/08/13518740_b1b71791444e5dec0018bcd60303445108442c12.cab>.
    error 0x8024402c
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: WinHttpQueryHeaders(WINHTTP_QUERY_CONTENT_TYPE) for X-CID failed. error 0x80072ef3
    2014-10-17 18:26:26:238  800 950 PT WARNING: ECP: DownloadCabFile: failed to get CDN Provider for error reporting, hr = 0X80072EF3
    2014-10-17 18:26:26:238  800 950 Misc WARNING: WinHttp: WinHttpQueryHeaders(WINHTTP_QUERY_CONTENT_TYPE) for X-CCC failed. error 0x80072ef3
    2014-10-17 18:26:26:238  800 950 PT WARNING: ECP: DownloadCabFile: failed to get CDN Country for error reporting, hr = 0X80072EF3
    2014-10-17 18:26:26:238  800 950 PT WARNING: ECP: Failed to download cab file from
    http://download.windowsupdate.com/c/msdownload/update/others/2014/08/13518740_b1b71791444e5dec0018bcd60303445108442c12.cab with error 0x8024402c
    2014-10-17 18:26:26:238  800 950 PT WARNING: ECP: This roundtrip contained some optimized updates which failed. New Update count = 34, Old Count = 60
    2014-10-17 18:26:26:317  800 950 PT   + SyncUpdates round trips: 1
    2014-10-17 18:26:26:317  800 950 PT WARNING: Sync of Updates: 0x8024402f
    2014-10-17 18:26:26:317  800 950 PT WARNING: SyncServerUpdatesInternal failed: 0x8024402f
    2014-10-17 18:26:26:317  800 950 Agent   * WARNING: Failed to synchronize, error = 0x8024402F
    2014-10-17 18:26:26:317  800 950 Agent   * WARNING: Exit code = 0x8024402F
    This is blocking further work.  Assistance would be greatly appreciated.

    I am having the exact same issue. Fresh build of Server 2012 R2 from the Microsoft Volume Licensing ISO. I tried before and after joining to the domain. Same error every time.  Firewall is turned off. No AV. We do have a cloud proxy service, but I bypassed
    that as a test and got the same error message.  I also tried to stop wuauserv and cleaning out the folder and starting it back up.  No joy as well.  This is a VM server running on ESXi 5.1.  Server 2008 servers dont seem to have
    an issue.  Server 2012 server don't seem to have an issue.  Only this new Server 2012 R2 server.  My logs are below:
    2014-10-28 14:28:46:104  696 4a4 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-10-28 14:28:46:104  696 4a4 WuTask Uninit WU Task Manager
    2014-10-28 14:28:46:198  696 4a4 Service *********
    2014-10-28 14:28:46:198  696 4a4 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-10-28 14:28:46:198  696 4a4 Service *************
    2014-10-28 14:29:24:198  696 5c8 Misc ===========  Logging initialized (build: 7.9.9600.17092, tz: -0400)  ===========
    2014-10-28 14:29:24:198  696 5c8 Misc   = Process: C:\Windows\system32\svchost.exe
    2014-10-28 14:29:24:198  696 5c8 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-10-28 14:29:24:198  696 5c8 Service *************
    2014-10-28 14:29:24:198  696 5c8 Service ** START **  Service: Service startup
    2014-10-28 14:29:24:198  696 5c8 Service *********
    2014-10-28 14:29:24:214  696 5c8 Agent   * WU client version 7.9.9600.17092
    2014-10-28 14:29:24:214  696 5c8 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-10-28 14:29:24:214  696 5c8 Agent   * Access type: No proxy
    2014-10-28 14:29:24:214  696 5c8 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-10-28 14:29:24:214  696 5c8 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-10-28 14:29:24:214  696 5c8 Agent   * Network state: Connected
    2014-10-28 14:29:24:214  696 5c8 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-10-28 14:29:24:214  696 5c8 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-10-28 14:29:24:510  696 5c8 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
    2014-10-28 14:29:24:510  696 5c8 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2014-10-28 14:29:24:542  696 5c8 DtaStor Data store successfully created
    2014-10-28 14:29:24:542  696 5c8 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-10-28 14:29:24:542  696 5c8 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-10-28 14:29:24:542  696 5c8 Agent   * WSUS server: <NULL>
    2014-10-28 14:29:24:542  696 5c8 Agent   * WSUS status server: <NULL>
    2014-10-28 14:29:24:542  696 5c8 Agent   * Target group: (Unassigned Computers)
    2014-10-28 14:29:24:542  696 5c8 Agent   * Windows Update access disabled: No
    2014-10-28 14:29:24:542  696 5c8 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-10-28 14:29:24:542  696 5c8 WuTask WuTaskManager delay initialize completed successfully..
    2014-10-28 14:29:24:542  696 5c8 Report WARNING: Failed to initialize event uploader for new server {9482F4B4-E343-43B6-B170-9A65BC822C77} with hr = 8024043d.
    2014-10-28 14:29:24:542  696 5c8 Report CWERReporter::Init succeeded
    2014-10-28 14:29:24:542  696 5c8 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-10-28 14:29:24:542  696 5c8 DnldMgr Download manager restoring 0 downloads
    2014-10-28 14:29:24:557  696 5c8 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-10-28 14:29:24:557  696 5c8 AU AIR Mode is disabled
    2014-10-28 14:29:24:557  696 5c8 AU   # AU disabled through User preference
    2014-10-28 14:29:24:557  696 5c8 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-10-28 14:29:24:557  696 5c8 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-10-28 14:29:24:557  696 5c8 AU AU finished delayed initialization
    2014-10-28 14:29:24:557  696 234 DnldMgr Asking handlers to reconcile their sandboxes
    2014-10-28 14:29:35:776  696 578 IdleTmr Incremented idle timer priority operation counter to 1
    2014-10-28 14:29:37:307  696 52c AU Triggering AU detection through DetectNow API
    2014-10-28 14:29:37:307  696 52c AU Triggering Online detection (interactive)
    2014-10-28 14:29:37:323  696 5c8 AU #############
    2014-10-28 14:29:37:323  696 5c8 AU ## START ##  AU: Search for updates
    2014-10-28 14:29:37:323  696 5c8 AU #########
    2014-10-28 14:29:37:323  696 5c8 SLS Retrieving SLS response from server...
    2014-10-28 14:29:37:323  696 5c8 SLS Making request with URL
    HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=871&L=en-US&P=&PT=0x7&WUA=7.9.9600.17092
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: Proxy List used: <172.25.7.9:80> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: Send request failed, hr:0x80072ee2
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=871&L=en-US&P=&PT=0x7&WUA=7.9.9600.17092>.
    error 0x80072ee2
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
    2014-10-28 14:29:58:339  696 5c8 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
    2014-10-28 14:29:58:339  696 5c8 SLS FATAL: SLS:CSLSDownloader::GetUrlContent: DoFileDownload failed with 0x80072ee2.
    2014-10-28 14:29:58:339  696 5c8 SLS FATAL: GetResponse failed with hresult 0x80072ee2...
    2014-10-28 14:29:58:339  696 5c8 EP FATAL: EP: CSLSEndpointProvider::GetWUClientDataAndInitParser - failed to get SLS data, error = 0x80072EE2
    2014-10-28 14:29:58:339  696 5c8 EP FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS - Failed to get client data and init parser, error = 0x80072EE2
    2014-10-28 14:29:58:339  696 5c8 EP FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x80072EE2
    2014-10-28 14:29:58:339  696 5c8 Agent WARNING: Failed to obtain the authorization cab URL for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0
    2014-10-28 14:29:58:339  696 5c8 Agent FATAL: Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0X80072EE2
    2014-10-28 14:29:58:339  696 5c8 IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 7; does use network; is not at background priority
    2014-10-28 14:29:58:339  696 5c8 IdleTmr Incremented PDC RefCount for Network to 1
    2014-10-28 14:29:58:339  696 5c8 IdleTmr Incremented idle timer priority operation counter to 2
    2014-10-28 14:29:58:385  696 5c8 Report ***********  Report: Initializing static reporting data  ***********
    2014-10-28 14:29:58:385  696 5c8 Report   * OS Version = 6.3.9600.0.0.196880
    2014-10-28 14:29:58:385  696 5c8 Report   * OS Product Type = 0x00000007
    2014-10-28 14:29:58:401  696 5c8 Report   * Computer Brand = VMware, Inc.
    2014-10-28 14:29:58:401  696 5c8 Report   * Computer Model = VMware Virtual Platform
    2014-10-28 14:29:58:401  696 5c8 Report   * Platform Role = 1
    2014-10-28 14:29:58:401  696 5c8 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Revision = 6.00
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0    
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Release Date = 2013-08-16T00:00:00
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Sku Number unavailable.
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Vendor = Phoenix Technologies LTD
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Family unavailable.
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Major Release = 4
    2014-10-28 14:29:58:401  696 5c8 Report   * Bios Minor Release = 6
    2014-10-28 14:29:58:401  696 5c8 Report   * Locale ID = 1033
    2014-10-28 14:29:58:401  696 5c8 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-10-28 14:29:58:401  696 5c8 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {4A8CCE12-100B-4178-998D-608DFBB0B2D0} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
    2014-10-28 14:29:58:432  696 b0c Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-10-28 14:29:58:432  696 b0c Agent *************
    2014-10-28 14:29:58:432  696 b0c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-10-28 14:29:58:432  696 b0c Agent *********
    2014-10-28 14:29:58:432  696 b0c Agent   * Online = Yes; Ignore download priority = No
    2014-10-28 14:29:58:432  696 b0c Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-10-28 14:29:58:432  696 b0c Agent   * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
    2014-10-28 14:29:58:432  696 b0c Agent   * Search Scope = {Machine & All Users}
    2014-10-28 14:29:58:432  696 b0c Agent   * Caller SID for Applicability: S-1-5-21-600452275-980750782-2124898778-9669
    2014-10-28 14:29:58:432  696 b0c SLS Retrieving SLS response from server...
    2014-10-28 14:29:58:432  696 b0c SLS Making request with URL
    HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=871&L=en-US&P=&PT=0x7&WUA=7.9.9600.17092
    2014-10-28 14:29:59:135  696 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
    2014-10-28 14:29:59:135  696 b0c Misc  Microsoft signed: NA
    2014-10-28 14:29:59:135  696 b0c Misc  Infrastructure signed: Yes
    2014-10-28 14:29:59:135  696 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP3958.tmp with dwProvFlags 0x00000080:
    2014-10-28 14:29:59:135  696 b0c Misc  Microsoft signed: NA
    2014-10-28 14:29:59:135  696 b0c Misc  Infrastructure signed: Yes
    2014-10-28 14:29:59:135  696 b0c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "117cab2d-82b1-4b5a-a08c-4d62dbee7782"
    2014-10-28 14:29:59:135  696 b0c SLS FATAL: SLS:CSLSRequest::RetrieveAdditionalAttributesIfRequired: CoCreateInstance failed with 0x80040154.
    2014-10-28 14:29:59:135  696 b0c Agent WARNING: Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x80040154
    2014-10-28 14:29:59:135  696 b0c Agent FATAL: Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0X80040154
    2014-10-28 14:29:59:135  696 b0c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
    2014-10-28 14:29:59:135  696 b0c Setup Checking for agent SelfUpdate
    2014-10-28 14:29:59:135  696 b0c Setup Client version: Core: 7.9.9600.17092  Aux: 7.9.9600.17031
    2014-10-28 14:29:59:135  696 b0c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SelfUpdate URL: "https://fe2.update.microsoft.com/v10/3/windowsupdate/selfupdate"
    2014-10-28 14:30:00:151  696 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-10-28 14:30:00:151  696 b0c Misc  Microsoft signed: NA
    2014-10-28 14:30:00:151  696 b0c Misc  Infrastructure signed: Yes
    2014-10-28 14:30:00:151  696 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP3D51.tmp with dwProvFlags 0x00000080:
    2014-10-28 14:30:00:167  696 b0c Misc  Microsoft signed: NA
    2014-10-28 14:30:00:167  696 b0c Misc  Infrastructure signed: Yes
    2014-10-28 14:30:00:167  696 b0c Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
    2014-10-28 14:30:00:167  696 b0c Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2014-10-28 14:30:00:167  696 b0c Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-10-28 14:30:00:323  696 b0c PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-10-28 14:30:00:323  696 b0c PT   + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
    https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
    2014-10-28 14:30:01:104  696 b0c PT WARNING: Cached cookie has expired or new PID is available
    2014-10-28 14:30:01:104  696 b0c PT WARNING: PTWarn: Anonymous plug-in skipped for WU
    2014-10-28 14:30:01:198  696 b0c Agent Reading cached app categories using lifetime 604800 seconds
    2014-10-28 14:30:01:198  696 b0c Agent Read 1 cached app categories
    2014-10-28 14:30:40:917  696 b0c PT WARNING: ECP: Failed to validate cab file digest downloaded from
    http://download.windowsupdate.com/d/msdownload/update/others/2013/09/9242543_a77d372b9c8b13c599a3daf4b321ea1903da9a72.cab with error 0x80091007
    2014-10-28 14:30:40:917  696 b0c PT WARNING: ECP: This roundtrip contained some optimized updates which failed. New Update count = 57, Old Count = 60
    2014-10-28 14:30:41:151  696 b0c PT   + SyncUpdates round trips: 14
    2014-10-28 14:30:41:151  696 b0c PT WARNING: Sync of Updates: 0x8024402f
    2014-10-28 14:30:41:151  696 b0c PT WARNING: SyncServerUpdatesInternal failed: 0x8024402f
    2014-10-28 14:30:41:151  696 b0c Agent   * WARNING: Failed to synchronize, error = 0x8024402F
    2014-10-28 14:30:41:151  696 b0c Agent   * WARNING: Exit code = 0x8024402F
    2014-10-28 14:30:41:151  696 b0c Agent *********
    2014-10-28 14:30:41:151  696 b0c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-10-28 14:30:41:151  696 b0c Agent *************
    2014-10-28 14:30:41:151  696 b0c Agent WARNING: WU client failed Searching for update with error 0x8024402f
    2014-10-28 14:30:41:151  696 b0c IdleTmr WU operation (CSearchCall::Init ID 1, operation # 7) stopped; does use network; is not at background priority
    2014-10-28 14:30:41:151  696 b0c IdleTmr Decremented PDC RefCount for Network to 0
    2014-10-28 14:30:41:151  696 b0c IdleTmr Decremented idle timer priority operation counter to 1
    2014-10-28 14:30:41:151  696 6fc AU >>##  RESUMED  ## AU: Search for updates [CallId = {4A8CCE12-100B-4178-998D-608DFBB0B2D0} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
    2014-10-28 14:30:41:151  696 6fc AU   # WARNING: Search callback failed, result = 0x8024402F
    2014-10-28 14:30:41:151  696 6fc AU #########
    2014-10-28 14:30:41:151  696 6fc AU ##  END  ##  AU: Search for updates  [CallId = {4A8CCE12-100B-4178-998D-608DFBB0B2D0} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
    2014-10-28 14:30:41:151  696 6fc AU #############
    2014-10-28 14:30:41:151  696 6fc AU All AU searches complete.
    2014-10-28 14:30:41:151  696 6fc AU   # WARNING: Failed to find updates with error code 8024402f
    Derek
    Systems Engineer
    Derek Desktop Engineer

  • Syspolicy_purge_history job getting failed (SQL Server 2012)

    Job Name  syspolicy_purge_history
    Step Name  Erase Phantom System Health Records.
    Duration  00:00:05
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed 
    Operator Net sent 
    Operator Paged 
    Retries Attempted 0
    Error Message :-
    A job step received an error at line 1 in a PowerShell script. The corresponding line is 'import-module SQLPS  -DisableNameChecking'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'The following error occurred
    while loading the extended type data file:
    Microsoft.PowerShell, D:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules\SQLPS\sqlprovider.types.ps1xml : File skipped because of the following validation exception: AuthorizationManager check failed..

    Hi nap_bhatt,
    Based on your description, we need to verify that if you get the error while starting the syspolicy_purge_history job manually in SQL Server 2012. If so, which account do you use to log on to the SQL Server instance and run the job?
    According to the error message “AuthorizationManager check failed” , it indicates that your account has no permission to execute the PowerShell script in SQL Server Agent job. To troubleshoot this issue, please make sure that your account has permissions
    to the SQLPS folder and it has rights to execute the PowerShell script.
    In addition, please use the “Get-ExecutionPolicy” PowerShell command to check the current status of execution policy, if the execution policy is set to “Restricted”, try to set it to “RemoteSigned” or “Unrestricted”. Please note that you need to set this
    execution policy in both the Windows PowerShell  and the SQL PowerShell consoles.
    For more information about syspolicy_purge_history job in SQL Server 2012,  please review this similar blog:
    SQL job “syspolicy_purge_history” fails on SQL 2012 .
    Thanks,
    Lydia Zhang

  • Automatic Virtual Machine Activation failing on Server 2012 R2 with Update

    Appears AVMA is now broken on new media with Update:
    Trying to use the Key from:
    http://technet.microsoft.com/en-us/library/dn303421.aspx
    en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso
    Receive the message "We Couldn't Verify the product Key. Please check your installation Media
    Works fine with
    en_windows_server_2012_r2_x64_dvd_2707946.iso
    I have downloaded the media more than once with same error.  Do we need to update the AVMA Key?
    Thanks

    Hi JAM ,
    Is the first ISO downloaded from MS official web site ?
    If yes , please use command " slmgr /dlv "to check the server edition , if it is evaluation edition please refer to the following similar thread :
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/d6792f61-36aa-46d5-abc6-880cd1437da6/windows-server-2012-evaluation-activation-issue?forum=winserver8setup
    Best Regards
    Elton JI
    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.

  • Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

    Shouldn't I be able to upgrade to 2008 R2?
    Current version:
    Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    I've the same problem as described above.
    My Version is: 10.0.2531.0 SP1
    Standard Edition (64-bit), on Windows Server 2003
    Additionally, I have SQL Server 2005 Developer installed on the same machine.
    I choosed SQL Server 2008 to upgrade to R2.
    In the log I found:
     2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' found no upgrade features.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_engine_core_inst_Cpu64'.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package  'sql_engine_core_inst_ctp6_Cpu64' with SkuValue=STANDARD ProductVersion=10.0.1600.22
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition STANDARD for feature package 'sql_engine_core_inst_Cpu64'.
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=STANDARD sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix found match in sku matrix.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_engine_core_inst_Cpu64' permits upgrade.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_is_Cpu64'.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package  'IS2005_Cpu64' with SkuValue=DEVELOPER ProductVersion=9.3.4035.00
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 9.0 and edition DEVELOPER for feature package 'sql_is_Cpu64'.
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=9.0 sourceEdition=DEVELOPER sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
    2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_is_Cpu64' is blocking upgrade.
    2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
    2010-10-01 17:54:31 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
    2010-10-01 17:54:31 Slp: Rule running on machine: <skipped>
    2010-10-01 17:54:31 Slp: Rule evaluation done   : Failed
    2010-10-01 17:54:31 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 R2 version and edition upgrade matrix in Books Online.
    Thanks,
    Patrik

  • Upgrading to Windows Server 2012 R2 from Server 2003

    If they plan to buy new hardware, then yes, this could be a great opportunity for you to learn and tinker with the new server without affecting the main production server. You can install Hyper-V, create some VMs, and learn what the different server roles do. Then perform the final migration when you're ready.
    There's tons of topics in the form and on Microsoft TechNet that'll walk you through, step-by-step, on migrating just about anything from 2003 to 2012. 
    I would of discouraged you if it was an in-place upgrade. If you're getting new hardware, take this as an excellent opportunity to educate yourself and don't feel afraid to reach out.

    Hi everyone! I'm relatively new to IT (I've only been working in a business environment for one year) and have already been tasked to build a new server for the company. Whoever built the current server configuration did a terrible job by "best practice" standards and the company wants to do a complete rebuild from the ground up. I have little experience in servers and feel I may be in over my head. At the same time this may be a perfect opportunity to test my skills and prove my worth.
    Do you have any tips/advice for setting up a new server (AD domain controller/file server/print server) while the server to be replaced is still running?
    This topic first appeared in the Spiceworks Community

  • Windows small business 2011 standard cannot be upgraded to windows server 2012 R2 Standard

    Can Sbs 2011 r2 standard upgrade to 2012 r2 standard?

    Hi,
    I agree with Cliff. There is no in-place upgrade and we have to do a migration.
    Regarding how to migrate Small Business Server, the following article can be referred to as reference.
    Windows Small Business Server Migration
    http://technet.microsoft.com/en-us/sbs/gg981878
    Best regards,
    Frank Shen

Maybe you are looking for