Issue "Error 1303 : Already defined"

Hi all,

I am working on Venus 5 with dynamic scheduler on a Vantage.
Since today, I have an error when I lauch my workflow : error 1303 identifier ‘StringTable’ has already been defined’ C:\Program Files (x86)\HAMILTON\HSLMECCLibEnu.hs_(79)
I didn’t make any modification on my methods, I only had a hard reboot of Venus
I tried restart everything.
I have never created any variable named StringTable

I CopyPast all lines of my Init method to new one, I don’t have this issue anymore but now I have it on my main method on my workflow.

Thank you for your help
Thibault

It looks like you have had some extra copies of libraries brought in to your local install from previous pkg imports. Your error is being triggered because both copies of a particular library are being included by various dependent files of your workflow and methods, and during run analysis the compiler recognizes that and throws an error.

Fortunately the fix is simple. You have a copy of the following library file outside of of the default library folder.

In your case it appears that the extra copy is directly in the root of the Hamilton folder. Delete the copy and you should be set.

-Nick

2 Likes

It works !
Thank you very much,

I didn’t installed any pkg recently, so I don’t know

Thank you Nick

Thibault

1 Like

Can I hijack this thread and ask how you are liking the dynamic scheduler? I’m interested in your experience, how many methods are running simultaneously, and how many devices you are integrating.

Thanks!!

Hello,

I have this issue again on my Vantage Venus 5 with scheduler. Its is my 2nd task which does the error. (my 1st task is an init methode and my 2nd is my main method)
I tried this fix, but it is not working, thus I have an error saying that this .hs_ is missing.
I tried to change my workflow, have multiple time the first task, and I still have the same error at the 2nd task.
I tried to redo from scratch the .wfl and init.med (not the main .med) and I have still this error.

Do you have any idea ?
Thank you
Thibault

Hi @Thib ,

Can you post a trace file of the error that you are encountering? An export would also be helpful to determine your issue. Based on your previous issues, I suspect a duplicate library is likely causing an issue where Task 1 is calling from one location and Task 2 is calling from another.