Fireworks 8 problem

[beeswax]

In one of our IT suites pupils are getting this message when trying to open Fireworks (8) -

 

Could not launch Fireworks. File is locked.

 

Dreamweaver, Flash etc are no problem. Tried Googling it but all likely sites are blocked by the LEA filter. Anyone encountered this problem? It works in other suites. It has been working until recently, so I suspect it may be an update of some sort.

[cromertech]

Is it installed to the machine locally or run from a software management system?

[beeswax]

It's installed as part of an image

[beeswax]

Uninstalling XPSP3 has done the trick, but I don't think this is the best way to go about it.

[FN-GM]

I was talking about this when I was in your office today, I predict it’s a profile issue. Try re-creating your profile on a SP3 machine

[AngryTechnician]

Sorry for the thread necromancy, but did this ever get sorted? We're having the same problem on an SP2 machine with Adobe Fireworks CS3.

 

Google gave me exactly 7 hits, 2 of which were a Scribd document which didn't contain the search keywords (I hate Scribd and their stupid index-gaming), 4 of which were forum posts in Portuguese from 2004 (the Google translation seemed to suggest that no-one ever fixed it), and the 7th was... this page!

 

Going to run ProcMon on it but I have a tenner that says it's something to do with our AppData redirection since that breaks so many Adobe products.

[5tu]

Now I'm the one who, 3 years later, will apologise for resurrecting an old old old old thread..... but....

 

on Windows 7 running Design and Web Premium CS6 I am getting many reports of students unable to open Fireworks and instead getting the error "Could not launch Fireworks. File is locked."

 

Did anyone manage to resolve this problem? @AngryTechnician Anything to do with redirected AppData?

[AngryTechnician]

Unfortunately since I've changed jobs I don't have access to the ticketing system where I would have recorded the answer. I seem to remember ProcMon did find the answer, so I'd make that your next port of call.

[5tu]

Unfortunately since I've changed jobs I don't have access to the ticketing system where I would have recorded the answer. I seem to remember ProcMon did find the answer, so I'd make that your next port of call.

 

 

Thanks @AngryTechnician. ProcMon did in fact reveal that .js files could not be written to student's redirected AppData\Roaming\Adobe folders due to File Screening settings in FSRM. Removing .js files from the "Executables" group within FSRM sorted it.

[mp4-dave]

I come from 7 years in the future where I was having exactly the same problem. Resolved by changing the File Screening as suggested by gybe78. Thank you very much.

[WhiteStar1]

I come from 7 years in the future where I was having exactly the same problem. Resolved by changing the File Screening as suggested by gybe78. Thank you very much.

I too am from the future - the year of the COVID-19 2020 and salute all of this thread for solving this problem and I am using Server 2016. To think this is still an issue now.