"access denied" to entire solution

Jul 5, 2012 at 4:55 PM

This extension looks really cool, so I've been trying to set it up. I have it in Visual Studio with P4Config detection, and VS2P4 identifies my root directory properly.

Then this happens - at least according to my ActivityLog:

 <entry>
    <record>520</record>
    <time>2012/07/05 16:37:06.585</time>
    <type>Information</type>
    <source>VS2P4</source>
    <description>09:37:06.445: Information: Starting to set file states for 32 files on background thread</description>
  </entry>
  <entry>
    <record>521</record>
    <time>2012/07/05 16:37:06.648</time>
    <type>Warning</type>
    <source>VS2P4</source>
    <description>09:37:06.648: Warning: P4Service.SendCommand() 2: C:\develop\MySolution\MySolution.sln - protected namespace - access denied.&#x000A;[repeats for the other 31 files.]</description>
  </entry>
  <entry>
    <record>522</record>
    <time>2012/07/05 16:37:06.648</time>
    <type>Information</type>
    <source>VS2P4</source>
    <description>09:37:06.648: Information: Finished setting file states on background thread for 32 files, took 33 msec</description>
  </entry>

I'm left with only the "Add" and "Refresh" commands. This despite the fact that my copy of P4V has no problems whatsoever.

Is this a bug, or am I missing something about p4 permissions?

Arithmomaniac

Coordinator
Jul 5, 2012 at 10:15 PM

It's not a known bug, and I haven't seen this issue before, but many others have. A google search for "p4 access denied protected namespace"

gives a lot of links. The best one I've seen is http://stackoverflow.com/questions/3506367/why-does-perforce-show-depot-contains-no-files-or-folders

You might try to run "p4 fstat" and other p4 commands from the command line in the directory where the .sln file is located. If that works and VS2P4 still doesn't, email me some more clues. brubaker dot dale at gmail.com 

Maybe I can help, maybe not...

 

Coordinator
Jul 5, 2012 at 10:16 PM

When I said in the previous answer that "many others have" seen this problem, I might have been misleading. No one has reported the issue with regard to VS2P4. Many have had the issue with P4 and P4V.