Inspiring

Answered

Presets corrupted and unable to create new ones 2022 Update 2

Forum|Forum|2 years ago
April 28, 2023
4 replies
455 views

Hi there,

we already updated on all seats and all worked fine at first. But now, after the last member in a common project started working on files we're experiencing a weird phenomenon: all preset files seem to be corrupt and are not showing in the Output panel even though the files are still there in the local project folders. And we can't create a new preset either!
Looking at the XML data everything seems to be fine. What could have gone wrong here before committing and pushing the first change made in a preset file with the RH 2022 Upd 2 to our Git repository?

This topic has been closed for replies.

Correct answer gbr_555

Aaaaaah - problem found: two newly edited preset files were corrupted by setting a path to a OneDrive folder. Now that I thinnk about it, that seems to be reasonable. Setting paths to cloud space should be prohibited in the dialog.

Peter Grainge

Community Expert

Glad you found it.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.

Peter Grainge

Community Expert

I hate asking questions like this but can you please check that all machines are showing 2022.2. If one machine did not update correctly, I wonder if that could cause corruption.

Are the problems on all machines? Would you agree that seems like some corruption in the source control? One idea is to pull a full copy to a new folder on one machine and see if the presets are OK. If they are copy them to the rogue folder using Explorer and see if they then hold good.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.

G

gbr_555Author

Inspiring

Update was correct at all seats - it was two corrupt preset files that disturbed loading all the others, too.

Peter Grainge

Community Expert

The thread you posted in should have been locked as it is not intended to be a general thread for any 2022.2 issues. One thread for all would be a nightmare. 🙂

I have branched it into a new thread. Existing links to your post should still work.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.

G

gbr_555Author

Inspiring

What's confusing here: In other projects that we converted from 2022.1 to 2022.2 all presets are okay - those predefined when a project is set up, and those we created in former RH releases.
The preset files we try to create in the "broken" project seem to be created in the backend but the dialog does not come up for definitions. That goes for all types of output presets.

G

gbr_555AuthorCorrect answer

Inspiring

Aaaaaah - problem found: two newly edited preset files were corrupted by setting a path to a OneDrive folder. Now that I thinnk about it, that seems to be reasonable. Setting paths to cloud space should be prohibited in the dialog.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded