- Posts: 568
- Thank you received: 72
Adding New Project causes INSERT statement conflict with FOREIGN KEY
- bruce.gibbins
- Topic Author
- Offline
- Platinum Member
-
Less
More
4 years 6 months ago - 4 years 6 months ago #18970
by bruce.gibbins
We recently upgraded to AETLP v.6.3.4.4 but found today that when adding a new PROJECT we receive the attached error indicating that an INSERT statement conflicted with the FOREIGN KEY constraint FK_OBJECT_TREE_OBJECT_TYPES
We are using SQL Server 2017
I could not tell you when this error first became a problem as we do not have the need to create new projects very often and it would have been several releases ago that we did.
The Project seems to get created and we can then delete it but I am not sure what downstream issues this may present.
Thanks in advance
We are using SQL Server 2017
I could not tell you when this error first became a problem as we do not have the need to create new projects very often and it would have been several releases ago that we did.
The Project seems to get created and we can then delete it but I am not sure what downstream issues this may present.
Thanks in advance
Last edit: 4 years 6 months ago by bruce.gibbins.
Please Log in or Create an account to join the conversation.
4 years 6 months ago #18972
by admin
Mike
ETL Architect
Replied by admin on topic Adding New Project causes INSERT statement conflict with FOREIGN KEY
Can you see mongodb as a connection?
If not you have to patch your repository as described here towards the end.
www.etl-tools.com/articles/january-etl-update.html
If not you have to patch your repository as described here towards the end.
www.etl-tools.com/articles/january-etl-update.html
Mike
ETL Architect
The following user(s) said Thank You: bruce.gibbins
Please Log in or Create an account to join the conversation.
- bruce.gibbins
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 568
- Thank you received: 72
4 years 6 months ago #18983
by bruce.gibbins
Replied by bruce.gibbins on topic Adding New Project causes INSERT statement conflict with FOREIGN KEY
Thanks. Seems to be that we missed the repo updates from September 2018 where as we had the ones you mentioned in the January Update.
May I suggest that the YEAR be added to these update pages as the post you mentioned is for "January 2018" I think whereas I raised this in 2019 and incorrectly assumed the January in the URL referred to January 2019.
thanks again
May I suggest that the YEAR be added to these update pages as the post you mentioned is for "January 2018" I think whereas I raised this in 2019 and incorrectly assumed the January in the URL referred to January 2019.
thanks again
Please Log in or Create an account to join the conversation.