cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment problem

Former Member
0 Kudos
73

Hi All,

I am facing one strange problem while deploying my WebDynpro application.

After I opened my NWDS the very first time application is deploying perfectly, from second time I am not able to deploy the application and getting the following error.

'Problem creating zip: C:\Working Copy\LCMHD_Overview\bin\hdmc\model\expexl\types\ExpExlStatusChange.gdictionary (The process cannot access the file because it is being used by another process)'

Please if anybody let me know what to do if you were faced same kind of errors before.

I tried by rebuilding the project and deploying but facing the same problem.

If I closed my NWDS the opened again and tries still the problem persists.

If I restarted my system it is working some times but not every time.

From the error message I understand that some file is being locked by some system process.

But do not have any idea of how to release the same.

I will really appreciate the reply's from you guys.

Thanks & Regards,

Seshu.

Accepted Solutions (0)

Answers (4)

Answers (4)

Rodrigo-Giner
Active Contributor
0 Kudos

mmm I never see this.

Check this list, to see if any of this option works.

- Right click in proyect name -> Repair -> Proyect Structure and classpath. Then deploy and run again.

- You could try to restart the J2EE engine.

- Reinstall SAP development studio.

Former Member
0 Kudos

hi Reddy,

With respect to your problem please try to clear the cache and then restart the NWDS.

Go and right click on the IE and click on properties and try to delete the temporary Internet files.

Now try to deploy ur application and see. Hope this would help.

Thanks,

kris

Former Member
0 Kudos

Hi Seshu,

It sounds like your NWDS installation has problems. The first thing I'd try is to download the installation from service.sap.com again and reinstall the software.

Which version of NWDS are you using?

Gareth.

Former Member
0 Kudos

Hi Seshu,

I don't have a direct solution for this But just try restarting just SDM instead of restarting engine which might help in reducing the time !!!

Regards, Anilkumar