Saturday, January 5, 2008

CS3 Sharing Violation

Have you received a "sharing violation" with CS3?

If so, here are a couple of things to check out.

First, CS3 provides automatic synchronization, so check first to see if you are synchronizing on the fly, and if so, disable synchronization until you correct the sharing violation issue. It may not be the cause, but it can be problematic. Also check your server setup; if you are running a testing server, then your current site or page may be trying to access the test server, and a failure will create a sharing violation. If that doesn't work, go next.

Next, you might try minimizing your screens to look for an alert. In every occurrence of a sharing violation that I have seen, the culprit was the temporary file, which is created because of leftover's in memory (on scratch) when you move from one file to another. Cancel the action. Test. If that doesn't work, go next.

Next, go into site management, and reveal all hidden files. Then look for a TMP file. These are the result of the above paragraph. They are duplicate files created when the first item occurs or when you have multiple sites open (there may be other situations that cause the temporary files to be created, but these two are predominate). Delete the temporary files. Test. If that doesn't work, go next.

Next, clear cache. If that doesn't work, reboot. CS3 creates its own conflicts...

^.com^

2 comments:

Anonymous said...

Thanks a lot! I found this very helpful

Anonymous said...

Thanks a lot! it was helpfull