EcoStruxure SEAL Forum
This forum is for engineers working EcoStruxure Building Operation, wanting to leverage the SEAL application to improve the efficiency in the engineering process.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-04 06:45 AM . Last Modified: 2024-12-05 03:57 AM
Hello, during deployment of my solution I keep getting the error “Object already exists on path”.
I have attached my solution, and these are the log messages that I got:
Checking application...
Compiling...
Warning: Unassigned IO point detected. Please allocate. Server 1 / VS01 / VS01-GT11 - Tilloppsgivare primärsida
Unassigned IO points will be downloaded as external IOs
Error: An object already exist on path. Path: /Server 1/VS01/IO/VS01-GT11 DbId:12030 Existing DbId: 5783
Used 1937 ms on compiling
Error: Error occurred during compilation
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-04 06:46 AM
Hello, thank you for your question.
Regarding the “Object already exists on path” error it most likely appears because you have multiple components with the same name in your solution. In this case I would guess you have two separate components named “VS01-GT11” leading to a naming conflict since EBO does not allow multiple objects with the same name on the same path.
If you can’t find any components with the same names in your solution, check that no objects are already present on the server at the path provided in the error message.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-04 06:46 AM
Hello, thank you for your question.
Regarding the “Object already exists on path” error it most likely appears because you have multiple components with the same name in your solution. In this case I would guess you have two separate components named “VS01-GT11” leading to a naming conflict since EBO does not allow multiple objects with the same name on the same path.
If you can’t find any components with the same names in your solution, check that no objects are already present on the server at the path provided in the error message.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.