Cannot start MSSQLSERVER service - Error 3414 - Solved

The actual problem was that the SQL server started but then stopped a few seconds later, causing the Windows Error 3414 to appear.

The 3414 error listed in the error log indicates that there are corrupt transactions that cannot be rolled back or forward.

You can find the following in Event viewer 
Application
Event ID: 9003
The log scan number (xx:xxx:x) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. 

System
Event ID: 7024
The SQL Server (MSSQLSERVER) service terminated with service-specific error 3414 (0xD56).

This is due to model.mdf corrupted you can find the same in ERRORLOG 
You can find it in Path Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

It could occur due to damaged controller, antivirus application, disk problems and other such issues. 

I tried to repair model.mdf with commercial MDF Repair products but model.mdf can't be repaired using this tool, still error occurred. I don’t find any information regarding the responsible issues,

So restoring from the last clean backup you have is the only option( Normally we won't take model, master mdf files). You can copy model.mdf and modellog.ldf from working SQL server instance from another server. (for safer you can backup a copy of model.mdf and modellog.ldf and place outside the \Data Folder.

Now try starting the SQL Service in services.msc. It worked for me :)

PHP & MySQL – Preventing MySQL Injection

http://www.goodphptutorials.com/out/Preventing_MySQL_Injection

FindSounds - Search the Web for Sounds

Search for sample sounds and sound effects at this file search engine. Offers directory, keyword and sonic similarity search functions.

www(dot)findsounds(dot)com

How to Transfer Files Between Dropbox, Google Drive, SkyDrive Online

http://www.guidingtech.com/11384/transfer-files-between-google-drive-dropbox-skydrive-online/

Table 'mysql.servers' doesn't exist + plesk

Usually after the upgrade there errors that arise with MySQL in Plesk while creating users, errors such as "Table 'mysql.servers' doesn't exist"



To solve do the following:

1.SSH to your server

2. mysql -uadmin -p`cat /etc/psa/.psa.shadow` mysql
 

or

mysql -u YOURUSERNAMEHERE -p

Here YOURUSERNAMEHERE=Your actual user name which you are going to use.

Hit enter, you’ll be asked for your mysql password.

3: Use the mysql database command:
        USE mysql;

4.Then RUN the following:

CREATE TABLE `servers` (
`Server_name` char(64) NOT NULL,
`Host` char(64) NOT NULL,
`Db` char(64) NOT NULL,
`Username` char(64) NOT NULL,
`Password` char(64) NOT NULL,
`Port` int(4) DEFAULT NULL,
`Socket` char(64) DEFAULT NULL,
`Wrapper` char(64) NOT NULL,
`Owner` char(64) NOT NULL,
PRIMARY KEY (`Server_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='MySQL Foreign Servers table';

If you don't have access to SSH, You can do this by logging into the webadmin for MySQL via Plesk, and running the above SQL command.

After that point, you will be able to add and delete as needed

And it worked for me:)

Hmail server with Round cube - SMTP Error (530): Failed to add recipient (SMTP authentication is required.)

I resolve this issue.
In the roundcube config file:

$rcmail_config['smtp_user'] = '%u';
$rcmail_config['smtp_pass'] = '%p';
$rcmail_config['smtp_auth_type'] = 'LOGIN';

file can be found in RoundeCube\Config\ main.inc.php

Cannot open database “ASPState” requested by the login. The login failed. Login failed for user ‘sa’

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Cannot open database “ASPState” requested by the login. The login failed.
Login failed for user ‘sa’.

Prompted with the infamous error as shown above. If you’re facing the same issue as mine when trying to run a web application connecting to MSSQL 2008 R2, then you might want to try:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regsql.exe -S DB_SERVER_NAME -E -ssadd -sstype p

P/S: browse to the designated folder before executing the program aspnet_regsql.exe

Hope it helps.

Update: IF you hit an error when running the command above like below:

Start adding session state.

…………………..
An error has occurred. Details of the exception:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Unable to connect to SQL Server database.

Solution: Proceed to SQL Configuration Manager and browse to SQL Server Network Configuration -> Protocols for MSSQLSERVER then enable Named Pipes. Restart the SQL Server and retry executing the command.

It worked!!!!!