Failed to check in resources into Dexterity DSCCS

This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.

This happened to me again the other day – and it took me a few minutes to resolve (and re-solve!) it again.

To me that sounds like blog material.

I had just finished creating and testing my new Dexterity integrating application and needed to check it into source control.  As I’ve noted previously, we use Visual Source Safe for this but that wouldn’t make a difference for the issue I ran into.

I chose to check in my dictionary – the process started and finished in a minute as it was a small customization.

The error report printed and to my surprise it listed two errors.

get_account.function

     Checking in

          Insufficient permissions to create filen

get_index.function

     Checking in

          Insufficient permissions to create filen

I checked my project in VSS and found all my other procedures/function and other items checked in just fine.  I did NOT find a get_account or get_index function checked in or out in that project.  They did not exist.  Also, how could I get an “Insufficient permissions” error when everything else checked into VSS correctly?  And just what the heck is a “filen” anyway?

So what else would I need permissions on?

The only thing I could think of was the temp folder specified in the Dexterity | Options | Source Control tab.  But that doesn’t seem right.  If it was a permissions issue on the folder itself, why did the other stuff check in OK?

When I opened the temp folder to take a look, I found the source of the problem.

The files get_account.function and get_index.function both already exist in my temp folder and they were marked read-only.

Things are clearing up now.  Dexterity is exporting the items to the temp folder.  These items previously existed in the temp folder and set to read-only and so therefore the write operation from Dexterity failed.  This was interpreted as a permissions error and the check-in failed.  Not sure why they were there but I think I had opened the files in Visual SourceSafe Explorer which must have copied them into my user temp folder and marked them read-only.

After deleting the 2 stray files, the last two functions were checked in successfully.

So what about the “filen” message?  Honestly I had always assumed that the message was just truncated on the report.  But after looking at the Dex.dic, this is message 406 and that is the full message.  So given the problem and solution, I think the last part of the message is just a typo.  “filen” should be just “file”.  And now it is more clear that that I didn’t have permissions to create a file which makes much more sense in the end.

Best Regards,
Patrick Roth

This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.