yea you can PM me over some addy's
@ Process
Visual Studio Debugger
Unable to Attach to the Process
Error Message
Unable to attach to the process. Debugger component on server received access denied while connecting to this machine.
There are two common scenarios that cause this error:
Scenario 1: Machine A is running Windows XP. Machine B is running Windows Server 2003. The registry on Machine B contains the following DWORD value:
HKLM\Software\Microsoft\MachineDebugManager\AllowL aunchAsOtherUser=1
User 1 starts a Terminal Server session (session 1) on machine B and starts a managed application from that session.
User 2, who is administrator on both machines, is logged onto Machine A. From there, he or she tries to attach to an application running in session 1 on Machine B.
Scenario 2: One user is logged onto two machines, A and B, in the same workgroup, using the same password on both machines. The debugger is running on Machine A and trying to attach to a managed application running on Machine B. Machine A has Network access: Sharing and security model for local accounts set to Guest.
To solve Scenario 1
Run the debugger and managed application under the same user account name and password.
To solve Scenario 2
From the Start menu, choose Control Panel.
In Control Panel, double-click Administrative tools.
In the Administrative tools window, double-click Local Security Policy.
In the Local Security Policy window, select Local Policies.
In the Policies column, double-click Network access: Sharing and security model for local accounts.
In the Network access: Sharing and security model for local accounts dialog box, change the local security setting to Classic, and click OK.
Source...MSDN
if it's not either of those (which I doubt it is) PM me the source, I would love to solve this issue (as I have never seen it before, and I love challenges
)
Possible trainer CA?
Originally Posted by XGelite
.
, its not defined and does not return a value. Lol