error I cant seem to fix (wodWebServer / wodWebServer.NET)

There was an error while trying to execute ASP.NET request: Type 'A.D' in assembly 'WeOnlyDo.Server.WebServer, Version=1.4.2.55, Culture=neutral, PublicKeyToken=920a81657bbc7540' is not marked as serializable.

at WeOnlyDo.Server.WebUser.ExecuteASPX(String PhysicalPath, String VirtualPath, String RelativeBinPath, String WebConfig)

http://23.249.165.147:8080/hello.html

the html page is a simple html page that says hello.

Thank you for any help I receive.

Hi.

Can you please tell me what environemnt are you using, so we can try to duplicate this error? Do you get it with our samples as well?

Regards,
Kreso

Yes, with your samples or ANYTHING with anything that process .aspx file

simple .aspx file that return straight html with no processing has same issue.

Windows Server 2008R2

Hi.

Can you please tell me what environemnt are you using, so we can try to duplicate this error? Do you get it with our samples as well?

Regards,
Kreso

http://184.154.74.147:8080/hello.aspx
http://184.154.74.147:8080/hello.html

This is windows server 2008R2

Yes, with your samples or ANYTHING with anything that process .aspx file

simple .aspx file that return straight html with no processing has same issue.

Windows Server 2008R2

Hi.

Can you please tell me what environemnt are you using, so we can try to duplicate this error? Do you get it with our samples as well?

Regards,
Kreso

I think the issue is how its compiled. Im compiling the site in visual studio before uploading to server.

http://184.154.74.147:8080/hello.aspx
http://184.154.74.147:8080/hello.html

This is windows server 2008R2

Yes, with your samples or ANYTHING with anything that process .aspx file

simple .aspx file that return straight html with no processing has same issue.

Windows Server 2008R2

Hi.

Can you please tell me what environemnt are you using, so we can try to duplicate this error? Do you get it with our samples as well?

Regards,
Kreso

Any Ideas? Im completely stumped as I can get it to work fine on other workstations etc... But I need to get this done here this afternoon. Rest of my project is done I can run on Clients system for this reason.

I think the issue is how its compiled. Im compiling the site in visual studio before uploading to server.

http://184.154.74.147:8080/hello.aspx
http://184.154.74.147:8080/hello.html

This is windows server 2008R2

Yes, with your samples or ANYTHING with anything that process .aspx file

simple .aspx file that return straight html with no processing has same issue.

Windows Server 2008R2

Hi.

Can you please tell me what environemnt are you using, so we can try to duplicate this error? Do you get it with our samples as well?

Regards,
Kreso

Hi.

Sorry, there's no way we can solve it saturday evening (in Europe). I have to install 2008R2 to see about the problem and why it happens to see possible solutions. I need a day or two to set things up.

Kreso

That sucks. Where is the documentation on how the server needs code to be compiled? Piple mode, integrated, classic etc.. Also, where is the documentation on how to extract error conditions from webserver?

Hi.

Sorry, there's no way we can solve it saturday evening (in Europe). I have to install 2008R2 to see about the problem and why it happens to see possible solutions. I need a day or two to set things up.

Kreso

Hi.

There is no such specific documentation. So far we didn't encounter this kind of errors, so there are no docs for it.

Kreso

OK, here is more info maybe you can now tell me what is going on:

I loaded your sample @
http://184.154.74.147:8080

Works fine, however when I ask for the file directly it fails
http://184.154.74.147:8080/Default.aspx

Hi.

There is no such specific documentation. So far we didn't encounter this kind of errors, so there are no docs for it.

Kreso

I surely cant be the only one who has experienced this.. Can anyone else help? Im going on 24hours straight working this issue.

OK, here is more info maybe you can now tell me what is going on:

I loaded your sample @
http://184.154.74.147:8080

Works fine, however when I ask for the file directly it fails
http://184.154.74.147:8080/Default.aspx

Hi.

There is no such specific documentation. So far we didn't encounter this kind of errors, so there are no docs for it.

