i put myself in a big problem
-
@Dashrender said:
@IT-ADMIN said:
the problem is that the SQL service doesn't want to run, it gives an error
that should be easy to fix
go to services and double click SQL and look what account it's using.
then create account on your domain give it a GOOD passwordthen go back to the service and put the domainname\user for the username and type in your password.. and you should be good to go for starting SQL.
thank you very much dude, you really saved me, the problem was due to SQL service not running because it was set to run using a local account, off course after this account was deleted the service cannot run, as soon as i changed the service logon account to domain administrator the service start successfully and the connection was successful
ouuuf it was a terrible nightmare but also a lesson
thank you @dashrender and thank you guys
-
Now that you have that working, don't stop there!
Create a dedicated user account in AD for SQL. Then assign it local admin rights on the SQL server. The replace the domain admin credentials you currently have running SQL.
Reasons for doing this: If you leave the Domain Admin user in there for SQL, if SQL is compromised, the hacker will have Domain Admin level privileges to your entire domain.
-
@Dashrender said:
Now that you have that working, don't stop there!
Create a dedicated user account in AD for SQL. Then assign it local admin rights on the SQL server. The replace the domain admin credentials you currently have running SQL.
Reasons for doing this: If you leave the Domain Admin user in there for SQL, if SQL is compromised, the hacker will have Domain Admin level privileges to your entire domain.
thank you for your advice, but i no longer care about security since everything is fine lol
as Scott mentioned: why i should care about the business if the owner don't care
i fear if i change something now i may get an issue, so i will just keep everything as it is -
@IT-ADMIN said:
thank you for your advice, but i no longer care about security since everything is fine lol
as Scott mentioned: why i should care about the business if the owner don't care
i fear if i change something now i may get an issue, so i will just keep everything as it isBecause you have changed the situation from what it was before. Before you upgraded to AD, the account was local, limiting liability only to that machine. Now if SQL is hacked, they potentially have full access to your entire network.
Making my suggested change will at least get you mostly back to the previous state, but not fully.
-
ok i do what you told me but i have to restart the SQL service so that the new logon account will take effect, when the HR Dept finish working with the payroll application then i can restart it
-
@IT-ADMIN said:
ok i do what you told me but i have to restart the SQL service so that the new logon account will take effect, when the HR Dept finish working with the payroll application then i can restart it
Sounds like a good plan
-
@Dashrender said:
@IT-ADMIN said:
ok i do what you told me but i have to restart the SQL service so that the new logon account will take effect, when the HR Dept finish working with the payroll application then i can restart it
Sounds like a good plan
thank you Sir
-
Glad to hear that everything is back up and working. Did anyone notice very much?
-
@scottalanmiller said:
Glad to hear that everything is back up and working. Did anyone notice very much?
hhhhh, no, the problem was solved silently
-
@IT-ADMIN said:
@scottalanmiller said:
Glad to hear that everything is back up and working. Did anyone notice very much?
hhhhh, no, the problem was solved silently
That's what I was wondering. Good deal.
-
You had an entire day of downtime on this and no one noticed?
-
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advises -
@IT-ADMIN said:
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advisesThat's great. I'm glad that it worked out so well.
The power of MangoLassi!!
-
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shift -
there is a big time diffidence btw qatar and US, when i post my problem it was early morning in US but it was the end of the day in Qatar
-
@scottalanmiller said:
@IT-ADMIN said:
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advisesThat's great. I'm glad that it worked out so well.
The power of MangoLassi!!
yeah, off course you are great guys
-
@IT-ADMIN said:
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shiftPeople who know me know I'm a gambler. I go to Vegas all the time, I blow money at various casinos throughout the country.
You just rolled a quick point on the craps table, you hit a blackjack on your first hand, you laid down $5USD on 21 red and it came up. You got seriously lucky. By pure chance you got out without anyone being the wiser.
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
Remember, the worst thing you can do as a gambler is go and do things without thinking. When I sit down and play blackjack, I have a good idea about the cards, the odds, where we are in the deck, what is available, what is not available. I calculate the risks, rewards, and make my decisions on that. As one should do when working on anyone else's machines.
-
@PSX_Defector said:
@IT-ADMIN said:
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shiftPeople who know me know I'm a gambler. I go to Vegas all the time, I blow money at various casinos throughout the country.
You just rolled a quick point on the craps table, you hit a blackjack on your first hand, you laid down $5USD on 21 red and it came up. You got seriously lucky. By pure chance you got out without anyone being the wiser.
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
Remember, the worst thing you can do as a gambler is go and do things without thinking. When I sit down and play blackjack, I have a good idea about the cards, the odds, where we are in the deck, what is available, what is not available. I calculate the risks, rewards, and make my decisions on that. As one should do when working on anyone else's machines.
yeah it was a good lesson for me, next time before doing any major change like this i will post it in ML to discuss with you the consequences, once it is approved then i will be ready to go
for the approval of the management (because Scott emphasize on this) they don't understand what active directory mean or what an additional domain controller mean, they are really far away from IT, so they told me do what should be done as long as it is free hhhhhh
for this reason i'm playing around with the servers and enjoy my time because no one understand what i'm doing (they understand only one thing : is the system down or not) so basically they know 0 or 1, -
@PSX_Defector said:
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
One more thing that has to be considered - the reward. How big is the payoff? In this scenario, the payoff, had everything worked perfectly, was effectively zero. There was risk without potential reward. That's a big deal too. He would not really have benefited here, even if things had not gone poorly.
-
@scottalanmiller said:
@PSX_Defector said:
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
One more thing that has to be considered - the reward. How big is the payoff? In this scenario, the payoff, had everything worked perfectly, was effectively zero. There was risk without potential reward. That's a big deal too. He would not really have benefited here, even if things had not gone poorly.
Agreed. This is betting on every horse in the race. Yeah, you win, but what do you get out of it? Maybe a dollar or two assuming that the longshot came in. If it was the 2-1, you are out money on the process.
See the road ahead, understand what is next, what you next move is, and it will usually work out. Something some folks don't understand.
