I recently ran into a problem where custom SharePoint solutions will randomly fail to deploy on any of the web servers in the farm. The nature of the problem was hard to debug. The failure can occur on any web server and on any resource file being deployed or when the solution is being retracted. The error message would be as follows:
"Copying of this file failed. This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again."
So it turns out that the internal exception that causes this problem is:
Failed to connect to an IPC Port: The system cannot find the file specified.
There is a new hotfix available for this which updates a .NET Framework DLL, which resolves this issue. The specific KB article that talks about this is
FYI: You need to have .NET Framework 2.0 Service Pack 2 installed before applying this fix.
If you want to debug this and confirm that the internal exception is actually the one noted above, there are 2 ways to use this.
Easy way: Look at the application event logs to see if this exception is logged.
Hard way: !!! Do not try this in Production !!! Read on…
- Download and install Debugging tools for Windows for the platform on which you are running.
- Using ADPlus, log all first chance .NET CLR exceptions.
- Note down the IIS worker process (w3wp.exe) PID corresponding to your app using using task manager
- Save the below script to Debugging tools for windows folder as LogExceptions.cfg
- Execute the command as: CScript adplus.vbs –p <PID> –c LogException.cfg
- Reproduce the problem.
- Inside the debugging tools for Windows folder there is another folder that is created that begins with Crash…The exceptions are logged in a text file that is named as PID-<PID>.exe…
Here is the script:
<Cmd>.loadby sos mscorwks</Cmd>