Optional: While the tool is running, you can run the SQL query from step 1 to verify that the count is being reduced. Run the following command: PurgeAppEndpointUserDataFromPSD.ps1 -PoolName -Command delete Open the output files and visually confirm that it's safe to delete their data. Run the following command: PurgeAppEndpointUserDataFromPSD.ps1 -PoolName -Command select The value returned may vary between individual Front-End servers in a particular pool. Optional: Run the following SQL query on the RTCLocal SQL instance of your Front-End servers to determine the current number of entries in the PersistedServiceData table. After the state transitions to Ready, all secondary replication tasks should have completed, and all application endpoints should now be able to complete conference operations.įollow these steps on every affected pool: When the state is Busy, there are still secondary replication tasks in progress, and therefore some portions of the application endpoints may still be affected. You can use the Get-CsPoolUpgradeReadinessState PowerShell command to determine whether all the secondary replication processes have completed. This issue may persist until the secondary replication process has completed. If you were actively affected by this issue before running this tool, you may notice that currently affected application endpoints continue to fail during conference operations, even after you run the tool. It also purges those entries from the PersistedServiceData table. This tool locates any entries related to conferences that were created by application endpoints but that have since been deleted. To prevent this issue, use the PurgeAppEndpointUserDataFromPSD.ps1 tool from the Skype for Business 2015 Resource Kit:
CREATE SKYPE MEETING FAILED FULL
This prolonged process causes queues on the server to become full for longer than expected, and it triggers replication failures during conference operations. When many conferences are created over time by a third-party application, the Persisted Service Data (PSD) table may grow to a size at which replication to the new secondary replicas takes an excessive amount of time to complete. Replication of stateful data from the primary Front-End server to both of its secondary Front-End servers fails while trying to create, modify, or delete a conference.ĭuring an outage or disconnect of one or more Front-End servers, the currently active Front-End servers may take ownership of certain sets of users, and in the process, require the creation of new secondary replicas for those users. The endpoint receives a "503 syncReplicationFailed" or "400 conferenceAlreadyExists" error for every conference it tries to create, modify, or delete. In this scenario, you find that some portion of the endpoints used by your applications cannot create, modify, or delete conferences. An outage or network disconnect occurs for one or more of your Skype for Business Server 2015 or Lync Server 2013 Front-End servers.You have one or more third-party applications using trusted application endpoints that create a large number of conferences.You have an on-premises Microsoft Skype for Business Server 2015 or Lync Server 2013 enterprise pool.
0 kommentar(er)