Kreso

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

Im running purely your examples at this point.

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

So, if you don't reference default.aspx, it works. If you reference default.aspx then it fails with the error? I assumed you have the code to 'ask for the file', sorry, I misunderstood the sentence.

Kreso

Private Sub initializewebserver()
web1 = New WeOnlyDo.Server.WebServer

web1.DocumentRoot = "c:\test\portal"
web1.DefaultPage = "Default.aspx"
web1.Port = 8080
web1.LicenseKey = "*************"
web1.Start()

End Sub

Private Sub web1_RequestDoneEvent(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestDoneArgs) Handles web1.RequestDoneEvent
'All we need to do in order to process web page is following line...
Try
Args.User.ExecuteASPX("c:\test\portal", "/", "/", "web.config")

Catch ex As Exception
addactivity(ex.Message)
End Try

End Sub

Im running purely your examples at this point.

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

No, I mean http://184.154.74.147:8080 works

http://184.154.74.147:8080/default.aspx does not

and its the same file because .defaultPage = default.aspx

So, if you don't reference default.aspx, it works. If you reference default.aspx then it fails with the error? I assumed you have the code to 'ask for the file', sorry, I misunderstood the sentence.

Kreso

And because of this , nothing else besides defaultpage works..

I am only using your samples at this point.

and I have tried this on 5 Windows servers now.

No, I mean http://184.154.74.147:8080 works

http://184.154.74.147:8080/default.aspx does not

and its the same file because .defaultPage = default.aspx

So, if you don't reference default.aspx, it works. If you reference default.aspx then it fails with the error? I assumed you have the code to 'ask for the file', sorry, I misunderstood the sentence.

Kreso

By using Try/Catches I have found that web1_RequestDoneEvent is not being called when the error happens(any page other than default)

Private Sub initializewebserver()
web1 = New WeOnlyDo.Server.WebServer

web1.DocumentRoot = "c:\test\portal"
web1.DefaultPage = "Default.aspx"
web1.Port = 8080
web1.LicenseKey = "*************"
web1.Start()

End Sub

Private Sub web1_RequestDoneEvent(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestDoneArgs) Handles web1.RequestDoneEvent
'All we need to do in order to process web page is following line...
Try
Args.User.ExecuteASPX("c:\test\portal", "/", "/", "web.config")

Catch ex As Exception
addactivity(ex.Message)
End Try

End Sub

Im running purely your examples at this point.

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

No exception is thrown on RequestDoneEvent (Because its not being called)

I tried to log "Hello" right before .Execute.aspx, and when calling default document (just root site) it logs fine, but when calling the page itself, it does not log. Therefore, the RequestDoone Event is not being called. So... The error is happening Before the RequestDoneEvent is fired.

By using Try/Catches I have found that web1_RequestDoneEvent is not being called when the error happens(any page other than default)

Private Sub initializewebserver()
web1 = New WeOnlyDo.Server.WebServer

web1.DocumentRoot = "c:\test\portal"
web1.DefaultPage = "Default.aspx"
web1.Port = 8080
web1.LicenseKey = "*************"
web1.Start()

End Sub

Private Sub web1_RequestDoneEvent(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestDoneArgs) Handles web1.RequestDoneEvent
'All we need to do in order to process web page is following line...
Try
Args.User.ExecuteASPX("c:\test\portal", "/", "/", "web.config")

Catch ex As Exception
addactivity(ex.Message)
End Try

End Sub

Im running purely your examples at this point.

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

When calling http://184.154.74.147:8080/Default.aspx

RequestHeadersDoneEvent is being fired before the error
RequestDoneEvent is not being Fired

The error is occurring somewhere between these event firings.

With no exception thrown.

No exception is thrown on RequestDoneEvent (Because its not being called)

I tried to log "Hello" right before .Execute.aspx, and when calling default document (just root site) it logs fine, but when calling the page itself, it does not log. Therefore, the RequestDoone Event is not being called. So... The error is happening Before the RequestDoneEvent is fired.

