CapableObjects forum » ECO » General discussions » .Net remoting

.Net remoting

pedro_brown — Tue, 23 Sep 2008 06:25:45 GMT

Hi everyone,

I spent my last two days trying to make a asp.net application work as a .Net remoting server for another vcl.net app.

I just can't seem to get it right. Apparently in my pc (localhost) everything works as it should, but that isn't the case in my production server.

The approach used was to add the section in the asp.net app web.config file.

I followed the Remote Persistence tutorial for VS, but it was hard because it isn't updated.

Can anyone help me?

Thanks.

RE: .Net remoting

smashed2bitz — Tue, 23 Sep 2008 06:25:45 GMT

[quote][b]pedro_brown (2008-09-06)[/b][hr]Hi everyone,

I'm pleased to announce that I managed to get my .Net remoting app working!

This is the article that helped me: http://www.glacialcomponents.com/ArticleDetails/CAOMN.aspx

Sorry if I disturbed any of you, and thanks again.[/quote]

Hi Pedro, I'm glad you got your app working!

I played with ECO .NET remoting before and only spent a morning, but didn't have much luck. Your pains, I'm sure, will be a great reference for when I work on my next ECO project where .NET Remoting is a good approach.

I haven't been on this site in almost a month, and right away from when I saw your original post, I got the sense it was either your Host blocking remoting (but you're still on port 80 so that was ruled out), or DNS issues. Errors you saw were "unable to find" kinds of messages, likely fails out almost immediately. I saw a similar problem when troubleshooting my Microsoft CRM 4.0 deployment... The settings int he database would store the name of the host eg. "SERVER01" and not the domain alias "CRMServerFarm.OurDomain.local"... the errors you were getting were similar in nature.

Cheers, and good luck in the future!

Tim

RE: .Net remoting

Jonas Hogstrom — Mon, 08 Sep 2008 15:01:36 GMT

Hi Pedro.

I'm glad that you found the solution, and that you shared the knowledge with us. The article you referred to was very easy to understand. I have updated the templates for Eco5 with commented out code that shows how to make the required change, and also updated the readme for each project type. All texts include a reference to the article in your post.

Thanks again for letting us know, and good luck now that you are up and running!

RE: .Net remoting

pedro_brown — Sat, 06 Sep 2008 22:42:04 GMT

Hi everyone,

I'm pleased to announce that I managed to get my .Net remoting app working!

This is the article that helped me: http://www.glacialcomponents.com/ArticleDetails/CAOMN.aspx

The article describes my problem and the solution. Gladly for me, the simple way worked.

...
<channels>
<channel ref="http" machineName="www.tectrilha.com.br">
<serverProviders>
...

In my opinion, this kind of information must be included in the RemotingPersistence.pdf tutorial.

I also wanna say that I really appreciate all the help that I received, especially from Jonas and Scott.

Sorry if I disturbed any of you, and thanks again.

RE: .Net remoting

Scott Price — Thu, 04 Sep 2008 19:59:32 GMT

Hi Pedro,

You know, I am coming back to an old comment I said. I don't actually think you need the call to [b]RegisterTcpServer()[/b]. This was something that was included in the templates for Win32 or service based applications to be able to register a remoting channel.

If I recall correctly, Jonas always used to point out to me that actually if it is hosted in an IIS web application, it could be commented out and then you should use the web.config to register a remoting service.

You actually use both mechanisms, and I'm beginning to wonder if this is the problem.

Sadly I don't have Delphi to compile the code with, so I would recommend you comment out RegisterTcpServer, see what errors you get, and try to check if the web.config is correct. Then try to get it running locally with only the web.config controlling the remoting configuration.

Kind regards, Scott :)

RE: .Net remoting

Scott Price — Thu, 04 Sep 2008 15:57:01 GMT

To be honest Pedro, I'm not sure what else to suggest at the moment.

I don't use Delphi.net for my Eco development, so I'm not likely to be a huge amount of help if investigating that side of it.

Are there firewalls/IPSec settings that are shared by the development machine and deployed server? Is there some common software installed on each that is intercepting/url rewriting occuring elsewhere in the process?

It looks like it's complaining in your case that it is unable to connect to the server, so I would go through the steps in between the communication, and ensure that there is nothing else in the way.

I'll have a little think about what might be in the way, or interfering, but I'm not experienced in that much of normal .net remoting, so I may not be much help at that point on.

Sorry I haven't been much help at present.

RE: .Net remoting

