Most of the time the SharePoint Timer Service is keeping hold on the files. You can try the following:
- stop SharePoint Timer Services on both WFEs
- perform IISRESET on both WFEs
- redo the deployment
- If successful restart the SharePoint Timer Services on both WFEs
This didn't work.
I have more detail now too.
I have 4 farms, F02 Test, F02 Prod, F04 Test, F04 Prod. The test/prod environments should mirror each other.
On F02 & Test/Prod the following solutions were not deployed
NintexForms2016core.wsp
| Last Operation Details: | Server Name : The solution has not been upgraded. |
Nintexworkflow2016core.wsp
Reason:
Server1: Error: The copying of this file failed: BinNintexWorkflowStartAutofac.dll.
The process cannot access the file 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BinNintexWorkflowStartAutofac.dll' because it is being used by another process.
Server2: Error: The copying of this file failed: BinNintexWorkflowStartAutofac.dll.
The process cannot access the file 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BinNintexWorkflowStartAutofac.dll' because it is being used by another process.
Server3: Error: The copying of this file failed: BinNintexWorkflowStartAutofac.dll.
The process cannot access the file 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BinNintexWorkflowStartAutofac.dll' because it is being used by another process.
Server4: Error: The copying of this file failed: BinNintexWorkflowStartAutofac.dll.
The process cannot access the file 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BinNintexWorkflowStartAutofac.dll' because it is being used by another process.
F02 also can't deploy nintexexternalconnection.wsp to the app server for the following reason:
C:WindowsTempsolution-0ba88400-31ea-462c-8603-6e4b34d70fec
intexexternalconnection.wsp could not be created because the contents could not be found under id 18a1869d-dd59-4c8f-8526-b946a649022a in the configuration database
These are in addition to the errors I noted in the first post.
Was this issue encountered on a fresh installation? If not, ensure all the older DB created for Nintex be deleted from the SQL and try again after an IISREST.
You could use "unlocker" tool or process explorer to see what process is blocking the file.
Process Explorer
Unlocker Download | ZDNet.de
Kind regards,
Enrico
Just to give an update - yes this was a fresh installation. After working with a Nintex engineer we discovered I needed to turn off the Nintex services on my app and web servers then redeploy the solutions. This resolved the problem.
Great to hear! Can you mark your question as answered to let other people see the problem has been resoved?
Could you clarify the solution? Do you mean you stopped the Nintex service within windows services on your WFE and APP servers?
Just confirming I also have to manually stop the Nintex services every time I do the upgrade deployment. I receive the same "process in use" error every time I try to deploy, and this happens in every farm, every time.
Solution: manually go into services.msc and stop all the Ninex services, before performing any installations/upgrades.
Then manually start the services after the upgrade.
