Reputation: 599
Sometime publishing fails during Transporting phase with error:
Could not transport tcm_0-333793-66560.Content.zip using HTTPS,cause: "Internal Server Error".
In cd_transport log, the error is:
2012-10-30 06:34:16,778 ERROR HTTPSTransportConnector - An unexpected error occurred while retrieving: "http://deployer/httpupload.aspx reason: Internal Server Error"
2012-10-30 06:34:16,793 ERROR HTTPSTransportConnector - Unable to send TransportPackage to url: "http://deployer/httpupload.aspx cause: Internal Server Error"
2012-10-30 06:34:22,600 ERROR HTTPSTransportConnector - An unexpected error occurred while polling: "http://deployer/httpupload.aspx reason: Internal Server Error"
After publishing again, I am able to publish the failed pages.
After setting the log level to "Debug" getting below information in 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
No information in cd_deployer.log file related to publishing error. It 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 IIS log:
In HTTPUpload log file, I can see the log details with status as 200 , 401 and 500. 200 being in large scale but their are also details with the status as "401" and "500".
Error details are
"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"
Upvotes: 4
Views: 1706
Reputation: 1584
It is related to maximum size limit on your deployer.Look at the deployer logs. Hope by increasing maxRequestLength and maxAllowedContentLength your problem get resolved.
Upvotes: 3