package build - tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the

[fortylove]

package build - tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the

Morning List, our FULL client/server build (GBRSPEC) failed on the weekend. I have never seen this error before and was hoping you might know what the problem is. I have pasted below a small piece of builderror.txt and the jde.log from the Deployment Server. Any ideas would be much appreciated.

Thank-You.

XE, XU7, SP 22, iseries 400, V5R2, World A7.3 Cum. 11

Builderror.txt on Deployment Server

11/27/2004 12:39:46 0 Spec file GBRSPEC begun.
11/27/2004 12:39:46 0 RDB record count in GBRSPEC : 2765120
11/27/2004 12:58:46 0 ERROR: Could not add record to Pack file GBRSPEC. Record: evseq: 37, esevsk: c7857d25-a240-11d0-a204-0000f6728a56. See jde.log for more information.
11/27/2004 12:58:46 0 ERROR: Could not add record to Pack file GBRSPEC. Record: evseq: 52, esevsk: c7857d25-a240-11d0-a204-0000f6728a56. See jde.log for more information.
11/27/2004 12:58:46 0 ERROR: Could not add record to Pack file GBRSPEC. Record: evseq: 58, esevsk: c7857d25-a240-11d0-a204-0000f6728a56. See jde.log for more information.
11/27/2004 12:58:46 0 ERROR: Could not add record to Pack file GBRSPEC. Record: evseq: 75, esevsk: c7857d25-a240-11d0-a204-0000f6728a56. See jde.log for more information.
11/27/2004 12:58:46 0 ERROR: Could not add record to Pack file GBRSPEC. Record: evseq: 89, esevsk: c7857d25-a240-11d0-a204-0000f6728a56. See jde.log for more



JDE.LOG on Deployment Server


2992/1396 Sat Nov 27 12:05:20 2004 jdb_rst.c1099
JDB9900307 - Failed to find table specifications
2992/1396 Sat Nov 27 12:05:20 2004 jdb_rq1.c1464
JDB3100007 - Failed to get valid table specifications
2992/1396 Sat Nov 27 12:05:20 2004 combined.c344
RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

2020/2976 Sat Nov 27 12:58:46 2004 PkgPack.cpp369
ERROR: fwrite failed, file '9Ûr
ÿ '.
2020/2976 Sat Nov 27 12:58:46 2004 PkgPack.cpp369
ERROR: fwrite failed, file '9Ûr
ÿ '.

2020/2976 Sat Nov 27 12:58:46 2004 PkgPack.cpp369
ERROR: fwrite failed, file '9Ûr
ÿ '.

2020/2976 Sat Nov 27 12:58:46 2004 PkgPack.cpp369
ERROR: fwrite failed, file '9Ûr
ÿ '.

2020/2976 Sat Nov 27 12:58:46 2004 PkgPack.cpp369
ERROR: fwrite failed, file '9Ûr


2020/2976 Sat Nov 27 13:03:27 2004 JDETAM.C2061
tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the file. WinErrNum=33. (\\missowdep1\b7333\py7333\package\pyxef6\spec\gbrspec.ddb)

2020/2976 Sat Nov 27 13:03:27 2004 JDETAMP.C4359
tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the file. WinErrNum=33. (\\missowdep1\b7333\py7333\package\pyxef6\spec\gbrspec.ddb)

2020/2976 Sat Nov 27 13:03:27 2004 JDETAM.C2061
tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the file. WinErrNum=33. (\\missowdep1\b7333\py7333\package\pyxef6\spec\gbrspec.ddb)

2020/2976 Sat Nov 27 13:03:27 2004 JDETAMP.C4359
tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the file. WinErrNum=33. (\\missowdep1\b7333\py7333\package\pyxef6\spec\gbrspec.ddb)

2020/2976 Sat Nov 27 13:03:27 2004 JDETAM.C2061
tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of the file. WinErrNum=33. (\\missowdep1\b73

 

[brother_of_karamazov]

Re: package build - tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of

What environment are you logged in to when conducting the build?

 

[wgrantusa]

Re: package build - tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of

I also get this same error message. I am signed on to the DS in the DEP7333 environment. I am thinking that some are people are connecting in over the weekend while I am trying to do a full package build. Do you think this is the problem?

Stephanie

 

[sashton]

Re: package build - tamfwrite: FAILED - The process cannot access the file because another process has locked a portion of

Hmmm...I would try a couple things. First, if you are building a DV full or a pathcode that might have developers checking objects in or out, disable Check-In Check-Out while doing the build. Just having users log in should not be a problem when doing a build. Checking in or checking out objects in OMW could be an issue. Second, I started building my Full pacakges from just a normal Fat Client workstation in whichever Path Code I am building. A couple things to make sure of is that the BusObj folder is empty. Also, disable any Anti-Virus software. I have been having clean full builds, both Client and 2 enterprise servers in 6 hours or less running it on a simlple P4 2.6Ghz workstation. Let me know if this helps.