pedro_brown — Tue, 02 Sep 2008 21:07:56 GMT

Hi Scott,

Thank you very much for helping me. I don't see the purpose of examining the Event Log of my host's server, because I made my developing machine into a internet server, and the same exception was raised.

I examined my Event Log, and It had nothing.

I also created a demo app in visual studio and deployed it. This is the exception, very similar to the old one:

System.Net.WebException was unhandled by user code
Message="Impossível conectar-se ao servidor remoto"
Source="mscorlib"
StackTrace:
Server stack trace:
em System.Net.HttpWebRequest.GetRequestStream()
em System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
em System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
em System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
em System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
em System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
em Eco.Persistence.IPersistenceMapper.get_SupportsSync()
em Eco.Persistence.Remoting.PersistenceMapperClient.ClientMapperImpl.Eco.Persistence.IPersistenceMapper.get_SupportsSync() na c:\dev\e4vs\source\Public.CLR\Persistence\PersistenceMapperClient.cs:linha 199
em Eco.Internal.TBoldSystemPersistenceHandler.get_SupportsSync() na source\ObjectSpace\BORepresentation\BoldSystemPersistenceHandler.pas:linha 312
em Eco.Internal.TBoldSystemPersistenceHandler.EnsureFirstCurrentToSyncVersion() na source\ObjectSpace\BORepresentation\BoldSystemPersistenceHandler.pas:linha 293
em Eco.Internal.TBoldSystemPersistenceHandler.GetAllWithCondition(AbstractCondition Condition, Int32 MaxAnswers, Int32 Offset) na source\ObjectSpace\BORepresentation\BoldSystemPersistenceHandler.pas:linha 169
em Eco.Services.Impl.ExtentServiceImpl.FetchAdjustedClassList(IClass fillClass) na c:\dev\e4vs\source\Public.CLR\ServicesImpl\ExtentServiceImpl.cs:linha 156
em Eco.Services.Impl.ExtentServiceImpl.EnsuredExtentForClass(IClass c, Boolean all) na c:\dev\e4vs\source\Public.CLR\ServicesImpl\ExtentServiceImpl.cs:linha 134
em Eco.Services.Impl.ExtentServiceImpl.Eco.Services.IExtentService.AllInstances(IClass c) na c:\dev\e4vs\source\Public.CLR\ServicesImpl\ExtentServiceImpl.cs:linha 186
em Eco.Internal.TBOS_AllInstances$BoldOclSymbolImplementations.Evaluate(IOclOperationParameters Params) na source\ObjectSpace\OCL\BoldOclSymbolImplementations.pas:linha 2335
em Eco.Internal.TBoldOclEvaluatorVisitor.VisitTBoldOclOperation(TBoldOclOperation N) na source\ObjectSpace\OCL\BoldOclEvaluator.pas:linha 212
em Eco.Internal.TBoldOclOperation.AcceptVisitor(TBoldOclVisitor V) na source\ObjectSpace\OCL\BoldOclClasses.pas:linha 776
em Eco.Internal.TBoldOcl.InternalEvaluate(String Ocl, IElement RootElement, IClassifier Context, SubscriberPair SubscriberBlock, IExternalVariableList VariableList) na source\ObjectSpace\OCL\BoldOcl.pas:linha 773
InnerException: System.Net.Sockets.SocketException
Message="Uma tentativa de conexão falhou porque o componente conectado não respondeu\rcorretamente após um período de tempo ou a conexão estabelecida falhou\rporque o host conectado não respondeu 10.100.1.32:80"
Source="System"
ErrorCode=10060
NativeErrorCode=10060
StackTrace:
em System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
em System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
em System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
InnerException:

RE: .Net remoting

Scott Price — Tue, 02 Sep 2008 17:27:21 GMT

Have you examined the Event Log from the actual server showing the problem?

I think we may find a clue or two there, as it may well be running in a more secure environment, and other factors might be coming into play here.

I look forward to hearing back from you when you have had time to examine them.

RE: .Net remoting

pedro_brown — Tue, 02 Sep 2008 16:04:37 GMT

Hi Scott,

This IP 189.13.127.153:81 is for my developing machine. I was running the app on IIS7 and Windows Vista, and trying to figure out what was wrong. The port 81 is my port of choice for my WebSite on IIS.

Again, locally everything worked fine, but when I tried to make my app hosted at (www.tectrilha.com.br/EcoRemoting1/) communicate to my machine, the same error occurred. I did this to try to spot something happening here. I even looked at 'Event Viewer' on Vista but didn't find anything.