By using Try/Catches I have found that web1_RequestDoneEvent is not being called when the error happens(any page other than default)

Private Sub initializewebserver()
web1 = New WeOnlyDo.Server.WebServer

web1.DocumentRoot = "c:\test\portal"
web1.DefaultPage = "Default.aspx"
web1.Port = 8080
web1.LicenseKey = "*************"
web1.Start()

End Sub

Private Sub web1_RequestDoneEvent(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestDoneArgs) Handles web1.RequestDoneEvent
'All we need to do in order to process web page is following line...
Try
Args.User.ExecuteASPX("c:\test\portal", "/", "/", "web.config")

Catch ex As Exception
addactivity(ex.Message)
End Try

End Sub

Im running purely your examples at this point.

Hi.

Can you please share your code? Did you put all of your code inside try..catch blocks so you catch the error by yourself?

Kreso

Hi.

I just installed fresh Win server 2008 R2 x64, and installed wodWebServer.NET from our website. I have run our "CS5 With ASPX" sample, and tried to open page through browser.

I tried through http://127.0.0.1, and then to access it directly using http://127.0.0.1/default.aspx

In both cases it worked properly. Here's screenshot of the URL.

What are you doing differently, can you show me steps I need to make to duplicate your problem?

Kreso

Then this is so irritating I want to throw something.

I have tried on another 2 servers and it fails everytime.

Im doing nothing except your samples.

I made a small vb.net app that loads webserver with your sample.

My configuration of the app has been posted already.

I am doing nothing except using your sample.

I am so pissed, I have to resort to IIS because this is not working.

I really wanted this to work.

I have nothing else to show you because its all your sample code. I have nothing Ive written running on the links I gave you.

Hi.

I just installed fresh Win server 2008 R2 x64, and installed wodWebServer.NET from our website. I have run our "CS5 With ASPX" sample, and tried to open page through browser.

I tried through http://127.0.0.1, and then to access it directly using http://127.0.0.1/default.aspx

In both cases it worked properly. Here's screenshot of the URL.

What are you doing differently, can you show me steps I need to make to duplicate your problem?

Kreso

The only difference is maybe setting to port 8080

Hi.

I just installed fresh Win server 2008 R2 x64, and installed wodWebServer.NET from our website. I have run our "CS5 With ASPX" sample, and tried to open page through browser.

I tried through http://127.0.0.1, and then to access it directly using http://127.0.0.1/default.aspx

In both cases it worked properly. Here's screenshot of the URL.

What are you doing differently, can you show me steps I need to make to duplicate your problem?

Kreso

Hi.

I just installed fresh Win server 2008 R2 x64, and installed wodWebServer.NET from our website. I have run our "CS5 With ASPX" sample, and tried to open page through browser.

I tried through http://127.0.0.1, and then to access it directly using http://127.0.0.1/default.aspx

In both cases it worked properly. Here's screenshot of the URL.

What are you doing differently, can you show me steps I need to make to duplicate your problem?

Kreso

Also hard code in your paths (document root)..

Hi.

I just installed fresh Win server 2008 R2 x64, and installed wodWebServer.NET from our website. I have run our "CS5 With ASPX" sample, and tried to open page through browser.

I tried through http://127.0.0.1, and then to access it directly using http://127.0.0.1/default.aspx

In both cases it worked properly. Here's screenshot of the URL.

What are you doing differently, can you show me steps I need to make to duplicate your problem?

Kreso

Hi.

I just tried VB sample, changed hardcoded paths, changed port to 8080 and opened it, worked in all cases.

I see there's some more code you've added such as 'addactivity', not sure where is that code coming from, can you please try with out samples without any changes to it.

Kreso

add activity is just a textbox that looks for activity from your control.

I just recently put that in to help troubleshoot issue.

So... I guess we are at a standstill.

You say your software works fine, and I cant get it to work with samples.

I guess Ill go to another solution.

Hi.

I just tried VB sample, changed hardcoded paths, changed port to 8080 and opened it, worked in all cases.

