No Numbers after March Lync 2013 Client update

Hi,
We have problems with the EWS sync after applying the March Lync 2013 client update. All contacts are synced from the users private contacts folder but no numbers are shown. After removing the update it is working fine again. We are not using UCS as
we are still on Exchange 2010.
Any ideas?
Kristian

I didn’t have this problem when I installed the update.
Did you download the update from
http://www.microsoft.com/en-us/download/details.aspx?id=42232 or
http://www.microsoft.com/en-us/download/details.aspx?id=42249?
Please check if this issue happens to other users.
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

Question about adding Distribution Groups to Lync 2013 clients

Hello Everybody,
Hopefully somebody can assist me with this issue. I created a Universal Distribution Group within our domain which consists of about 75 people. I logged onto the lync server and ran Update-CsAddressBook waited for it to complete and then
followed Terence Luk guide to force the lync 2013 client update http://terenceluk.blogspot.com/2013/02/forcing-lync-2013-client-to-download.html However
even after the update has completed I am unable to locate this group in the lync client any suggestions would be greatly appreciated.

Hi,
Please type the complete sip address to search it.
If the issue persists, please remove lync profile and sign in again.
Kent Huang
TechNet Community Support

Dial-In Conferencing page does not open from Lync 2013 client

Hello Everyone,
I am facing this strange issue with my Lync Clients. All the users started experiencing the same behavior. So, I think this has something to do at the Server side.
Earlier, when trying to open the Dial-in conferencing settings from the Lync Client (Tools --> Dial-in conferencing settings), it would automatically open the Dial-In conferencing settings in a new web page. But, recently this is not happening. The strange
thing is I will be able to open the dial-in conferencing settings manually from a web browser by typing in the URL.
Has anyone experienced similar issues in the past? I would appreciate any ideas regarding this from your part so that I can try to resolve this. Thanks in advance.

Hi,
Try to rerun Step 2-Setup or Remove Lync Server Components and then test again.
Check if Lync Address Book update to the latest status.
Make sure all Lync 2013 client update to the version.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Client Not Display Numbers in Contact Card

Hi
I have a problem where Lync 2013 client connecting to Lync 2010 backend appears not download the contact list completely. Lync 2010 clients are all operating normally. On Lync 2010 client, you can view all contact details including Enterprise Voice
numbers and cell numbers for all users. However on Lync 2013 clients, Lync contact details for some users do not populate completely. In most cases, Enterprise numbers/Work Numbers/Mobile Numbers are missing. If the contact is pinned then the details
are retrieved.
In cases where Work/Voice/Cell numbers are not displayed, affected users is limited to making lync to lync calls only. The user can still dial the number and get through without any issues.
I have deleted and contacts cache on Lync 2013 but this has not helped.
Regards

Hi,
How about check the contact of “Outlook Test” user from the Lync 2010 client?
According to the second screenshot, since it’s an external account, the information will be limited.
Thanks,
Simon Wu
TechNet Community Support

Lync 2013 Client pops up automatically while typing in Word , Excel in Windows 7 after upgrade from Lync 2010 client

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+MCTS

Hi
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)

Auto logout or disconnect of Lync 2013 client after inactivity

Is there any way to configure the Registry or perhaps a GPO so that Lync 2013 clients running on Windows 7 will auto logout or disconnect from the server if they have been inactive after a certain amount of time? Searched around and could not find anything.
I found the link below but it uses Preferences which have undesirable side affects.
http://unifiedme.co.uk/2014/01/lync-2013-group-policy-enforce-ringtones-centrally/

Hi,
There is no method naturally to auto logout of Lync 2013 after inactivity. You may need to configure auto-logoff Windows after idle time to log off the Lync can check
the thread below to configure auto-logoff Windows:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/2d618fdb-faf7-41a1-9207-ff07b8d29091/how-to-automatically-log-off-idle-users?forum=winserversecurity#c7c21990-73b4-41ac-a9b5-4d571372ec10
Or you may need to custom your own Lync client, you can post the question on MSDN Lync SDK forum. Thank you for your understanding.
Here is the link to MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/communicatorsdk/threads
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
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

