Jump to content
LynnB

SERIOUS problem with random corrupt files

Recommended Posts

Hello,

Publisher 1.7.2.471. Windows 10

I have been trying to dedicate my workflow to move to Publisher from InDesign. I am having some serious doubts if Publisher is ready.

Today I have my second Pub file that all of the sudden goes bad. Working and saving (I save often out of habit) and all of the sudden, I get a dialog box (attached) that reads, "Failed To Save Document: <my file name>. Save failed due to internal error."

Some background on this file:
- Is a multi-page document with a lot of placed images.
- Image types are EPS, AI, and JPG
- I cannot save the file as when I try to, this same box pops up.
- I cannot SAVE AS the file as when I try to, this same box pops up.
- This time I was able to export the file as a PDF

Steps to try to resolve:
- I removed each placed file and found an offending file.
- Deleting that placed file worked...temporarily, meaning that I removed other files and then saved and got the message again.
- Now that initial offending AI file could be placed, but this time now an EPS file was causing issues
- Removing second offending file would allow me to save, WITH the first offending file placed.
- Offending files attached here
- Cutting offending AI file from document and placing in new document and saving worked fine. But, I add offending file 2 to new document, then I get the error on saving.
- If I place (cnt-shift-M) the EPS file in the new doc and save, it saves fine, for a few saves, then I get the error again. Very random.
- When doing this, I have both documents open and switch between docs with cntrl-tab (no idea if this matters to anything)
- Pasting the EPS file from the first document into the second causes the error.

Is there a support email address I can send my pub file to, rather than posting it in a public forum?

Hope to get this resolved as I'd like to use Publisher, but if I don't have confidence that it won't kill my files, I have to stick with InDesign.

Let me know if you need more information. Thanks,

Lynn

BD_Publisher_Bad_File_02.jpg

YourTownMonthlyLogo CMYK.ai

Sutter_Health_PAMF_2lines_clr_cmyk.eps

Share this post


Link to post
Share on other sites

Update. Just placed my offending EPS file in the same document, and then saved and this time I was offered a SAVE AS option. See attached.

Files are being saved to an internal SSD drive.

 

 

BD_Publisher_Bad_File_03.jpg

Share this post


Link to post
Share on other sites

I placed the offending files in a new Publisher document and have played with it for a while, adding random objects, saving and saving as, but no problems experienced so far. The offending files are just fine and very plain so I cannot see they could themselves cause any problems. 

Do you have a possibility to save your document on an external drive to see that is not an issue with hard drive? (On the other hand, if there is an issue, it might naturally affect also operation of applications on the computer.) Have you run any diagnostic tool on your hard drive?

Share this post


Link to post
Share on other sites

Just commiserating with you here....
I've run into the exact same dialog box, saved it out as PDF (since I hadn't saved as diligently as you), imported the PDF and discovered many of my text boxes much tighter than the originals. Could not reproduce in my case.

Also be careful, I've discovered that text in linked text boxes getting "lost" somewhere during modifications in other parts of the document.

I may just stick with InDesign for a little while longer.

Share this post


Link to post
Share on other sites

Thank you all for the replies.

@Lagarto - Don't have an external drive at my location to save to. I have ran diagnostics on my drive and all comes up fine. Publisher is the only program I have run into problems with. I have placed that file in other documents to test and really don't believe the issue is related to that particular file as I have run into this issue now multiple times without using that file.

@Brian - I am going back to InDesign until this can get figured out. Can risk having a file go bad without any sort of recovery file access.

@Pauls - Free space is 527GB.

I had a different file go bad on me today. Same error but nothing to do with those other files that I referenced, thus it is telling me the issue is not with the files being placed, but perhaps with Publisher.

I can no longer trust Publisher, so unfortunately I am going back to InDesign. I really wanted to believe in Publisher, but just can't right now with this major bug. I will give it a try after a couple more updates perhaps.

Not sure if sending in one of my bad files would help Affinity diagnose. Asked for email address to send to in initial post, if there is interest from them.

Open to other suggestions for what might be going on or what to try.

Thanks,
Lynn

 

Share this post


Link to post
Share on other sites

i assume you have tried to save files to a local drive (rather than a server location)?

