while connecting to SQL Server got a issue

Issue while connecting to SQLServer

Found the error below

And I have a look on this C:\Program Files\Microsoft SQL Server\MSSQL10_50.EUEPRD\MSSQL\Log

Error I got

2013-06-20 18:54:27.70 Logon       Error: 18401, Severity: 14, State: 1.

2013-06-20 18:54:27.70 Logon       Login failed for user 'sa'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]

2013-06-20 18:54:28.43 spid7s      Signing sps ...

2013-06-20 18:54:28.43 spid7s      Dropping existing Agent certificate ...

2013-06-20 18:54:28.44 spid7s      DBCC TRACEON 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.

2013-06-20 18:54:28.44 spid7s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.

2013-06-20 18:54:28.92 spid7s      DBCC TRACEOFF 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.

2013-06-20 18:54:28.92 spid7s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.

2013-06-20 18:54:29.09 spid7s      Error: 5123, Severity: 16, State: 1.

2013-06-20 18:54:29.09 spid7s      CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'C;\data\temp_MS_AgentSigningCertificate_database_log.LDF'.

2013-06-20 18:54:29.09 spid7s      Error: 5123, Severity: 16, State: 1.

2013-06-20 18:54:29.09 spid7s      CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'C;\data\temp_MS_AgentSigningCertificate_database_log.LDF'.

2013-06-20 18:54:29.10 spid7s      Error: 1802, Severity: 16, State: 4.

2013-06-20 18:54:29.10 spid7s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

2013-06-20 18:54:29.10 spid7s      Error: 912, Severity: 21, State: 2.

2013-06-20 18:54:29.10 spid7s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

2013-06-20 18:54:29.11 spid7s      Error: 3417, Severity: 21, State: 3.

2013-06-20 18:54:29.11 spid7s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

2013-06-20 18:54:29.60 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

And tried C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Binn>sqlservr.exe

But no luck

Again try one more Option:-

If your Database is still in the upgrade script mode as soon as it starts up . Do the following.

1. Enable trace flag 902 on the instance of SQL Server 2008 . To do this, follow these steps:
   a. Open SQL Server Configuration Manager.
   b. In SQL Server Configuration Manager, click SQL Server Services.
   c. Double-click the SQL Serverservice.
   d. In the SQL Server Properties dialog box, click the Advanced tab.
   e. On click the Advanced tab, locate the Startup Parameters item.

f. Add –T902 to the end of the existing string value, and then click OK.
g. Right-click the SQL Serverservice, and then click Start.

2. Open SQL Server Management Studio, and then connect to the instance of SQL Server 2008.
3. Run the following statements:

EXEC sp_configure 'affinity mask',0
RECONFIGURE;
GO

4. In SQL Server Configuration Manager, right-click the SQL Serverservice, and then click Stop.
5. Remove trace flag 902 on the instance of SQL Server 2008. To do this, delete –T902 from the string value that you updated in step 1f.
6. Right-click the SQL Serverservice, and then click Start.

Note:-

Suppose this is also not working you needs to restore the master database from backup.