RE: .Net remoting

Scott Price — Mon, 01 Sep 2008 15:40:02 GMT

I have deployed the application to a server I can examine in more detail Pedro, and I am getting a DCOM error listed in the servers SYSTEM branch of the Event Log.

Can you please re-try to connect to the server with your Eco Winform Client, and make a note of the date and time you get the error. If you have access to the System branch of the servers Event Log, please try to see if you can find a matching error at approximately the same date and time.

Please check this, or check it with your ISP's technical support, and let me know.

RE: .Net remoting

Scott Price — Mon, 01 Sep 2008 14:54:40 GMT

Hi Pedro,

I am actually having difficulties communicating with this URL, or the site:

http://www.tectrilha.com.br/EcoRemoting1/WebForm1.aspx

I cannot actually get this to load in a web browser at all at the moment, it often keeps coming up with this error:

[quote]
Server Error in '/EcoRemoting1' Application.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 189.13.127.153:81
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 189.13.127.153:81[/quote]

Here notice the IP and in particular, the port. Is this one communicating with a database on another machine, or is it just supposed to be using the memory sharing object?

Do your websites have sufficient rights to perform remoting on that machine?

I also noticed that it seems to be redirecting:

[quote]Stack Trace:

[SocketException (0x274c): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 189.13.127.153:81]
System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +1073657
System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) +33
System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) +217

[WebException: Unable to connect to the remote server]
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +2668969
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +717
Eco.Persistence.IRemotePersistenceMapperProvider.GetPersistenceMapper(Int32 typeSystemHash) +0
Eco.Persistence.Remoting.PersistenceMapperClient.GetMapper(Boolean refresh) +230

[RemotingException: PersistenceMapperClient failed to connect to the server.
Message: Unable to connect to the remote server
Server URL: [b]http://pedrobrown.dyndns.org:81/EcoRemoting1WebServiceServer.rem[/b]][/quote]

Is this correct? It is then being redirected to this different Url?

I am not sure if that would affect ECO, but it is something else worth noting at this point in time, as it isn't direct to the server with the Url you mentioned earlier.

I will look into this a little more.

RE: .Net remoting

pedro_brown — Fri, 29 Aug 2008 19:54:05 GMT

Hi Scott,

First of all, thank you very much for trying to help me in this situation.

About your comment that you managed to deploy my app and communicate with it inside your own machine: I'm able to do that to. When I test this app inside my network, everything works as it should. The problem is the internet. This application (that you deployed locally) is also at http://www.tectrilha.com.br/EcoRemoting1/WebForm1.aspx and I can't communicate with it.

I read in some places like I said in my last post, that .net remoting works diferentlly when its over the internet. Today I also created a simple app with VS to try remoting, and it also failed.

I also tried to deploy on a friends machine and access trough the internet http://mp-pedro.ath.cx/Tectrilha/WebForm1.aspx and the same problem occurred.

I'm really lost on this.

Thanks.

RE: .Net remoting

Scott Price — Fri, 29 Aug 2008 18:46:34 GMT

Nope, ignore my last comments. I tested by commented out the web.config and it wouldn't work without it. :)

I could get your application to work as the webform1.aspx, and I wrote a quick and simple VS2008 project to connect to and use the exposed:

http://localhost/PedroBrown/EcoRemoting1WebServiceServer.rem

service, and consumed it in my VS2008 C# WinForm application without a problem.

It does make me wonder if there is a security, or permissions issue somewhere, perhaps with access to some resource (database or gac perhaps), or even a firewall not allowing the communications?

RE: .Net remoting

Scott Price — Fri, 29 Aug 2008 18:16:04 GMT

Now I don't use Delphi any longer, so I may not be remembering correctly, but I think you need to [b][i]Either[/i][/b] define the service in the web.config [b]OR[/b] do the code that you have included in your persistence mapper provider:

[quote]
class function TPersistenceMapperProvider.RegisterTcpServer(Port: integer; ServerName: string): TcpChannel;
var
provider: BinaryServerFormatterSinkProvider;
props: IDictionary;
chan: TcpChannel;
begin
provider := BinaryServerFormatterSinkProvider.Create();
provider.TypeFilterLevel := TypeFilterLevel.Full; // Needed for serializations
props := Hashtable.Create();
props['port'] := port;
chan := TcpChannel.Create(props, nil, provider);
ChannelServices.RegisterChannel(chan, false);
RemotingConfiguration.RegisterWellKnownServiceType(
typeof(TPersistenceMapperProvider),
ServerName,
WellKnownObjectMode.Singleton);
Result := chan;
end;
[/quote]

I do not think you need to do both, infact if I remember correctly, this can cause problems.

I think if you keep the code and remove the web.config, or keep the web.config and comment out this code block, and test again you may have a more useful result.

Sadly I don't have a Delphi with which I can make test changes to your code.

Scott :)

