Bug: Permissions against schema

kbriankelley

Following best practice of assigning permission against schema. No changes to schema other than permissions. For instance:

GRANT SELECT ON SCHEMA::dbo TO SomeRole;
GRANT INSERT ON SCHEMA::dbo TO SomeRole;
GRANT UPDATE ON SCHEMA::dbo TO SomeRole;
GRANT DELETE ON SCHEMA::dbo TO SomeRole;
GRANT EXECUTE ON SCHEMA::dbo TO SomeRole;

Commit to TFS failing on Updating local source control information. Information given is:

The list of changes to commit was out of date, so the commit was refused by...
Expected to add 1 files, but only 0 were added.
[/code]

Chris Auckland

Thanks for your post.

I haven't seen this specific error before, so can I ask exactly what you were doing at the time?

Is this when you're linking a new database to TFS, or are you using an existing repository?

Do you have the necessary permissions to check in and create files in the TFS repository?

Is it only when you're committing these schema permissions changes that you get the issue, or do you have a similar problem committing other objects as well?

BradLarsen

Any updates on this issue? I'm getting the same error message. I'm just trying to commit a small change to a stored procedure... Changing the data type of a parameter from TinyInt to SmallInt.

I don't really understand how the list of changes is out of date. Here's my full process:
1) I went to the GetLatest screen, refreshed, there are no changes.
2) I went to the Commit Changes screen just to be sure, I have no changes pending to commit.
3) I make my edit to the sp.
4) I go to the Source Control window to Commit my Changes. I see a single Edit, with no conflicts.
5) When I try to commit, I get the error, every time.
I have closed SSMS and restarted a couple of times, not really sure where to go next.

Thanks for any suggestions you can provide.

mattkarp

We got the same, "The list of changes to commit was out of date", error when trying to commit a list of specific objects (table and views). What we discovered is that the list of objects which we were changing were all manually rolled back in TFS the day before. We then went to TFS directly and manually made the changes we were trying to commit via SQL Source Control. We then got latest via SQL Source and made a test comment in one of those objects which we manually checked in via TFS and checked in the test comment via SQL Source no problem. It essentially reset the "state" of those objects on TFS after they had been rolled back.

chrisherring

I am getting this error also: "The list of changes to commit is out of date, so the commit was refused by the server".

I am using GIT. The changed object is a stored procedure. I have tried modifying the SP again (adding a comment), but I still get the same error.

I can commit other changes, but no changes related to this object.

Brian Donahue

Hi all,
My interpretation of this message is that the underlying source control system has a conflict that cannot be resolved by SQL Source Control - it's the type of conflict the underlying source control system has its' own methods for dealing with so usually resolving the conflicts in the source control platform itself is the way to go.

reach4thelasers

I am getting this same error with the latest version of SQL SourceControl v3.0.10.34.20.

My repository is up-to-date and there are no conflicts. I've spent an hour trying to fix this already don't know what else to try