headToWorkingBase didn't get set

• 
  Hi @Dkaur
  
  Sorry you're getting this issue!
  
  Could I ask, have you tried unlinking and relinking the database from SQL Source Control? sometimes this can help clear any cache that might be causing an issue.
  
  Let me know if that works or if you require further help!

  DanC June 15, 2020 11:34

  - 0 +
• 
  I have the exact same issue. Yes, I unlinked and relinked and still have the same issue. This product is 100% unusable in the current state. Please provide a fix, or a link to the previous version so I can get this working again.

  EZLinks June 15, 2020 14:22

  - 0 +
• 
  Hi @EZLinks
  
  Apologies the steps didn't help to resolve the issue!
  
  Could you try switching branches using git cmd and committing to see if the error persists?
  
   If you're able to provide me with the version number you were on previously I can give you a direct link.

  DanC June 15, 2020 14:33

  - 0 +
• 
  I did unlink and re link the database. I use SVN, not GIT. I still get error:
  headToWorkingBase didn't get set
  

  Dkaur June 15, 2020 19:34

  - 0 +
• 
  Hi @Dkaur and @EZLinks can I ask, if you upgrade to 7.127 and perform a refresh does this resolve the issue?
  
  Also is this occurring for multiple projects or just the one?
  

  DanC June 18, 2020 11:01

  - 0 +
• 
  I deleted the two conflicting object in the repository using Repo browser. It works fine after that.

  Dkaur June 18, 2020 19:42

  - 0 +
• 
  There were no updates available, so I assume I am running the latest, and can not even check the version with Help|About... since it totally crashes the environment and presents an exception dialog saying "Object reference not set to an instance of an object."  Just getting tired of the updates breaking so frequently from red gate lately.

  EZLinks June 19, 2020 15:33

  - 0 +
• 
  Hi @EZLinks
  
  Sorry to hear that!
  
  Could you reach out to us on support and we can troubleshoot these issues with some extra information and try to find a solution!

  DanC June 19, 2020 15:37

  - 0 +
• 
  I have had an open ticket now for over 5 days and absolutely zero resolution for this critical issue. For as much money as I've spent on licenses, I would expect better. This solution has been unusable since late last week.

  EZLinks June 19, 2020 15:50

  - 0 +
• 
  Hi @EZLinks
  
  Sorry, I've found your ticket and the issue is no longer to do with "headToWorkingBase didn't get set" and so we're having to investigate multiple issues which takes time unfortunately.
  
  
  

  DanC June 19, 2020 15:58

  - 0 +
• 
  I am actually still getting this error "headToWorkingBase didn't get set" when I re-link to my Git repo, however the biggest issue is the inability to use the product at all due to additional errors following this initial error message.

  EZLinks June 22, 2020 14:59

  - 0 +
• 
  Same problem suddenly started occurring with one database using version 7.2.20.12234.
  Logs show " A duplicate definition was found for the column xxx" exceptions.
  Why? Column, by definition, cannot be duplicate.

  rick June 01, 2021 16:09

  - 0 +
• 
  Hi @rick@syncbak
  
  Would you be able to reach out and submit a ticket to support?

  DanC June 02, 2021 08:50

  - 0 +

Add comment

Please sign in to leave a comment.