AE crash

#1

I tried to run Ae and i got a license error which told me to reinstall AE to fix the problem.
Well, i tried that and now i get this error.

AE error:sfntread library error. (83::4)

AE warning. unknown BiB error.sfntread library error, CT, O (83::4)

AE can’t continue: sorry, AE crashed.

anyone experience this problem.

#2

What system and OS are you running? Did you call Adobe? That sounds like the DLL is messed up. You may not have un-installed it completely before re-install.

If you have a recent PC or MAC - you might be able to restore the Hard Drive/Computer to the state it was in before AE crashed.

Other than that - call Adobe if doing a clean install doesn’t help…

#3

i am running xp. yeah, i am about to hit up the adobe support right now. earlier i googled the error and found a way to fix

Issue

        When you start Adobe After Effects CS3 on Windows, the program returns two error messages and does not start: 

After Effects error: sfntread library error (83::4)         
   and         
   After Effects warning: Unknown BIB Error. sfntread library error, CT, 0 (83::4) 

          [b]Solution[/b]

        [b]Disable the System DLL Fragmentation Workaround.[/b]

[ol]
[li]Navigate to the After Effects preferences file: [/li]>
Windows XP: C:\Documents and Settings<username>\Application Data\Adobe\After Effects\8.0

   Windows Vista: C:\Users\<username>\AppData\Roaming\Adobe\After Effects\8.0

[li]Double-click on the AfterFX8.ini file to open it in Notepad.[/li]> [li]In the [System DLL Fragmentation Workaround] section, change the Enable Workaround=1 value to Enable Workaround=0.[/li]> [li]Choose File > Save.[/li]> [li]Close Notepad.[/li]> [li]Start After Effects.[/li]> [/ol]

In my Afterfx8.ini file the value to enable workaround was already at 0, so that fix didn’t work. I uninstalled photoshop, illustrator, and after effects and then reinstalled them and that didnt work. I will try adobe support.

thanks for the help

#4

Aw man - that totally sucks. Sorry that this happened to you. Hope it gets resolved. You could always do a drive wipe and then system re-install. But more than likely it was a windows update that screwed it all up - especially if you are on a network.

#5

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.