64 Bit Server Problem

[omni]

Roger,

I would like to readdress this issue.

We have users, and all new users, utilizing windows Server 2008 64-bit. We have this here also.

On half the systems we can compile (for testing,etc) but nothing will run if compiled on that computer. Gives a weird Alaska (190.331)error saying "Xbase development file has stopped working" and closes. If we copy over precompiled source it works fine on the server. I have checked server versions, and that does not appear to matter.
We have two users, both with Server 2008 standard, ver 6.1, build 7600. One works fine, the other will not run unless we sent over compiled exe program. Both have the same express and Alaska. We are compiling on the server, not thru a work station. (remote access and/or gotomypc)
I am just wondering if possibly a security setting or something else on the server might be causing the problem, since it does not appear to be window version or our version that impacts it> I was hoping somebody else may have run accross the same problem.

Thanks


Fred
Omni

[rdonnay]

Fred -

I was working with a customer last week who runs 2008 server and he has not reported such a problem, however his compiling is always done on a workstation.

Are you saying that you are compiling the code on the server (via RDP or Citrix) ?

Roger

[Auge_Ohr]

Server 2008 64-bit.
...
Alaska (190.331)error saying "Xbase development file has stopped working" and closes.
...
If we copy over precompiled source it works fine on the server.

v1.9.331 is not "certificate" for Win7 / W2K8.

The Error is know and you can get a Hotfix from Alaska for SL1 v1.9.355

[rdonnay]

Aha! This is good to know.

I was not aware that 331 is incompatible with 2008 Server.

Thank you.

[Auge_Ohr]

hi,

i wonder why People still use v1.9.331 (or older Version) ?
every registered Xbase++ User can download SL1 "Patch" without active Subscription from Alaska Website for FREE !!!

... but for Hotfix ( compile/link/64bit/Server) you need a active Subscription

[rdonnay]

I don't know why either.

My next release of eXpress++ will still support 331 and 355, but nothing earlier.

I have been using 355 for over a year.

[omni]

I have never had a reason to upgrade my Alaska, at least until now.

So what you are saying is that I have to update (free update) from their web site, but will need to pay to get the hot fix?

Just want to be clear.

And Roger, yes, we are compiling directly on the server, at times. I know if we connect to a work station its not an issue, but users do not want to be interrupted and almost 100% of our clients have access via server, mostly remote access. Just a few still use gotomypc.

But if there is a fix, why does it work on some, but not on others?

Fred

[Auge_Ohr]

I have never had a reason to upgrade my Alaska, at least until now.

hm ... there are 19 Hotfix before v1.9.355

So what you are saying is that I have to update (free update) from their web site,

there a 2 Version of SL1 :
1st "full" which need a active Subscription for Download
2nd "without visual Style" which is a "Patch" for "original" v1.9.311 which is FREE.

i prefer Version "without visual Style", but it does not meen that is does not have "visual Style" ...

but will need to pay to get the hot fix?

Hotfix can only be download if you have a active Subscription.