MalwareBytes SQL Server Install
Should be fairly simple to answer because SOMEONE out there has been through my pain. I'm trying to install MalwareBytes Management Console using SQL Server and it refuses to find my server using what I know is a good path for the database address.
Database Address: SERVER\MSSQLSERVER
User: SandboxAdmin
Password: Whatever
I keep getting the error message that the management console cannot find my SQL Server. The SQL Server Browser service IS running, TCP and Named Pipes are on, I migrated a working SQL Server Express database onto SQL Server and I'm just trying to reconnect it (it was successfully attached).
Any help would be appreciated!
Database Address: SERVER\MSSQLSERVER
User: SandboxAdmin
Password: Whatever
I keep getting the error message that the management console cannot find my SQL Server. The SQL Server Browser service IS running, TCP and Named Pipes are on, I migrated a working SQL Server Express database onto SQL Server and I'm just trying to reconnect it (it was successfully attached).
Any help would be appreciated!
The instance name 'MSSQLSERVER' is normally the default instance. Try leaving off the '\MSSQLSERVER' and just connect to the database server by the server name.
No difference. It is still reporting that it cannot connect to the server. I've tried IP address too...same issue.
I assume you connected via the Management Studio to attach the database.
Under Management, can you open the most recent log? Confirm that when the server comes up, (1) it is using a normal port (hopefully 1433).. if it isn't, the log will tell you what port it's using , and that there aren't login errors.
In the properties of the server, confirm security is configured to Mixed mode authentication, not Windows mode. (Again, I'm making an assumption that your login/password above are SQL logins.)
Hmm.. One other thought. You moved this database... did you happen to create the login for SandBoxAdmin on the new server? (The logins live in the master database. The users live in your database. I have a suspicion that you have an orphaned user, if you didn't explicitly copy the login.)
Under Management, can you open the most recent log? Confirm that when the server comes up, (1) it is using a normal port (hopefully 1433).. if it isn't, the log will tell you what port it's using , and that there aren't login errors.
In the properties of the server, confirm security is configured to Mixed mode authentication, not Windows mode. (Again, I'm making an assumption that your login/password above are SQL logins.)
Hmm.. One other thought. You moved this database... did you happen to create the login for SandBoxAdmin on the new server? (The logins live in the master database. The users live in your database. I have a suspicion that you have an orphaned user, if you didn't explicitly copy the login.)
Hi Rich - Yes, DB is attached, SandboxAdmin user is created, port is 1433. As a matter of security, we do not allow mixed mode. I will try that for testing purposes however (good idea).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Rich - I took your idea and it logged in on the first try after creating a SQL user. After doing a little bit more digging into why this happens, it would appear that MalwareBytes ONLY supports SQL authentication and doesn't support Windows authentication (really disappointing). We'll have to figure out where to go from here (enterprise security decision).
That is...unless you know of a way to trick Malware Bytes into thinking it is using SQL authentication. I believe I remember way back in the day there was a way to do this with ODBC, but I'll have to knock the rust off of that part of my brain.
That is...unless you know of a way to trick Malware Bytes into thinking it is using SQL authentication. I believe I remember way back in the day there was a way to do this with ODBC, but I'll have to knock the rust off of that part of my brain.