ms lync 2013 could not be installed error code 1603

Many of the error codes are used only internally.For more information, see SQL Server Profiler. Use the Microsoft SQL Server Profiler to help catch or monitor database errors.

To help find or watch for specific issues in ULS data, use the ULS Viewer.For more information about using ULS logs, see the Project Support blog article Project Server 2010: What to Expect when you get the Unexpected, and search the blog for 'reading ULS logs.'.For an explanation, see the Checking Errors section in Getting Started with Development for Project 2010.

Use the Unified Logging Service (ULS) trace logs.

Use the application event log on the Project Server computer.

For WCF-based applications, you can use to get a PSClientError object and also to get additional error information.

For ASMX-based applications, use .SoapException with the PSClientError object to show a list or hierarchy of errors in a PSI method call.

For more information about errors, you can do the following: MSI (s) (BC:50) : No System Restore sequence number for this installation.Many of the error codes are general and can have multiple possible causes. MSI (s) (BC:50) : RESTART MANAGER: Session closed. MSI (s) (BC:EC) : MainEngineThread is returning 1603 MSI (s) (BC:EC) : Deferring clean up of packages/files, if any exist Installation success or error status: 1603. Product Name: UserProfileManager SDK snap-in. MSI (s) (BC:EC) : Windows Installer installed the product. MSI (s) (BC:EC) : Product: UserProfileManager SDK snap-in - Installation failed. Return value 3.Īction ended 12:21:18: INSTALL. MSI (s) (BC:EC) : Product: UserProfileManager SDK snap-in - This setup requires PowerShell 2.0 to be installed.Īction ended 12:21:18: LaunchConditions. MSI (s) (BC:EC) : Doing action: LaunchConditionsĪction ended 12:21:18: SetInstallDIR. From the MSI logs, we could see installer is looking for powershell 2.0 to install the UserProfileManagerSDK snap-in.

Ms lync 2013 could not be installed error code 1603