User Profile
Adrian_Fleisch_LID
Iron Contributor
Joined 10 years ago
User Widgets
Recent Discussions
Re: Skype for Business Server 2019 CU1... When?
Yes, it's here: https://support.microsoft.com/en-us/help/4470124/updates-for-skype-for-business-server-2019 Download here: https://www.microsoft.com/en-us/download/details.aspx?id=58347 More info here (thanks to Greig Sheridan): https://greiginsydney.com/sfbs-2019-cu1-july-2019/2.8KViews0likes0CommentsAfter file store move, RGS not working
Hey all At a customer I had to move the Skype for Business File Store from a Enterprise Pool to a new Location. I used the MS Docs: https://docs.microsoft.com/en-us/skypeforbusiness/manage/topology/move-file-store-data Almost all went well, but after removing the old Share, the RGS won't work anymore. In the eventlog the following error is showing: Event ID: 31192 Source: LS Response Group Service General: Workflow has setting that are not valid. The workflow "xx" with GUID "xxx" has settings that are not valid and will be terminated: File "\\old_share\....." not found. Why the RGS still search on the old Share? When I create a new RGS the same happend. The file will saved in the new File Share, but the Event is showing, that the file is not found in the old Location. What I missed? Where can I configure the Path of the Files? Regards1KViews0likes1CommentSkype for Business Server 2019 CU1... When?
Hey There Skype for Business Server 2019 is GA since 10-22-2018. Are there any News about CU1 with some of the feature from the Ignite 2018: SEFAUtil – PowerShell based HTML5 based Modern Control Pane Meetings in Cloud HA/DR: RGS included in backup Cloud Call Queues Or did I miss something… Thanks, AdrianSolved3.4KViews0likes7CommentsRe: Skype for Business and Server 2016
Post from Cian Allner (https://techcommunity.microsoft.com/t5/Skype-for-Business-IT-Pro/Official-Skype4B-support-on-Windows-Server-2016/m-p/78025#M2089) ------------ As of today Windows Server 2016 support for Skype for Business Server 2015 is here! It's now official https://support.microsoft.com/en-gb/help/4015888/cumulative-update-adds-supports-for-windows-server-2016-to-skype-for-b: "We are happy to announce that Skype for Business Server 2015 is supported to run on Windows Server 2016 - if you have the May 2017 update (aka CU5) for Skype for Business Server installed."16KViews0likes0CommentsRe: Skype for Business and Server 2016
Windows Server 2016 is not supported as an operating system for Skype for Business Server 2015, anymore! The article that mentioned support was published prematurely and was pulled. See: https://techcommunity.microsoft.com/t5/Skype-for-Business-IT-Pro/Official-Skype4B-support-on-Windows-Server-2016/m-p/78025#M2089 https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Announcing-the-release-of-Skype-for-Business-Server-Cumulative/bc-p/73600#M315 so let's wait again...16KViews0likes1Comment.NET Framework 4.7 and Skype for Business
The Exchange Team Blog relased the following Info: "At this time, .NET Framework 4.7 is not supported by Exchange Server. " https://blogs.technet.microsoft.com/exchange/2017/06/13/net-framework-4-7-and-exchange-server/ What about Skype for Business?Solved9.2KViews1like10CommentsRe: Lync 2013 - No connectivity with any of Web Conferencing Edge Servers
Hey There is a new Technet Blog article about these Issue (with workarounds): https://blogs.technet.microsoft.com/uclobby/2017/05/24/lyncsfb-server-event-41026-ls-data-mcu-after-may-2017-net-framework-update/19KViews1like1CommentRe: Skype for Business Server 2015 vs Windows Server 2016
It is Supported: https://support.microsoft.com/en-gb/help/4015888/supports-to-use-windows-2016-as-the-operating-system-in-skype-for Thanks to Paul Lange on the Discussions: https://techcommunity.microsoft.com/t5/Skype-for-Business-IT-Pro/Skype-for-Business-and-Server-2016/m-p/350422.3KViews2likes0CommentsRe: Error after Update to CU5 (6.0.9319.281)
The point is, first you have to Update all the FrontEnd Server bevor you Update the Backend. Like it's written in the article https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015. For me, I stopped after the Error was shown on the first FrontEnd Server. I wanted to make sure that there was no other problem, like this one: https://itbasedtelco.wordpress.com/2017/05/17/warning-may2017-windows-update-may-break-skype-for-business-2015-server/ When I have time, I will update all the Server and the Backend.5KViews0likes0CommentsError after Update to CU5 (6.0.9319.281)
After an Update to CU5 (6.0.9319.281) on the first Server of a Skype for Business Enterprise Pool the following Error is showing, around every 3 Minutes: Warning: EventID 57006 "RtcDb Sync Agent sproc failed" Error: EventID 57005 "Error encountered pushing data to RtcXds Blob Store" Bevor I will Update the other Server I need to know what that error means and how to fix it. Any Idee? Or should I update all Server and Update the Database and the Error disappear? Regards Adrian Event ID 57006: RtcDb Sync Agent sproc failed #CTX#{ctx:{traceId:10006, activityId:"944e5513-5bea-4b4d-87f9-6724e271ca2d"}}#CTX# Sproc: [XdsQueryCriticalDocumentSignatures] Exception: [System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'XdsQueryCriticalDocumentSignatures'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.Rtc.Common.Data.DBCore.Execute(SprocContext sprocContext, SqlConnection sqlConnection, SqlTransaction sqlTransaction) ClientConnectionId:fe8376da-4987-43e9-9d2a-4c12dfd128a1 Error Number:2812,State:62,Class:16] Event ID 57005: Error encountered pushing data to RtcXds Blob Store #CTX#{ctx:{traceId:10006, activityId:"944e5513-5bea-4b4d-87f9-6724e271ca2d"}}#CTX# Push cycle identifier: [srvbalyfe08.bag.int.2fd688f5-0f3a-407f-bab5-3fa5c3757443] ItemCount: [0] Error Message: [PushController: XdsQueryCriticalDocumentSignatures failed: System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'XdsQueryCriticalDocumentSignatures'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.Rtc.Common.Data.DBCore.Execute(SprocContext sprocContext, SqlConnection sqlConnection, SqlTransaction sqlTransaction) ClientConnectionId:fe8376da-4987-43e9-9d2a-4c12dfd128a1 Error Number:2812,State:62,Class:16] Cause: Possible issues with back-end database. Resolution: Ensure the back-end is functioning correctly5.1KViews0likes7CommentsSkype for Business Server 2015 and SQL Server 2016
Is or when is SQL Server 2016 supported as a Back end databases for Skype for Business Server 2015? On the Technet (https://technet.microsoft.com/en-us/library/dn951388.aspx#DBs) only SQL 2008 R2, 2012 and 2014 are listed? Any News about the use of SQL 2016 with Skype for Business? Or is there a Timeline about that? Regards9.3KViews1like14CommentsSkype for Business and Server 2016
Hey On the Technet https://technet.microsoft.com/en-us/library/dn951388.aspx no support for Server 2016 is listed: These are the OS that will allow you to install and successfully use Skype for Business Server 2015. Windows Server 2012 R2 Datacenter OS with all required updates installed. Windows Server 2012 R2 Standard OS with all required updates installed. Windows Server 2012 Datacenter OS with all required updates installed. Windows Server 2012 Standard OS with all required updates installed. So whats about Server 2016? Is it suppored or not? Any Timeline? RegardsSolved19KViews0likes11CommentsRe: Cloud PBX - Tenant Location
I also Talked to MS Support and I get these answer: More explicitly, in order to be able to purchase and assign the PSTN Calling Domestic or Domestic and International plan, you need a tenant to have been registered in the country for which these plans are available. So it's not possible to ad US-based number to a user on a Europe Tenant. Because there are no Callin plans available for instance Switzerland, where my Tenent is registered. Or I'm wrong?3.2KViews0likes6Comments
Recent Blog Articles
No content to show