StrataFrame Forum » Enterprise Server - V1 » Issues » ES Server was down

RE: ES Server was down

Trent L. Taylor — Wed, 04 Jun 2008 13:46:20 GMT

I fixed my post typo :D...boy, you are keeping toes lately :P

ES Server was down

Greg McGuffey — Wed, 04 Jun 2008 13:46:20 GMT

My companies ES server went down tonight at around 5pm PST. The error was related to the being unable to contact the 'activate.micro4.com' server.

This doesn't seem like it should happen, that if you licensing server goes down, my server goes down as well. Please advise if there was some configuration I should have done or if there was some other issue I could address. My ES server was attempting to contact 'activate.micro4.com' whenever a user attempted to login (maybe other times as well, but we never got past login).

RE: ES Server was down

Greg McGuffey — Wed, 04 Jun 2008 13:33:52 GMT

[quote]...We just missed a spot, so it is [now] fixed and all is well [/quote]

Glad to be of service! ;)

(finding the bug!) :w00t:

RE: ES Server was down

Trent L. Taylor — Wed, 04 Jun 2008 13:21:39 GMT

Good. The activation server part won't fail any more. This was just a bug under certain conditions...we really try hard to never let the server die. We just missed a spot, so it is now fixed and all is well :)

RE: ES Server was down

Greg McGuffey — Wed, 04 Jun 2008 11:27:55 GMT

Trent, so far all looks good. The issue I was having with FillMultipleDataTables seems to be fixed. Haven't tested the issue with the activation server yet.

RE: ES Server was down

Trent L. Taylor — Mon, 02 Jun 2008 17:25:59 GMT

I have posted a build that addresses both of the issues that you have run into on ES. You can get it here: http://forum.strataframe.net/FindPost16782.aspx

Let me know if you have any issues. We did prove it and test it, so you should be good, but we made a change the the MicroFour License Base.dll assembly which changed the public token key. It should now match the ES assemblies...so if you have more than one version of this in the GAC (if they are even in the GAC), delete the one that has a public token key that doesn't match the ES assemblies.

RE: ES Server was down

Greg McGuffey — Mon, 02 Jun 2008 11:18:45 GMT

Thanks Trent! I do have an immediate need for this. :ermm:

RE: ES Server was down

Trent L. Taylor — Mon, 02 Jun 2008 11:03:26 GMT

We have found the location that could cause this to fail and will be posting a fix with the next update. Just thought you would like to know :) If you have an immediate need for this, let me know, but there will be another 1.6.6 build here pretty quick as there is a new language that we failed to implement in the previous build (Czech). So probably sometime this week.

RE: ES Server was down

Greg McGuffey — Tue, 27 May 2008 14:05:13 GMT

Thanks!

RE: ES Server was down

Trent L. Taylor — Tue, 27 May 2008 13:39:49 GMT

Working on a reproduction...I will let you know when I have something for you.

RE: ES Server was down

Greg McGuffey — Tue, 27 May 2008 13:24:58 GMT

Any progress?

RE: ES Server was down

Trent L. Taylor — Fri, 23 May 2008 13:08:13 GMT

I got your email and we will take a gander at it ;)

RE: ES Server was down

Greg McGuffey — Fri, 23 May 2008 10:29:36 GMT

This is good to hear (that this wasn't supposed to happen). Now to see why. Yes we received an exception email every time someone tried to connect to ES. I'll email you one of those emails (they were all the same).

There were some earlier exceptions, but my sys admin had changed the smtp IP and not told me, so those exceptions just resulted in an exceptions that the smtp server didn't exist.

RE: ES Server was down

Trent L. Taylor — Fri, 23 May 2008 09:53:16 GMT

Greg,

This actually should not have happened. Did you get an exception email that the ES will send you if an exception is thrown? If so, I would really like to see it. We are going to see if we can reproduce this because as of right now, you are the only one that is reporting this...and there are a number of other ES users out there.

You are right in that we had the servers down last night for 3 hours....long story....but in any case, this should definitely not happen. Any additional details and how you discovered this would be great to have so that we can trouble shoot!