Problem: SAP Content Server Comes to a Standstill 

If an SAP Content Server in productive use comes to a sudden standstill, it is more important to try to solve the problem quickly than to establish the exact cause. This section describes a possible procedure for resolving a Content Server standstill.

Procedure

...

       1.      For example, check in the Database Manager GUI, whether the Log Area or the Data Area is full. For information on Content Server standstills and the fill level of the database instance, see Monitoring the Fill Level of the Database Instances.

○       If the log area is full or almost full (>95 %),

make a Log Backup.

Once some of the log entries have been backed up, you can continue working with the content server.

To ensure that the log area does not become full again, you should activate the Automatic Log Backup.

○       If the data area is exhausted:

It must be increased in size ( Creating, Displaying, and Deleting Volumes).

       2.      Check the capacity of the database instance again.

       3.      Restart the Web service, as described in Starting and Stopping the Content Server Correctly.

       4.      Restart the database host.

You should also make a note of the incident, including the date and time, the server name, and how you solved the problem, so that you can trace the cause if errors become more frequent.

Other Possible Causes of the Problem

Check the following in the ISS Management Console:

●      Do the port numbers on the SAP system and the Content Server match?

●      Are the website settings correct?

●      Does the virtual directory “ContentServer” still have execution authorization?

●      Is the site active?

●      Have you checked that the security settings are correct?