I sometimes get a save error, but that is because the office shared servers have been set up badly - and give permission errors occasionally...

Share this post


Link to post
Share on other sites
14 hours ago, Lynn Bantley said:

@Lagarto - Don't have an external drive at my location to save to. I have ran diagnostics on my drive and all comes up fine. Publisher is the only program I have run into problems with. I have placed that file in other documents to test and really don't believe the issue is related to that particular file as I have run into this issue now multiple times without using that file.

Did I undestand correctly that you have experienced this error with very small files, as well (e.g., with newly created files where you have placed the kinds of single eps or ai files that you had attached in your post)? I can imagine that complex files may cause different kinds of problems, but if you have constantly experienced corruption problems also with small, newly created files, and you have run disk diagnostics on your drive, then there might be something wrong with the installation or Affinity-related registry entries, so uninstall/reinstall might help. 

Share this post


Link to post
Share on other sites

I noticed the following in the flix list of latest Designer and Photo beta (the equivalent beta has not been released for Publisher, yet):

"Fixed crash when install location contains a non-ASCII character"

Do you happen to have installed Publisher in custom location (I think that older Windows OS versions might also have localized standard paths)?

 

Share this post


Link to post
Share on other sites

I uninstalled and am reinstalling. As with the first install, I left the default install location as is. It is being installed to "C:\Program Files\Affinity\Publisher".

Not that it should matter, but all working files exist on my additional internal D drive. My folder structure for all of my files are saved in a "d:\_documents\<whatever client name folder>\<whatever job it is folder>". I'd hope that the underscore in the folder name would not cause an issue. If it did, I'd expect this weird behavior with all of my Pub files.

Thanks for your continued input on this issue!

 

Share this post


Link to post
Share on other sites

Does not really seem the problem could be related to "non-ascii" characters in file names (and at least in the installation path), but one never knows (e.g., InDesign may still fail to recognize an image file as a valid TIFF file if its file name contains a non-ascii character), so it was worth a try.

Just curiois: do you make much cross editing within Affinity apps, or have you experienced these problems also when you have edited the file with just Publisher? 

Share this post


Link to post
Share on other sites

Are all the linked files on the local drive too?

Any on drives connected with cloud storage ?


Living the Dream since 1964 - about 25 years left

Share this post


Link to post
Share on other sites

@Pauls - I am on all local drives that reside within my laptop.

@lagarto - When experiencing my issues, all work has been done in Publisher. Not using Studio Link if that is what you are referring to.

I removed and reloaded Publisher the other day as well as loading the current Beta, but am a little gun shy to use it for real work now that I have had this issue. Sticking to InDesign, but know I have to spend some time in Pub again to see if these issues remain.

Thanks for the support and questions guys.

 

Share this post


Link to post
Share on other sites

Thanks - could you let us know the make and model. The only things I can suggest is doing a disk check on the drives to make sure they are OK and maybe trying without any anti-malware or ant-virus software disabled to rule them out. Your file is saving just fine here.


Living the Dream since 1964 - about 25 years left

Share this post


Link to post
Share on other sites

Hope you manage to resolve the problem at some time. It sounds as if it could be a drive related yet you have not experienced problems with other software, and you mentioned you have run a diganostics tool on your drives. If you have separate physical disks for your C and D drive (rather than one physical disk partitioned to have two drives), I'd still try to saving the .afpub files on your C drive for a while to see if this resolves the problem.

 

Share this post


Link to post
Share on other sites

I ran some disk diagnostics, chkdsk, etc. All appears fine from doing so.

Drives are:
C: = AMD-RAID PC401 NVMe SK hy SCSI
D: = NVME Samsung SSD 970 SCSI

C is listed as RAID but I am not using any sort of RAID. Stock from Dell.

Just curious why all the talk about network drives and bad drives being a cause of this issue. Never experienced any sort of saving issues with software other than Affinity.

@Lagarto - Running two physical drives.

 

image.png

Share this post


Link to post
Share on other sites

