Deploying not happening in publishing process

3
votes

I am trying to publish to local file system, however publishing is not happening properly and its failed to deploy in my 2011 GA VM environment.

I am getting "Polling for notification for destination: YTnMgU6u5Vh09cOGUG7ouA== has exceeded polling attempts for transaction: tcm:0-121257-66560" error in "Preparing Deployment" stage.

I have used the “Local File System” protocol in my publication target and I have provided path like d:\tridion\publish.

And I have provided the same path in cd_storage_conf.xml under the <storage type=”filesystem”>. All other storage types are commented.

And in cd_deployer_conf.xml , quee location path is c:\tridion\incoming.

When I publish any page into my publication target, the zipped package is placed in the d:\tridion\publish and it’s not deployed.

Do I need to do any other thing to deploy the zipped package?

2
tridiontridion-2011tridion-content-delivery
Do you have a deployer service running? Is it reading from the incoming folder? Is there a cd_core log or cd_deployer log with errors? - Quirijn
Shouldn't the path for the Local File System protocol and the Deployer queue location be the same? At the moment your package is being created somewhere the Deployer isn't monitoring. - Neil
@@Quirijn: I dont have the deployer service in the VM. At the same time in my VM some other publication targets are there and those are using https protocol and they are storing the contents in the broker db. the zipped package is placed in the path what i give in the publication target only. - user1428019

2 Answers

6
votes

The path provided in the cd_deployer_conf.xml (the one you specify in Queue/Location!!!) needs to be the same one you provide in your publication target (in your case you have in the publicationTarget some path on D drive while in the deployer conf you have another one from C drive). Then you also need make sure that your deployer is initialized. You can easily determine if your deployer is initialized by looking if the meta.xml is regenerated in the deployer incoming folder.

Not sure if this is relavant but you might be interested also in how to install the deployer: as a .NET WebSite, as a Java WebSite or Windows Service

Hope this helps.

2
votes

You say your working sites use HTTP sender/deployer. In that scenario your deployer is triggered by the HTTP servlet which receives the transport package.

When you use local file system - you MUST configure your deployer to work in a different way. It has to run as some form of background service. Typically on a windows box this means installing the deployer as a windows service. Keep in mind that this will then probably have additional config files for the deployer and broker/storage.