Hey Damon Vogel,
Thanks for the quick reply.
We actually do have an Alias to our network in the volumes folder.
But we are still having the same problem, is there anything else you can suggest to try to debug this error.
Sample of the error : Error opening URL 'file:////Volumes/Websites/OurServer/test.swf'
I wish that I could be more help, but that's what cleared up that issue for me. To use your Error as the example, as soon as I included an alias to the "Websites" directory to my Volumes folder, it started working for me.
Can you navigate via the Volumes folder all the way to your test.swf?
Have you tried the test.swf with a local account to confirm that it is an issue with Flash and not your file?
Besides that kind of elimination troubleshooting, I don't have that much more for you.
Hope it helps...
I actually just figured out what the problem was,
It had to do with permission accessing the folder, the folder was a super mac user (Wheel) and as a staff account I was not granted access.
So if anyone else is having this same problem just make sure you create a new Alias that is accesible within your account.
Thanks for the help DV.
I'm having this exact same problem except I'm not running Flash on a network. Code snippets opens blank, and Flash won't open the .swf file. I get 'error opening url...'
Also I see the same white square instead of the normal welcome screen on launch.
My Mac is running File Vault as it is required by my company. I've tried making sure all the permissions to the library allow access, but nothing I have tried has fixed the problem. I had our help desk reinstall Flash twice to try to get it to work, but I have had no success.
Any help is appreciated.
Just adding my 2 cents as I encountered this exact issue and solved via this helpful post.
For me the solution was to use Workgroup Manager and adjust the managed preference for the machine with CS5's Login items.
I had previously been adding several useful AFP shares at login in this manner, but the option to "Add network home share point" was unchecked. Checking this item and rebooting the dev machine resolved the issues noted in the post.
Best and HTH.