While doing the full publish the following error comes. Can anyone suggest on what can be the issue :

Compiling eSpace Compiling 'om_e_smb'.
Internal Error The 'BasicTypeList<Integer>' name is already in use.  

What are you publishing, a full solution? Are you doing it via Service Center or LifeTime? What causes the error? An eSpace? An extension? You are providing us with way too little information for an answer.
Sorry for the insufficiency of info.
I am getting the error given below for both the scenarion

1. A full solution is being published via Service Center. 2. Lifetime .

This is everytime after a perticular espace (Example :Util eSpace) .How to track why this error is coming?

The 'BasicTypeList<Integer>' name is already in use.
Environment Information  
Exception Details:
[1] Internal Error: The 'BasicTypeList<Integer>' name is already in use.
   at outsystems.runtimecommon.HEMessageException.<init>(Unknown Source)
   at outsystems.hubedition.compiler.utils.IIIIiiiiiIIiiI.$hxf(Unknown Source)
   at outsystems.hubedition.compiler.utils.IIIIiiiiiIIiiI.$lpf(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.afterLoad(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.<init>(Unknown Source)
   at outsystems.hubedition.compiler.Compiler.innerCompile(Unknown Source)
   at outsystems.hubedition.compiler.Compiler.compile(Unknown Source)
   at outsystems.hubedition.compiler.Compiler.$abl(Unknown Source)
   at outsystems.hubedition.compiler.iiiiIiiiiIIiII.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.compiler.utils.CompilerUtils.withOverridenSettings(Unknown Source)
   at outsystems.hubedition.compiler.IiiiiiiiiiIiii.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.ThreadStart.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:682)


Do you also get this error when manually publishing the affected eSpace? Or only when publishing a full solution?
No I do not get this error when I pubish the espace manually. I get the error only when I do a full sollution publish and lifetime move from one environment to other.
That is decidedly weird. Have you contacted OutSystems support about this? It may be a platform bug.
This same problem occured for me too. Unable to deploy the eSpace using lifetime.

03-10-2015 10:54:35 The 'BasicTypeList<int>' name is already in use.

With service studio the publish to the next staging environment went through fine.
I also experience this error with a particular espace when:
  1. Deploying my application over to another environment using LifeTime
  2. Publishing my application via ServiceCenter
Strangely, I am able to publish that espace via ServiceCenter or ServiceStudio.

This is my workaround:
I changed the input parameter of public method from <List of User Identifier> to <List of Integer>.
Tata! I am able to deploy via LifeTime and ServiceCenter after this.

Apparently having <List of EntityRefInteger> as parameter in a public method causes this error. Try using <List of Integer> instead. You can still convert it back using IntegerToEntityRefInteger after that.
Seems like a platform bug to me.

Hope this helps :)

Running on Outsystems Platform Version

Same error here. On platform, Lifetime or SC.

When publishing via Studio ( the problem doesn't occur.

Pretty sure I reported this as a bug ages ago.


Same error here on


This problem was already fixed in the versions and (Platform Server .NET and Java).

The bug caused two different types in OutSystems (for example, Integer List and User Identifier List) to be translated to the same underlying type (in this case List<int>), resulting in a compilation error as you've seen. The error would occur when compiling a Solution or Application. If you publish the eSpace alone, it should not happen.

You can avoid the problem by using a Record List instead of List for the OutSystems type.

I hope this information can help you overcome the problem.

Thanks Cláudia, that's informative, and good news :).

Great news... Thanks