Re posting this in the new forums to keep the topic alive.
Does anyone have any recommendations on where to start with this? I am running on a Windows XP Pro machine. I was recently running Norton 2007 Internet Security and Anti-Virus. I completely un-installed all Norton components including live update so that I would switch over to Blink. I heard how great Blink was on the Security Now Podcast, but I am starting to get frustrated that I can't even get it to start up after a simple install.
I downloaded beta 3.1 after I could not get version 3.0 to start on my machine. I cannot get 3.1 to start either. Every time I try to start the Blink service, even after several reboots, it tells me it could not be started and to check the event viewer.
I am getting the following error dialog when I try to start Blink by clicking on start->all programs->eEye Digital Security->Blink->Blink:
"The Blink service failed to start (0x80040202). For more information please check the Windows event log."
In the windows event log I see the following:
"Failed to open BlinkRm COM interfaces. (Error: 80080005 - Server execution failed)"
I tried starting if from the services panel and I get the following error:
"Could not start the eEye Blink Engine service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."
When I check the Event Viewer, I am finding the following critical error (same as above):
"Failed to open BlinkRm COM interfaces. (Error: 80080005 - Server execution failed)"
I have checked the dependencies and it looks like all of the required dependencies are started.
I have also updated my MSXML libraries to Version 4 by going to this link, however, that this not resolve the problem either.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en
I am now waiting on the new build that was mentioned in the prior posts to see if that will resolve this problem. One of the folks at Eeye had me run this command: Cacls C:\WINDOWS\system32\MFC71.DLL
And it produced the following results:
C:\DOCUME~1\RICH>Cacls C:\WINDOWS\system32\MFC71.DLL
C:\WINDOWS\system32\MFC71.DLL BUILTIN\Power Users:C
BUILTIN\Administrators:F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\NETWORK SERVICE:(special access:)
DELETE
SYNCHRONIZE
FILE_READ_DATA
C:\DOCUME~1\RICH>
The feedback I received was that some other installer angled the permissions on this file instead of letting it use parent’s permissions. So, they (Eeye) are now offering a different build which might resolve this problem. I will report back if the new build works for me.