I see there's some more code you've added such as 'addactivity', not sure where is that code coming from, can you please try with out samples without any changes to it.

Kreso

I really wish there was a way to fix this... I have been looking around and there is nothing really that works like this should..

But, I just cant make it work.

I can get it to work on any windows 10/XP box, but when I install my app on any server, I get that error.

Im pretty desperate at this point.

Hi.

I just tried VB sample, changed hardcoded paths, changed port to 8080 and opened it, worked in all cases.

I see there's some more code you've added such as 'addactivity', not sure where is that code coming from, can you please try with out samples without any changes to it.

Kreso

Hi.

Ok, so let's fix it. But I can't duplicate the problem, so there's something obviously different on your setup than mine.

I installed clean Win2008 Server R2 x64, used our setup package downloadable from our website, and tried to run it there, got no issues.

What kind of setup do you have? How can I see the error for myself, in order to try to find the solution for your problem?

Regards,
Kreso

I will pay whatever you need to help. Thank you.

Server: Server2008 R2 X64
Url to App: http://23.249.165.147

Module Module1
    Dim WithEvents web1 As WeOnlyDo.Server.WebServer
    Sub Main()
        initializewebserver()
    End Sub
    Private Sub initializewebserver()
        web1 = New WeOnlyDo.Server.WebServer

        web1.DocumentRoot = "c:\portal"
        web1.DefaultPage = "Default.aspx"
        web1.Port = 80
        web1.LicenseKey = "XXXXXXXXXXXXXXXX"
        web1.Start()

    End Sub


#Region "Webserver Code"
    Private Sub web1_RequestDoneEvent(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestDoneArgs) Handles web1.RequestDoneEvent
        'All we need to do in order to process web page is following line...

        Args.User.ExecuteASPX("c:\portal", "/", "/", "web.config")

    End Sub

    Private Sub RequestHeadersDoneDelegate(ByVal Sender As Object, ByVal Args As WeOnlyDo.Server.WebRequestHeadersDoneArgs) Handles web1.RequestHeadersDoneEvent

    End Sub


#End Region
End Module

Hi.

Ok, so let's fix it. But I can't duplicate the problem, so there's something obviously different on your setup than mine.

I installed clean Win2008 Server R2 x64, used our setup package downloadable from our website, and tried to run it there, got no issues.

What kind of setup do you have? How can I see the error for myself, in order to try to find the solution for your problem?

Regards,
Kreso

Inside c:\portal is your test site Website1 for ASPX only, nothing else

Hi.

Ok, so let's fix it. But I can't duplicate the problem, so there's something obviously different on your setup than mine.

I installed clean Win2008 Server R2 x64, used our setup package downloadable from our website, and tried to run it there, got no issues.

What kind of setup do you have? How can I see the error for myself, in order to try to find the solution for your problem?

Regards,
Kreso

Hi.

There is no need to pay anything, but I need to know WIndows server setup. Not your code. Let's try with our samples first, without any changes. Do they work? If they don't, what do I need to set on Windows server to have error like yours?

Kreso

Im only running your samples.

I just sent server terminal access information to your email.

Hi.

There is no need to pay anything, but I need to know WIndows server setup. Not your code. Let's try with our samples first, without any changes. Do they work? If they don't, what do I need to set on Windows server to have error like yours?

Kreso

I put sourcecode in folder on desktop

Im only running your samples.

I just sent server terminal access information to your email.

Hi.

There is no need to pay anything, but I need to know WIndows server setup. Not your code. Let's try with our samples first, without any changes. Do they work? If they don't, what do I need to set on Windows server to have error like yours?

Kreso

Hi.

Thanks for server info, but we will not connect there, at least not yet. I trust that you see the error, so I don't need to see it by myself also. I need a way to duplicate it, for me, known environment, so I can possibly install debugging tools.

From what I know, your server could have 100s of add-ons that could interfere with the internet traffic and stuff, and trying to figure out where the error comes from goes out of scope of protocol/component support. We may need to install source there for debugging too, and we can't do it on 3rd party systems.