Lync 2013 Clients prompting repeatedly for credentials for calendar data from outlook

Our Exchange server had crashed recently (nothing major) and a reboot of the CAS server resolved the issues. However since then all our domain computers with Lync 2013 clients are prompting for credentials for calendar data from outlook. We would but in
our domain credentials but it still asks. It would sometime ask once a day or sometimes repeatedly throughout the day.
I have look on the forums and tried fixes that included: editing IIS Autodiscover and ESW to use NTLM first , rebuilt lyncs cache in app data etc and none seems to resolve the issue. Any help would be appreciated.
Note: Our Lync 2013 environment is internal only. Only users on domain computers can access the service. We do use a proxy server here for internet but I do not believe Lync is going through the proxy since its internal to our network only. This is NOT happing
to our users with the Lync 2010 client.

Please update your Lync client with the latest version.
You can check the following KB:
http://support.microsoft.com/kb/2825630/en-us
November 7, 2013 update for Lync 2013 fix the issue Proxy authentication dialog box appears when you sign in to Lync 2013.
Lisa Zheng
TechNet Community Support

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: 0

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.'
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.

Schedule a meeting via Lync 2013 client

Hi All,
quick run down of my set up,
Exchange 2013 SP1 (no UM) and new installation of Lync 2013 FE with Feb 2015 cumulative updates (no Ent voice )
haven't integrated Exchange with Lync.
my problem is when i try to schedule a meeting with a colleague via Lync 2013 client it says "no free/busy information could be retrieved and if i let it stay open for 5 min it will come up or unless I unselect and reselect the user the information
comes up.
any idea what's causing thus and how to fix it?
Thanks in advance

Not sure of a fix, but Michael LaMontange posted a workaround for it:
http://realtimeuc.com/2013/04/no-free-busy-when-scheduling-meeting-from-lync/
Some other thoughts here:
http://www.doitfixit.com/index.php?option=com_content&view=article&id=82:no-freebusy-information&catid=34:exchange-2010&Itemid=53
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 client - Set people to "Blocked Contacts" relationship by default?

We are in the process of implementing Lync Server 2013 (on-premises). We have already implemented one front end pool and one edge pool and successfully tested the basic functionality. Now we are moving on to configuring the various policies based
on our requirements. One requirement that has come late in the planning is to prevent people from receiving IMs unless they explicitly allow people to IM them and to have the ability to whitelist IMs from people on an individual basis. This is a feature
that was submitted as a requirement by way of our IT HelpDesk manager.
From what I gather, this could be accomplished if someone had the ability to set the default to the "Blocked Contacts" relationship for everyone instead of "Colleagues". In my research on how to set that as the default, I found
a setting "ShowManagePrivacyRelationship" in Set-CsClientPolicy. I created a new per-user client policy called "TEST" and applied it to myself. Then I set ShowManagePrivacyRelationShip to $true via PowerShell on the TEST policy.
However, even hours after making the change and signing out and back into the Lync 2013 client, I still don't see any change in functionality or new options.
Now, if I instead sign in with the Lync 2010 client, I can indeed see a "Manage Privacy Relationships" option in a drop-down near the right side of the client which takes me to a view where I can see and move "People in my company" and
"People in domains connected to my company" pseudo-contacts from the "Colleagues" relationship to "Blocked Contacts" and this accomplishes exactly what we want to do.
Where can I find the "Manage Privacy Relationship" setting in Lync 2013 client? If there is no setting called that, how can I accomplish what I am trying to do using Lync 2013?
I would rather not use the Lync 2010 client, as our HelpDesk technicians all use Windows 8.1 and Office 2013.