RE: .Net remoting

Jonas Hogstrom — Fri, 29 Aug 2008 08:50:24 GMT

[quote][b]pedro_brown (2008-08-27)[/b]

One thing that makes me curious is that the following works:

constructor EcoRemoting1EcoSpace.Create;
var
PersistenceMapperProvider1: PersistenceMapperProvider;
s: string;
begin
inherited Create;
InitializeComponent;
// TODO: Add any constructor code here
[b]PersistenceMapperProvider1 := Activator.GetObject(TypeOf(PersistenceMapperProvider), PersistenceMapperClient1.Url) as PersistenceMapperProvider;
s := PersistenceMapperProvider1.EcoSpaceTypeName;[/b]
end;

Does this say anything to you?
[/quote]

those lines will not cause any network traffic, so that is not surprising that you won't get any exceptions from them.

RE: .Net remoting

pedro_brown — Fri, 29 Aug 2008 04:06:13 GMT

Hi everyone,

Thanks for all the answers. I didn't manage to get my application working, but I did two more tests.
First I hosted my app on a private server: http://mp-pedro.ath.cx/Tectrilha/WebForm1.aspx and tried do get remoting to work. It didn't! this server is a simple IIS using a dns host. This makes me think that maybe there is some configuration to be donne and its not my web host's fault.

The other thing is that I found this article: [url=http://www.eggheadcafe.com/articles/20021202.asp]Marshal Objects ByRef Over The Internet With .NET Remoting[/url] that didn't say much to me, but for you guys might.

Thank you all for the help.

RE: .Net remoting

Scott Price — Thu, 28 Aug 2008 13:22:24 GMT

Hi Pedro,

I am sorry, but I am heading out in 1 hour, so I don't really have time to look into it now. I will have my laptop with me, and I will try to take a look this evening.

However, I have read my way through most of the post.

In all the exceptions you post, the IP address is: 10.100.x.x

Is this your internal network address of the pc against which you are trying to run your tests, or is this the error message you are receiving from the remote server once deployed?

RE: .Net remoting

pedro_brown — Wed, 27 Aug 2008 22:41:44 GMT

Hi Jonas,

I really don't know. I've been talking to my host provider, but they keep saying that there is nothing to prevent such connections.

About the velocity reviews, I've already seen that post.

One thing that makes me curious is that the following works:

constructor EcoRemoting1EcoSpace.Create;
var
PersistenceMapperProvider1: PersistenceMapperProvider;
s: string;
begin
inherited Create;
InitializeComponent;
// TODO: Add any constructor code here
[b]PersistenceMapperProvider1 := Activator.GetObject(TypeOf(PersistenceMapperProvider), PersistenceMapperClient1.Url) as PersistenceMapperProvider;
s := PersistenceMapperProvider1.EcoSpaceTypeName;[/b]
end;

Does this say anything to you?

Thanks very much

RE: .Net remoting

Jonas Hogstrom — Wed, 27 Aug 2008 22:02:23 GMT

I tried to google the error code and came up with the following post that might be relevant.

http://www.velocityreviews.com/forums/t114346-deploying-aspnet-20.html

Other than that, could there be any firewalls or settings in IIS that prevents you from accessing this remoted object?

RE: .Net remoting

pedro_brown — Wed, 27 Aug 2008 18:00:07 GMT

Just is case you don't wanna download the zip file,

[SocketException (0x274c): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.100.1.32:80]
System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +3335242
System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) +97
System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) +623

