Access Denied Perforce Win Serv 2003

Hi

First, thank you for fixing the issue with the NullReferenceException on the environments page.

I now have an issue with Access Denied when trying to set up

I have a win 2003 server running perforce 2007.3 - the client tools we use are Perforce 2010.2. I downloaded and installed the agent, selecting the local agent and port 81.

When I added the server to build master - everything went well - except I have the error icon in the list of server. (It took me a little while to find the message .) Message was Error scanning agent for dubmomttpro (2)

But the agent status was- hosted: Yes (an agent is installed on the remote server.)

As initially I could not find the error message log, I went on to configure the Source Control provider. That went well. But when I tried to use the .Net application wizard, I was unable to select the solution file. First I got a dialog containing HTML, next I got the yellow screen of death with Access denied.

The firewall is off on both the BuildMaster and Perforce server. So I am not sure why access is denied. (The BuildMaster server is win 2008 R2)

Is there an easy way to diagnose this? Or, given that this is an evaluation, can I just re-install the agent on the Perforce server and try the Soap-hosted Agent? Or is there a way to configure the agent?

Thanks

This sounds unrelated to Perforce, and I believe it's just an agent connection issue. The self-hosted agent is configured by the installer, and it's simplest to just re-install it since they're lightweight.

For other users experiencing a problem like this, make sure to take note which type of agent is being installed. If you're using a service-hosted agent, make sure to select the TCP-based self-hosted agent when adding it to BuildMaster. If you are going to use IIS to host the agent, make sure to select the SOAP-based IIS-hosted agent when adding it to BuildMaster.

To test whether the IIS (SOAP-based) agent is available from the BuildMaster server, you can simply visit a URL from the BuildMaster server: http://agent-server-hostname:port/agent.asmx

To verify whether the Self-Hosted (TCP-based) agent is available, you can telnet to the agent (e.g. "telnet bm-agent-server 81") from the BuildMaster server. If you can connect at all then it is working (there would be no text response). You can also run "netstat -a" on the agent's server to verify that the port is being listened on.

I have re-installed the agent on the perforce box as as soap agent and no longer see an error on the servers page. Instead I have the ready icon. So all seems well, but I still get the Access denied when I try to connect via the providers page.

When I enter into the browser the url http://agent-server-hostname:port/agent.asmx I get connection was reset. Do I need IIS enabled?

The SOAP-based agent is the IIS-hosted agent, so IIS would need to be enabled. The installer for that agent will automatically set up IIS for you.