Publishing stuck to waiting for deployment

Question

i have configured 2013 sp1 into the environment. At the time of publishing my pages has got stuck into the publishing queue with "waiting for deployment status". I am not able to understand the problem. i have successfully transported the package but unable to deploy it.

Please find the cd_core.log file errors below

Retrieving list of files from location: {C:\inetpub\Deployment_Test} with extension{.progress} 2014-12-13 13:34:15,416 DEBUG HttpUpload - Retrieving list of files from location: {C:\inetpub\Deployment_Test} with extension{.progress} 2014-12-13 13:34:15,416 DEBUG HttpUpload - Found {0 } files in folder {C:\inetpub\Deployment_Test} 2014-12-13 13:34:15,416 DEBUG HttpUpload - Found {0 } files in folder {C:\inetpub\Deployment_Test} 2014-12-13 13:34:15,432 DEBUG HttpUpload - Retrieving list of files from location: {C:\inetpub\Deployment_Test} with extension{.Content.zip} 2014-12-13 13:34:15,432 DEBUG HttpUpload - Retrieving list of files from location: {C:\inetpub\Deployment_Test} with extension{.Content.zip} 2014-12-13 13:34:15,432 DEBUG HttpUpload - Found {21 } files in folder {C:\inetpub\Deployment_Test} 2014-12-13 13:34:15,432 DEBUG HttpUpload - Found {21 } files in folder {C:\inetpub\Deployment_Test} 2014-12-13 13:34:15,463 INFO HttpUpload - Received incoming file with name: tcm_0-189-66560.Content.zip 2014-12-13 13:34:15,463 INFO HttpUpload - Received incoming file with name: tcm_0-189-66560.Content.zip 2014-12-13 13:34:15,463 DEBUG HttpUpload - Storing incoming file in destination: C:\inetpub\Deployment_Test\tcm_0-189-66560.Content.zip_tmp 2014-12-13 13:34:15,463 DEBUG HttpUpload - Storing incoming file in destination: C:\inetpub\Deployment_Test\tcm_0-189-66560.Content.zip_tmp 2014-12-13 13:34:15,463 DEBUG HttpUpload - Moving Tmp file to C:\inetpub\Deployment_Test\tcm_0-189-66560.Content.zip is successful. 2014-12-13 13:34:15,463 DEBUG HttpUpload - Moving Tmp file to C:\inetpub\Deployment_Test\tcm_0-189-66560.Content.zip is successful. 2014-12-13 13:34:19,009 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:19,009 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:24,042 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:24,042 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:29,084 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:29,084 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:34,106 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:34,106 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:39,122 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:39,122 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:44,155 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 2014-12-13 13:34:44,155 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request

Answer 1

The error you found suggests your cd_deployer_conf.xml configuration file is invalid; could you post the contents of this file here (or better yet; try with the sample file provided by Tridion?)

Answer 2

Waiting for deployment usually means the Publishing Service finished rendering the content and it is trying to contact the Deployer to tell it to deploy the content. The deployer is usually running as its' own website or sometimes configured to run as a Windows Service. I would suggest to open the Publication Target and see the URL of the Deployer and try to connect to it from the CMS Publisher Server.