Document name Phone-link – Server down after Windows 10 Major OS update Author  Anita Robson Publish Date 11/03/2021 Version  1.0

 

 

1. Version Information 

 

 

Date Author Update Information  Version 11/03/2021 Anita Robson 1st draft 1.0

 

 

2. Document Purpose & History

 

This document is intended to provide the reader with the necessary steps on how to setup recover the Phonelink server after a major Windows 10 OS update

 

 

Phone-link – Server down after Windows 10 major Windows 10 OS update

 

 

 

Windows 10 Major OS updates, e.g 1803, 1809, 1903, 1910, 2004, 2010; cause the server software database to either hang at startup with a loading bar, or it will present itself as a fresh install that has lost it’s existing database.

 

This is caused by major Windows 10 updates detaching the underlying database from the system instance and not allowing it to reattach once the update is complete.

This will affect all Windows 10 installs running version 2.5.38 and greater, and will affect your server every time a major Windows update is released.

 

To resolve this issue you can must save the linked Batch file to the affected server, and run this Batch file with Administrative access.

This can be done by right clicking on the saved Batch file and choosing Run As Administrator.

 

You can download the Batch file from here; https://downloadmgmt.blob.core.windows.net/misc/UCServerDatabaseFix.bat

 

 

 

 

This batch file cannot cover all edge cases. 

 

If your server is still not working after running this batch file, please log a ticket with us and we will investigate.

 

If you prefer to perform the steps run by this batch file yourself, you can follow the below instructions.

Please note, depending on your software version, the name of UCServer and UCTelephony will be different.

 

Please note, the following instructions will change depending on your existing database location.

If you have a UCServer.mdf file located within C:ProgramDataUCServer then please use the below Modern Database Location instructions. Otherwise skip to Legacy Database Location further down the page.

 

Modern Database Location

  • Login as the local system administrator, or a user with administrative access.
  • Run services.msc.
  • Stop all UC services i.e UCServer and UCTelephony
  • In windows explorer browse to C:ProgramDataUCServer
  • Create a new folder called Backup inside the UCServer folder.
  • Copy both UCServer.mdf and UCServer_log.ldf to the Backup folder created previously.
  • Browse to “%windir%SysWOW64configsystemprofileAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstances
  • Delete the MSSqlLocalDB folder entirely. If you get a warning that a file is in use, please wait at least 5 minutes and try again.
  • Restart any UC services i.e UCServer and UCTelephony
  • Wait approx. 30 seconds after any UC Servers have been started, and stop them again.
  • Copy the files from C:ProgramDataUCServerBackup back to C:ProgramDataUCServer when prompted confirm overwrite the files.
  • Restart the UCServer service
  • Restart your PC and make sure that the system restarts as expected, and your UCServer is working as expected.

 

Legacy Database Location

  • Login as the local system administrator, or a user with administrative access.
  • Run services.msc.
  • Stop all UC services i.e UCServer and UCTelephony
  • In windows explorer browse to C:windowssystem32Config   – you will be prompted to “Click Continue to permanently get access to this folder” Click continue
  •  
  • Click on folder “systemprofile” and do the same as above.
  • Copy the files from C:windows.oldwindowssystem32configsystemprofile to C:Windowssystem32Configsystemprofile 
  • When prompted confirm overwrite the files.
  • Browse to “%windir%SysWOW64configsystemprofileAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstances
  • Delete the MSSqlLocalDB folder entirely. If you get a warning that a file is in use, please wait at least 5 minutes and try again.
  • Restart the UCServer service
  • Restart your PC and make sure that the system restarts as expected, and your UCServer is working as expected.