- Initializing Visual Studio
- Visual Studio is missing the CloudBees Build Acceleration menu
- Application Data folder could not be created. make: * [all]
- For VS2005 SP1 builds, the build is not broken up and runs as one large job
- Build terminated with “not making progress” error
- Visual Studio quits immediately at the start of the build
- Error “’devenv’ not found” is displayed
- Error “Unable to build specified project” or missing file errors
- Error “msbuild not found”
- Missing DLL errors or Visual Studio installation is corrupt
- Error “command line too long”
- The build is slow (not parallelized) and/or each line of the build output is prefixed with 1>, 2>, etc
- Error: ‘|’ not recognized
- When virtualizing the Visual Studio toolchain, regsvr32 fails trying to register a DLL that uses debug CRT DLLs
- Particular projects do not build under Electrify
- CloudBees Build Acceleration menu in Visual Studio is grayed out (disabled)
- Using Visual Studio 2010, a project fails at link when using the add-in but succeeds when using Visual Studio alone
- Upgrading only cluster agents to CloudBees Build Acceleration v7.0 might cause an error
This section describes how to initialize Visual Studio and then fix common issues after you verify that Visual Studio initialized properly.
If you do not virtualize the toolchain and did not initialize Visual Studio on every agent host for each ECloudInternalUser during installation, you must do the initializations manually. Each agent runs as user ECloudInternalUser1, ECloudInternalUser2, and so on.
On each agent host:
Log into the user account.
Run Visual Studio.
Choose Tools > Options and browse to Project and Solutions > Build and Run.
Set the maximum number of parallel project builds to 1.
Choose Help > Customer Feedback Options.
Initialize the Customer Experience Improvement Program to either Yes or No.
3:Error: Adding Build menu item: Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
"%PROGRAM_FILES%\Microsoft SDKs\Windows\v7.0A\Bin\gacutil.exe" -i "%PROGRAM_FILES%\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\stdole.dll"
Run Visual Studio and check if the CloudBees Build Acceleration menu is present.
If Step 3 doesn’t work, install the Office 2003 Update: Redistributable Primary Interop Assemblies from https://download.cnet.com/Office-2003-Update-Redistributable-Primary-Interop-Assemblies/3000-2064_4-10742122.html.
This resets the menus.
Do one of the following:
Use one of the solutions described in the “What does it mean when Visual Studio reports "The Application Data folder for Visual Studio could not be created"?” Ask article at https://ask.cloudbees.com/questions/707/what-does-it-mean-when-visual-studio-reports-the-a.html.
Use ecdevenv locally (so that
devenv.exedoes not need to run on the agent).
There are many reasons for this error. It usually occurs when a build has shown a modal dialog box (that is not visible to the build user) and is waiting for input.
The build is slow (not parallelized) and/or each line of the build output is prefixed with 1>, 2>, etc
Check that the Visual Studio Converter is installed on the agents or build machine. (Go to Tools > Add In Manager.)
For VS2005 SP1, check if the hotfix is installed (see above).
When virtualizing the Visual Studio toolchain, regsvr32 fails trying to register a DLL that uses debug CRT DLLs
Do one of the following:
Copy debug DLLs from
<VSINSTALLDIR>\VC\redist\Debug_NonRedistto the target directory (the location of the DLL that is being registered)
Also, the debug log will contain:
AddCommandControls failed for Build: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
When upgrading the cluster agents only to CloudBees Build Acceleration v7.0, be advised that an older eMake client will run the same version of eMake on the agent (if it is available). This might result in the following error:
NMAKE : fatal error U1073: don’t know how to make '|'