Hello, I recently purchased FW CS3 for my work laptop. Since installation I am having a serious error that produces a pop up that will not let me get around it. as soon as I close it it pops up again and will not let me resume working in the program, eventually freezing and I have to Ctrl - Alt - Delete and do a hard shut down via the task manager. This occurs every time I try to open an existing file, export or save as. Very annoying and is preventing me from completing work. The pop that I get says "This file is not encrypted, but an encryption rule is defined for the file." I have attached a screen shot of this. If you have any idea what could be causing this and what I can do to prevent/eliminate this it would be greatly appreciated!
I've not seen this error message before, maybe someone else has and will pop in to help. :-)
Does this happen when you try and open a specific file, or when you try and open *any* file?
What you could try is to reset the preferences file to see if that helps in any way: (It doesn't hurt anything - it just sets the preferences file back to it's default state).... this has helped others with varying start up problems.
Restore default preferences
If this doesn't work and no-one else pops in with a suggestion, then the only other support avenue is to contact Adobe Support directly.
No. it is not fixed. and the response is not the right answer. There seems to be a problem with FW CS3 working on corporate computers with certain types of file encryption. My company issued me a laptop (we are now on the second laptop) to work remotely. everything i open a file (any file) i can work for a few minutes then this error keeps popping up over and over and over again and will not let me work on the file. I have to control alt delete and end the program. My company issued me another laptop with a new configuration on it, but we still use the same type of file encryption and I am getting the same error with the new computer and new configuration. This DOES NOT happen when I am in PShop or DW CS3. I have an old copy of FW MX that I have been using as a work around in hopes that they fix this problem. Its sad because I would love to be able to take advantage of all the new features in the adobe version of FW.
If anyone gets any new information on this problem please take a second to post. hopefully adobe will patch this asap. But so far nothing......
Have you contacted Adobe tech support? This is a user-to-user forum and it sounds like the problem arises from your company's special operating requirements, not something that an average user would encounter.
I had the same issue today, with a new installation of Fireworks on an encrypted XP SP3 system.
I spent a while with Adobe tech support and they had me check out permissions etc, make some changes by adding 'everyone' with 'full access' rights to individual files.
This *appeared* to fix things, but later I realised that it had no effect.
What I found was that if I use Fireworks' own browse dialogue to open a file, I would get the "This file is not encrypted, ..." error. But if I used any other method to open the file - browse in Windows Explorer then right-click, open with Fireworks, or drag from Windows onto open Fireworks window, or open from Bridge etc, then I got no error.
OK it's a pain not being able to use the Fireworks browse dialogue, but frankly I use other methodds to open my files 90% of the time anyway.
HTH anyone else having the same issue.
I am recieving the same error. This is on a fresh installation of Windows XP SP3 (fully updated thourgh Microsoft Update) with Utimaco Safeguard Enterprise 188.8.131.52 encryption software running. I have updated Fireworks to version 184.108.40.2063.
The error occurs:
1 in 4 times trying to save file as...
1 in 6 times trying to open files through Fireworks' menu tree
1 in 20 times trying to open files right from Windows Explorer.
1 in 6 times trying to open files through Fireworks' hotkeys (ctrl+o)
Never (or at least 0 in 30) while opening Save File As... using hotkeys (ctrl+shift+s)
Has anyone found a fix for this yet? Judging by the 1,135+ views, I'd say this is a pretty important issue. Do Adobe personnel check this?
hi Steve. Yes we use encryption software on all our remote machines. I
am still having the error as of the last time I checked. I ended up reverting back to an old copy of Macromedia FW
to work with when I am on this machine. Really a drag to have to lose some of the improvements of newer versions. Hopefully Adobe can find a fix for this issue and patch it.
Do you know which encryption software you are using? We have SafeGuard Enterprise http://www.sophos.com/products/enterprise/encryption/safeguard-enterpr ise/
Since we're all in the Utimaco Safeguard boat, Steve and Johnny, I'm going to try encrypting with TrueCrypt instead to see if there's any improvement - this is of course assuming that our encryption software is (somehow) causing the conflict... and Utimaco is not a very friendly program to begin with, so I wouldn't bet against it.
I am a Sophos employee and I wanted to let everyone know that you may want to contact our support number and speak with one of our support engineers. We may be able to help you correct the issues you are seeing using Adobe Fireworks. The number is 1-888-SOPHOS-9. Then press 4 for technical support and then 8 for the encryption queue.
Hi Tiny, My problem was resolved on my machine. Since all of this happened at the same time, I cant be sure which was one worked. I am assuming it was the Sophos upgrade but I cant be 100%.
My Company Support Team Upgraded:
1. OS from XP to Win7
2. Sophos SafeGuard from 4.0 to 5.50.0
3. FW CS3 to FW CS5
one or any combination of all 3 did the trick for me. I was frustrated that they kept telling me there was not a new version of Sophos available for me but as soon as my laptop was upgraded, i noticed it. I am having no issues now and have not had the encryption error at all sicne the upgrade of all 3 of the mentioned products. That said, up until the point of the upgrades, CS3 was not working with my then current copy of Sophos so I guess the answer to your question is no, it was not resolved with my originals posts versions.
thanks for following up!