Troubleshooting - Database Server#

SQL Reporting Services#

SQL Server Reporting Services is a server-based report generation software system that can be used to prepare and deliver a variety of interactive and printed reports. It is administered via a web interface.

There are two methods for checking if the SQL Reporting Services is working properly:

SQL Reporting Services Windows Service#

1. Login on the Database server.
2. Click on Start, Execute and type Services.msc.
3. A new windows appears where all the system services are displayed with the actual service state.
4. Look for the SQL Reporting Services service.
5. Check for the service status column. This column value must be Started. If not, right-click on the service and click on Start.

SQL Reporting Services website#

1. Open the browser and type the report administration address. Refer to Analytics Security for more information about the report administration address.
2. If the SQL Server Reporting Services is displayed, the service is running properly. If the browser returns an error, follow the steps described in the 1st Method to start the SQL Server Reporting Services service.

Refer to Reporting Services Troubleshooting ⧉ for more information.

Resolving the Maximum Request Length Exceeded Exception in SQL Server Reporting Services#

When attempting to use a report while supplying a very large parameter (with 39k Products in this example), the following error might be occur:

By default, the maximum file size that can be deployed to SQL Server Reporting Services is 4 megabytes. We will now walk through the steps on how to resolve this issue:

1. Go to the ReportServer sub-directory where SQL Server Reporting Services is installed. In this example, the path to the ReportServer directory is C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer:

   

2. Open the web.config file with a text editor such as Notepad or Visual Studio. Search the web.config file for httpRunTime and add maxRequestLength with a file size in bytes. In this example we are setting the maxRequestLength to 8388608 which is 8 MB. Save the web.config file:

   

3. Save the web.config file and keep in mind that the changes to the web.config file do not become effective until Reporting Services is restarted!

SQL Server Browser#

SQL Server Browser runs as a Windows service on the server. SQL Server Browser listens for incoming requests for SQL Server resources and provides information about SQL Server instances that are installed on the computer.

There are two methods for checking if the SQL Server Browser is working properly:

SQL Server Browser Windows Service#

1. Login on the Database server.
2. Click on Start, Execute and type Services.msc.
3. A new windows appears where all the system services are displayed with the actual service state.
4. Look for the SQL Server Browser service.
5. Check for the service status column. This column value must be Started. If not, right-click on the service and click on Start.

SQL Server Browser in SQL Server Management Studio#

1. Open the SQL Server Management Studio.
2. Open the Server Name combo box, and click on Browse for more.... A dialog window appears.
3. Click on the Network Servers tab and wait a few seconds when the list box is refreshed.
4. Look for for the Critical Manufacturing SQL Server Database Instance. If the database instance is in the list, the SQL Server Browser is running properly. If the server instance is not on the list, follow the steps described in the 1st Method to start the SQL Server Browser service.

Refer to SQL Server Browser Service ⧉ for more information.

SQL Server Agent#

SQL Server Agent is a Microsoft Windows service that executes scheduled administrative tasks, which are called jobs.

There are two methods for checking if the SQL Server Agent is working properly:

SQL Server Agent Windows Service#

1. Login on the Database server.
2. Click on Start, Execute and type Services.msc.
3. A new windows appears where all the system services are displayed with the actual service state.
4. Look for the SQL Server Agent services (Online and ODS).
5. Check for the services status columns. The column values must be Started. If not, right-click on the service and click on Start.

SQL Server Agent in SQL Server Management Studio#

1. Login to the SQL Server Management Studio.
2. Look for the SQL Server Agent. It should look like this picture:
3. If the SQL Server Agent looks like , right-click on the SQL Server Agent and click on Start.

If you have problems with the execution of a SSIS package in SQL Server Agent, see the Troubleshooting: SSIS Package Execution Using SQL Server Agent ⧉ for more information.

SQL Server VSS Writer#

SQL Server provides support for Volume Shadow Copy Service (VSS) by providing a writer (the SQL writer) that can be used to back up database files.

To check if the SQL Server VSS Writer is working properly, follow the steps:

1. Login to the Database server.
2. Click on Start, Execute and type Services.msc.
3. A new windows appears where all the system services are displayed with the actual service state.
4. Look for the SQL Server VSS Writer service.
5. Check for the service status column. This column value must be Started. If not, right-click on the service and click on Start.

Please refer to the section Integration Services Troubleshooting ⧉ for more information.

SQL Server#

Microsoft SQL Server is a Windows service that provides a relational model database server. There are two methods of checking if the SQL Server Browser is working properly:

SQL Server Windows Service#

1. Login to the Database server.
2. Click on Start, Execute and type Services.msc.
3. A new windows appears where all the system services are displayed with the actual service state.
4. Look for the SQL Server (Online and ODS) service.
5. Check for the services status columns. The column values must be Started. If not, right-click on the service and click on Start.

SQL Server in SQL Server Management Studio#

1. Login to the SQL Server Management Studio.
2. Look for the server icon. It should look like this figure:
3. If the SQL Server instance looks like , right-click on the SQL Server instance and click on Start.

Replication#

For more information about troubleshooting on replication system, see Replication.

Data Purge#

The Data Purge job removes data for terminated entity instances from the MES Database database for which the retention time has been reached.

To check if the Purge Job is working properly, follow the steps:

1. Login on the SQL Server Management Studio.
2. Expand the SQL Server Agent and then expand the Jobs tree node.
3. Lookup for the Purge Entity Types job. right-click in the job and click on View History. The job's history is displayed.
4. In the job's history, if everything went right, all lines must have a icon. If there are some instances with , expand the message and click on the step or steps marked with . In the lower pane, check the error details to figure out how to solve the problem.