Image taken from Webcam not getting saved on the server

Question

1.00/5 (3 votes)

See more:

Hello!!!

I Have hosted an application on iis. When i am using this application and taking image using Webcam it is not getting saved in a folder on server how ever if i run the application locally image is getting saved. I unchecked the Read only property of the folder even of the whole application but it still doesn't works.Please tell me how to solve this problem.

Posted 27-Sep-12 2:19am

ujjwal uniyal

Add a Solution

Comments

ZurdoDev 27-Sep-12 10:59am

It's likely a permissions issue. Find the user account that is running the Application Pool in IIS and make sure that account has permissions to write to the folder.

Sergey Alexandrovich Kryukov 27-Sep-12 13:31pm

Maybe, but it would be safe to say this is the issue of having insufficient information. OP needs to log related events on the server side and see what the logs tell.
--SA

fjdiewornncalwe 27-Sep-12 13:43pm

Agreed. I have a hunch the OP is using an ActiveX control to capture the image and that the saving process is happening on the client side, not the server as they expect. Added on top of that is the permissions issue that Ryan noted which would affect the client side save as well.

Sergey Alexandrovich Kryukov 27-Sep-12 16:18pm

Right. After this your comment, I decided to try to generalize the approach OP would needs to take. Then, if the problem still cannot be resolved, this approach will allow to pose informative questions in this forum.

Please see -- what do you think?
--SA

ujjwal uniyal 28-Sep-12 0:37am

Thanks to all of you for your advise and suggestions. The issue was with the permissions. I granted permission to IIS User for writing the files and it worked. :) Thanks again

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-09-27T10:16:00

Please see the comments to the question. In response to the comment by Marcus Kramer, I decided to generalize the approach you need to develop. This is easy enough:

Debug.
Where debugging is too difficult, devise a facility to make the code feasible for debugging. Not all code has to go to deployment, by the way. Development-only projects can be important, as well as skeleton prototypes.

Example: debugging of the Windows service can be difficult. It the problem persists, it's good to put most of the code in some library assembly and use it from two applications: one being Windows service, and another one, say, a console application doing basically the same job. Most bugs could be detected using just the console variant of the application.
Where that is still difficult, log sensitive information on everything which is important or can be problematic: "before and after" such actions. Don't forget to catch all exceptions in the stack frame on the very top of the stack of each thread and make sure you always log all the comprehensive exception information at those points.

First of all, I would advice to use the class System.Diagnostics.EventLog:
http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx[^].

—SA