SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This 2 external lists are different projects, which developed by VS 2012. So when I deploy one of them, they have to not effect eachother. But these effects eachothers.

Here is the situation:

Project1 deployed , Project 2 doesn't work.

Project2 deployed , Project 1 doesn't work.

How can I avoid it?

share|improve this question
Check the ULS log during installation of the second solution. Probably some code or artifacts in the solution is not able to be run or created due to the first solution / project – Robert Lindgren Jun 19 '13 at 9:06
In the logs when deploying both, there is no clue. When project1 deployed there is only logs about project1 during this job. – e.ozmen Jun 19 '13 at 11:37
OK, i still think that the solutions are trying to create the same list or something like that. Whereby the last one installed fails due to a lack of error handling – Robert Lindgren Jun 19 '13 at 11:58
Is it possible to creating the same list? Because they are different VS Sharepoint Projects. I'm looking more deeply into the logs :/ – e.ozmen Jun 19 '13 at 12:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.