I imported content from staging to PROD - got all the content, tags, sitemap etc. The html content publishes fine but I cannot publish the content records that contain PDFs.
Here is the error in the publishing server log for one of the records:
Unable to publish file Agenda: Object reference not set to an instance of an object.
Location: Asi.Business.ContentManagement.Publishing.PublishProcess.CopyFile
Any help?
Eric,
If I export content from the site, restore the database to when there was no WCM content and import the files again, I should be able to publish them, correct? I am wondering if purging the content from the site did not delete the corresponding row in the DocumentStorage table?
I tried this using a couple content records and it worked but I want to be sure.
Thanks!
That won't work -- the problem is that the DocumentStorage rows (which ContentFile depends on) don't get included in the export, so when you import them into the production server, those rows don't get imported/created, which is what causes the failure -- the issue is that the rows are not there, not that they are there improperly.
I think the problem is that the updatedbyUserKey and createdbyUserKey that I have in DEV do not exist in PROD. That is why when import/export is done within the same site, it works but not when its done from DEV to PROD.
What do you think?
I believe the Updated By and Created By user keys get replaced by the user key of whoever you're logged in as when you import the objects, so that shouldn't be a problem.
To test it, you could create a blank content record (fill in title, but don't add any web parts) on the dev server as a user who doesn't exist on the prod server, export it, and import it into the prod server. If that works, the userkeys aren't the issue.
I've seen the issue from a few other folks and I'm fairly certain the DocumentStorage rows not existing in the production server are the issue, if the only ones you can't publish are the ones using ContentFile.
I agree with you on the DocumentStorage rows not existing. My guess is that the rows do not get created because of the Userkey not exsiting in PROD. Will test some more.
Thanks for your help, Eric!
They don't get created because no code was ever written to include them in the exported XML (and the import code was never updated to understand how to import them, either).
As I said, you will need some manual process (your choices being manually editing each affected web part and re-uploading the file, OR manually copying the contents of the DocumentStorage table from staging to prod, e.g. by using bcp or similar) to move the information to the production server.
We have customers with thousands of pdfs. This defect will stop them from being able to implement WCM. We need this fixed.
The problem is that the
The problem is that the DocumentStorage rows do not get included in the export/import (this is a bug and ASI Tech Support is aware of it).
If you can edit the ContentFile web part(s) in question, you can reupload the missing file and the record should publish correctly.
Alternately, you could bulk-copy the DocumentStorage table from your dev database to your production database, then republish the affected content records.