SQL SERVER DBA, Linux and Azure

SQL Server Reporting Service Start Error 1053 The Service Did Not Respond

Reporting Server Error 1053: The service did not respond to the start or control request in a timely fashion.


Solution

1. Open regedit

2. Locate here : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. Change ServicesPipeTimeout value.

If the ServicesPipeTimeout entry does not exist, you have to create it. You can follow add steps like below.

Add Step 1: Below Control section Edit > New > DWORD Value.
Add Step 2: Type ServicesPipeTimeout
Add Step 3: Right-click ServicesPipeTimeout and click Modify.
Add Step 4: Decimal 60000, OK
This value represents the time in milliseconds before a service times out.


4. Restart computer.

Result


SQL SERVER – ERROR MESSAGES (severity levels)

Each error message displayed by SQL Server has an associated error message number that uniquely identifies the type of error. The error severity levels provide a quick reference for you about the nature of the error. The error state number is an integer value between 1 and 127; it represents information about the source that issued the error. The error message is a description of the error that occurred. The error messages are stored in the sysmessages system table.

We can see all the system messages running following statement in query analyser.

SELECT * FROM master.dbo.sysmessages

The severity level are displayed in the table below.

0 to 10             Messages with a severity level of 0 to 10 are informational messages and not actual errors.

11 to 16           Severity levels 11 to 16 are generated as a result of user problems and can be fixed by the user. For example, the error message returned in the invalid update query, used earlier, had a severity level of 16.

0 to 10             Messages with a severity level of 0 to 10 are informational messages and not actual errors.

11 to 16           Severity levels 11 to 16 are generated as a result of user problems and can be fixed by the user. For example, the error message returned in the invalid update query, used earlier, had a severity level of 16.

17                    Severity level 17 indicates that SQL Server has run out of a configurable resource, such as locks. Severity error 17 can be corrected by the DBA, and in some cases, by the database owner.

18                    Severity level 18 messages indicate nonfatal internal software problems.

19                    Severity level 19 indicates that a no configurable resource limit has been exceeded.

20                    Severity level 20 indicates a problem with a statement issued by the current process.

21                    Severity level 21 indicates that SQL Server has encountered a problem that affects all the processes in a database.

22                    Severity level 22 means a table or index has been damaged. To try to determine the extent of the problem, stop and restart SQL Server. If the problem is in the cache and not on the disk, the restart corrects the problem. Otherwise, use DBCC to determine the extent of the damage and the required action to take.

23                    Severity level 23 indicates a suspect database. To determine the extent of the damage and the proper action to take, use the DBCC commands.

24                    Severity level 24 indicates a hardware problem.

25                    Severity level 25 indicates some type of system error.







Finding Fragmentation script in SQL Server

select
object_schema_name(ps.object_id) as ObjectSchema,
object_name (ps.object_id) as ObjectName,
ps.object_id ObjectId,
i.name as IndexName,
ps.avg_fragmentation_in_percent,
ps.page_count
from sys.dm_db_index_physical_stats(db_id(), null, null, null, null) ps
inner join sys.indexes i
on i.object_id = ps.object_id and
i.index_id = ps.index_id
where
avg_fragmentation_in_percent > 5 -- reorganize and rebuild
and ps.index_id > 0
order by avg_fragmentation_in_percent desc