I got some problem when I tried to install Windows Server Update Services on my Test Windows Server 2012 Sp1 with SQL Server 2012 Sp1 installed. The Role installation worked fine. When after a post-installation runs it fails. After some research, I notice the post-installation didn’t found the wsusutil.exe tool (Wsus post-installation use this tool to do a post-installation). I’d a simple file search on server, and found the tool under c:\Program Files\Update Services\Tools. Run it from a powershell console:
If you have install Wsus and choosed Database, run this command:
wsusutil.exe postinstall CONTENT_DIR="WSUS-CONTENT-PATH" SQL_INSTANCE_NAME="SQL-SERVER-NAME"
If you have install Wsus and choosed WID database, run this command:
wsusutil.exe postinstall CONTENT_DIR=C:\WSUS INSTANCE_NAME="computername\database_instance_name"
During SQL 2012 SP1 installation on a Windows 2012 Server i got the following Error.
The installation finished with some error.
To fix this, first I need to install .Net Framwork 3.5 and then mount my windows 2012 media as D:\ and run the follwoing command as administrator.
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs
I rerun the SQL setup and successfully installed it.
During the installation of the new System Center Configuration Manager 2012 with Microsoft SQL Server 2012 I got the following error and the installtion couldn´t continue.
ERROR: Failed to get SID for user (NT Service\MSSQLSERVER)
ERROR: Failed to get the buffer size for LookupAccountName. Error= 1722
To fix it: I creat a domain account that has administrative right on the server and change the service account that the SQL services are running with to it and ran the setup again. This time it finished with no errors.
Have you ever been troubleshooting a problem with remote SQL or remote DB connection and want to see if an account could make a remote connection to SQL but didnt want to install the SQL tools? There is a simpel way to test the database connection.
Just go anywhere on your system and create an empty text file named anything but instead of txt make sure the extension is UDL. Then, double-click on the file and up pops a SQL connectivity window to allow testing of remote SQL connections.