Migrating 2010 cms to 2013 cms fails with not accessible

im trying to decommission 2010 and 1 of the steps is to move the cms database to the 2013 side, but whenever i try to run the move command it fails with 
Move-CsManagementServer : Cannot move Central Management Server. The new
Central Management Store located at "lynp02.company.com\rtc" is not
accessible.
At line:1 char:1
+ Move-CsManagementServer
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Move-CsManagementServer], Exce
   ption
    + FullyQualifiedErrorId : Move not supported.,Microsoft.Rtc.Management.Dep
   loyment.MoveCms.MoveCmsCmdlet
current setup
1 lync 2010 std edition server with CMS file store/store and store scp dbs hosted locally on itself.(no sql is involved).
2 lync 2013 servers std edition.
the only database that resides on a sql server is the archiving database(which i already setup a new sql archiving database for 2013).
all other lync dbs reside locally on their front end server installs.
2010
lnCp01.local.net\rtc
2013
lynp01.local.net\rtc
lynp02.local.net\rtc
i have already moved all users to the lyncp02.local.net front end server and into the 2013 pool. but cant move the CMS.
any help would be appreciated.

Hi,
Please check to ensure the SQL Server (RTC) service is running on the new front end.
Also check SQL configuration manager and ensure that TCP/IP is enabled for client protocols under client configuration (although this should be enabled).
You may also re-run the database installation procedure for the CMS outlined here;
http://technet.microsoft.com/en-us/library/jj688013.aspx (assuming that you've already performed it once).
You may need to include the -clean switch if you have already done this, then attempt to move it again.
Attempt the move command from an elevated management shell (administrative credentials)
Kind regards
Ben
Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you've asked, please mark the thread as answered to aid others when they're looking for solutions to similar problems or queries.
For Fun: Gecko-Studio | For Work:
Nexus Open Systems

