Workarounds for subscriptions that cannot be published after you install SQL Server after you modify the computer name

Due to the need to configure a publication subscription, it has been reported that "SQL Server replication requires an actual server name to connect to the server and does not support connections through aliases, IP addresses, or any other alternative names." Please specify the actual server name "xxxx" (Replication utlities). "

After some analysis, it was found that the machine name was modified after installing SQL Server, and running the following two statements can be seen as follows:
Use master

SELECT @ @servername;    

Select SERVERPROPERTY (' servername ')

If these two results are inconsistent, the machine names are changed, and the error is reported when the configuration is copied.
--To fix this problem
--Execute the following statement, and then restart the SQL service after completion
If SERVERPROPERTY (' servername ') <> @ @servername
Begin
declare @server sysname
Set @server = @ @servername
exec sp_dropserver @server = @server
Set @server = Cast (serverproperty (' servername ') as sysname)
exec sp_addserver @server = @server, @local = ' local '
End
Finally, do not forget to restart the SQL Server service, when you are finished, run:
Use master
Go
SELECT @ @servername;
Select SERVERPROPERTY (' servername ')
Back to normal.

Workarounds for subscriptions that cannot be published after you install SQL Server after you modify the computer name