Error 1603 Installing Lync 2013 client
Hello,
I am working in an Enterprise company.
All computers are Windows 7 + Office 2007 SP3.
I need to prepare a Silent installation of Lync 2013.
I created a basic config.xml file and configured a new msp file with all setting needed.
This is the command i used:
Setup.exe /adminfile lync.msp /config config.xml
Nearly at the end of the installation, it fails.
These are the critical information from the Log file:
Error: Failed to install product: C:\MSOCache\All Users\{90150000-012C-0000-0000-0000000FF1CE}-C\LyncWW.msi ErrorCode: 1603(0x643).
Error attaching to OSE, error 0x00000000
What does is means?
Full log file - here
https://onedrive.live.com/?cid=d99573b9fc48b9d4&id=D99573B9FC48B9D4%21268&Bsrc=Share&Bpub=SDX.SkyDrive&authkey=!
Thank you
Amir
Error 1603 occurs during MSI or a software installation.
Please check you can install
LyncWW.msi manually.
Make sure the install package is not interrupted.
Lisa Zheng
TechNet Community Support
Similar Messages
-
Can't open email items from search after installing Lync 2013 client
Hello,
We're deploying Lync 2013 in our environment.
At the moment we're using Office 2010 on the clients.
For testing the deployment I've installed the Lync 2013 client.
After installing, when I perform a search on my pc and outlook items are found, they suddenly appear with an Outlook 2013 icon.
When doubleclicking, nothing happens, neither when I rightclick.
I've checked the "associate a file type or protocol with a prgram", and "set your default programs" in the control panel.
In neither of them I can find the Outlook 2013 icon, and for email, every file type is configured to open with Outlook 2010.
Does anyone know what might be the problem. We have this problem with every user for which we install the Lync 2013 client.You can do the following to restore functionality:
If you have office 2010 use the keys below, the Lync install will change them to Office15:
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}]
@="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-110"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\DefaultIcon]
@="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-504"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\InprocServer32]
@="C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL"
"ThreadingModel"="Apartment"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\ShellFolder]
"Attributes"=dword:20140000 -
Get error when install Lync 2013
Hello,
I get these errors when try to steup or Remove Lync Server Components:
An error occurred while applying SQL script for the feature RtcDatabaseStore
An error occurred while applying SQL script for the feature LyssStore
Database 'lyss' exists but not accessible. It must be repaired manually or dropped and a new one created. if you want to preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
please help, thanks!
stmartYes other is up.
I install this server get the error when try to create CSDatabase:
this is the error log:
RtcDyn db state is: DbState_NotAccessible
Dyn Data Path = D:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Dyn Log Path = D:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.
Creating database rtcdyn from scratch. Data File Path = D:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Log File Path= D:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.
Setting the database rtcdyn to single user mode.
Failed to drop database. Alter failed for Database 'rtcdyn'. .
Setting the database rtcdyn to multi user mode.
Unable to open the physical file "D:\CsData\RtcDatabaseStore\rtclocal\DynDbPath\rtcdyn.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
Could not restart database "rtcdyn". Reverting to the previous status.
ALTER DATABASE statement failed.
File activation failure. The physical file name "D:\CsData\RtcDatabaseStore\rtclocal\DynLogPath\rtcdyn.ldf" may be incorrect. -
Successfully installed Lync 2013 via Click-to-Run, but getting "Choose your product" prompt
After installing Lync 2013 client using method
Click-to-Run "Deploy Office 365 ProPlus from an on-premises location",downloaded Office source is on local hard drive with the
"config.xml" shown below.
I'm getting "Choose your Product" prompt after signing-in. We have Office 365 Enterprise E3 plan and we just wanted to upgrade Lync 2010 to Lync 2013 (not the Basic).
<Configuration>
<Add SourcePath="E:\Temp" OfficeClientEdition="32" >
<Product ID="LyncRetail">
<Language ID="en-us" />
</Product>
<!-- <Product ID="VisioProRetail">
<Language ID="en-us" />
</Product> -->
</Add>
<Display Level="NONE" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="E:\Temp" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Though Lync will continue to work when you close the window. I need to deploy the full 2013 client to several
machines locally.
Thanks.Hello,
Looks like you‘ve tried a hybrid deployment with Lync 2010 and 2013, right? This might be the reason why Lync 2013 keep prompting to choose your product. Lync 2013 will automatically identify the products that it found for your account which you used to
login Lync 2013.
So, please try to remove any earlier version (Better to remove all Office 2010 suite) on your computer and try a fresh installation again. Let’s see the "Choose your product" prompt would appear again. -
Error 1603 installing microsoft sql native client
error 1603 installing microsoft sql native client
Sagar Chavanhave a look at this link
http://support.microsoft.com/kb/834484
Satheesh
My Blog |
How to ask questions in technical forum -
Installing Lync 2013 and remove 2010 client via SCCM
We have Windows 7 x64 PC’s running Lync 2010 64-Bit client.
What I need to do is install the Lync 2013 32-Bit client and then uninstall the Lync 2010 64-Bit client.
Using the Office Customization Took, I am able to install the Lync 2013 client fine, however the 2010 client isn’t not removed.
Here is what I did:
-Have the standalone Lync 2013 installer.
I then copied the Lync 2010 64-bit install files into a new folder in the Lync 2013 source files.
This folder is c:\Lync2013\Lync2010
-Created MSP file using OCT set to never reboot.
-Under ‘Add installations and run programs’ option, I specified the Lync 2010 to be removed post install of Lync 2013.
The Command line: [post install] [INSTALLLOCATION]\Lync2010\LyncSetup.exe /silent /uninstall
-Loaded this into SCCM and set to run at a logon event.
As stated above, Lync 2010 is not removed.
A few questions:
Is this even possible using the OCT?
In the OCT, is it a problem trying to mix two different installers?
One 32-Bit, the other 64-Bit?
If not, then is the command line correct for the Lync 2010 uninstall?
If no for # 3, how do I make SCCM use the correct path to the package where the Lync 2010 install files are?
In the OCT, do I need to have the Lync 2010 command line as:
\%WINDIR%\SystemWOW64\CCM\Cache\nameofpackage
Please help me alleviate some frustration with any ideas for the above.You can use the command msiexec.exe /uninstall “C:\Program Files (x86)\OCSetup\Lync.msi” to uninstall Lync 2010.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
I'll try this, thanks! For the post uninstall of Lync 2010 using the OCT, should I also ad /quiet switch or /no restart to suppress dialog boxes and not restart the PC when the removal is complete? Or will the OCT prevent it from being restarted
and 'suppress modals' as I set this during the install of Lync 2013. -
Silent Uninstall lync 2013 client
Hi,
i try to uninstall Lync 2013 Client silently but no matter what i try Lync won't uninstall.
maybe someone can explain me what i'm doing wrong
I tried the recommended command
copy "%~DP0uninstall_lync.xml" "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup
Controller\uninstall_lync.xml"
"%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
Config File
<Configuration Product="LYNCENTRY">
<Display Level="None" AcceptEULA="TRUE" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<Logging Type="standard" Path="c:\windows\log\" Template="Microsoft Office Lync Uninstall(*).log" />
</Configuration>
Log:
2014/11/24 14:49:11:039::[4844] PERF: TickCount=11665520 Name=OBootStrapper::Run Description=Begin function
2014/11/24 14:49:11:040::[4844] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
2014/11/24 14:49:11:040::[4844] Running 32-bit setup on a 64-bit operating system.
2014/11/24 14:49:11:040::[4844] Command line: "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
2014/11/24 14:49:11:040::[4844] Parsing command line.
2014/11/24 14:49:11:040::[4844] Config XML file specified: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
2014/11/24 14:49:11:040::[4844] Uninstall requested for product: LYNCENTRY
2014/11/24 14:49:11:040::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
2014/11/24 14:49:11:060::[4844] Preferred product specified in config.xml to be: LYNCENTRY
2014/11/24 14:49:11:060::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
2014/11/24 14:49:11:060::[4844] Logging type standard specified in config.xml.
2014/11/24 14:49:11:060::[4844] Log directory: c:\windows\log\ specified in config.xml
2014/11/24 14:49:11:060::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
2014/11/24 14:49:11:060::[4844] Display level none specified in config.xml.
2014/11/24 14:49:11:075::[4844] Using setup controller dll at location [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
2014/11/24 14:49:11:075::[4844] Verify file signature in "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe"
2014/11/24 14:49:11:129::[4844] C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe is trusted.
2014/11/24 14:49:11:129::[4844] Verify file signature in "C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL"
2014/11/24 14:49:11:198::[4844] C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL is trusted.
2014/11/24 14:49:11:296::[4844] Using setup controller dll at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
2014/11/24 14:49:11:296::[4844] PERF: TickCount=11665785 Name=OBootStrapper::Run Description=Calling RunSetup
2014/11/24 14:49:11:302::[4844] PERF: TickCount=11665785 Name=RunSetup Description=Begin function
2014/11/24 14:49:11:303::[4844] WER element [P2] is set to value [OSETUP.DLL]
2014/11/24 14:49:11:303::[4844] WER element [P3] is set to value [15.0.4569.1503]
2014/11/24 14:49:11:304::[4844] Catalyst execution began: 11/24/2014 14:49:11.
2014/11/24 14:49:11:305::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
2014/11/24 14:49:11:307::[4844] Preferred product specified in config.xml to be: LYNCENTRY
2014/11/24 14:49:11:307::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
2014/11/24 14:49:11:307::[4844] Logging type standard specified in config.xml.
2014/11/24 14:49:11:307::[4844] Log directory: c:\windows\log\ specified in config.xml
2014/11/24 14:49:11:307::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
2014/11/24 14:49:11:307::[4844] Display level none specified in config.xml.
2014/11/24 14:49:11:308::[4844] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [enabled] for the [UninstallExecutionMode]
2014/11/24 14:49:11:308::[4844] Ensuring the install-state of setup controller files for product [LYNCENTRY].
2014/11/24 14:49:11:308::[4844] Warning: Product registation information for 'LYNCENTRY' not detected. ErrorCode: 1011(0x3f3). Failed attempt to force-repair setupexe boot files.
2014/11/24 14:49:11:308::[4844] Searching for default versions of resource files under the folder [C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller].
2014/11/24 14:49:11:328::[4844] Found [1] resource files under the default folder.
2014/11/24 14:49:11:328::[4844] Running in [UninstallExecutionMode]. Run from TEMP folder at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214].
2014/11/24 14:49:11:345::[4844] Loaded resource file [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUPUI.DLL] (CultureTag=de-DE).
2014/11/24 14:49:11:345::[4844] WER element [SuppressModal] is set to value [false]
2014/11/24 14:49:11:346::[4844] WER element [P1] is set to value [15.0.4569.1503]
2014/11/24 14:49:11:346::[4844] Loaded Dll : C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL.
2014/11/24 14:49:11:346::[4844] Catalyst version is : 15.0.4569.1503
2014/11/24 14:49:11:346::[4844] JobExecutionMode is UninstallExecutionMode.
2014/11/24 14:49:11:547::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
2014/11/24 14:49:11:547::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
2014/11/24 14:49:11:548::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
2014/11/24 14:49:11:548::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
2014/11/24 14:49:11:548::[4844] Ensuring the install-state of setup controller files for all Products.
2014/11/24 14:49:11:548::[4844] Opening registry key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller files for product [LYNC].
2014/11/24 14:49:11:549::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
2014/11/24 14:49:11:549::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0407-1000-0000000FF1CE}].
2014/11/24 14:49:11:549::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0407-1000-0000000FF1CE}' is '5'.
2014/11/24 14:49:11:549::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:13:038::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0000-1000-0000000FF1CE}].
2014/11/24 14:49:13:038::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0000-1000-0000000FF1CE}' is '5'.
2014/11/24 14:49:13:038::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:15:639::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-006E-0407-0000-0000000FF1CE}].
2014/11/24 14:49:15:639::[4844] Product INSTALLSTATE for ProductCode '{90150000-006E-0407-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:15:639::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:18:424::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0410-0000-0000000FF1CE}].
2014/11/24 14:49:18:424::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0410-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:18:424::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:20:222::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0407-0000-0000000FF1CE}].
2014/11/24 14:49:20:222::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0407-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:20:222::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:21:766::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-040C-0000-0000000FF1CE}].
2014/11/24 14:49:21:767::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-040C-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:21:767::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:23:339::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0409-0000-0000000FF1CE}].
2014/11/24 14:49:23:339::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0409-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:23:340::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:25:046::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002C-0407-0000-0000000FF1CE}].
2014/11/24 14:49:25:047::[4844] Product INSTALLSTATE for ProductCode '{90150000-002C-0407-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:25:048::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:26:619::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012B-0407-0000-0000000FF1CE}].
2014/11/24 14:49:26:620::[4844] Product INSTALLSTATE for ProductCode '{90150000-012B-0407-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:26:620::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:28:951::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012C-0000-0000-0000000FF1CE}].
2014/11/24 14:49:28:951::[4844] Product INSTALLSTATE for ProductCode '{90150000-012C-0000-0000-0000000FF1CE}' is '5'.
2014/11/24 14:49:28:952::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
2014/11/24 14:49:36:136::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
2014/11/24 14:49:36:136::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
2014/11/24 14:49:36:136::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
2014/11/24 14:49:36:136::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
2014/11/24 14:49:36:136::[4844] Not showing message because suppress modal has been set. Title: 'Setupfehler', Message: 'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
2014/11/24 14:49:36:136::[4844] Message returned: 1
2014/11/24 14:49:36:141::[4844] Error: Catalyst boot time check failed Type: 66::PreReqCheckFailure.
2014/11/24 14:49:36:141::[4844] Catalyst execution finished: 11/24/2014 14:49:36. Return code: 30066. Exception caught: PreReqCheckFailure.
2014/11/24 14:49:36:141::[4844] PERF: TickCount=11690621 Name=RunSetup Description=End function
My next attempt was to look for MSI Files in Windows\Installer and the Uninstall RegKey
MsiExec.exe /X{90150000-012C-0000-0000-0000000FF1CE} /qn /norestart /L*v
"c:\windows\log\Microsoft_Lync_2013_Update_KB2817626_x86_0185_Install.LOG"
MSI (s) (10:4C) [15:10:52:612]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (10:4C) [15:10:52:628]: SRSetRestorePoint skipped for this transaction.
MSI (s) (10:4C) [15:10:52:631]: End dialog not enabled
MSI (s) (10:4C) [15:10:52:631]: Original package ==> C:\Windows\Installer\bfb379.msi
MSI (s) (10:4C) [15:10:52:631]: Package we're running from ==> C:\Windows\Installer\bfb379.msi
MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90150000-012C-0000-0000-0000000FF1CE}'.
MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (10:4C) [15:10:52:649]: Opening existing patch 'C:\Windows\Installer\bfb3d2.msp'.
MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb37a.msp'.
MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb386.msp'.
MSI (s) (10:4C) [15:10:52:651]: SequencePatches starts. Product code: {90150000-012C-0000-0000-0000000FF1CE}, Product version: 15.0.4569.1506, Upgrade code: {00150000-012C-0000-0000-0000000FF1CE}, Product language 0
MSI (s) (10:4C) [15:10:52:652]: Note: 1: 2205 2: 3: MsiPatchMetadata
MSI (s) (10:4C) [15:10:52:652]: SequencePatches returns success.
MSI (s) (10:4C) [15:10:52:652]: Final Patch Application Order:
MSI (s) (10:4C) [15:10:52:652]: {27D7A8D0-8E28-4A2A-A1D4-473E31DF6438} -
MSI (s) (10:4C) [15:10:52:652]: {73E81413-5A7E-40A3-9BD5-821ADDF30B10} -
MSI (s) (10:4C) [15:10:52:652]: {D448DFE1-B83E-4394-9484-25563EFBF58D} -
MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisablePatch' is 0
MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (10:4C) [15:10:52:653]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4569.1506
DEBUG: Error 2746: Transform 90006E0401000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:653]: Skipping validation for patch transform #90006E0401000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4420.1017
1: 2746 2: 90006E0401000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0401000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0401000015.0.4420.1017. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4481.1005
1: 2746 2: 90006E0401000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0402000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0402000015.0.4481.1005. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4569.1506
1: 2746 2: 90006E0402000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0402000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4505.1008
1: 2746 2: 90006E0402000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0402000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4505.1008. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4454.1509
1: 2746 2: 90006E0402000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0402000015.0.4454.1509 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4454.1509. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0405000015.0.4481.1005
1: 2746 2: 90006E0402000015.0.4454.1509 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0405000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4481.1005. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4569.1506
1: 2746 2: 90006E0405000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0405000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4505.1008
1: 2746 2: 90006E0405000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0405000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4505.1008. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4454.1004
1: 2746 2: 90006E0405000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0405000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0405000015.0.4454.1004. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4481.1005
1: 2746 2: 90006E0405000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0406000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4481.1005. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4569.1506
1: 2746 2: 90006E0406000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0406000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4433.1507
1: 2746 2: 90006E0406000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0406000015.0.4433.1507 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4433.1507. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0406000015.0.4505.1008
1: 2746 2: 90006E0406000015.0.4433.1507 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0406000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4505.1008. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4569.1506
1: 2746 2: 90006E0406000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0407000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0407000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4420.1017
1: 2746 2: 90006E0407000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0407000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0407000015.0.4420.1017. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4481.1005
1: 2746 2: 90006E0407000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0408000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0408000015.0.4481.1005. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4569.1506
1: 2746 2: 90006E0408000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0408000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4505.1008
1: 2746 2: 90006E0408000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0408000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4505.1008. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4454.1004
1: 2746 2: 90006E0408000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0408000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4454.1004. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0409000015.0.4569.1506
1: 2746 2: 90006E0408000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0409000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4569.1506. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0409000015.0.4420.1017
1: 2746 2: 90006E0409000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0409000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4420.1017. Will not apply because previous transform was invalid
MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0C0A000015.0.4569.1506
1: 2746 2: 90006E0409000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
DEBUG: Error 2746: Transform 90006E0C0A000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0C0A-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000
MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
MSI (s) (10:20) [15:16:59:076]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (10:20) [15:16:59:076]: Produkt: Microsoft Lync 2013 -- Das Entfernen ist fehlgeschlagen.
MSI (s) (10:20) [15:16:59:077]: Das Produkt wurde durch Windows Installer entfernt. Produktname: Microsoft Lync 2013. Produktversion: 15.0.4569.1506. Produktsprache: 0. Hersteller: Microsoft Corporation. Erfolg- bzw. Fehlerstatus der Deinstallation: 1603.
MSI (s) (10:20) [15:16:59:079]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
MSI (s) (10:20) [15:16:59:085]: Deferring clean up of packages/files, if any exist
MSI (s) (10:20) [15:16:59:085]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
MSI (s) (10:20) [15:16:59:085]: Unable to delete the file outside of the engine. LastError = 2
MSI (s) (10:20) [15:16:59:085]: MainEngineThread is returning 1603
MSI (s) (10:4C) [15:16:59:089]: RESTART MANAGER: Session closed.
MSI (s) (10:4C) [15:16:59:089]: No System Restore sequence number for this installation.
=== Protokollierung beendet: 24.11.2014 15:16:59 ===
MSI (s) (10:4C) [15:16:59:090]: User policy value 'DisableRollback' is 0
MSI (s) (10:4C) [15:16:59:090]: Machine policy value 'DisableRollback' is 0
MSI (s) (10:4C) [15:16:59:090]: Incrementing counter to disable shutdown. Counter after increment: 02014/11/24
14:49:36:136::[4844]
Error: Product
is not installed, therefore transition to
MMode is unsafe
for product: LYNCENTRY
Type: 27::InstalledProductStateCorrupt.
2014/11/24
14:49:36:136::[4844]
Not showing message because suppress modal has been
set. Title:
'Setupfehler', Message:
'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
From the snippet of the log, it appears that the product installation has been corrupted. Probably, try to repair it from Control Panel first and then test the command again?
Also, is it Microsoft Lync Basic 2013?
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. -
We have in our enterprise the following scenario:
1 - Lync 2013 client is installed
2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
on the browser, using Lync Web Plug-in?Thanks for the response,
First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue. -
Cant install Lync 2013 eval on vista
I wast to install Lync 2013 eval version on my vista but it gives error that it can be installed on windows 7 or later, why this descripency? is there a patch for vista?
Hi,
You can change to use Lync client 2010 on Windows Vista. Lync client 2010 supported OS:
Windows 7, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2, Windows XP Service Pack 3.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support -
Unable to search GAL on Lync 2013 Front End Pool through Lync 2013 client
I'm in the beginning of a 2010 to 2013 migration and I'm currently testing co-existence functionality between pools. I've noticed that users cannot search the GAL from their Lync client after being moved to the 2013 pool.
When trying to access the internal URL https://fepool13.domain.com/abs/handler the user is prompted to login and after three failed attempts, receives "401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission
to view this directory or page using the credentials that you supplied".
Searching withing a Lync 2010 or Lync 2013 client returns no results, but there are no errors as well as nothing in the event logs or tracing folder regarding not being able to search.
The 2010 pool has been in production for a few years now and when accessing its internal ABS URL https://fepool10.domain.com/abs/handler the user is granted access after a successful login.
In the IIS logs there are slightly more detailed 401 error codes, but I’m not sure what to make of them.
The rtcab database appears to have user information and all three front end servers appear to be syncing with active directory. I say the rtcab database appears to have user info because the AbUserEntry table is filled with User ID'd, GUID's and a
bunch of other stuff.
The authentication on 2013 front end servers “internal lync website/abs/handler” is set to 1. Negotiate, 2. Ntlm - which is the same as the 2010 front end servers.
Any ideas?Hi,
Which step did you do among migration from Lync Server 2010 to Lync Server 2013?
Did you already move CMS from Lync Server 2010 to Lync Server 2013?
Please create a new Lync account on Lync Server 2013 pool and test the issue again.
Please check if User Replication has completed with the help of the link below:
http://technet.microsoft.com/en-us/library/jj204680.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support -
I have installed 2010 Microsoft office 2010 home and business version for my laptop,and I have installed lync 2013.Now i want create online lync meeting from outlook,but i am unable view that lync icon in outlook.Please give me the solution for this issue.
Regards
RaghavendarHi Raghavendar,
Generally, when you install Lync 2013 in the computer with Office 2010, a Lync Meeting Add-in will be installed and enabled in Outlook 2010. Please follow these steps to check it:
1. In Outlook, click the File tab, click Options, and then click
Add-Ins.
2. Please take one of the following actions:
If the add-in is in the Inactive Application Add-ins list, follow these steps:
a. In the Manage drop-down list at the bottom of the dialog box, click
COM Add-ins, and then click Go.
b. Click to select the check box next to the add-in, and then click OK.
The New Online Meeting button should now be available in
Calendar View, and the Online Meeting button should be available when you create a new calendar item.
If the add-in is in the Disabled Application add-ins list, follow these steps:
a. In the Manage drop-down list at the bottom of the dialog box, click
Disabled Items, and then click Go.
b. Select the add-in, and then click Enable.
c. Restart Outlook, and then verify that the add-in is displayed in the
Add-ins dialog box.
The New Online Meeting button should now be available in
Calendar View, and the Online Meeting button should now be available when you create a new calendar item.
3. In Event Viewer, view the Application log to see whether an error was logged for Outlook, for Lync 2013, the Lync Meeting Add-in for Microsoft Office 2013.
Thanks,
Winnie Liang
TechNet Community Support -
App V 5.0 Sequence - Lync 2013 Client
Hello,
Could you please help me find sequencing steps to virtualize Lync 2013 Client (Basic/Enterprise) using App-V 5.0 SP2?
Regards,
Srinivasa PrasadFollow that link for advice on how to download Office click-to-run and convert it to an App-V package...
When I did this, I set the Product ID in the CustomConfig.xml file as ProPlusVolume and used ExcludeApp tags to exclude all apps except for Lync:
Access
Excel
Groove
InfoPath
OneNote
Outlook
PowerPoint
Project
Publisher
SharePointDesigner
Visio
Word
Here is the info on how to configure this file:
http://technet.microsoft.com/library/jj219426(v=office.15).aspx
I believe it is also possible to set the Product ID to Lync, but not sure of the exact value to set and I have not tried this myself. Bonus tip - when you deploy Lync 2013 virtually, the plugins automatically integrate with the locally installed copy of
Outlook!
Dan Gough
UK App-V MVP
packageology.com
@packageologist
LinkedIn -
Hello All,
Facing very much weird issue for only 4 users in my organization. This 4 users are migrated to Lync 2013 pool from Lync 2010 pool with Lync 2010 client migrated to Lync 2013 client.
Now whenever this users are typing in (apps like word, excel) automatically pops up Lync 2013 client which is annoying.
All my users are Windows 7 with latest updates & updates Lync 2013 with latest updates installed.
Any help really appreciated.
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTSHi
The solution is to do a ‘repair’ install of Office 2013. This will reregister the needed components and the popups will stop.
A repair install can be done from ‘Programs and Features’, highlight Office 2013 and click ‘Change’. When the install wizard appears, choose the ‘repair’ option.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP) -
No audio device detected - Lync 2013 Client
I have a brand new Dell Latitude E6430 laptop running Windows 7 x64 SP1. I installed Office 2013, including the Lync 2013 client. We are running Lync 2013 server as well. I have connected three different audio devices.
Polycom CX600 phone.
Plantronics Bluetooth headset.
Logitech Video Camera (The video on this works with Lync but no audio)
I cannot get Lync to recognize either of them. I can see them as devices in Windows but within Lync I only get a screen that says "We didn't find an audio device, which you need for calling". Does anyone have any idea on how to resolve this issue?
It is driving me crazy. Especially since it worked perfectly on my old laptop that had the same OS and patches, etc...
Thanks for your help in advance.
JamieHad the same issue. For me it required uninstalling the Intel Widi device from device manager. I think it was titled "wiusb" or something similar. It was in its own group in device manager. After uninstalling that, Lync would then
recognize my mic/speakers again.
I had the exact same problem as everyone else. I purchased two Dell Latitude E6530 laptops with Windows 7 Pro 64-bit. Both laptops had the issue. I uninstalled the WIUSB devices, restarted Lync, and Lync suddenly is able to detect devices...
I refreshed device manager to see if the devices would auto-install again... but there weren't detected again.
William Christenson
This worked for me as well. Uninstalled the WIUSB and WIUSB Host Controller which was present under its own group, Exit Lync process and started again, it detected the Sound Devices again. Definitely a driver conflict but it was quick resolution to uninstall
and get it working. No other issues with user as far as another device stopped working due to uninstallation of the devices.
It does not look like any driver conflicts, all other software detects audio device perfectly (Skype, Recorder,softphone, Lync 2010 etc.), but only Lync 2013 client keeps saying ""we didn't find an audio device". it appears the faulty in Lync 2013 client -
No coexistence, Totally decom Lync 2010, then install Lync 2013
I have went through decomming Lync 2010 Enterprise on prem with the desire to go to Lync 2013 Hosted Multi-Tenancy, using the same domain.
So, as you can imagine doing this in a test env. (mirroring the prod env.) I have uninstalled Lync 2010, followed all best practices, made sure ADSI ref. were gone to Lync 2010 (to my knowledge).
Now that I have uninstalled the last Lync 2010 boxes, Installed Lync 2013 on the first frontend server, fired up the setup and went through the topology builder wizards, and after filling out Edge server pools, etc, I have a topology showing Lync 2010 and
2013. Is that correct? This is my first time installing 2013 Lync. Is Lync 2010 supposed to be showing in the topology?
Maybe this is normal for 2013, maybe this doesnt matter for me to continue. I'd just like to cleanly get rid of any 2013 references or leftovers.
JoshHi,
Agree with Anthony and Rodolfo.
Here is Lync server 2013 topology (I didn't deploy Lync server 2010):
What's more, please check if you remove all Lync server 2010 information from AD.
If you meet error about remanent Lync information in AD, you can refer to the link of "Remove Lync from Active Directory":
http://blog.armgasys.com/?p=320
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support
Maybe you are looking for
-
I recently was given someone else's ipod touch. It has some songs I would like to keep, but most I would like to delete without losing the one's I like. Is there anyway to either upload songs to itunes in my mac or sync a playlist with the ipod wit
-
hi every one, my requirement is If the transfer order is confirmed - i.e. VBUK-LVSTK (Overall WM status) is C, HU determination should be done using FM - HU_GET_HUS by passing delivery number in IS_OBJECTS. HU can be picked from table ET
-
Acrobat 7-how to keep author name in Note Tool permanently blank?
One of my main uses for Acrobat is to review academic documents, which is meant to be done anonomously. When I use Tools>Commenting>NoteTool, my login name appears in the Note Tool box, even though I have deselected "Always use Log-in name for author
-
Oracle AQ with Orion 2.0 application server
Hi, I'm trying to use Oracle AQ/JMS as queue for a J2EE message driven bean running in an Orion 2.0 application server. To connect the bean with the queue I have to configure a resource provider. By now, the only resource provider I found is the clas
-
Is there a "Task Manager" for HyperV Guests?
I have read articles such as http://msdn.microsoft.com/en-us/library/cc768535(v=bts.10).aspx that indicate which performance counters to watch in the Guest. An article is fine but the day-to-day network Admin needs better than that. They need a tool