Similar Messages

  • Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

    Hi,
    I am trying to deploy Office 2013, along with SP1, in the following order:
    1. Prompt to close all office apps and continue (vbs)
    2. Installation of Office 2013, using modified msp.
    3. Restart
    4. Installation of SP1 with command line /passive /norestart.
    I am doing this all through a package I created in SCCM 2007 R2.
    The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
    Manual installation, through command prompt, with the same switches works fine.
    The error is only when remotely deploying.
    The system is Windows 7 X86 with latest SP.
    Please help!

    Hi,
    Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
    By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
    http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
    (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Project Server 2013: QueueUpdateProject2 fails with LookupTableItemInvalidLookupTable error

    Hi,
    We have a strange problem here using the newly introduced QueueUpdateProject2 PSI method in WebSvcProject. The server is running version 15.0.4481.1005 (Project Server 2013, March 2013 PU). Here's the minimum repro code:
    projectService.CheckOutProject(projectUid, sessionUid, sessionDescription);
    var projectDataSet = projectService.ReadProject(projectUid, DataStoreEnum.WorkingStore);
    projectDataSet.Project[0].SetModified(); // Simplest repro
    var jobUid = Guid.NewGuid();
    projectService.QueueUpdateProject2(jobUid, sessionUid, projectDataSet, false);
    Unfortunately the QueueUpdateProject2 queue job always fails with error LookupTableItemInvalidLookupTable for this project. Here's the full error information as shown in PWA:
    LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07:
    LookupTableItemInvalidLookupTable (11073). Details: id='11073' name='LookupTableItemInvalidLookupTable' uid='b1c62182-924c-e311-9404-00155d027b07'.
    Queue:
    GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='b020bf82-924c-e311-9404-00155d027b07' JobUID='f294b911-f500-45bc-91ec-a493bdf3d07a' ComputerName='1beb2ff2-5dc9-4136-aa24-1c2be86c5768'
    GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='ce4e569c-0aa5-70d6-c576-8b3b764d14f1'. For more details, check the ULS logs on machine
    1beb2ff2-5dc9-4136-aa24-1c2be86c5768 for entries with JobUID
    f294b911-f500-45bc-91ec-a493bdf3d07a.
    Here are some corresponding entries from the ULS log:
    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     myzo Medium   Error is: LookupTableItemInvalidLookupTable. Details: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07 . Standard Information: , LogLevelManager Warning-ulsID:0x6D797A6F has no
    entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     4zbp Monitorable PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|my\account, PSI: [TrackingId:fa790381-924c-e311-9404-00155d027b07][ResourceId:3222f5b7-c13b-e311-9404-00155d027b07][SessionGuid:db83645c-50e1-4368-a59f-94df13ff7d5e][SessionDescr:][JobGuid:af20bf82-924c-e311-9404-00155d027b07][ProjectGuid:81a4a757-c446-e311-9404-00155d027b07][PS_AC][400]
    Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07     at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader
    cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName, Int32 projType, Boolean ... ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82* Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     4zbp Monitorable ...isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData,
    String winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    We would be happy to provide more information if needed. Project Professional can open and save the project just fine, so it seems to be unrelated to other forum posts (1, 2).
    Has anybody seen this before? Any hints on where to search or what to look for?
    Thanks,
    Thomas
    TPG The Project Group
    [1] http://social.technet.microsoft.com/Forums/projectserver/en-US/da3c0d64-1ced-45dd-ace6-ce821fd1c362/what-are-the-lookup-fields-in-the-local-project-cant-publish-project-to-the-server
    [2] http://answers.microsoft.com/en-us/office/forum/office_2010-project/error-110730x2b41-importsave-to-project-server/03fd792f-4451-4512-ac0b-ddad946c3e3

    Just to clarify,  I get these errors in the ULS logs:
    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
    Server        Active Cache Save        myzo        Medium        Error is: LookupTableItemInvalidLookupTable.
    Details: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a . Standard Information: PSI Entry Point:  Project User: i:0#.w|africa\spsetupdev Correlation Id: f6a91701-62f1-e311-944d-00155de84b1a PWA Site URL:
    http://epmdev.af.didata.local/PWA SA Name: SharePoint_EPM_Dev_ProjectServerService PSError: LookupTableItemInvalidLookupTable (11073), LogLevelManager Warning-ulsID:0x6D797A6F has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
    Server        Active Cache Save        4zbp        Monitorable        PWA:http://epmdev.af.didata.local/PWA,
    ServiceApp:SharePoint_EPM_Dev_ProjectServerService, User:i:0#.w|africa\spsetupdev, PSI: [TrackingId:f6a91701-62f1-e311-944d-00155de84b1a][ResourceId:f6760993-7a33-47ef-8cea-0c9cc5231ae7][SessionGuid:6c189001-cd9e-e311-9426-00155d879c00][SessionDescr:ZABRYSVEPMD01\Dev
    PWA][JobGuid:d3e31201-62f1-e311-944d-00155de84b1a][ProjectGuid:7537ccc0-7692-4456-93dd-fc7adcb5d1c8][PS_AC][807] Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a    
    at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName,
    Int32 projType, Boolean isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData, String
    winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
    And in addition to that, we get the Error  9000 when saving in MSP.  
    Still downloading the files, but the more and more I look at it I'm hopeful this will solve our problem.
    http://blogs.umtsa.co.za/nicoo

  • SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

    SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The virtual directory 'ecp' already exists under 'server/name'.
    Parameter name: VirtualDirectoryName".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    !! And now transport service won't start and mail is unavailable !!
    Any help would be appreciated.
    I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

    Hi,
    Thanks for your response.
    From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2010 Sp2 update rollup 7 fails with error code 80070643 on Sbs 2011

    Hello Everyone,
    When i trie to install rollup 7 voor exchange 2010 sp2 (sbs 2011) it gives me error code 80070643. I cannot find much to solve this problem. Update rollup 8 installs fine. I've read on internet that every rollup must be installed to succesfully install exchange
    2010 sp3. Can anyone help me with this error?

    I just installed exchange 2010 sp3, but it does not finish. It stops at 'client access role'
    This is in the log;
    [10-08-2014 21:55:24.0121] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'server.company.com', Preferred Global Catalog: 'server.company.com', Preferred Domain Controllers:
    '{ server.company.com }'
    [10-08-2014 21:55:24.0121] [2] Beginning processing Start-SetupProcess -Name:'iisreset' -Args:'/noforce /timeout:120'
    [10-08-2014 21:55:24.0137] [2] Starting: iisreset with arguments: /noforce /timeout:120
    [10-08-2014 21:55:31.0640] [2] Process standard output: Attempting stop...
    Internet services successfully stopped
    Attempting start...
    Restart attempt failed.
    The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start.  The service, or dependent services, may had an error during its startup or may be disabled.
    Process standard error:
    [10-08-2014 21:55:31.0640] [2] [ERROR] Unexpected Error
    [10-08-2014 21:55:31.0640] [2] [ERROR] Process execution failed with exit code 1062.
    [10-08-2014 21:55:31.0640] [2] Ending processing Start-SetupProcess
    [10-08-2014 21:55:31.0640] [1] The following 1 error(s) occurred during task execution:
    [10-08-2014 21:55:31.0640] [1] 0.  ErrorRecord: Process execution failed with exit code 1062.
    [10-08-2014 21:55:31.0640] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1062.
    [10-08-2014 21:55:31.0640] [1] [ERROR] The following error was generated when "$error.Clear();
        Start-SetupProcess -Name "iisreset" -Args "/noforce /timeout:120"
    " was run: "Process execution failed with exit code 1062.".
    [10-08-2014 21:55:31.0640] [1] [ERROR] Process execution failed with exit code 1062.
    [10-08-2014 21:55:31.0640] [1] [ERROR-REFERENCE] Id=ClientAccessServiceControl___ef7fa14362774cd9af8882d6287b640a Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [10-08-2014 21:55:31.0640] [1] Setup is stopping now because of one or more critical errors.
    [10-08-2014 21:55:31.0640] [1] Finished executing component tasks.
    [10-08-2014 21:55:31.0672] [1] Ending processing Install-ClientAccessRole
    Anyone has any ideas?

  • Office 2013 Installer - Fails with No Errors

    Hello,
    I ran into issues on two different Windows 8 (64-bit) machines today, both with Office 2013 Pro Plus (32-bit) installed. I could not get the installer to come up to add a module (or make any other changes).
    On one of the PCs, I tried running the Fixit to remove Office, since the option of the "Online Repair" was not accessible, (installer would not start). Fixit removed Office, but after a reboot, it still would not run the office installer, even
    with Office 2013 completely gone.
    Things I tried:
    - Disabled anti-virus (windows defender)
    - Run with elevated privileges (I'm a domain admin and UAC is off, but just to be safe)
    - Removed skydrive
    - Cleaned out temp directory
    - Scanned for registry errors (none)
    - Re-downloaded the installer DVD
    - Made sure no pending windows update
    - Reboots (lots of times, definitely after the uninstall)
    - Checked the install log in %temp%, this is what I get:
    2013/08/12 13:51:14:263::[2848] PERF: TickCount=1295931 Name=OBootStrapper::Run Description=Begin function
    2013/08/12 13:51:14:264::[2848] Operating System version: 6.2.9200 . Platform ID: 2
    2013/08/12 13:51:14:264::[2848] Running 32-bit setup on a 64-bit operating system.
    2013/08/12 13:51:14:264::[2848] Command line: "F:\SETUP.EXE"
    2013/08/12 13:51:14:264::[2848] No command line arguments given
    2013/08/12 13:51:14:513::[2848] Verify file signature in "F:\SETUP.EXE"
    2013/08/12 13:51:14:562::[2848] F:\SETUP.EXE is trusted.
    2013/08/12 13:51:14:562::[2848] Verify file signature in "F:\proplus.ww\OSETUP.DLL"
    2013/08/12 13:51:14:598::[2848] F:\proplus.ww\OSETUP.DLL is trusted.
    2013/08/12 13:51:14:612::[2848] Using setup controller dll at [F:\proplus.ww\OSETUP.DLL].
    2013/08/12 13:51:14:612::[2848] PERF: TickCount=1296274 Name=OBootStrapper::Run Description=Calling RunSetup
    This is almost identical to what I see on the other PC, except with different drive letters.
    THERE ARE NO ERROR MESSAGES - no popup, no installer dialog - nothing, which makes it really hard to troubleshoot. And it's happening on both Windows 8 machines that have had Office 2013 installed. I am so frustrated right now after wasting half of today
    troubleshooting this.
    Any thoughts?

    Hi
    Let’s follow these steps: 
    Make sure you have end the tasks of setup.exe and integratedoffice.exe.      
       1. Press the Ctrl + Alt+ Delete key -> Click on Task Manager to open.      
       2. Under Processes tab -> Select setup.exe -> Click on End Process.    
        3. Under Processes tab -> Select integratedoffice.exe -> Click on End Process.  
      Restart the computer in Clean Boot and install Office 2013. Follow the steps:
           http://support.microsoft.com/kb/929135
       Note: After you have finished troubleshooting in clean boot, ensure you restart the computer in normal mode.
    In addition, you can also refer to the following link to try more methods:
    http://support.microsoft.com/kb/2822317/en-us
    Regards

  • Project Server 2010 - Update Scheduled Queue job failed with error message" Error no 131- AssignmentAlreadyExists"

    Hello,
    When I tried to update the schedule of the project , the job failed with the error message " AssignmentAlreadyExists". I further looked into the ULS logs but it wasn't that helpful.
    This is the message I found in ULS logs "type = UpdateScheduledProject failed at Message 5 and is blocking the correlation Errors: AssignmentAlreadyExists,Leaving Monitored Scope (FillTypedDataSet -- MSP_WEB_SP_QRY_ReadTimeSheetAssignmentsAndCustomFieldData).
    Execution Time=398.730006187937"
    Pplease help me to understand the root cause of this problem.
    I have verified all the assignments in the plan and I did not find any duplicates.
    Thanks in advance.
    Sesha

    This issue might need detailed troubleshooting, I would suggest you raise a support case with Microsoft.
    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
    the thread.

  • LogProviders.Add fails with "not recognized as a valid log provider type." in Data Tools but not BIDS

    In attempting to add standard DTS logging to a package via Data Tools, I found that my attempt to execute:
            Dim provider As LogProvider = p.LogProviders.Add("DTS.LogProviderTextFile.2") 
    (or any other log provider type,) resulted in:
    The log provider type "DTS.LogProviderTextFile.2, {0A039101-ACC1-4E06-943F-279948323883}" specified for log provider "{CC5CB9A4-E0D5-4ECD-8F4E-1E8FB9BDE8A6}" is not recognized as a valid log provider type. This error occurs when an
    attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name.
    I created a new package with a single script task using only the example code from the MS documentation for Embedding Logging Programmatically at:
    http://msdn.microsoft.com/en-us/library/ms136023(v=sql.110).aspx
    consisting of:
    Imports Microsoft.SqlServer.Dts.Runtime
    Module Module1
    Sub Main()
    Dim p As Package = New Package()
    Dim loggingConnection As ConnectionManager = p.Connections.Add("FILE")
    loggingConnection.ConnectionString = "C:\SSISPackageLog.txt"
    Dim provider As LogProvider = p.LogProviders.Add("DTS.LogProviderTextFile.2")
    provider.ConfigString = loggingConnection.Name
    p.LoggingOptions.SelectedLogProviders.Add(provider)
    p.LoggingOptions.EventFilterKind = DTSEventFilterKind.Inclusion
    p.LoggingOptions.EventFilter = New String() {"OnPreExecute", _
    "OnPostExecute", "OnError", "OnWarning", "OnInformation"}
    p.LoggingMode = DTSLoggingMode.Enabled
    ' Add tasks and other objects to the package.
    End Sub
    End Module
    I get the same error as listed above in SQL Server 2012 Data Tools on three separate machines.  On my primary dev box, where the code fails in Data Tools, running the exact same code in BIDS runs without problems.
    Importing the working BIDS package into Data Tools also fails with the same error.
    I have not encountered any other 2012 Data Tools issues, but logging is a core pattern that makes me worry that this is a problem that may emerge with other functions in the DTS toolset.
    Thanks for any help!!

    Arthur,
    Great idea, I verified that the Integration Services for 2012 was not installed.  I installed the new SSIS service and verified that SQL Server Integration Services 11.0 was running (previously only 10.0 was running.)
    Initially, I experienced an error message trying to run my simple script above:
    Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0,...
    I followed the steps at the MS link for Could not load file or assembly ‘Microsoft.VisualStudio.Tools.Applications.Core’
    and loaded the missing x64 runtime from edist/VSTA/runtime/x64/VSTA_RT30.msi
    on the distribution media as recomended.
    The script ran, but returned the error listed in the beginning of this message.  I then tried:
    - turning off the 10.0 service
    - setting the project's Run64BitRunTime value both false and true
    - changing the reference to Microsoft.SqlServer.ManagedDTS.dll from C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies to C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\v4.0_11.0.0.0__89845dcd8080cc91
    all of these resulted in the same failure.
    Thank you for the suggestion, I really thought it would be on target.  Alas, it wasn't the fix.
    It is so weird that all the other stuff I'm doing (a very elaborate programmatic package generator doing some tricky stuff,) works fine and only this super basic logging fails!!!!
    Thanks again,
    --Tim

  • Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

    When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
    I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.)  I also tried using the OTC, custom XML
    file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
    Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
    instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
    Thanks

    Hi,
    Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
    You try to modify registry then you wont face issue.
     The issue when you hit a "1653" is that Windows
    Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
    error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
     these are the issues I've seen:
    Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "logging"= "voicewarmup"
    kirtesh

  • CR 2010 msi (32 bit) runtime fails with error 1904, win 8.1 and many dll's not registered

    I searched the KB articles  on 1904 error, but nothing for win 8 and few for vb 2010 msi. windows platform.
    I had been using cr 2008 32-bit runtime with no problem. But now I am trying to install an application that was created in vb 2010 and I need the cr 2010 runtime.  I started to install the cr 2010 runtime 32 bit.  This is a 64 bit machine but the application was created for 32 bit and I have been using 32 bit when installing msi on other x64 platforms with no problems..  This was a test machine.  It has installed the visual C++ redistributable x86 and 64 bit , versions 2005, 2008, 2010 and 2012.  bit.  The cr 2010 32 bit runtime is the one that fails.
    During installation of the CR 2010 msi a message said that the 2008 msi had to be uninstalled which it did automatically.  But later I received the error 1904 message.  There are about 21 dll's that were listed as not registering.
    I uninstalled the cr 2008 32 bit runtime and tried again, but that did not help.
    I tried running the CR 2010 msi as administrator to no avail. 
    I tried uninstalling all other crystal -related software and updates to no avail.
    I tried disabling windows defender, to no avail.
    My OS platform is Windows 8.1

    Hi Suzanne
    Something does not sound right; The CRVS MSI should not have required an uninstall of CR 2008 runtime as these are side by side compatible...
    Re. Information on CRVS and WIN 8.1, see this KBA:
    2012075 - Installing Crystal Reports for Visual Studio 2013 SP 9 - 1904 error - Failed to register a SAP component - HRESULT -2147010895 or HRESULT: 0x80073715
    Now, irrespective of the above KBA which discusses MS VC++ dependency, the CRVS MSI contains the C++ runtime so it is quite confusing as to why the issue. Note that the MSM files do not install the C++ dependencies due to MS licensing restrictions.
    There is 10 different CRVS MSI files - one for each Service Pack. Which one are you using? Can you provide the link you used to download the MSI?
    Is this computer some special OEM edition? Surface Pro?
    Have a look at this KBA:
    1611044 - How to enable Windows Installer Logging on Crystal Reports MSI files?
    See if the logs tell you anything.
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • Mailbox migration 2010 SP3 to 2013 error

    We have a migration problem, a single 2010 server with all the roles migrating to 2013 with separate CAS and DB roles. Approx 50% of mailboxes are getting stuck and reporting "Transient error MapiExceptionNetworkError has occurred. The system will retry
    (1/60)" and "Relinquishing job because the mailbox is locked".
    I have tried restarting the services suggested in another thread (Mailbox Migration Service and Search) but it makes no difference.
    Any suggestions?
    Thanks!
    Ben

    Hi ,
    Please find the below mentioned points.
    1.Please share me the output for the below mentioned command.
    Get-MoveRequestStatistics -Identity [email protected] -IncludeReport | Export-CSV C:\MRStats.csv
    2.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.I mean the database where you are going to move the mailbox.
    3.If your exchange 2013 environment is having an single exchange server and target database copy doesn't have the second copy then we need to set the below parameter value to none for that particular database.
    DataMoveReplicationConstraint : None
    (or)
    If your exchange 2013 environment is having an multiple exchange server and target database copy is having  the second copy then we can set the below parameter value to secondcopy.
    DataMoveReplicationConstraint :Secondcopy
    Note : After anyone of the above change ,Microsoft exchange mailbox replication service needs to be restarted.
    4.Restart the Microsoft exchange mailbox replication service and check the results.
    5. Have you tried moving the same mailboxes to the different databases.
    6.Please check the mailbox size which you are trying to move to a different database.Because there might be lot of possibilities to have the target database with limited size.
    Please feel free to reply me if you have any queries.
    Thanks & Regards S.Nithyanandham

  • Installation fails with "not enough space" message ...

    Installing Application Server 8.1 on Solaris Sparc on network with lots of space but get this message in the log file of the failed installation:
    ERROR - exception while updating command line utilities
    Not enough space
    ERROR - default domain creation returned following exception: /home/lm71165/SUNWappserver/bin/asadmin: not found
    INFO - End core server configuration.
    Any ideas on why this occurs?
    Thanks.

    "Not enough space" message is issued by J2SE due to lack of swap space and not disk space per se in this case.
    To resolve this, first uninstall partial installation using provided uninstall utility (available in installation directory). Then, make sure that you free some additional swap space: delete all unnecessary content from /tmp partition and shut down all unnecessary processes running on the system. Once you do this, you can restart the installation.

  • Reports constantly fail with Not Authorized Error

    I have been using version of ARD for years now - and overall I love it. BUT-there's always a but - the reporting component has me at about the end of my last nerve. A couple of times a year I need to run diferent reports for inventory and planning purposes - and every year the reports fail over and over again with no real explanation and never any solution. All the computers on my network are running the latest version of the client and I always keep the Admin server up to date. All I can do is delete all the computers - restart - re-add them - change their report upload schedule- and repeat 10 times until they finally work. Has anyone else ever come across a solution that actually works for this.

    Well I use to some times enoucnter an issue when reporting would fail. When I did, I would select the computer records that had the error. I would then get info on those effected computer record. I would change the reporting time/day of the week to a few minutes from the current time/day of the week. I would also make sure that the IP address i'm currently at is listed as the ARD server to report to in the computer record.
    I would then wait a few minutes past the set reporting time, before trying to run a report.
    What I did to fix this issue long tearm.
    make sure the clients are set allow ARD reporitng
    set ARD computer to have a static IP. (that way when the clients try to report in, they're reporting to the right computer)
    set ARD computer to never sleep, leave ARD open. (at least for date/times a client  computer ould call in to report)
    for desktops, auto turn on/wakeup/boot on the day of the week they should report in. On the clients energy saver set so the computers wouldn't sleep for at least 30 minutes. set reporting on those client to be about 20 minutes after the computer boot/wakes/starts up.
    for laptops set reporting to happen at a time/day of the week client computer will most likely going to be on & connected to your network.
    Depending on how many computers you have you may want to spread your reportings out.

  • Firmware-upgrade failed router not accessible

    during firmware-upgrade the connection to E4200 got lost due to power-outage, now the E4200 router is not accessible, power-led flashes ...
    the factory-ip-address 192.168.1.1 responds on ping, but nothing else ...
    how to get a working environment back?

    Once reset the router. Steps to reset the router:
    Push the reset button on router for 30 seconds, turn off the router wait for 30 seconds and then power it on. After this process reconfigure the router. Power light should blink when you perform the reset process.
    Once the light gets stabilize on the router perform the following steps:
    #  Open up the browser and on the address bar type 192.168.1.1, it will prompt for the username and password. Provide the username as 'admin' and password as 'admin' or 'password'. Then it will open up the Router setup page.
    # Then click on status and check the firmware version. If its not updated then upgrade the firmware once again.
    # Then after firmware upgrade  reset the router again as explained above.
    Then uninstall the existing Cisco connect software from the computer. After uninstallation then configure the router again using Cisco Connect CD as you did earlier.

  • Issue with Update Rollup 5 for Exchange 2010 SP3 - Mailboxes that were auto mapped not working

    Below is  my response in another thread but creating a new one in the hopes that someone has the same issue and a solution besides mine below.
    Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
    Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
    What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
    Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
    the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
    I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
    This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

    Not sure why it was suggested to use the auto mapping feature to grant permissions because that is the component that is causing the issue. Also, there is nothing wrong with the auto configuration because the user can access their own mailbox just fine and
    also select mailboxes in their Outlook that were NOT auto mapped.
    With that said, here is how I fixed them all.
    Remove the permissions using the Exchange Console. Don't forget Send As
    Wait about 15 minutes. The mailbox should disappear from the users Outlook
    Open an Exchange PowerShell window and run the following command:
    .\add-mailboxpermissionsnoautomap.ps1 -Identity mailbox -User user -AccessRights FullAccess
    Have the user add the mailbox to their Outlook using the manual process.
    All is well....
    If you don't have the PS script add-mailboxpermissionsnoautomap.ps1, you can download it. I stumbled across it a few years ago and use it all the time. If you can't find it, just use the Exchange built in command for adding mailbox folder permissions but
    specify automap $false.
    The idea here is to grant the user access without auto mapping.

Maybe you are looking for