Holding down the keys resets the prefs. Se that thread for the exact same suggestion:
If it doesn't stick, you have a permissions problem or some tool is blocking the file or restoring an old, damaged one. And the permissions issue may exist on a more general level when AE fails to initiaklize the PS component. I had some detailed blurb on theat on my error code database a lifetime ago, but the site is long dead, so I can't point you to any links...
I had read that they were supposed to reset the preferences, but for me nothing seems to get reset (my workspace is still my custom workspace, and the Media & Disk Cache and Memory & Multiprocessing settings that I have changed are still changed) it just allows me to open projects. It turns out I can't RAM preview or render like this, however. When I reset After Effects, again without holding down Ctrl-Alt-Shift, I can open native CS6 projects that do not have .psds referenced in them, and can render them, and can RAM preview.
Rebooting hasn't helped either, for the record
Also, if I open Adobe Media Encoder, and try to import an After Effects Composition, if it is a CS6 project and does not have .psds in the project, it opens fine. If it does have .psds in the project, it says "Connecting to Dynamic Link Server", then only shows me the compositions in the project that do not have .psds! wtf
Now, I get the same ( 83 :: 8 ) error listed above, followed by a new dialog window that reads:
After Effects error: Crash in progress. Last logged message was: <4488> <DynamicLink> <5> C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Then, when I click OK, I get:
After Effects can't continue: sorry, After Effects has crashed. For After Effects Help and Support, go to http://www.adobe.com/go/learn_ae_support. If you still can't resolve the issue, please contact Adobe Technical Support (2).
( 0 :: 42 )
Clicking OK to that gives me a chance to save the latest project, then the standard Windows 7 crash dialog window opens, the one that gives me the choice of "Check online for a solution and close the program" or just "Close the program" and lets me View problem details, which are:
Problem Event Name: APPCRASH
Application Name: AfterFX.exe
Application Version: 126.96.36.1998
Application Timestamp: 4f6d63ab
Fault Module Name: StackHash_a85b
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec4aa8e
Exception Code: c0000374
Exception Offset: 00000000000c40f2
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: a85b
Additional Information 2: a85ba096cc6b6acabe6eaf35bf34dc60
Additional Information 3: f862
Additional Information 4: f86227a9dfa15a47cdb6c94bb0d08360
Finally got to speak to Adobe customer support on the phone. They had me try a number of things that didn't work. First, at a command prompt with administrator privileges, she had me type:
del %temp%\*.* /s /q
To clear the temp files out. That didn't fix it. Next, she had me type these lines into the same command prompt:
icacls "%userprofile%\AppData\Local" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Roaming" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Local" /T /C /grant system:F
icacls "%userprofile%\AppData\Roaming" /T /C /grant system:F
Also didn't change anything. Finally using RegEdit, we went to Computer/HKEY_CURRENT_USER/Software and deleted the Adobe folder containing all Adobe registry keys. Also no help, so we restored my registry from a backup we had made. She said that was all her document had for her to try, and that I would need to make a new user account on the computer. When I did that, the new user can indeed open the troublesome projects and import .psds.
It's not the greatest solution ever, but at least there is one, just in case anyone else has the same issues.
if on windows machine, make sure the temp/tmp system environmental variables point to %USERPROFILE%\AppData\Local\Temp, if it is in a different location, you'll experience crashes in various Production Premium programs (bridge, prelude), not able to import psd in premiere or AE, photoshop gives some strange error on swapfile as it tries to open it up on root of C:. You can run the individual programs elevated, though dynamic link won't work between programs like PPro/AE.
Hope it helps.
Son of a *****. That's the problem. I have a separate scratch drive that I use for all my temp folders, because my system drive is an SSD and I wanted to keep the wear and tear down on it, and once I got my new user account set up, the same problem started happening. And Adobe support definitely did not check that. Dude, THANK YOU SO MUCH
Also for the record, in a different thread someone reported running After Effects as an administrator got rid of the error messages, and it does, but Premiere Pro's Dynamic Link Server doesn't work and you lose the ability to drag-and-drop items from Windows Explorer into your Project window when you run AE as an administrator. So it looks like the only real fix is to have your temp folders set to their default locations.
I am experiencing the same problem on a brand new win7, x64 machine, 32gb ram and system on 250GB SSD (C) and userprofiles on D drive. When opening a downloaded AEP project I consistently get the "Not enough memory to initialize SPL" error. I like to have userdata on a volume separate from system data for backup and other reasons.
If running in Administrator mode, or running a profile located on the C drive (the original Administrator account) then it works ok.
Setting the system environment variables to point to %USERPROFILE%\AppData\Local\Temp does not help.
Nor if they are hardcoded. In fact I am unsure what happens when no one is logged in with the suggested setting, since %userprofile% has no value in that case. Setting system variables to point to a user folder seems like a poor idea to me, generally speaking. But most importantly it does not resolve the issue.
Any ideas anyone?
The problem is when your temp folders are ANYWHERE except for the standard Windows location. Not having your user profiles on the C: drive is definitely what's causing the problem. Your choices as of now are to run as administrator every time, and lose the ability to import Premiere Pro projects into After Effects and lose the ability to drag and drop assets into your projects, or you can use the administrator on C: to run After Effects.
Ideally if it's a simple issue they could patch this issue, and make After Effects ask the OS where to look for temp files, instead of hard coding the location. But that could be a house of cards, where a lot of other code relies on that. Realistically that will probably not get fixed since I don't think many people change their default temp locations (even if 100s or 1000s of people do, you have to think of it in terms of their entire installed user base, probably not that large of a percentage).
Well, the good news is that YOU CAN have your AE CS6 working, including dynamic link to AP, and at the time, you can have your user data whenever you want. You just have to create a "fake" temp folder in C:, like this "C:\Users\WHATEVERYOURUSERNAMEIS\AppData\Local\Temp".
Check all the permissions and ownerships for your user name.
Then, go to My PC, right click Properties / advanced.../ environment variables... and check that you have both TEMP and TMP pointing to "C:\Users\WHATEVERYOURUSERNAMEIS\AppData\Local\Temp" (hardcoded)
Restart and there you have.
As far as I remember this issue, it occured to me, and to many others, because we wanted to change Windows's default user location. Say that you want to have ALL your data in a separate drive D: instead of Windows system drive (typically C:). Just in case you want to reinstall your operating system, for instance.
You can do this without any problem by fiddling a little with the Windows registry an then creating a new user account that will be created wherever you want. By doing this, you are also creating a default temp directory (let's say D:\MyUserName\AppData\Local\Temp) that will be used by nearly all the aplications.
The problem with After Effects is that it will keep trying to use Window's default temp directory, which is (should be) in C:\. But it is no longer there, because you changed it to your custom location.
So, basically, the solution is telling After Effects "So, you want a temp directory in c:\? there you have it, just for you. The rest of us will work in D:"... It's a patch, I know, but is easy and harmless, and just to allow AE to start.
Nevertheless, once AE has started , you can go to preferences and specify where you want your scratch disks and so on... so, all you sensible data would go wherever you want.
I hope that After Effects staff will take note of this issue and solve it in future versions.
I too am experiencing this issue in CS6 and I don't like the suggested "solutions". Like many people with updated hardware, I have my boot disk as an SSD on C:. I've also got all my User folders on the D: drive. A well-behaved Windows application is expected to use %USERPROFILE%\AppData\Local\Temp which in my case would be D:\Users\xxx\AppDataLocal\Temp.
I'm not going to mess up my clean layout to put some bogus folders on my C: drive or to always run in Admin mode. Certainly Adobe must have a better solution in mind than to always assume that users are stored on the C: drive. That is just not following the Windows standard. Please Adobe, can you fix this in a CS6 update? It's wrong.
For the sake of completeness:
Windows 8 Pro x64
Intel Core i7-3770 @ 3.4GHz
C: 256GB SSD (Boot/Windows/Programs)
D: 2TB HD (Users/Footage/Output)
(resurrecting an old thread, because this just hit me)
I agree that Adobe's code seem wrong here, but I worked around it through a compromise:
My Temporary directory is in D:\Temp, so I created a symlink on C:
mklink /D C:\Users\<myuserid>\AppData\Local\Temp D:\Temp
and then changed my environment variables TEMP and TMP for <myuserid> profile to:
Sure, it's silly - but, After Effects CS6 now imports .PSD files without a complaint and without requiring Administrator privileges. Something to consider.