Sometimes a publication fails during the transport phase with the error "Internal server error"

Sometimes a publication fails at the transportation stage with an error:

Failed to transfer tcm_0-333793-66560.Content.zip using HTTPS, call: "Internal server error".

In cd_transport log error:

2012-10-30 06: 34: 16,778 HTTPSTransportConnector ERROR - An unexpected error occurred while receiving: "http: //deployer/httpupload.aspx reason: Internal Server Error"

2012-10-30 06: 34: 16,793 ERROR HTTPSTransportConnector - Cannot send TransportPackage to url: "http: //deployer/httpupload.aspx reason: Internal server error"

2012-10-30 06: 34: 22,600 HTTPSTransportConnector ERROR - an unexpected error occurred during polling: "http: //deployer/httpupload.aspx reason: Internal Server Error"

After posting again, I can post the failed pages.

After setting the log level to "Debug", getting below information in the cd_core.log file

2012-10-30 11:47:39,260 ERROR HTTPSTransportConnector - Unable to send TransportPackage to url: "http://deployer/httpupload.aspx cause: Internal Server Error" 2012-10-30 11:47:39,260 DEBUG TransportPoolManager - "Connector is registered for reuse: HTTP[Password[******], UserName[server\tridion], URL[http://deployer/httpupload.aspx]] available: 1" 2012-10-30 11:47:39,260 DEBUG ParallelDestinationWorker - Received item from transport destination: yyK/eL9dJ29chwTx2vRFrQ== 2012-10-30 11:47:39,260 INFO TransportItem - Received transport feedback, transport state is: failed=true for transaction: tcm:0-334545-66560 

There is no publication error information in the cd_deployer.log file. He just says

  2012-10-30 11:58:23,249 DEBUG TransactionHeader - Writing[TransactionHeader transactionId=tcm:0-334566-66560 control=COMMIT] to C:\Temp\tcm_0-334566-66560.Content\transaction.xml 

Information in the IIS Journal:

In the HTTPUpload log file, I can see the log data with the status of 200, 401 and 500. 200 are on a large scale, but they also contain information about the status of "401" and "500".

Error Details:

  "2012-10-31 12:54:39 W3SVC1485900680 100.100.100.100 GET /httpupload.aspx fileName=tcm_0-337505-66560.state.xml&action=remove 80 - 192.168.168.14 - 401 2 2148074254" 
+4
source share
1 answer

This is due to the maximum size limit of your deployer. Look at the deployment logs. Hope by increasing maxRequestLength and maxAllowedContentLength, your problem will be solved.

+3
source

Source: https://habr.com/ru/post/1442921/


All Articles