Inspiring

Answered

RH2022 - Can't create output on an SSD

Forum|Forum|1 year ago
July 9, 2024
4 replies
554 views

I have RH 2022.4.179. When I try to build output (I've tried Frameless and Responsive) to an external SSD, I always get error "EISDIR: illegal operation on a directory, readlink," which is a nodejs error where it's trying to read a directory like it's a file. I can create output on my "HD" (which is an SSD), and on an external disk-type HD - why not on external SSD's? The project is simple, basically just a test project with a few simple htmls. Does anyone know of any limitations? Both the extrnal HDs that fail are exFAT, not ntfs.

__PRESENT

__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT

This topic has been closed for replies.

Correct answer Jeff_Coatsworth

You've probably identified the issue - it's the file system being used. But you can confirm that with the RH folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

Peter Grainge

Community Expert

Having reformatted my SSD to NTFS, the project on that drive now generates correctly as does the one on D Drive generating to the SSD.

________________________________________________________

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

Interesting. I hadn't realised my SSD was exFAT. Currently backing it up and will reformat it tomorrow and test again. It looks like what used to be is no more and the formatting is the issue.

________________________________________________________
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

RoboHelp is designed to generate the output to the same drive as the project. To get it on another partition or drive, you need to then publish it. That can be done by using the Publish feature or a simple copy.

That said, what you are seeing is not what I would expect and not what I get when I try the same thing. I just see a dialog saying the generation failed. Are you a Windows user or Mac?

For test purposes, generate to the same partition/drive and see what happens.

Otherwise it is as @Jeff_Coatsworth has suggested.

Let us know how you get on.

________________________________________________________

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.

D

deltechwriterAuthor

Inspiring

I'm on Win 11. My project is on the same external HD as the output folder, but RH just won't create complete output there. Up one folder, down one folder, should be simple. It creates some files, but does not finish. If you right-click on the output preset name and View Log, that's where I found the error.

Peter Grainge

Community Expert

I thought you were working on different drives.

I have just tried generating from D drive (a partition) to X drive, an SSD. and that fails.

I also copied the project from the D drive to the X drive and generated to the X drive. Again if failed.

In both cases the log gives this error. (Right click the preset to access the log).

The generation is fine when both project and output are on my hard drive. I think the answer you will get is both project and output must be on the hard drive. Let us know.

________________________________________________________

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.

Jeff_Coatsworth

Correct answer

Community Expert

You've probably identified the issue - it's the file system being used. But you can confirm that with the RH folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

D

deltechwriterAuthor

Inspiring

Yeah, I have a sneaking suspicion it's an unintended consequence of their build stream - something losing a race, maybe (like the internal build system looking for a file before the file system says it's there). I'll try the support people.

Peter Grainge

Community Expert

Let us know what they tell you. It has always been the case you should generate to the same partition/drive for the last twenty years or so.

________________________________________________________

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.

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