Lync 2013 services restart every 24hours
Hi,
I am having real issues with a Lync 2013 deployment that every day, at 17:03, restarts all its services.
The services stop fine, and all start fine within a minute or two. But it obviously cuts all calls off that are taking place and doesn't allow for immediate call back until the FE service starts. A minute or so before the restart, the only warning in
event viewer is 51029 - The MCUFactory failed to connect to Fabric Pool Manager.
The Master replicator agent is the first service to appear in event viewer as stopping. Anyone faced this issue before? Doesn't correspond to anything in scheduled tasks.
Cheers
Alistair Cameron
Hi,
Please try to restart Lync Server and start the service again. If the issue persists, please make sure you have installed the latest update.
Best regards,
Eric
Similar Messages
-
Call Manager Cisco SOAP - CDRonDemand Service restarts every 8-10 minutes
Hello there,
I just upgraded a customer to 10.5.1.10000-7 of call manager. Now the Call Manager Cisco SOAP - CDRonDemand Service restarts every 8-10 minutes.
I tried:
-rebooting the cluster (pub and sub)
-restarting the CDR and Soap related servers
-turning off CDR under service parameters and restarting services.
Any other thoughts? all replication reports look good
thanksHi,
you have probably only two options. Let a TAC person look into it if you really want to know whats wrong.
The other option would be to deactivate "Cisco SOAP - CDRonDemand Service" since no appplication is using CDR on demand. That service is only used when an application is pulling CDR records derectly out of the database which seems not be the case.
Eike -
Timer Services restart every minute
Hi,
I have a SharePoint 2010 Standard Server with SP1. I find that the Timer Services start and stop every minute. The below log appears every time the timer service restart. Would anyone help to solve this? Thanks.
The timer service is starting
06/18/2014 16:07:34.23 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Topology 2myf Medium Disabling the configuration filesystem and memory caches.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Waiting for mutex to initialize type dictionary
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Obtained mutex
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering assemlies and sequences
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence2] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence2] for [Microsoft.SharePoint.SPSite], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsServiceApplicationSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsServiceApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsDatabaseSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsDatabase], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageApplicationSequence] for [Microsoft.SharePoint.Administration.SPUsageApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageDatabaseSequence] for [Microsoft.SharePoint.Administration.SPUsageDatabase], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServerSequence] for [Microsoft.SharePoint.Administration.SPWebServiceInstance], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServiceSequence] for [Microsoft.SharePoint.Administration.SPWebService], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequence] for [Microsoft.SharePoint.SPWebTemplate], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence2] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Reading xml configuration files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade
06/18/2014 16:07:34.26 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\dlcupgradeb2b.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelMobileViewerUpgradeConfig.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelServicesUpgradeConfig.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgrade.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgradeB2B.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\IpfsUpgrade.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgrade.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgradeB2B.xml.
06/18/2014 16:07:34.31 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUpgrade.xml.
06/18/2014 16:07:34.33 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUserProfilesUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OSSSearchUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\PPSUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SecureStoreServiceUpgradeConfiguration.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SiteUpgraderConfigSPS.xml.
06/18/2014 16:07:34.45 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgrade.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgradeB2B.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\Wdsrv_Upgrade.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WebAnalyticsUpgradeConfiguration.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WSSSearchUpgrade.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgrade.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgradeB2B.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcIisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.WebUI.Mobile.Upgrade.ExcelMobileViewerSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 11.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.Server.MossHost.Upgrade.ExcelServicesSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 11.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.FarmUpgradeSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.ServiceUpgradeSequence] for [Microsoft.Office.InfoPath.Server.Administration.FormsService], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.OsrvPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateServiceSequence] for [Microsoft.Office.Server.Administration.SessionStateService], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateDatabaseSequence] for [Microsoft.Office.Server.Administration.StateDatabase], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateServiceSequence] for [Microsoft.Office.Server.Administration.StateService], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 17.
06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence] for [Microsoft.Office.Server.Administration.ProfileDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.SocialDatabaseSequence] for [Microsoft.Office.Server.Administration.SocialDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileApplicationSequence] for [Microsoft.Office.Server.Administration.UserProfileApplication], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.ServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceApplicationSequence] for [Microsoft.Office.Server.Search.Administration.SearchServiceApplication], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchAdminDatabase], Phase: 0, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchMetadataDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchPropertyStoreDatabase], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchGathererDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchGathererDatabase], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSDatabaseSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceDatabase], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Upgrade.BIMonitoringServiceApplicationSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreDatabaseSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreServiceApplicationSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplication], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataDatabaseSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceDatabase], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataApplicationSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.PrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.WebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.QueueDatabaseSequence] for [Microsoft.Office.Word.Server.Service.QueueDatabase], Phase: 2147483647, Order: 11.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.ServiceAppSequence] for [Microsoft.Office.Word.Server.Service.WordServiceApplication], Phase: 2147483647, Order: 11.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.StagerDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsStagerDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WarehouseDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWarehouseDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebServiceSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebService], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplicationSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplication], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchDatabaseSequence] for [Microsoft.SharePoint.Search.Administration.SPSearchDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Ready to initialize the type dictionary
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Type dictionary initialized.
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Mutex released.
06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: CanUpgrade [SPConfigurationDatabase] returned: True.
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: NeedsUpgrade [SPConfigurationDatabase] returned: True.
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: IsBackwardsCompatible [SPConfigurationDatabase] returned: True.I have the following finding from the Event Viewer.
Event 7022
The Forefront Identity Manager Synchronization Service service hung on starting.
Event 7024
The Forefront Identity Manager Synchronization Service service terminated with service-specific error %%-2146234334.
Event 7031
The SharePoint 2010 Timer service terminated unexpectedly. It has done this 4007 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
Event 11016
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
and APPID
{000C101C-0000-0000-C000-000000000046}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
I found this
post talking about the solution of this problem. Can anyone help to explain the solution to me?
Also, I try to stop the user profile service and user profile sync service and restart both. The timer service restart problem has gone!! However, new error in the event viewer.
Event ID 3
Microsoft.ResourceManagement: System.InvalidOperationException: This Forefront Identity Manager system resource cannot be deleted.
at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception)
at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Delete(Message request) -
Lync 2013 Desktop does not start on WIndows 8.1
My Office 365 version of Lync 2013 64bit crashes every time I start it. There is no error message just the "Microsoft Lync has stopped working" message with Close option. In further looking for a solution, I found the suggestion to
uninstall the Intel Bluetooth drivers but my system uses Realtek Filter drivers. I have looked in the event logs and found:
Log Name: Application
Source: Windows Error Reporting
Date: 2014-09-11 1:47:20 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: --------Win8
Description:
Fault bucket 85949488684, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: lync.exe
P2: 15.0.4641.1000
P3: 53c5ce3c
P4: KERNELBASE.dll
P5: 6.3.9600.17055
P6: 532954fb
P7: e06d7363
P8: 0000000000005bf8
P9:
P10:
Attached files:
C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d
Analysis symbol:
Rechecking for solution: 0
Report Id: aa908032-39db-11e4-8280-48d224dc5142
Report Status: 0
Hashed bucket: 61000269e077a9a343a6fe9bbb7efc54
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-11T17:47:20.000000000Z" />
<EventRecordID>143379</EventRecordID>
<Channel>Application</Channel>
<Computer>Fedmet-YL-Win8</Computer>
<Security />
</System>
<EventData>
<Data>85949488684</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>lync.exe</Data>
<Data>15.0.4641.1000</Data>
<Data>53c5ce3c</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.3.9600.17055</Data>
<Data>532954fb</Data>
<Data>e06d7363</Data>
<Data>0000000000005bf8</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml</Data>
<Data>C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d</Data>
<Data>
</Data>
<Data>0</Data>
<Data>aa908032-39db-11e4-8280-48d224dc5142</Data>
<Data>0</Data>
<Data>61000269e077a9a343a6fe9bbb7efc54</Data>
</EventData>
</Event>
A lot of sites suggest to uninstall Intel Bluetooth drive but I does not have Intel Bluetooth.Go to your computer manufacturer’s website and update all driver packages for your computer, especially:
Audio drivers
Bluetooth drivers
System chipset drivers
webcam drivers
Important Note:
If you use office 64 bit, Lync 2013 must be 64 bit also. {And vice versa, If you use office 32 bit, Lync 2013 must be 32 bit}
Also check answer of Eric to fix this issue
http://social.technet.microsoft.com/Forums/en-US/e8268935-e97c-4033-9a2e-02734b4390bf/lync-2013-client-on-windows-81-stuck-at-starting?forum=ocsclients
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali -
Lync 2013 isn't saving conversation history in Lync, Saves to Outlook just fine.
So in my Lync client, I have the Conversations icon that has tabs under it for All, Missed, and Calls.
All of those tabs are blank in my program. They said "You'll see your recent conversations here", but there's nothing there. I do see my old conversations in Outlook just fine, but Lync itself isn't saving them.
What's even worse is that my Conversations icon has a '5' next to it and says I have 5 missed conversations. I click it and the tabs are blank.
Any thoughts on this? Most issues I see are when Outlook isn't logging the conversations so my issue is backwards...Hi,
Please check your settings:
1. On the Lync main window, click Options button, and then click Personal;
2. In the Personal information manager section, select "Microsoft Exchange Or Microsoft Outlook" from Dropdownlist;
3. Checked all checkboxes under this field;
4. Exit Lync 2013 and restart it;
5. Check the result.
If the issue still persists, please try to repair this Office program:
Repair Office programs
http://office.microsoft.com/en-in/outlook-help/repair-office-programs-HA010357402.aspx
Best regards,
Karen Hu -
Lync 2013 clients behind TMG 2010
Hi
My escenario is as follow
Lync Client 2013 --> TMG 2010 --> ISP Router (without fillter ports)
I have a problema with this escenario because TMG drop me the voice calls and sudendly drop me the connection with the server.In TMG i created the following rullo
From internal to external, and URL Set (*.microsoftonline.com,
*.microsoftonline-p.com , *.onmicrosoft.com, sharepoint.com, *.outlook.com )
Protocols: http, htpps, RTP, SIP, Sip Server, Sips, Sips Server,
50040-50059 TCP Outbound
50000-50019 UDP Send Receive
3478 UDP Send Receive
59999 UDP Send Receive
50020-50039 UDP Send Receive
So what is the problema with this TMG 2010 (with all updates, SPs and rollouts)
ThanksHi,
The following blog might help.
http://www.jaapwesselius.com/2012/12/21/publish-lync-2013-services-in-tmg-2010/
(Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce
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. -
Hello
I have Lync 2013 and 2010 , still i didn't finish my migration completely from 2010 to 2013 .this is coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013 front end and backend server's .
later on after restarting both the front end and the back end server's i start having hundred's of these error's related to "LS Call Park Service".
so any advice for these issue ? and what is the effect for these error .
below is the error I got .
The database being used by Group Pickup is not the appropriate version.
The database is not the correct version:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
Actual... SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
Cause: The database has not been upgraded.
Resolution:
Upgrade the database to CU1.
==============================================================
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
=============================================================================
Kind Regards
MKHello
thanks Holger for u r replay .
due to the Microsoft article about the cu :
I run only :
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase command to apply the changes.
here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
VERBOSE: Install databases required by Lync Server role(s).
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
Checking state for database rtcxds.
State of database rtcxds is DbState_RequiresMinorUpgrade.
Database rtcxds set to mode Restricted.
Dropping all procedures, functions and views from database rtcxds.
Executing RtcDb.sql...
Adding master role...
Setting owner for database rtcxds to sa.
Creating login MyDomain\RTCHSUniversalServices.
Creating user MyDomain\RTCHSUniversalServices.
Creating Schema MyDomain\RTCHSUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
Setting the database rtcxds to multi user mode.
Database rtcxds is set to multi user mode.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcshared.
Database created by script "RtcSharedDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
Checking state for database rtcab.
State of database rtcab is DbState_RequiresMinorUpgrade.
Database rtcab set to mode Restricted.
Dropping all procedures, functions and views from database rtcab.
Executing RtcAbTypes.sql...
WARNING: Warning: Failed to execute batch --
-- Copyright (c) Microsoft Corporation. All rights reserved.
exec sp_addrole N'ServerRole'.
Executing RtcAbDb.sql...
Setting owner for database rtcab to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
Setting the database rtcab to multi user mode.
Database rtcab is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
Database created by script "RgsConfigDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
Database created by script "RgsDynDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
Checking state for database cpsdyn.
State of database cpsdyn is DbState_RequiresMinorUpgrade.
Database cpsdyn set to mode Restricted.
Dropping all procedures, functions and views from database cpsdyn.
Executing CpsDyn.sql...
Setting owner for database cpsdyn to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
Setting the database cpsdyn to multi user mode.
Database cpsdyn is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
Database created by script "ArchivingDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
State of database LcsCDR is DbState_RequiresMinorUpgrade.
WARNING: The database LcsCDR being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
WARNING: The database LcsCDR being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
Database LcsCDR set to mode Restricted.
Dropping all procedures, functions and views from database LcsCDR.
Executing CdrDb.sql...
Setting owner for database LcsCDR to sa.
Creating login MyDomain\CSAdministrator.
Creating user MyDomain\CSAdministrator.
Creating Schema MyDomain\CSAdministrator.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
Setting the database LcsCDR to multi user mode.
Database LcsCDR is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing CdrJobs.sql...
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
State of database QoEMetrics is DbState_RequiresMinorUpgrade.
WARNING: The database QoEMetrics being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
WARNING: The database QoEMetrics being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
Database QoEMetrics set to mode Restricted.
Dropping all procedures, functions and views from database QoEMetrics.
Executing QoEDb.sql...
Setting owner for database QoEMetrics to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
Setting the database QoEMetrics to multi user mode.
Database QoEMetrics is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing QoEJobs.sql...
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
VERBOSE: No changes were made to the Central Management Store.
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
PS C:\Users\MK>
I hope some one can confirm no issue with what I did ??
Kind Regards
MK -
Lync 2013 Android - your server configuration has changed. Please restart Lync
Lync 2013 on Android devices is giving error after every 5 minute "your server configuration has changed. Please restart Lync".
Calls gets dropped when this error occurs.
we are using server 2012 R2 as reverse proxy and have changed the Proxy time out for External web service URL to 960 secs with no luck.Hi M.Irfan84,
I would like to confirm the following information.
1. Do we have run “iisreset /noforce” to apply the change?
2. And does this issue only impact on Android device?
Best regards,
Eric -
Lync 2013 Authenticating with Windows Account Every Minute
Seeing a strange issue with Lync 2013 client logging into my Windows Account about every 1-2 minutes. We are using Lync Server 2013 (on-premise) so it makes no sense that it is logging into and authenticating against Windows Account. This was causing major
issues as my Windows Account password was different than my company domain login. This was causing Lync to use the "wrong" password to login into Windows Account. I changed the passwords to match and now still seeing Lync logging in constantly
into Windows Account.
This is adding up to a LOT of data traffic. Lync should NOT be authenticating every 1-2 minutes into my Windows (Live) Account. Help please!Hi,
Did the issue happen only for you or for multiple users?
Please exist Lync client, delete user profile on local computer with the following path, then restart Lync client:
%UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support -
Team,
Unable to start FE service on one of the FE server, 2 Enterprise lync 2013 pool one FE in each pool, only following error in event vrw,
Log Name: Lync Server
Source: LS Server
Date: 12/30/2013 12:10:55 PM
Event ID: 12290
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: ACS465-BH102.me.ykgw.net
Description:
The evaluation period has expired.
The evaluation period for Microsoft Lync Server 2013 has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Cause: The evaluation period for Microsoft Lync Server 2013 has expired.
Resolution:
Please upgrade from the evaluation version to the licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Server" />
<EventID Qualifiers="50152">12290</EventID>
<Level>2</Level>
<Task>1000</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:10:55.000000000Z" />
<EventRecordID>73953</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
Log Name: System
Source: Schannel
Date: 12/30/2013 12:13:36 PM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:13:36.779033200Z" />
<EventRecordID>83985</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="3668" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Server is already on Full version, ran Reset-CsPoolRegistrarState
for fillrest as wel as serviceret
Followed below as well,
http://social.technet.microsoft.com/Forums/lync/en-US/2a7e27ce-2dea-4e37-91ea-1ed42e110198/issue-updating-from-eval-to-volume-licenses?forum=ocsplanningdeployment
Currently done failover to another pool and users can login,
however i cant get the front end service on this server.Any pointers would be appreciated.
Praveen | MCSE Messaging 2003rit, the command is not doing the trick since its already full version,
PS C:\Users\lyncadmin> Get-CsServerVersion
Microsoft Lync Server 2013 (5.0.8308.0): Volume license key installed.
only one server in one pool, total two pools.
Lync 2013 is on Win 2008 R2, and the event in system im inclining to since i have tried all,
Log Name: System
Source: Schannel
Date: 12/30/2013 9:26:34 AM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T06:26:34.877077500Z" />
<EventRecordID>64911</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="620" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Praveen | MCSE Messaging 2003 -
Sql reporting services stops every 24 hours for a short time then restarts
I have noticed that recently in sccm 2012 sp1 the sql reporting services stops every morning at 7:58 am and restarts after a minute or two. The only entry in the event logs is when it stops. I don't see anything tied in with it that stops or
starts at the same time and there are no tasks or anything like that which would point to this time frame. I just thought I would throw this out there to see if anyone had any ideas. Usually with something of this nature there are some corresponding
log entries that go beyond the service stopping, but in this case there isn't. Thanks for any help you can provide.I think I found out what was going on. I approached this from a different angle and was directed to the sql reporting services logs and found information on the reporting web server stopping. Researching that yielded the following information.
It appears that this is a result of the SSRS Web Server recycling the App Domain, which is supposed to be a pretty normal process. In fact, the configuration file for this process defaults to recycling the app domain twice daily. This lines up
with the time frame that the reporting service is stopping. It restarts it in less that two minutes and logs the recyling in the reporting services log twice daily so why I'm not seeing this entry in the event logs twice daily or even every day must
be a timing thing. I think if it takes an extra millisecond or two to recycle the app domain, it dumps an entry into the windows event logs and the sccm component status monitoring.
http://ask.sqlservercentral.com/questions/97176/reporting-web-server-stopped.html -
How do I enable users to attend on Lync 2013 meeting on Windows 2008 R2 Terminal Services/XenApp 6?
Hi,
We are not using Lync internally. But some of my users need to attend Lync 2013 meetings. We run a Windows 2008 R2 Terminal Services/XenApp environment. Users are not allowed to install applications.
In the past, I was able to install administratively a Lync 2010 attendee client.
How do I enable my users to attend a Lync 2013 meeting?
Thanks.This is not viable. I don't know which user is going to be attending Lync meetings from suppliers or customers ahead of time and have no contacts to request a test meeting. This is a loop. How does Microsoft expect sysadmins to support their products if
the client software is not easily available.
At this point if I have a user who needs this, I will only know about it after the meeting has failed. At that point the user is not very receptive to the idea of involving his contact in troubleshooting and setting up test meetings. It's even worse if it's
an executive.
Is there any way of pre-installing the pre-requisites for attending Lync 2013 meetings?
My only choice is to inform my user community that we have no way of supporting Lync and request that they use GotoMeeting or WebEx with their contacts who try to do a Lync meeting.
I am very disappointed in Microsoft's approach with Lync 2013.
Thanks for your time. -
Hi All,
Need to restart exchange server 2013 services automatically at a certain period of time is there a script to schedule to automate can you please help me step by step process.
Thanks & Regards, Santosh Chowdary Vasireddy System Administrator Prolifcs DHFLVC Silicon Towers, 5th Floor, Survey #14, Kondapur, Hyderabad – 500 032. Work +91 40 3999 1999 Ex.1656 l Cell +91 9849277255 l [email protected] A Global
Provider of IBM, Microsoft and Testing Solutions Award Winner for Technical Excellence, BPM, SOA, Portal and GovernanceYou can create a PS1 file and run it in a scheduled task.
The PS1 files will need to have this.
Restart-Service MSExchangeTransport
Restart-Service MSexchangeIS
etc...
How to add a Scheduled task is given in this link.
http://www.mikepfeiffer.net/2010/02/creating-scheduled-tasks-for-exchange-2010-powershell-scripts/ -
Lync 2013 Cloud Service Limitations
Can anyone point me to some references on the limitations with Lync 2013 in the
cloud? What are some pros and cons about cloud services with voice and video?How much of this list is still true to the limitations of Lync Online?
The features not available are:
Searching for employees by their skillset in an on-premise SharePoint Server and SharePoint Online
Persistent group chat
Connect (federate) to IBM Sametime unified communications platform
IM/presence federation with XMPP networks such as Jabber and Google Talk
IM/presence with AOL and Yahoo
Authenticated experience in Lync Web App
Outlook delegation for scheduling online meetings
Generate a link to schedule a meeting via web page
Schedule an online meeting in Outlook Web App
Dial-in audio conferencing on Lync Server
Multimedia content upload
Screen shot capture (including annotation)
Interoperability with on-premise video conferencing systems
Make incoming/outgoing calls over the phone network (PSTN dialling)
Call hold/retrieve
Dial-out over the phone network (PSTN) for meetings
Advanced call controls including transfer, forward and simultaneous ring
Access to Exchange Online voice mail
Team calling
Delegation for voice, for example, boss delegates to secretary
Call park
Outgoing Direct Inward Dialing (DID) manipulation
Enhanced 9-1-1 for location by emergency services
Dial plans and policies
IP desk phone support
Survivable Branch Appliances for branch office resiliency
Call admissions control
Support for analog devices such as a fax
Response groups
Private line (secondary DID for executives)
Interoperation with third-party private branch exchange (PBX)
Presence interoperation with third-party PBX
Remote call control (RCC) (also known as “click-to-call”) with on-premises PBX
Malicious call trace
Unassigned number
Network Quality of Service (QoS) and Differentiated Services Code Point (DSCP)
Media path optimisation
Phone number management
Call detail recording (CDR) and billing reporting
Integration with call centre solutions (Aspect)
Connect to IP phones (Lync 2010 Phone Edition)
Advanced interface for receptionists (Lync 2010 Attendant client)
Legacy clients (eg. Office Communication for Mac, 2007 R2, Mobile for Windows Mobile 6.x)
Anti-malware scanning for meeting content and file transfers
Instant message archiving (server-side only)
Exchange Unified Messaging (UM) interoperation with Exchange Online
Exchange UM interoperation with Exchange on-premise
Use the same domain for Lync on-premise and Lync Online users
Splitting workloads (for example, running IM/presence/voice on-premises, and conferencing in the cloud)
Attendee/user reporting
Reporting (using call recording and Quality of Experience)
Server side APIs to connect to other programs -
Lync 2013 client deployment via SCCM 2012 forcing restart
All,
I am attempting to deploy the Lync 2013 x86 client via SCCM 2012 to 158 machines running the Office 2010 suite. My package runs, and the installs complete but they are forcing a restart after the install even though I have gone in to everything that I can
think of to tell the install not to force a restart. I am a newb in the ways of SCCM so I have been self teaching, and I may have missed something.
I have gone into the config.xml and changed the value SETUP_REBOOT to NEVER.
In the program properties I have RUN set as HIDDEN, and AFTER RUNNING set to NO ACTION REQUIRED.
Is there something that I am missing to stop the users machine from restarting after the install completes?Great, unfortunately it will be because files (usually shared DLLs) are in use as Office is opened, despite it being an older version.
Agree it's not optimal, I usually just tell clients that they will need to reboot, or that it will push out overnight (when I schedule it) and their computer will restart, so make sure they save everything.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
Maybe you are looking for
-
my facetime dont work whith lion
-
I am looking for a real time CRM consultant who can teach me in Bangalore ?
I am looking for a real time CRM consultant who can teach me in Bangalore ? Call me on 7204246238
-
Using OTO CTS+ in Solution Manager 4.0
Hi everybody, I'm trying to configure the OTO in Solution manager, I somehow configured something as described in the CTS+ guide, I also was able to create a Project as shown in the RKT-solman. What i'm missing now is how do i use this tool, from beg
-
In oracle Httpuritype - Not getting the output correctly
Hi, I am trying out httpuritype in oracle for the first time. My requirement is to get the input string and the from_language and to_language and has to be converted accordingly. I am using oracle 11.2.0.1. So had setup acl explicitly and started wri
-
Update Script Problem CS2 to CS3 ( Time/Date/Year Script NOT WORKING IN CS3?
The below script works in CS2 but not in CS3? WHY? //DESCRIPTION: Use to insert date/time into document. if (app.documents.length == 0) { exit() } insertDTs(app.documents[0]); function insertDTs(aDoc) { var curPrefs = aDoc.characterStyles[0].extractL