The IIS issue sounds like you need to either have each site on a different port or use Server Name Indication in the bindings if you have to use 443.
That last SQL error looks like either the service isnt running or firewall blocking the SQL port?
Yes some of the words for IIS sound familiar. Unlike SQL I have absolutely no experience with IIS prior to this job.
I've restarted the SQL Service (I think, I also googled how to do that during the session) and it wouldn't budge.
So SQL Server is installed and you can open the SQL Server Manager? You can see all the databases there?
If you go into the actual SQL Server console (Not the manager) it is there that you can see if the server is active and turned on? It looks like thats where you need to look. This error seems to indicate that the connection string is wrong or it isn't what you think it is. The SQL Server Console will tell you this. This is not a RBAC error.
Someone like
Phazael
I believe has a lot experience with this kind of thing. Sorry if I added the wrong person.
When the customer opened the SQL manager he could only see his own user and the sa. He couldn't see all the NT Service logins and ##MS Policy etc. Usually that's a strong warning sign that the user connected to SSMS doesn't have the rights to see or change anything, and that was the case.
He was on default permissions. He didn't know the password for the SA user or any other user with admin rights. He literally had locked himself out of his own SQL server within a day of installing it.
No wait, strike all that, that was a different customer yesterday. I'll not delete it because it was so fucking hilarious to see mr google fu try to break into his own server. But also sad because if I had the inside knowledge I could have reset SA for him. And charged for that. Anyways, back to the original problem.
Yes, we saw everything, the user was sysadmin on the SQL Server. I could delete databases, I could alter permissions and everything. The SQL server was also installed locally on the application server where I was running the msi that creates the database. I've done this part of the installation like a hundred times at this point, and never did I run into a problem like that. Everything seemed in order, permissions were there, correct user was in use, it should have worked. And it did not.
Oh and since I skipped on that part the last time: we don't install SQL for them. That's their infrastructure and therefore their job. Also because we don't have the training to do that. Another reason I'm looking for a MOC we can do. I'd like to be able to install our thing all the way on a blank, new server without having "real IT" preinstall the server features for me.
one more thing: feels odd to browse FOH on company time and actually have it be relevant for the company.