[WebException: Unable to connect to the remote server]
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +4596611
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +1713
Eco.Persistence.IPersistenceMapper.get_SupportsSync() +0
Eco.Persistence.Remoting.ClientMapperImpl.Eco.Persistence.IPersistenceMapper.get_SupportsSync() +94
Eco.Internal.TBoldSystemPersistenceHandler.get_SupportsSync() +50
Eco.Internal.TBoldSystemPersistenceHandler.EnsureFirstCurrentToSyncVersion() +17
Eco.Internal.TBoldSystemPersistenceHandler.GetAllWithCondition(AbstractCondition Condition, Int32 MaxAnswers, Int32 Offset) +102
Eco.Services.Impl.ExtentServiceImpl.FetchAdjustedClassList(IClass fillClass) +270
Eco.Services.Impl.ExtentServiceImpl.EnsuredExtentForClass(IClass c, Boolean all) +1226
Eco.Services.Impl.ExtentServiceImpl.Eco.Services.IExtentService.AllInstances(IClass c) +74
Eco.Internal.TBOS_AllInstances$BoldOclSymbolImplementations.Evaluate(IOclOperationParameters Params) +364
Eco.Internal.TBoldOclEvaluatorVisitor.VisitTBoldOclOperation(TBoldOclOperation N) +1446
Eco.Internal.TBoldOcl.InternalEvaluate(String Ocl, IElement RootElement, IClassifier Context, SubscriberPair SubscriberBlock, IExternalVariableList VariableList) +1467
Eco.Internal.TBoldOclService.BaseEvaluate(IElement root, IClassifier Context, IExternalVariableList vars, String expression) +87
Eco.Internal.TBoldOclService.Evaluate(IElement root, String expression, IExternalVariableList vars) +17
Eco.Web.UI.WebControls.EcoDataSourceView.DoSelect() +724
Eco.Web.UI.WebControls.EcoDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +2122
System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +23
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +270
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +97
System.Web.UI.Control.EnsureChildControls() +149
System.Web.UI.Control.PreRenderRecursiveInternal() +71
System.Web.UI.Control.PreRenderRecursiveInternal() +255
System.Web.UI.Control.PreRenderRecursiveInternal() +255
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3532

Thanks

RE: .Net remoting

pedro_brown — Wed, 27 Aug 2008 17:57:25 GMT

Hi everyone,

I started this topic some time ago, when I was first trying to develop an application based on Eco IIS Remoting. At that time, I managed to get remoting working for some time. I know that this is gonna sound awkward, I thought that the remoting issue was solved, but it isn't.

After getting things to work, I put them aside and kept developing the app. For my surprise when I tried to put it on production again, it failed.

I'm really lost in this. I've tried everything. My last attempt was to create a simple demo app from Eco Project Wizard and deploying it. The situation is: A asp.net app witch is the Remote Server being accessed by another app on my web server works fine. The problem occurs when I try to access the server from my machine. I simply don't have a clue of what is happening.

If you want, you can access [url=http://www.tectrilha.com.br/EcoRemoting1/WebForm1.aspx]http://www.tectrilha.com.br/EcoRemoting1/WebForm1.aspx[/url], there you can see the same application that is in the zip file deployed.

I'm attaching some files, one with the error and stack trace that I recieve.

I really need someone's help on this.

Thanks in advance.

RE: .Net remoting

pedro_brown — Thu, 07 Aug 2008 17:12:47 GMT

Never mind. I managed to get things working. Acctually I don't know what was wrong.

My solution: PersistenceMapper := Activator.GetObject(TypeOf(TPersistenceMapperProvider),'http://www.tectrilha.com.br:80/os/MsProjectRemoteServer.rem') as TPersistenceMapperProvider;

RE: .Net remoting

pedro_brown — Thu, 07 Aug 2008 15:33:09 GMT

Can someone help me on this?
Thanks

RE: .Net remoting

pedro_brown — Thu, 07 Aug 2008 03:13:07 GMT

Hi everyone,

I didn't say anything else about this because I was occupied finishing my application and was to busy to try all your suggestions.

Now I finished it and have to deploy. I did a simple .net remoting app following an microsoft 'how to', as our friend guest00 suggested. To my surprise it worked like a charm. If needed I can attach it here.

Next I decided to log all server side errors and send them to my email. When trying to connect from the client app, no exception is raised on the server.

Then I turned off my firewall but it didn't solve the problem.

I executed the app on a pc with the english version of the .net framework. That is the error message that I recieve:

"A connection attempt failed because the connected party did not correctly properly respond after a period of time, or established connection failed because connected host has failed to respond 10.100.1.32:80."

This is the exactly error message. I would be very very grateful if someone could help me on this, due to deadlines of this project.

Thankyou very much.

RE: .Net remoting

Jonas Hogstrom — Sat, 02 Aug 2008 01:59:07 GMT

That is a good suggestion. Add logging of any exception that occurs on the server. Write to a local file (that you know you have write access to).