Old IDES System State

2008-11-27: WebGUI is available again!

Access via WebGui is now available again. We had issues with the disk utilization, that are fixed now. 

2008-11-26: WebGUI is down!

At the moment the logon to the IDES System via WebGUI is not possible. You can use a locally installed SAP-Logon instead. You find information about the configuration in our FAQ.

2008-09-19: System is up again!

Finally we are done implementing EHP3. The system is up and running again. You can reactivate your users on http://ides.consolut.eu/user

2008-09-16: System is down a bit longer...

We are sorry to inform you that the implementation of EHP3 is not yet finished. Therefore the system will be down a bit longer. We hope to be finished on Friday at the latest.

2008-09-11: System is down until Tuesday...

We install Enhancement Pack 3 in the system. Therefor the system will be down for a few days. We think it will be up again on tuesday.

2008-08-16: System is up again ...

Unfortunately a crazy person deleted the license. Therefore, we had again to limit the authorizations again. Unfortunately, we have to tell you, if this happens again, we will have to stop this free of charge service ;-(

2008-08-15: License deleted by "somebody nice! => system down for the next days ...

As some nice person deleted the license in the system, the system is down now ... we will let you know, when this is fixed.

2008-08-14: No more new users!

Because of licensing issues consolut can not provide new users for the free IDES.

2008-08-08: The consolut IDES System is up again ;-))

The IDES System is up and all IDES users are locked. So, please unlock them, when you want to use the system (as you know, that they are locked again after "non-usage", please only unlock when you need it because of licenses)
You can unlock your user as you are used to at: www.ides.consolut.eu/user
Let us hope, that nobody crashes the system again ...

2008-08-01: The consolut IDES System is down!

The IDES System is down because somebody has destroyed it by purpose ;-(((
We are working on a solution and try to prevent that this happens again. Unfortunately, this means, that we have to reduce the authorization of your accounts and have to prevent repository changes in client 500 as well ;-(