Hi Maesto,
A few things to check:
1) Can OneWorld find Visual C++ to do the build? Test it this way:
- Open a command prompt
- type "nmake"
you should get this message:
"Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop."
If you get this message:
"nmake" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
oops, if you get a message that the program "nmake" can't be found, then you need to set environment variables so Visual C++ is visible to OneWorld. Do this by looking in C:\Program Files\Microsoft Visual Studio\VC98\Bin\vcvars32.bat and copying this information to the environment variables on your build machine *AND* on the enterprise server.
2) Assemble the package from the environment you are building for (that is, if the package is for PD7333, assemble signed in to PD7333). If you build from the deployment server, build from the environment DEP7333. If you do it from the environment you are building for, you'll get problems since the Deployment Server will have some files you are trying to replace locked since it is using them. If you build from another workstation, build from the environment you are building for.
Try those out-- I chased the first problem for a month once. Hope this helps.