DevForce 2010: BOS Connection Lost

Print Page | Close Window

BOS Connection Lost

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=2088
Printed Date: 10-Jun-2026 at 5:03pm

Topic: BOS Connection Lost

Posted By: eniben
Subject: BOS Connection Lost
Date Posted: 24-Aug-2010 at 11:34am

Hi,

Under what circumstances will one get the following error (extracted from debuglog.xml)?

<entry id="30" timestamp="2010-08-24T16:48:43" username="USERNAME" source="IdeaBlade.Cab.UI.Services.DevForceLoggingService:Error">Persistence Connection Exception

An error occurred while receiving the HTTP response to http://testsrv:9999/EntityServer_EXTENSION. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.</entry>

The application starts up okay. In 2-tier mode, there are no issues or complications. In n-tier mode, it starts up just fine, spitting out a number of queries that yield data for configuring the Windows client - menu, display grids, etc.

The first two forms come up fine. We try displaying a report and then come up short with the error above.

Replies:

Posted By: ting
Date Posted: 24-Aug-2010 at 3:42pm

It's hard to tell from the information above, although if you're doing n-tier across a WAN, port 9999 likely going to be an issue. Trap the exception in the Visual Studio debugger and see if the inner exception provides any clues.

You might also try deploying a trivial app that you can create from the DevForce template to get a copy of our standard deployment configuration. Porting the DevForce 2009 configuration files is usually more complicated than necessary.

What reporting system are you using?

Posted By: eniben
Date Posted: 24-Aug-2010 at 10:17pm

Hi,

We were using Crystal Reports for Visual Studio 2008 and have ported to Crystal Report for Visual Studio 2010.

We're running n-tier on a LAN and the issue doesn't just come up when we're trying to print a report. It occurs when you start moving between screens and racking up queries. I actually used port 9989 with the standard template for Windows Forms n-tier deployment and that worked fine (after I ironed out some issues on my end with the connection strings). There doesn't seem to be any issue there cos it just keeps going even though I didn't try printing a report.

I tried deploying the BOS on IIS running on one of our Windows Server 2003 machines and came up short. It said it couldn't start the EntityServer_EXTENSION.svc service. Maybe I was just being lazy or need a clean machine (because the site on IIS we used runs off port 8787). That's when I resorted to ServerService.exe which is the way we were running DevForce 2009.

We've never really had success deploying on IIS or the ASP.NET Development Server so having it run on the ASP.NET Development Server that comes with Visual Studio 2010 (on my machine) was a major boost to confidence. Put it on a LAN and it all goes poof.

I know I am doing something wrong just can't figure out what it is.

Posted By: eniben
Date Posted: 25-Aug-2010 at 2:48am

Hi,

Just tried the app again locally using ServerService to host the BOS and the same behaviour. It starts out fine, I keep the app busy and after about a minute it just blows up with that same error.

I flip to another screen since the EntityManager tends to remember which query type cause an error and then I get a very curious exception.

System.InvalidOperationException{"DataSource fetch strategies are not allowed when disconnected."}.

This particular query requires a FetchStrategy.DataSourceOnly; and the em is disconnected? Is ServerService killing the connection for some reason?

Just a wild thought. Do we need to define the SessionKey on both the client and server or just the server? Could that have anything to do with it, cos I have it defined on the server-side but not the client-side.

Posted By: ting
Date Posted: 25-Aug-2010 at 5:12pm

Yes, the EntityManager becomes disconnected when there is a connection error or if the server throws an exception. Did you implement any server-side logic (e.g. in the EntityServerQueryInterceptor or InvokeServerMethod)? On saves, the EntityServerSaveInterceptor and Validation logic is also triggered.

You should not specify the ServerEncryptionKey on the client.

Can you open up a support case and send:

1) Server-side configuration files, and server-side debuglog.xml when the error occurs

2) Client-side configuration files, and client-side debuglog.xml when the error occurs

Posted By: ting
Date Posted: 25-Aug-2010 at 6:22pm

Just rembered this:

When deploying on Windows Server 2003 without IIS (that is when using ServerConsole.exe or ServerService.exe) you need to have two copies of the config file.

For the Console server you should have both:

ServerConsole.exe.config

ServerConsole.config

For the Service server you should have both:

ServerService.exe.config

ServerService.config

This is a known bug with Windows Server 2003:

http://blogs.msdn.com/b/junfeng/archive/2006/08/09/692996.aspx - http://blogs.msdn.com/b/junfeng/archive/2006/08/09/692996.aspx

Posted By: eniben
Date Posted: 26-Aug-2010 at 12:20am

Hi Ting,

Thanks. I will try out your suggestion. I really wasn't aware of the "known" bug.

Kind of curious though, why is it like that? Also, I am not doing SxS?

Will keep you posted.

Posted By: eniben
Date Posted: 26-Aug-2010 at 3:20am

I have filed a support request with Id [#7458].

Print Page | Close Window