Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to start capture #18

Open
GoogleCodeExporter opened this issue Apr 11, 2015 · 6 comments
Open

Fails to start capture #18

GoogleCodeExporter opened this issue Apr 11, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Attempt to start a capture by Creating a Process or Attaching to a Process.
2. oSpy will say "Could not load file 'oSpyAgent.dll' or one of its
dependencies. The system cannot find the file specified."

What is the expected output? What do you see instead?
oSpy should not show an error.

What version of the product are you using? On what operating system?
1.10.4 on Windows XP.

Please provide any additional information below.
I checked oSpyAgent.dll with Dependency Walker. It complained about not
finding ieshims.dll and wer.dll. I do not know what these files are, but I
don't seem to have them.

Original issue reported on code.google.com by [email protected] on 13 Dec 2009 at 5:21

@GoogleCodeExporter
Copy link
Author

Does this apply to all processes/applications? (Even something as simple as 
FlashFXP or 
Windows Live Messenger) Do you have any AV software installed/running?

Original comment by [email protected] on 15 Mar 2010 at 12:41

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 15 Mar 2010 at 12:41

@GoogleCodeExporter
Copy link
Author

Yes, this occurs with Windows Live Messenger as well.

I tested it out a little bit more, and I see it only fails if I try "Create a
Process" first. Then it doesn't work if I use "Attach" either.

If the very first time I use "Attach to a Process", then it works fine.

The Dependency Walker thing looks to be a red herring. It seems simply that 
using
"Create a Process" changes the working directory, and then oSpy doesn't use a 
full
path to load oSpyAgent.dll.

Original comment by [email protected] on 15 Mar 2010 at 2:38

@GoogleCodeExporter
Copy link
Author

Aha! Thanks a lot for spotting that! I'll fix this for the next release.

Original comment by [email protected] on 15 Mar 2010 at 6:32

@GoogleCodeExporter
Copy link
Author

I'm also facing this problem. 
Have you fixed that already? 

Thanks

Original comment by [email protected] on 17 Sep 2010 at 2:53

@GoogleCodeExporter
Copy link
Author

I have the same issue. When will it be fixed ?

Screenshot:
http://www9.picfront.org/token/Bqvm/2011/04/28/1950087.jpg

Original comment by [email protected] on 28 Apr 2011 at 9:39

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant