Issue:
When we run the
setup for the installation of SCCM 2012/Current Branch, Primary/Central Site we
get the following error message in the Configmgrsetup.log
Cause:
This happens because the name of the Windows Server with the SQL Server instance installed was renamed before starting the installation of SCCM Site Installation.
Solution:
Open the SQL
Management Studio on the SQL Server and login with the required credentials.
Run the following
stored procedures to check the current name of the server in sys.servers of the SQL Servers.
Exec
SP_Helpservers;
Go
If you find the old
server name as a result of the above query then run the following procedures to
first delete it from sys.servers and then update it with the current name.
Exec
sp_dropserver <Old name>; (For default
instance)
Go
Exec
sp_addserver <New Name> ; (For default
instance)
Go
OR
Exec
sp_dropserver <old name\instance name>; (for
Named Instance)
Go
Exec
sp_addserver <New Name\Instance name>;
(for Named Instance)
Go
After renaming the
server name in sys.servers of the SQL servers run the following query to check
if the name is changed or not
Select
@@ServerName;
It will return the current name
of the Server.
Now restart the
Instance of the SQL from the SQL Configuration Manager and reboot the
server.
Once the server is
up and running after the reboot run the
configmgr setup. The setup will first run to uninstall the Site
components that got installed in the
last failed attempt.
After the Uninstall
setup is finished run the configmgr setup once again to start the Site
installation. This time the same error
should not come up during the setup SQL Database step of the Site installation
process.
It’s fully-licensed, safe and secure to make use of, and it’s as reputable as mobile casinos come. State laws as written are currently in opposition to gambling, save for horse racing. The state doesn’t enable fantasy sports activities, either and there’s been little political urge for food for authorized 카지노사이트 sports activities betting.
ReplyDelete