Original User: crafty762
Is it possible for you to restart your MSSQL Server instance on the database server? We use Oracle, but we've seen similar errors when our DBMS pipes do not use the next correct number for something like object ID. This can occur if you've truncated a table and re-loaded it from another source. Restarting Oracle for us allows the pipes to be cleared out. Perhaps this issue also occurs with SQL Server. I'm sorry I don't have a better explanation than this, but it may be helpful to you.
Another thing you can do is to drop the MV view, perform the compress, and then re-create it (you can script this too).