David:
Yes, I have all of those relationships categories in Lync 2013. What I am missing is the ability to set the rest of the organization to
Blocked Contacts by default. I can do this with the Lync 2010 client using the same user login and the same Lync Server 2013 environment.
The following image demonstrates the location of the Manage Privacy Relationships option I would like to leverage in Lync 2013. The image is of the Lync 2010 client.
https://www.dropbox.com/s/i0g83i9su9e5zox/Manage_Privacy_Relationships.png
If I click that Manage Privacy Relationships option, I end up on the following screen. Note that there is a
People in my company object under Colleagues.
https://www.dropbox.com/s/kkatgtoexea7evt/Default_Privacy_Relationships.png
I am able to move that People in my company object to another relationship option. I moved it to
Blocked Contacts, as you can see below.
https://www.dropbox.com/s/956kw0ih15uksgr/People_In_Company_Blocked.png
As you can see in the following image, after making this change if I do not have a person on my Contacts list, they are unable to IM me. As you can see in my Lync 2013 client relationships list, no one is in my
Blocked Contacts list yet the Lync Test Account is being blocked due to the fact that I put People in my company there and haven't added them to my Contacts list.
https://www.dropbox.com/s/cue09wjj8tidbau/Blocked.png
After adding the Lync Test Account to my Contacts list, the Lync Test Account is able to IM me.
https://www.dropbox.com/s/nalju5ia980lc30/Unblocked.png
I hope these images help make clear that there seems to be a capability present in the Lync 2010 client that I am unable to locate in the Lync 2013 client. I can't find this
Manage Private Relationships option anywhere in the Lync 2013 client or any other option that lets me see those People in my company and People in domains connected with my company objects.
With regards to the EnablePrivacyMode option, I am already aware of it and that is not what we are looking for.

Lync 2013 Client crashes

Eventlog message:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xc0000017
Fault offset: 0x0000c41f
Faulting process id: 0x2918
Faulting application start time: 0x01cecb1ab5a8cccf
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5806ca39-372c-11e3-af61-002618927526
We are having this on a few lync clients. The crashes are at random, a few times per day. Generally happens when the client is idle. Windows 7 systems, with the latest version of the client. (15.0.4517.1504)Any ideas?

Hi Everett.Chris,
Did you solve the issue with the suggestion Waqas105 provided?
Did you install Bluetooth on your computer? If yes, please remove it and test the issue again.
Please also make sure you remove all instances of the Lync 2013 Security Update KB2817465.
If the issue persists, please past the entire log or message when Lync client crashes so that we know which file cause the issue.
Best Regards,
Eason Huang
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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.
Jamie

Had 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

Lync 2013 Clients in Child Domain Log "The server returned HTTP status code '403 (0x193)' with text 'Forbidden'."

Hey All, I am really stumped on this one.
Environment - Is using split DNS
Forest Root Domain - Contains new Lync 2013 Server Standard, ADDS, DNS, Enterprise CA, Workstations
Clients in this domain connect and work beautifully. No errors.
Child Domain - ADDS, DNS, Workstation, Lync 2013 client
Client autodiscovers, and then asks for a password. Enter the password and this comes up...
Can't sign in to Lync, You didnt get signed in, It might be your sign-in address or logon credentials.. blah blah blah"
Client log shows
Error:
There was an error communicating with the endpoint at 'https://domainlync13srv.Domain.net/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '403 (0x193)' with text 'Forbidden'.
The server understood the request, but cannot fulfill it.
As far as i can tell certificates are correctly configured with all the SAN's possible in my forest. The user is correctly set up in Lync control panel. Autodiscovery seems to be working as it should. EWS is working correctly.
Repaired client, removed cached creds, has all lync 2013 updates no dice
Thank you all!

I am an IDIOT.
I did not prepare the child domain with the LYNC setup tool. Logged on to a file server in the child domain with domain admin rights and sure enough the setup said the domain was "partial". Ran the setup and bam it all started working.

No Numbers after March Lync 2013 Client update

Similar Messages

Maybe you are looking for