StrataFrame Forum » Enterprise Server - V1 » Issues » Unhandled Exception

Unhandled Exception

Larry Caylor — Fri, 16 Mar 2007 10:35:39 GMT

I’ve got the ES server set up on Windows Server 2003 Web Edition with SP1. I’m able to access the ES status page but when it try to run a client application I get the following exception. Any suggestions on what I may have missed?

-Larry

RE: Unhandled Exception

Trent L. Taylor — Fri, 16 Mar 2007 10:35:39 GMT

Great! Glad you got it going!

RE: Unhandled Exception

Larry Caylor — Fri, 16 Mar 2007 10:28:57 GMT

Ben,

Thanks for the timeout hint… It’s working now:) It turned out that it was the client that couldn’t reach the ES server because of a configuration error in the host header value in IIS. I was spinning my wheels trying to figure what could be preventing the ES server from seeing the SQL server.

-Larry

RE: Unhandled Exception

StrataFrame Team — Fri, 16 Mar 2007 08:43:19 GMT

hrm... that could mean that either the enterprise server itself it timing out against SQL Server, or your EnterpriseDataSourceItem is not reaching the enterprise server. Put Timeout=10; on the end of your SQL Server connection string within the ES configuration and if you get a different response after only 10 seconds, then you'll know that the ES cannot reach SQL Server. However, if it still takes 30 seconds to come back, and you get the same message, then your client cannot reach the ES.

RE: Unhandled Exception

Larry Caylor — Thu, 15 Mar 2007 17:54:42 GMT

This is what comes back after a long wait.

RE: Unhandled Exception

StrataFrame Team — Thu, 15 Mar 2007 17:11:50 GMT

What exactly is the timeout error? Is it wrapped in an exception that was thrown by the ES itself and sent back over, or is it an HTTP timeout exception?

RE: Unhandled Exception

Larry Caylor — Thu, 15 Mar 2007 16:58:31 GMT

When I think of host name I think of the server host name, not the DNS name of the website. Anyway I’ve got that fixed and now I’m getting timeout errors. The only thing I can think of is the connection string in the data source which looks okay. I dropped a plain old client/server SF application on the ES server and it can connect to the database server so I know the DB server is reachable from the ES server. What next?

RE: Unhandled Exception

Trent L. Taylor — Thu, 15 Mar 2007 14:30:56 GMT

[quote]Would this make a difference? [/quote]

Yes. Since the hostname is part of the license file then the host name provided must match what is shown in the Server Status page under Server Hostname.

RE: Unhandled Exception

Larry Caylor — Thu, 15 Mar 2007 13:33:38 GMT

I checked the keys and they match. I also tried setting the client and server to IsEncryped = False and IsCompressed = False and received the same error. I’ve installed ES under the server’s default website. The hostname in the server license is“my.host.name” while it’s “my.host.name/StrataFrameES” in the EnterpriseDataSourceItem. Would this make a difference? I’ve made sure to restart IIS after any changes.

RE: Unhandled Exception

Trent L. Taylor — Thu, 15 Mar 2007 12:56:23 GMT

This generally occurs when the pre-shared key is not the same on both the server and the client. If you go to the server status page, make sure that you are initializing the client connection with the same key.

[codesnippet]
'-- Establish Locals
Dim loESDS As MicroFour.StrataFrame.Data.Enterprise.EnterpriseDataSourceItem

    '-- Create the Enterprise Server data source item
    loESDS = New Enterprise.EnterpriseDataSourceItem("", "My.Host.Name", 80, "", New SqlDataSourceItem(""))

    '-- Set the encryption and compression properties. Refer to the documentation for more
    '   information about these settings.
    loESDS.IsEncrypted = True
    loESDS.EncryptionKey = New Byte() {1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24}
    loESDS.EncryptionVector = New Byte() {1, 2,3,4,5,6,7,8}
    loESDS.IsCompressed = True

    '-- Manually add the ES data source
    DataBasics.DataSources.Add(loESDS)[/codesnippet]

When you get the message "Bad Data" it means that the server and the client connection are not talking with the same handshake. You can also get this message when you add a license file and do not restart the application pool (just restarting IIS will restart the pool also).