RTM (no SP) | SP1 | SP2 | SP3 | SP4 | |
---|---|---|---|---|---|
![]() codename ? | CTP2.3 | ||||
![]() codename | 12.0.2000.8 | 12.0.4100.1 or 12.1.4100.1 | |||
![]() codename Denali | 11.0.2100.60 | 11.0.3000.0 or 11.1.3000.0 | 11.0.5058.0 or 11.2.5058.0 | ||
![]() codename Kilimanjaro | 10.50.1600.1 | 10.50.2500.0 or 10.51.2500.0 | 10.50.4000.0 or 10.52.4000.0 | 10.50.6000.34 or 10.53.6000.34 | |
![]() codename Katmai | 10.0.1600.22 | 10.0.2531.0 or 10.1.2531.0 | 10.0.4000.0 or 10.2.4000.0 | 10.0.5500.0 or 10.3.5500.0 | 10.0.6000.29 or 10.4.6000.29 |
![]() codename Yukon | 9.0.1399.06 | 9.0.2047 | 9.0.3042 | 9.0.4035 | 9.0.5000 |
![]() codename Shiloh | 8.0.194 | 8.0.384 | 8.0.532 | 8.0.760 | 8.0.2039 |
![]() codename Sphinx | 7.0.623 | 7.0.699 | 7.0.842 | 7.0.961 | 7.0.1063 |
Ads
23 September 2015
SQL Server Version List
22 September 2015
The version of the report server database is either in a format that is not valid, or it cannot be read.
Problem :
The
version of the report server database is either in a format that is not valid,
or it cannot be read. The found version is '163'. The expected version is
'162'. (rsInvalidReportServerDatabase)
Solution:
1. Verify the ReportServer Database compatibility.
2. Change the Compatibility to previous version and restart the services.
3. If the above fails check the RSEXEC role has been granted for the DBO
- Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases.
- In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles.
- Right-click db_owner, and click Properties.
- On the Database Role Properties page, click Add.
- On the Select Database User or Role page, type RSExecRole, and then click OK twice.
- Repeat these steps with the ReportServerTempDB.
- Restart the SSRS Services.
4. If above is already in place then it could be the latest security patch applied on the SQL Server.
5. Verify any CU/Hotfix which has been applied and caused the issue.
6. Rollback the patch or if its on cluster apply the same patch on the other node too.
Note: Even though SSRS is not a cluster aware component But this security patch will also apply on the SQL Server and makes SSRS to stop working.
01 August 2015
COM Surrogate has stopped working" while viewing photos in Windows Photo Viewer Win7 64 Bit
ERROR:
Solution :
Step 1: open CMD with elivated privilages
Step 2: Run the below commands one by one.
C:\>regsvr32 vbscript.dll
C:\>regsvr32 jscript.dll
C:\>regsvr32 jscript.dll
regsvr32 vbscript.dll regsvr32 jscript.dll
28 July 2015
Could not redo log record - DB is SUSPECT Mode
We recently faced this issue after the maintenance window. The user database went to suspect mode and it was unable to bring online due to below error.
This case we rebuilt the logfile, to bring the DB online.
ERROR
Could not redo log record (1327929:29486:115), for transaction ID (1:1223281085), on page (1:1333024), database 'TestDB2 ' (database ID 8). Page: LSN = (1327558:113348:307), type = 2. Log: OpCode = 5, context 29, PrevPageLSN: (1327929:29486:18). Restore from a backup of the database, or repair the database.
Msg 3313, Level 21, State 2, Line 1
This case has only below options:
1. Restore the DB from the backup strategy.
2. Try DBCC REPAIR with REPAIR_FAST | REPAIR_REBUILD (No Data Loss)
3. Final is REPAIR_ALLOW_DATA_LOSS
Alternate Solution:
===================
ALTER DATABASE TestDB2 REBUILD LOG ON (NAME=TestDB2_Log, FILENAME='D:\SQLLog\TestDB2_Log.ldf')
dbcc checkdb (testdb2)
ALTER DATABASE testdb2 SET MULTI_USER
Note: This approach might lead to data loss. Make sure we have enough backups in place.
This case we rebuilt the logfile, to bring the DB online.
ERROR
Could not redo log record (1327929:29486:115), for transaction ID (1:1223281085), on page (1:1333024), database 'TestDB2 ' (database ID 8). Page: LSN = (1327558:113348:307), type = 2. Log: OpCode = 5, context 29, PrevPageLSN: (1327929:29486:18). Restore from a backup of the database, or repair the database.
Msg 3313, Level 21, State 2, Line 1
This case has only below options:
1. Restore the DB from the backup strategy.
2. Try DBCC REPAIR with REPAIR_FAST | REPAIR_REBUILD (No Data Loss)
3. Final is REPAIR_ALLOW_DATA_LOSS
Alternate Solution:
===================
ALTER DATABASE TestDB2 REBUILD LOG ON (NAME=TestDB2_Log, FILENAME='D:\SQLLog\TestDB2_Log.ldf')
dbcc checkdb (testdb2)
ALTER DATABASE testdb2 SET MULTI_USER
Note: This approach might lead to data loss. Make sure we have enough backups in place.
27 July 2015
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452)
Solution :
1. Go to C:\Windows\System32\drivers\etc
2. Open HOSTS File in notepad (Run as Admin)
3. Add below lines:
127.0.0.1 localhost
127.0.0.1 mycomputername -- this will be computer name
4. Save and close the notepad.
5. Connect SQL Server
Source:
http://blog.sqlauthority.com/2012/09/06/sql-server-fix-error-cannot-connect-to-login-failed-the-login-is-from-an-untrusted-domain-and-cannot-be-used-with-windows-authentication-microsoft-sql-server-error-18452/
1. Go to C:\Windows\System32\drivers\etc
2. Open HOSTS File in notepad (Run as Admin)
3. Add below lines:
127.0.0.1 localhost
127.0.0.1 mycomputername -- this will be computer name
4. Save and close the notepad.
5. Connect SQL Server
Source:
http://blog.sqlauthority.com/2012/09/06/sql-server-fix-error-cannot-connect-to-login-failed-the-login-is-from-an-untrusted-domain-and-cannot-be-used-with-windows-authentication-microsoft-sql-server-error-18452/
Subscribe to:
Posts (Atom)
-
Find More On : - http://www.sqlserver-training.com/250-sql-queries-interview-question-answers/-#5+ SQL Queries Interview Questions ...
-
http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx#BKMK_requirements How accounts are created through wizards in ...
-
ERROR: report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the o...