The serialization issues are actually one of my main worries with Affinity apps. Serif has shown great promise feature-wise, but the bread-and-butter things seem to need some serious attention. Personally I am not too enthusiastic about the concept of across-editing capabilities and common file format, as easy exchange of data has not been much of a worry when using Adobe apps. Editing is never far away, and e.g. most of the Illustrator objects can be copied across to InDesign using the Clipboard, etc.

But file corruption is a serious problem, and securing that you do not easily lose your job is one thing that Adobe has done right, starting from CS v.1 (those who are old enough to remember what it used to be like with PageMaker know what I am talking about). So that's why I have been curious to know what could be the reason for the problems you have experienced.

I have not experienced any i/o related problems with Affinity apps myself, and I have not seen many posts that report these kinds of problems, but there are posts that report problems with unexpectedly big file sizes, linking/embedding and especially importing files from cloud resources, problems related to across editing, etc., so this is one of the issues that I am following very closely.

I'd appreciate if you could have patience and continue troubleshooting these issues for a while, as I think this could help us all to have a true alternative in this business!

Share this post


Link to post
Share on other sites

>>I'd appreciate if you could have patience and continue troubleshooting these issues for a while, as I think this could help us all to have a true alternative in this business!<<

Absolutely. I'm patient with this stuff. Hope I didn't sound impatient. :)

Since I had a few files go bad, I have resorted back to InDesign, but will try to fit a few simpler jobs into using Pub. Just can't risk doing a lot of work then getting stuck like this again.

I'd love to see Affinity succeed and be a direct competitor to the other company. 

Thanks for all of your input!

Share this post


Link to post
Share on other sites

What is strange is that you seem to have received different kinds of error message related to the same problem (inability to save an already saved file), at least one related to user privileges, and one related to internal error. 

One thing that could poterntially have effect on an application's ability to save files that it has opened is having a background task that e.g. creates backup copies of documents, or an antivirus application that controls access of apps to certain locations on the system. For that purpose there might be point in saving in a location on your D drive that such apps are not watching for their operations.

.If you typically save to a custom location on your D drive, does the problem also appear if you save somewhere along your "My documents" folder path?

Do you have "My documents" (the system default folder for user documents) still on you C drive, or have you moved its location to the D drive?

Share this post


Link to post
Share on other sites

Ok, then it seems less likely that this is in any way affected by a security feature like Windows or Bitdefender watched folders that control's "suspicious" file activity (as this typically involves only access to standard paths).

I have created now a 300 page document with about 220 pages text and about 100 print-quality photos (producing a very manageable file size of 32MB), in purpose of testing how Publisher copes with such a document (seeing if the file gets absurdly big at some point, as there have been reports of these kinds of problems, or if it gets corrupt at some point when editing and saving the content), but so far no problems. However there seems to be some law according to which such test files never fail, and when I actually need to deliver something real, only then things get broken. Anyway, to add the risk for vulnerability, I have placed this file under the standard system dcouments path.

Share this post


Link to post
Share on other sites

I migrated from pageplus to publisher, so a lot of my publisher files are very large (based on the fact they were opened pdf files and then manually converted to publisher).

Some of my files are 900mb in size with 140 pages and embedded images (rather than linked) and so far, it has worked without issue. I save regularly and create pdf versions regularly (in case of future corruption) but have not needed to recover any so far...

I use publisher every day on a dell - and never have any of the issues you mention. I know this doesnt specifically help you, but its to demonstrate this might be a local issue rather than a programming issue.

Share this post


Link to post
Share on other sites

Follow-up on this thread.

Last week rebuilt my windows computer from scratch...SSD formatted, and then fresh install of Win 10 1903, drivers, updates, and all software. 

Running the latest 1.7.3 Publisher. Worked up the courage to create a job, and BOOM!...thirty minutes into the job, a corrupt file. Could not save!

I started removing placed eps files and found one that when removed, allowed me to save the file. Pasting same file back in then causes the file to go corrupt. Doing a new placement of the EPS file I can then save...for the time being. When this happened to me previously, I thought I found the offending file, but it was a false positive as later on another file, that was already placed in the document, became an offender.

Very random.

So, I am stepping away from Publisher now with a strong No confidence vote, and returning to InDesign. I really want to give Pub a good run but will not subject my workflow to this fear of corruption. Perhaps a couple versions down the line I will try again. :(

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.