Scalix Forums

I have been using Scalix Community Edition for several weeks with the Outlook connector without problems.

However, starting today (1 July), I can no longer connect via Outlook (web works OK). I get an error message: "You are not licensed to signon to this server".

Has some time limit expired?

My server is Centos (RHEL clone) 4.4. I'm using Outlook 2003.

Hy @ all !


I have the same problem ! Since 1st of July i cannot connecto to my scalix box via outlook connector. SAC & Webmail are working fine.

I've re-installed the whole scalix machine,.. no improvement till now,..also deleted all
accounts and message store
my server is a fedora core 4 with scalix 10.0.5 (community edition) and the outlook connector is 11.0.4 (i know,.. that's not the best choice,.. by it worked for half a jear)

any ideas?

I am running community version 10.x
2 of my laptops have Outlook Connector 11.x, and the other has Outlook Connector 10.x

I have no problems connecting with the 10/10 matchup, but the 11/10 matchup posts that same error.

I suppose it is time to upgrade the server to 11.

We are having the same problem...
Community Edition ver 10.0.5.3

The error message is "You are not licensed to signon to this server"

Any ideas on how to resolve this problem?

SAC and webmail are working fine.

I have several companies using the same setup, that's scalix 10 with connector 11.0.4 / 11.1.0, we are all getting the same message since july 1st. It is definately date orientated as changing the pc date back to before july 1st allows connection (obviously unnacceptable) I have also found scalix connect 10 to be OK. Is there any way round this other than reverting all of these people back to scalix connect 10 ??

@primordius:

I would hold off before you upgrade the server, if I were you. I'm already using 11 on both server and connector.

It looks like a problem with v11 of the connector, irrespective of server version?

Hmm this is somewhat frustrating...

Downgrading my connectors to 10 at the moment. Any ideas here Scalix fellas????

Oops - ignore my last post! I just checked the version of my server (using the webmail Help->About...) and it is 10.0.5.3, not 11 as stated before.

So connector 11 with server 11 might work. I'm trying it now. Sorry for the mix-up!

MrCyrix wrote:I have several companies using the same setup, that's scalix 10 with connector 11.0.4 / 11.1.0, we are all getting the same message since july 1st. It is definately date orientated as changing the pc date back to before july 1st allows connection (obviously unnacceptable) I have also found scalix connect 10 to be OK. Is there any way round this other than reverting all of these people back to scalix connect 10 ?? :cry:

Just to confirm that this is exactly the same problem we have. Changing the PC date resolves - so it is a 1st July 2007 cut-off, almost like a year 2000 bug!

I've just upgraded the server to the latest community version (11.1.0.10849) and that seemed to fix it.

Thank you very much to everyone who posted here.

All,

as per release notes, running a Scalix 11 connector against a Scalix 10 server is *not* supported at all and can, in the worst case and depending on character sets used, lead to data corruption in the message store.

As a general statement, the server must always have a higher version number than the connector (which makes sense because the server is easier to upgrade as there are usually fewer servers than clients).

We also did change the license negotiation mechanism in Scalix 11; as a result and to enformce this, the Scalix 11 connector has a timebomb mechanism that doesn't physically work it in the unsupported confirguration running against an older server after July 1st, 2007.

The obvious solution is to upgrade the server - which you should have done in the first place.

In general, when running mixed versions of Scalix components, I recommend reading the Release Notes carefully - they will have pointers to what's supported and what isn't.

Cheers,
Florian.

Thanks for the reply to those of us having problems, even if it was in a rather self righteous tone.
Obviously you are correct and we should have all been good girls and boys and read the release notes, but often in this busy world of ours these things go by the wayside, (a lesson to us all as we are now busier than ever because of this) However you state that it is easier to upgrade the servers as there are fewer of them. I would tend to dissagree as the connector is a quick upgrade where as the server requires on O/S upgrade as well. Fedora core 4 to 5 in this case.
Thanks anyway, Scalix is generally an excellent product (at least if you don't let activesync anywhere near it.

Sorry, didn't mean to sound that way. Lots of stuff going on these days and I might be a bit stressed out.... Also, we should have made that more clear in a technical way as well, i.e. we should have stopped running connector 11 against a 10 server in the first place if we were not going to support it. This was discussed within our product team at one time, but somehow the ball got dropped in favor of other things.

Having said that, reading your post and given that I just spoiled my reputation anyway (hope not beyond repair ), I'll just add one more strike to it - the fact that those community distros change so frequently and we simply don't have the resources to support more than one of them (i.e. fc4 or fc5 or fc6 and soon fc7, same for opensuse) at a time is the very reason why we actually do recommend running Scalix on an enterprise distro such as RHEL or SLES; in fact, up until a year ago, we actually did not officially support the community distros for production ('for evaluation and testing purposes only') for this very reason. With the introduction of low-cost Small Business Edition, we have relaxed that requirement (and have always been lenient about it anyway, never rejecting a support case), yet still recommend against using them to avoid the upgrade treadmill.

I hope everyone at least can agree that a server upgrade on a stable, unchanged OS platform such as RHEL4 is relatively painless....

Cheers - and again sorry should my wording have sounded inappropriate...

Florian.

MrCyrix wrote:Thanks for the reply to those of us having problems, even if it was in a rather self righteous tone.
Obviously you are correct and we should have all been good girls and boys and read the release notes, but often in this busy world of ours these things go by the wayside, (a lesson to us all as we are now busier than ever because of this) However you state that it is easier to upgrade the servers as there are fewer of them. I would tend to dissagree as the connector is a quick upgrade where as the server requires on O/S upgrade as well. Fedora core 4 to 5 in this case.
Thanks anyway, Scalix is generally an excellent product (at least if you don't let activesync anywhere near it.

I'm in the same boat - about to upgrade from FC4 to FC5 before upgrading from Scalix 10 to 11. I've posted about the upgrade process (viewtopic.php?t=8046) as I have to do this upgrade quickly and also remotely.
Any pointers appreciated before I dive in!!

That's ok, were all stressed i guess..............lol
I see your point about using rh enterprise etc, I will maybe have to consider this for future installs.

Thanks again