Hi Justin,
connection between TMS and condcutor is on https only. So for any information exchanged to/fro from TMS and conductor will use https connection.
the error points that something is wrong with the https connection, probably https communication is getting reset or broken time to time. you can collect the wireshark from condcutor and tms and check if you see the same https error.
reagrding the error you mentioned this is conductor replying to probably one of message from TMS in reply to conf creationg message from TMS.
this could be a possibility because of the https connection error. after the tms conf creation message reach to conductor, condcutor instructs the mcu to create conf and then after successfull conf creation on mcu forwards the feedback message to TMS, now if the feedback for conf creation is lost in between because of https connection error then TMS will send another message for conf creation and since the conf is already created and running, condcutor replies to TMS with the message that conf alreadt present.
i hope the above explains the theory for the error you are seeing. i think with wireshark capture you can get more information on this. if the problem persist and you can't find any specific reason i advise you to open TAC case.
Thnx
Alok
