timallen
Well Known Member
Solution: Server Package Won\'t Build
Recently we had problems with a OneWorld Xe installation. Enterprise Server packages would not build. Our Enterprise Server is a Windows 2000 Server.
The symptoms were that the server package would say that it had built successfully, but the bin32 directory in the Enterprise Server would be empty after installing the build.
The problem was that I had not set the environment variables on the Enterprise Server to allow OneWorld to find the Visual C++ nmake facility. Another consultant (thanks Ottaviano!) found this by opening a command line on the Enterprise Server and typing "nmake". It gave us an error of not finding the "nmake" application.
We then found the Visual Studio vcvars32.bat application (which vc++ uses to set environment variable for command line use) and transferred its contents to the Environment variables for all users.
Now package builds for the Enterprise Server go fine.
Recently we had problems with a OneWorld Xe installation. Enterprise Server packages would not build. Our Enterprise Server is a Windows 2000 Server.
The symptoms were that the server package would say that it had built successfully, but the bin32 directory in the Enterprise Server would be empty after installing the build.
The problem was that I had not set the environment variables on the Enterprise Server to allow OneWorld to find the Visual C++ nmake facility. Another consultant (thanks Ottaviano!) found this by opening a command line on the Enterprise Server and typing "nmake". It gave us an error of not finding the "nmake" application.
We then found the Visual Studio vcvars32.bat application (which vc++ uses to set environment variable for command line use) and transferred its contents to the Environment variables for all users.
Now package builds for the Enterprise Server go fine.
