Copiar un project a otro server

[Emerald]

Muchas gracias a todos por su ayuda!

Definitivamente no puedo debuguear desde mi máquina un proyecto que está en otra máquina, ya no me voy a quebrar tanto la cabeza.. haré los cambios en mi máquina, después´pasaré esos cambios al server y en el browser veré estos cambios...

Si encontré info en FAQ´s, la pasé a los administradores del server, pero no es posible hacer esto, en fin, muchas gracias

Can’t connect to a remote machine because of RPC issue
* this information is from one of KB articles. Thanks for “Mike Clay” who wrote this KB.
If you see the below error messages while you are connecting to remote machine with “Processes” dialog.

Error while trying to run project: Unable to start debugging on the web
server. Not enough storage is available to complete this operation.

Or, you see the below, during ASP.NET debugging.
Error while trying to run project: Unable to start debugging on the web
server. Unable to map the debug start page URL to a machine name.


Please make sure that RPC is working properly between your machine and the remote machine. the reason of RPC issue can be from
1. Debugging through a firewall. Microsoft does not recommend or support remote
ASP.Net debugging through a firewall. The best way to do overcome this is use
Terminal Services to log into the remote server and debug locally.

2. One common failure for RPC is the inability to resolve the remote machine
name. RPC relies on name resolution for communication between machines. If
you are unable to resolve the remote servers machine name to the correct IP
address errors may occur.

3. RPC Traffic can flow in one direction but not the other. RPC traffic must be
able to go from the machine used to do the debugging to the remote server and
from the remote server back to the machine used to do the debugging in order
to successfully debug remotely. Make sure that RPC communication is enabled
in both directions.

To analyze your RPC, you can use “RPCPing” tool