Trying to compile to Word .docx, which I have done hundreds of times prior, but now I am consistently getting the attached error. What has changed in the last week?
The .doc converter is also not working. I have disabled my anti-virus and reattempted the conversion with the same results.
Hi Sp33dMan and welcome to the forum.
To the best of my knowledge, nothing on the Scrivener side has changed in the last week.
However, I have seen Win 10 updates on my PC, MS Office updates on my Mac, and anti-virus updates on both of my systems.
I’d start by checking your computer’s anti-virus, firewall, proxy, VPN, and other security tools to see if any of them were updated and are now blocking Scrivener or one of its components.
A lot of those updates ran in the background, so they might not be easily identified. But, if Scrivener isn’t blocked in the quarantine files and Word works fine otherwise, we can do some additional troubleshooting with this Scrivener project.
My next test would be to see if this error is only seen when you’re compiling this project or if it happens in multiple Scrivener projects.
If you only have one Scrivener project, you might try opening Scrivener’s Interactive Tutorial from its Help menu. Scrivener will ask you to name the file and choose a save location for it. Since this is just a test, you can save it to your Desktop. Then, please see if it will compile.
If the Tutorial does not cause this same error, then it is possible that your project has some flaw.
You could create a new project using this same project template and then open the new project side by side on your computer with the existing project. You could drag the contents of the existing project’s Binder into the new project and test that new project.
Does the error occur again? If it does not, then you can use this new project as your working project.
If the compile error happens in the second project, then we can narrow it down to something project-specific and start looking at items you’ve recently imported or text you’ve added since the last successful compile.
I was finally able to make it work by getting rid of my versioning numbers. The compile started dropping the basic file extension and using my versions number as the extension.
Now this will just cause issues being able to tell which version I am looking at.
Were you adding version numbers in the file name with a dot, as e.g. “Version 1.00”? That would confuse the system into treating the text following the period a an extension, but you should be able to work around it easily then by just using a different character, eg. “Version 1-00”.