I suggest you start from the scratch, your way - same as we do. Take clean Windows server, and try it there. Then build it up until you see it fails for you. Otherwise, I am not sure how we can help since we don't know where/how it's actually running.

Regards,
Kreso

Its a clean Server. Just installed last week. Nothing on it. I verified your login.

This happens on other servers as well.

You are free to install anything you need to debug. I included the source code form your sample on desktop.

Hi.

Thanks for server info, but we will not connect there, at least not yet. I trust that you see the error, so I don't need to see it by myself also. I need a way to duplicate it, for me, known environment, so I can possibly install debugging tools.

From what I know, your server could have 100s of add-ons that could interfere with the internet traffic and stuff, and trying to figure out where the error comes from goes out of scope of protocol/component support. We may need to install source there for debugging too, and we can't do it on 3rd party systems.

I suggest you start from the scratch, your way - same as we do. Take clean Windows server, and try it there. Then build it up until you see it fails for you. Otherwise, I am not sure how we can help since we don't know where/how it's actually running.

Regards,
Kreso

We have approx 85 Server on this network and another 25 on another. Ive tried it on 12 servers now. From scratch and have the same issue on every one. Thats why I gave you access to server, source code, and your samples.

If there is something wrong with server, please let me know what it is so I can make the change. However, the server roll outs are standard windows load + service packs.

No IIS, no anything but updated .net framework.

Hi.

Thanks for server info, but we will not connect there, at least not yet. I trust that you see the error, so I don't need to see it by myself also. I need a way to duplicate it, for me, known environment, so I can possibly install debugging tools.

From what I know, your server could have 100s of add-ons that could interfere with the internet traffic and stuff, and trying to figure out where the error comes from goes out of scope of protocol/component support. We may need to install source there for debugging too, and we can't do it on 3rd party systems.

I suggest you start from the scratch, your way - same as we do. Take clean Windows server, and try it there. Then build it up until you see it fails for you. Otherwise, I am not sure how we can help since we don't know where/how it's actually running.

Regards,
Kreso

Ok, I see the error. But I don't see visual studio, so I can't even debug your app or any changes to it.

I will try to do the same on our local environment, without any visual studio, and with folder in local path. Need to reinstall Win2008 since we deleted it from last week. Will take a day or two.

Kreso

One more question, since I will try this locally. Is this 'Standard' or some other edition of WIn2008?

Kreso

Standard.
You wanted Visual Studio loaded on the server?

One more question, since I will try this locally. Is this 'Standard' or some other edition of WIn2008?

Kreso

Yes, but not sure if it will be enough, since we will not transfer our source code as well to 3rd party server, so there's no point. I thought I may try a tweak or two to see if I can get it running.

I will try this locally.

Kreso

Ok, I have visual studio being installed on that server. Should be good to go in 10 min.

Yes, but not sure if it will be enough, since we will not transfer our source code as well to 3rd party server, so there's no point. I thought I may try a tweak or two to see if I can get it running.

I will try this locally.

Kreso

Whatever you need let me know.

Yes, but not sure if it will be enough, since we will not transfer our source code as well to 3rd party server, so there's no point. I thought I may try a tweak or two to see if I can get it running.

I will try this locally.

Kreso

Hi.

I think I was able to duplicate this issue, and it's fixed now. Please download latest version from our website (make sure Version property returns 1.4.2.56).

If you're licensed user, then request update from

https://www.weonlydo.com/index.asp?update=1

You may need to uninstall current version.

Let me know how it goes!
Kreso

YES!!!!!!!!!!!

Its now working!!

Thank you so much!!! I'm so glad I came back. Thank you again!

Hi.

I think I was able to duplicate this issue, and it's fixed now. Please download latest version from our website (make sure Version property returns 1.4.2.56).

If you're licensed user, then request update from

https://www.weonlydo.com/index.asp?update=1

You may need to uninstall current version.

Let me know how it goes!
Kreso