Sql-server – SQL Server Management Studio 2012 – password lag and failure

I think i can tell you exactly what the issue is, I spent over 48 hours trying to sort this. didnt find anything on the net. also happen to be with 1and1

look at these settings:

IP security policies.....

which opens box...............Packet Filter Properties near the bottom of the list there is a box ticked called :

'Close MSDE (TCP/UDP)' (I am asuming that MSDE = Microsoft SQL Database Engine?) Select it Press Edit...

which opens box............... Edit Rule Properties Select (again) >> 'Close MSDE (TCP/UDP)' Press Edit...

which opens box................IP filter List then you will see a list of ports tcp 1433, udp 1434 {Thats our list of ports all down as a blocking rule.....}

I think what needs to be done from here is either....

close that screen ..IP filter List on the screen Edit Rule Properties there is a tab Filter action, could just change that from Block to permit? (maybe changing it to permit, will allow us to tick the "Block All" option again - which sounds safer, but the support guys said there is a know bug, so might not work)

or

on the Packet Filter Properties

just untick the the rule 'Close MSDE (TCP/UDP)'

you might have to untick the rule 'Block ALL' to get it running

its probably to late for this to help you, but hopefully will help someone else with the same issue.

Troubleshooting: Connecting to SQL Server When System Administrators Are Locked Out:

Resolution

Start the instance of SQL Server in single-user mode by using either the -m or -f options. Any member of the computer's local Administrators group can then connect to the instance of SQL Server as a member of the sysadmin fixed server role.

To start the SQL with -m (from a console running as administrator):

net stop mssqlserver
cd "c:\program files\Microsoft SQL Server\...\MSSQL\binn"
sqlservr -c -m

Or, if you have a named instance:

net stop mssql$<INSTANCENAME>
cd "c:\program files\Microsoft SQL Server\...\MSSQL\binn"
sqlservr -c -m -s <INSTANCENAME>

There are alternative means as shown in How to: Configure Server Startup Options, but I always preffer start from command prompt for something like this. After you start the instance with -m:

1. Open with SSMS using Run as Administrator
2. At the first prompt don't click connect but say cancel
3. Open a new query window and then connect to the database with that query window

4. Now add yourself to the SQL sysadmin group

   create login [domain\you] from windows;

   exec sp_addsrvrolemember 'domain\you', 'sysadmin';

Now shutdown your SQL Server and restart it normally (start back the service). domain\you is now a sysadmin on the server and can administer it. You don't need to run SSMS as administrator.