generating output files: MyWebHelp, MyMSWord

[Paul-NY]

Hi
When using Build Primary previously, I have been able to successfully generate MyWebHelp, MyMSWord output files with the project I am currently working on.

However, today, I am now getting "access denied" errors for a few files (.jpg, .js files) when I try to generate MyWebHelp, MyMSWord output files that are a part of the project. Nothing has changed with my PC and the only changes I've made to the project are content updates and maybe a few new images.

Has anyone experienced this before?

Paul

[bobmoon]

When you do a build, Flare deletes the content in your Output folder in preparation for creating the new content. An "access denied" message during a build sounds like Flare is unable to delete your Output folder content. Is there some way that the content in your Output folder has been marked read only? Did you perhaps check in your Output folder to source control?

Try going into your Output\UserName\TargetName folder and delete everything manually. If that doesn't work, then post back with the specific error.

Bob

[tomjohnson1492]

I publish my webhelp to a SharePoint destination. I recently reformatted my computer and reinstalled Flare. When I tried to publish to the destination, I kept getting an error message that said "Access is Denied." The folder denied access was SharePoint (even though I was logged in to that site).

To solve the problem, I mapped a network drive to the SharePoint location. The interesting thing is that my destination path doesn't include the network drive at all (Z://). The destination path in Flare is just \\corporatesite\somedirectory\somefolder. I guess having a network drive with this location mapped to the Z:// drive means something special to my computer, because after that it worked.

[RamonS]

That means that Flare seems to have a problem with UNC paths. I'd consider that a bug.

[Andrew]

That means that Flare seems to have a problem with UNC paths. I'd consider that a bug.

Yep, I've seen the same issue myself (though I thought it was an issue of network segments at the time). I'll submit a bug report.