When opening Dreamweavr CS5, error says. Ordinal 3879 could not be found in dynamic link library libeay32.dll. I can x out and Dreamweaver loads. Can I get a copy of this dll to replace the corrupted one, or must I uninstall and reinstall the program?
I just started experiencing the same problem today. Dreamweaver was working fine when I last tried it (about a week ago).
Mine just freezes at startup and I have to end the Dreamweaver.exe process to get that dialog.
I just started seeing the exact same error message, but I am using Dreamweaver CS4. The file libeay32.dll does not exist on my computer, though there is one called libeay32_0.9.6l.dll in c:\windows\system32 folder.The zip file in the answer no longer exists, so I can't try it. Dreamweaver does start up after displaying this message two or three times.
I installed the library you sent, which is the same size (824K) and date (9/10/2008) as my original file. I continue to see the same error message 3 times whenever I start Dreamweaver CS4:
The ordinal 3879 could not be located in the dynamic link library LIBEAY32.dll
Dreamweaver does start up and appears to behave normally after that. I've been using this program for a couple of years now, but this error just started yesterday.
This library can also be found in two other Adobe directories (I only own Dreamweaver): Adobe Bridge CS4 and Adobe Device Central CS4. The file in both of those directories is 996 Kb and is dated 8/28/08 in the first and 8/6/08 in the second. I tried copying one of those files into the Dreamweaver CS4 directory, got the same error. Tried copying the other and got a different error and Dreamweaver wouldn't start. When I rename both of those files so they can't be found, I get the original error message on startup, so it doesn't appear that those libraries are being accessed.
The first time I saw the error, I didn't write it down, but I noticed it said something about Owl. None of the subsequent error messages have said anything about Owl. I notice that there are files called AdobeOwl.dll and AdobeOwlCanvas.dll in my Adobe Dreamweaver CS4 directory. Could these have anything to do with the problem?
I found the actual error in my event logs:
Application popup: Owl Orphanage: Dreamweaver.exe - Ordinal Not Found : The ordinal 3879 could not be located in the dynamic link library LIBEAY32.dll.
That message appeared three times at startup. Ever since then, the same thing occurs but the "Owl Orphanage:" prefix is no longer in the error message.
I'm seeing this too--anyone figure out the cause or have a fix from Adobe?
My setup: DW CS5 on WinXP with TrendMicro AV.
The odd part:
I have it installed on both a desktop and laptop, and while they differ in occasional details, they're pretty much a mirror. The desktop pops the message 3 times and then (apparently/hopefully) runs normally. The laptop doesn't generate the error at all. Tried copying the 830KB, 4/2/10 file from laptop -> desktop despite the two having same file specs--no change. Also tried copying a different size/date libeay32.dll from Device Central (my only other CS5)--got different error and reverted. Also tried a detailed file compare of the two installations, and found three config XMLs with minor date differences, but all pre-dating the error's appearance.
BTW, this isn't exactly solved anymore since rogerinarcata seems to have pulled his file. Not that it was a complete fix anyway, since I expect I'm not the only one hesitant to take candy from strangers (no offense Roger! :-).
I just started getting a similar error, except mine says "The ordinal 3712 could not be located ...". I can either OK the error dialog twice or exit the dialog and Dreamweaver CS5 starts up normally and appears to work fine, including Secure FTP (which is the reason those SSL DLLs are there). But the error message is annoying.
I tried copying libeay32.dll and ssleay32.dll from the directories of other applications (including Photoshop CS5 and other programs in the CS5 suite), but all those resulted in Dreamweaver hanging when I tried to connect to an SFTP server. Anyone have any other ideas or perhaps an explanation and a fix from Adobe? I know they want everyone to upgrade to CS6, so they probably aren't paying any attention to CS5 users' needs anymore, which really stinks.
UPDATE: Just as suddenly as this problem appeared, it just vanished in the last day or two. I honestly don't have any idea what changed, unless it was the Adobe Acrobat update a couple of days ago.