Access Violation - 1.5.8.305 - WeOnlyDo Discussion board

Access Violation - 1.5.8.305 (General questions)

by selisoft, Wednesday, April 27, 2011, 22:56 (4957 days ago)

Hello,
I'm trying to evaluate Webserver 1.5.8.305 on Windows 2008x64SP2, but everytime I run a program in VB6-IDE or compiled EXE, it gives me
---------------------------
Error
---------------------------
There was an error: Generic error for access violation.
---------------------------
OK
---------------------------

Can you help me?

Thank, you
Josef

Re: Access Violation - 1.5.8.305

by wodSupport, Wednesday, April 27, 2011, 22:58 (4957 days ago) @ selisoft

Hi. Although this seems completely unrelated, I think we've seen this error before when you already had some web server running on the same port. Can you stop other web server, or change port to something else than 80?

I know error is weird - but this is actual exception returned from the NET framework, we just pass it to the application.

Kreso

Re: Access Violation - 1.5.8.305

by selisoft, Wednesday, April 27, 2011, 23:19 (4957 days ago) @ wodSupport

Thanks for your quick reply.

It's strange, I use ActiveX-Sample 1. Simple - manual response and changed BindIP to 192.168.1.200 and Port to 9099 in the wodWebServer1 properties window.
-> The error comes up

Now adding this code before wodWebServer1.Start in Form_Load, no error occurs, and MsgBox results are and 80

<<<<<
MsgBox wodWebServer1.BindIP '->
MsgBox wodWebServer1.Port ' 80

wodWebServer1.BindIP = 192.168.1.200
wodWebServer1.Port = 9099

' Now return values are correct
MsgBox wodWebServer1.BindIP '-> 192.168.1.200
MsgBox wodWebServer1.Port ' 9099
<<<<<

Seems the values from wodWebServer1 properties window are not used. The values are not even saved and restored when the project is closed and reopened.

Thank you,
Josef

Re: Access Violation - 1.5.8.305

by wodSupport, Wednesday, April 27, 2011, 23:21 (4957 days ago) @ selisoft

Hi. THanks. I'll check it out, but I'm not sure if this can be fixed since property bag changes can cause previous EXEs to crash in that case.

I would suggest, anyway, to switch to COM version. It's same sample but everything is done from the code.

So, this error is now gone?


Kreso

Re: Access Violation - 1.5.8.305

by selisoft, Wednesday, April 27, 2011, 23:32 (4957 days ago) @ wodSupport

Kreso,
yes, the error is gone, thanks.
You should at least mention this issue in the docs/faq
Bye, Josef