Jenkins build using DISM randomly started giving ERROR 50 (WINPE error) - windows

I have a jenkins pipeline job, it successfully built last week, this week I've started getting errors and failed builds. The environment hasn't changed.
Edit: the node is server 2016
jenkins#CIBUILD2 C:\Build\workspace\BC870-OP\Build>REM ******************* D DRIVE ***********************************************
jenkins#CIBUILD2 C:\Build\workspace\BC870-OP\Build>copy /Z /Y /B \\someserver\share\Windows10\BC870\BaseImages\\BC870_1.0.0.0_D.wim .\ || goto error
Access is denied.
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Error: 50
The request is not supported.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Failed to build image with error 1
The copy function works fine from the command line. I believe the issue is the next line in the batch file that is a dism command. mount_d is previously set to C:\mount_d and the wimfile is called out in another included batch script.
%dism% /MOUNT-WIM /WIMFILE:"%Win10_Base_Image_D%" /INDEX:1 /MOUNTDIR:%mount_d% || goto error
and here is the DISM log file.
2022-01-10 11:23:05, Info DISM PID=4664 TID=2572 Scratch directory set to 'C:\Users\jenkins\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2022-01-10 11:23:05, Info DISM PID=4664 TID=2572 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM PID=4664 TID=2572 Successfully loaded the ImageSession at "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM" - CDISMManager::LoadLocalImageSession
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM DISM Manager: PID=4664 TID=2572 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: Host machine information: OS Version=10.0.14393, Running architecture=amd64, Number of processors=4
2022-01-10 11:23:05, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1
2022-01-10 11:23:05, Info DISM DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /UNMOUNT-WIM /MOUNTDIR:"c:\\mount_c\\bc870-op" /DISCARD
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Warning DISM DISM Provider Store: PID=4664 TID=2572 Failed to load the provider: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2022-01-10 11:23:05, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
[4664] [0x80070002] FIOReadFileIntoBuffer:(1381): The system cannot find the file specified.
[4664] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[4664] [0xc142011c] WIMGetMountedImageHandle:(2897)
2022-01-10 11:23:05, Info DISM DISM WIM Provider: PID=4664 TID=2572 [c:\\mount_c\\bc870-op] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2022-01-10 11:23:05, Error DISM DISM WIM Provider: PID=4664 TID=2572 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2726 - CWimManager::InternalOpUnmount(hr:0x80070032)
2022-01-10 11:23:05, Error DISM DISM WIM Provider: PID=4664 TID=2572 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4249 - CWimManager::InternalCmdUnmount(hr:0x80070032)
2022-01-10 11:23:05, Error DISM DISM WIM Provider: PID=4664 TID=2572 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x80070032)
2022-01-10 11:23:05, Error DISM DISM WIM Provider: PID=4664 TID=2572 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2203 - CWimManager::ExecuteCmdLine(hr:0x80070032)
2022-01-10 11:23:05, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4664 TID=2572 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM PID=4888 TID=2448 Scratch directory set to 'C:\Users\jenkins\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2022-01-10 11:23:05, Info DISM PID=4888 TID=2448 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM PID=4888 TID=2448 Successfully loaded the ImageSession at "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM" - CDISMManager::LoadLocalImageSession
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2022-01-10 11:23:05, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2022-01-10 11:23:05, Info DISM DISM Manager: PID=4888 TID=2448 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: Host machine information: OS Version=10.0.14393, Running architecture=amd64, Number of processors=4
2022-01-10 11:23:05, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1
2022-01-10 11:23:05, Info DISM DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /cleanup-wim
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-01-10 11:23:05, Warning DISM DISM Provider Store: PID=4888 TID=2448 Failed to load the provider: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2022-01-10 11:23:05, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2022-01-10 11:23:05, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2022-01-10 11:23:05, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
[4888] Badly formatted drive string: D:\. This drive will not be cleaned.
[4888] Badly formatted drive string: E:\. This drive will not be cleaned.
2022-01-10 11:23:05, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2022-01-10 11:23:05, Info DISM DISM.EXE:
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2022-01-10 11:23:05, Info DISM DISM Provider Store: PID=4888 TID=2448 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
I'm struggling to even figure out what component here is causing the error. Any help is greatly appreciated.


Jenkins had stopped referencing the network share password credentials correctly.
The pipeline script needed modified to recreate the share connection.

Related

Android Studio: The emulator process for AVD Nexus_6_API 30 has terminated

I'm a newbie to Android Studio and I install Android Studio 2021.1.1 from scratch on Windows 10, but when I want to run the emulator, it just can't be launched with this error:
in the log located at C:\Users\xxx\AppData\Local\Google\AndroidStudio2021.1\log, I got some info as below. So can anyone help to figure it out?
2022-03-24 16:09:10,973 [ 826150] INFO - testKnownPluginVersionProvider - 'gradle' plugin missing from the offline Maven repo, will use default 7.1.2
2022-03-24 16:09:11,368 [ 826545] INFO - ativeWorkspaceModificationTask - NDK support for project 'Demo1' is disabled because the project doesn't contain any valid native configurations.
2022-03-24 16:09:27,095 [ 842272] WARN - vdmanager.AvdManagerConnection - Error setting permissions for C:\Users\xxx\temp\emu.tmp
2022-03-24 16:09:29,433 [ 844610] INFO - manager.EmulatorProcessHandler - Emulator: C:\Users\xxx\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -studio-params C:\Users\xxx\temp\emu.tmp -avd Nexus_6_API_30 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | Crash service did not start
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator:
2022-03-24 16:09:39,471 [ 854648] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: INFO | Android emulator version 31.2.9.0 (build_id 8316981) (CL:N/A)
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741819 (0xC0000005)
2022-03-24 16:09:45,515 [ 860692] WARN - manager.EmulatorProcessHandler - Emulator terminated with exit code -1073741819
2022-03-24 16:09:55,157 [ 870334] WARN - com.intellij.util.xmlb.Binding - no accessors for com.intellij.openapi.updateSettings.impl.pluginsAdvertisement.PluginAdvertiserExtensionsStateService$State
2022-03-24 16:09:55,188 [ 870365] INFO - rationStore.ComponentStoreImpl - Saving appClangTidySettings took 16 ms, FileTypeManager took 15 ms, PluginFeatureService took 15 ms, VcsApplicationSettings took 16 ms
2022-03-24 16:09:55,701 [ 870878] INFO - rationStore.ComponentStoreImpl - Saving Project(name=Demo1, containerState=COMPONENT_CREATED, componentStore=C:\N-20L6PF1KPTJU-Data\xxx\Documents\99.Self.Learning\00.Android)XDebuggerManager took 30 ms
For the permission under C:\Users\xxx\temp*, it has no difference if I set it to full-control or read-only.

I don't know exactly what's the rc, but when I tried Nexus 6 API 28, it works.

vagrant hangs up after fixed port collision

I am trying to bring up vagrant on a Windows machine.
It hangs up after
Fixed port collision for 22 => 2222. Now on port 2200.
A part of the debug log is below:
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x44e7760>
DEBUG environment: Attempting to acquire process-lock: fpcollision
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: fpcollision
INFO handle_port_collisions: Detecting any forwarded port collisions...
DEBUG handle_port_collisions: Extra in use: []
DEBUG handle_port_collisions: Remap: {}
DEBUG handle_port_collisions: Repair: true
INFO handle_port_collisions: Attempting to repair FP collision: 2222
INFO handle_port_collisions: Repaired FP collision: 2222 to 2200
INFO interface: info: Fixed port collision for 22 => 2222. Now on port 2200.
INFO interface: info: ==> vlad: Fixed port collision for 22 => 2222. Now on port 2200.
==> vlad: Fixed port collision for 22 => 2222. Now on port 2200.
INFO environment: Released process lock: fpcollision
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSValidIds:0x44431c8>
INFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "list", "vms"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: "vlad_vlad" {efce349f-2b2e-40db-9a14-2298d3024638}
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<VagrantPlugins::SyncedFolderNFS::ActionCleanup:0x435c3a8>
DEBUG host: Searching for cap: nfs_prune
DEBUG host: Checking in: windows
INFO nfs: Host doesn't support pruning NFS. Skipping.
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x4263ca8>
INFO subprocess: Starting process: ["C:\\Windows\\System32\\WindowsPowerShell\\v1.0/powershell.EXE", "-NoProfile", "-ExecutionPolicy", "Bypass", "$PSVersionTable.PSVersion.Major"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 2
I do not have the slightest idea of how to proceed. Any help is appreciated.

After powershell installation vagrant continued with the setup of the VM

Teamcity on EC2 "Could not determine the local IP address (...): unknown error"

I'm trying to setup Teamcity on an EC2 Ubuntu instance.
I've:
Downloaded the package through wget http://download.jetbrains.com/teamcity/TeamCity-9.0.4.tar.gz. Unpackaged it.
Unpackaged it: tar -xvzf TeamCity-9.0.4.tar.gz.
sh Teamcity/bin/teamcity-server.sh start.
I can't access the web-app, and when I check the logs, says:
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Complete log:
INFO - jetbrains.buildServer.STARTUP - Starting TeamCity server
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
INFO - jetbrains.buildServer.STARTUP - TeamCity version: 9.0.4 (build 32407), data format version 709
INFO - jetbrains.buildServer.STARTUP - OS: Linux, User: ubuntu, JRE: 1.8.0_45-b14 Java HotSpot(TM) 64-Bit Server VM
INFO - jetbrains.buildServer.STARTUP - JVM parameters: -Djava.util.logging.config.file=/home/ubuntu/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/home/ubuntu/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djsse.enableSNIExtension=false -Djava.awt.headless=true -Djava.endorsed.dirs=/home/ubuntu/TeamCity/endorsed -Dcatalina.base=/home/ubuntu/TeamCity -Dcatalina.home=/home/ubuntu/TeamCity -Djava.io.tmpdir=/home/ubuntu/TeamCity/temp
INFO - jetbrains.buildServer.STARTUP - Garbage collection: Copy, MarkSweepCompact
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/7.0.59
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Servlet real path: /home/ubuntu/TeamCity/webapps/ROOT/
INFO - jetbrains.buildServer.STARTUP - Current stage: TeamCity server is shutting down
INFO - jetbrains.buildServer.STARTUP - Stopping the main application
INFO - jetbrains.buildServer.STARTUP - The main servlet is not initialized, nothing to shut down.
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Any hints on how to solve it?
I have Teamcity's web-app working on my local machine (also Ubuntu, and the same Teamcity package).

Read the shell script TeamCity/bin/teamcity-server.sh, it is written with limitation, the script can't run out of the application folder.
export CATALINA_OPTS
CATALINA_HOME=./..
CATALINA_BASE=./..
So you should cd to the bin folder and run :
cd Teamcity/bin
sh teamcity-server.sh start
Let me know if it fixs your issue or not.

Can't connect in Ubuntu box from Windows host in Vagrant

I'm having problems trying to ssh in an ubuntu box inside my windows machine. I'm following the basic Getting Started tutorial from Vagrant site (http://docs.vagrantup.com/v2/getting-started/up.html)
Software Versions:
Vagrant: 1.7.2
Virtualbox: 4.3.22
SO: Windows 7
Box: hashicorp/precise32
The scenario:
When I hit vagrant up everything goes according to plan: services and vm starts, but in the final step, which vagrant tests the ssh, it fails after severals Warning: Connection refused. Retrying...
After that when I open the Virtualbox GUI, I can log in the box and check that openssh-server is running. When I try to ssh through the command line I get the error:
ssh 127.0.0.1 -p 2222
ssh: connect to host 127.0.0.1 port 2222: Bad file number
When I hit vagrant ssh (with the logs in INFO level), I get this output:
INFO global: Vagrant version: 1.7.2
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_EXECUTABLE="C:\\dev\\tools\\Vagrant\\embedded\\gems\\gems\\vagrant-1.7.2\\bin\\vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\\dev\\tools\\Vagrant\\embedded"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: VAGRANT_LOG="INFO"
INFO global: Plugins:
INFO global: - bundler = 1.7.11
INFO global: - mime-types = 1.25.1
INFO global: - rdoc = 4.0.0
INFO global: - rest-client = 1.6.8
INFO global: - vagrant-share = 1.1.3
INFO manager: Registered plugin: box command
INFO manager: Registered plugin: destroy command
INFO manager: Registered plugin: global-status command
INFO manager: Registered plugin: halt command
INFO manager: Registered plugin: help command
INFO manager: Registered plugin: init command
INFO manager: Registered plugin: list-commands command
INFO manager: Registered plugin: vagrant-login
INFO manager: Registered plugin: package command
INFO manager: Registered plugin: plugin command
INFO manager: Registered plugin: provision command
INFO manager: Registered plugin: push command
INFO manager: Registered plugin: rdp command
INFO manager: Registered plugin: reload command
INFO manager: Registered plugin: resume command
INFO manager: Registered plugin: ssh command
INFO manager: Registered plugin: ssh-config command
INFO manager: Registered plugin: status command
INFO manager: Registered plugin: suspend command
INFO manager: Registered plugin: up command
INFO manager: Registered plugin: version command
INFO manager: Registered plugin: ssh communicator
INFO manager: Registered plugin: winrm communicator
INFO manager: Registered plugin: Arch guest
INFO manager: Registered plugin: CoreOS guest
INFO manager: Registered plugin: Darwin guest
INFO manager: Registered plugin: Debian guest
INFO manager: Registered plugin: ESXi guest.
INFO manager: Registered plugin: Fedora guest
INFO manager: Registered plugin: FreeBSD guest
INFO manager: Registered plugin: Funtoo guest
INFO manager: Registered plugin: Gentoo guest
INFO manager: Registered plugin: Linux guest.
INFO manager: Registered plugin: Mint guest
INFO manager: Registered plugin: NetBSD guest
INFO manager: Registered plugin: NixOS guest
INFO manager: Registered plugin: OmniOS guest.
INFO manager: Registered plugin: OpenBSD guest
INFO manager: Registered plugin: PLD Linux guest
INFO manager: Registered plugin: RedHat guest
INFO manager: Registered plugin: SmartOS guest.
INFO manager: Registered plugin: Solaris guest.
INFO manager: Registered plugin: Solaris 11 guest.
INFO manager: Registered plugin: SUSE guest
INFO manager: Registered plugin: TinyCore Linux guest.
INFO manager: Registered plugin: Ubuntu guest
INFO manager: Registered plugin: Windows guest.
INFO manager: Registered plugin: Arch host
INFO manager: Registered plugin: BSD host
INFO manager: Registered plugin: Mac OS X host
INFO manager: Registered plugin: FreeBSD host
INFO manager: Registered plugin: Gentoo host
INFO manager: Registered plugin: Linux host
INFO manager: Registered plugin: null host
INFO manager: Registered plugin: Red Hat host
INFO manager: Registered plugin: Slackware host
INFO manager: Registered plugin: SUSE host
INFO manager: Registered plugin: Windows host
INFO manager: Registered plugin: kernel
INFO manager: Registered plugin: kernel
INFO manager: Registered plugin: docker-provider
INFO manager: Registered plugin: Hyper-V provider
INFO manager: Registered plugin: VirtualBox provider
INFO manager: Registered plugin: ansible
INFO manager: Registered plugin: CFEngine Provisioner
INFO manager: Registered plugin: chef
INFO manager: Registered plugin: docker
INFO manager: Registered plugin: file
INFO manager: Registered plugin: puppet
INFO manager: Registered plugin: salt
INFO manager: Registered plugin: shell
INFO manager: Registered plugin: atlas
INFO manager: Registered plugin: ftp
INFO manager: Registered plugin: heroku
INFO manager: Registered plugin: local-exec
INFO manager: Registered plugin: noop
INFO manager: Registered plugin: NFS synced folders
INFO manager: Registered plugin: RSync synced folders
INFO manager: Registered plugin: SMB synced folders
INFO global: Loading plugins!
INFO manager: Registered plugin: vagrant-share
INFO vagrant: `vagrant` invoked: ["ssh"]
INFO environment: Environment initialized (#<Vagrant::Environment:0x36893d0>)
INFO environment: - cwd: C:/dev/local-server
INFO environment: Home path: C:/Users/vitallan/.vagrant.d
INFO environment: Local data path: C:/dev/local-server/.vagrant
INFO environment: Running hook: environment_plugins_loaded
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x2c494c8>
INFO environment: Running hook: environment_load
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x2cc93a0>
INFO cli: CLI: [] "ssh" []
INFO loader: Set :root = #<Pathname:C:/dev/local-server/Vagrantfile>
INFO loader: Loading configuration in order: [:home, :root]
INFO command: Active machine found with name default. Using provider: virtualbox
INFO environment: Getting machine: default (virtualbox)
INFO environment: Uncached load of machine.
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "--version"]
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO loader: Set "27710496_machine_default" = []
INFO loader: Loading configuration in order: [:home, :root, "27710496_machine_default"]
INFO box_collection: Box found: hashicorp/precise32 (virtualbox)
INFO environment: Running hook: authenticate_box_url
INFO host: Autodetecting host type for [#<Vagrant::Environment: C:/dev/local-server>]
INFO host: Detected: windows!
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x376dbc8>
INFO warden: Calling IN action: #<VagrantPlugins::LoginCommand::AddAuthentication:0x4727a18>
INFO warden: Calling OUT action: #<VagrantPlugins::LoginCommand::AddAuthentication:0x4727a18>
INFO loader: Set :"28616568_hashicorp/precise32_virtualbox" = #<Pathname:C:/Users/vitallan/.vagrant.d/boxes/hashicorp-VAGRANTSLASH-precise32/1.0.0/virtualbox/Vagrantfile>
INFO loader: Loading configuration in order: [:"28616568_hashicorp/precise32_virtualbox", :home, :root, "27710496_machine_default"]
INFO machine: Initializing machine: default
INFO machine: - Provider: VagrantPlugins::ProviderVirtualBox::Provider
INFO machine: - Box: #<Vagrant::Box:0x474dfb0>
INFO machine: - Data dir: C:/dev/local-server/.vagrant/machines/default/virtualbox
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "--version"]
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b"]
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO command: With machine: default (#<VagrantPlugins::ProviderVirtualBox::Provider:0x487e4f8 #logger=#<Log4r::Logger:0x487e4c8 #fullname="vagrant::provider::virtualbox", #outputters=[], #additive=true, #name="virtualbox", #path="vagrant::provider", #parent=#<Log4r::Logger:0x37e65e8 #fullname="vagrant", #outputters=[#<Log4r::StderrOutputter:0x375fd50 #mon_owner=nil, #mon_count=0, #mon_mutex=#<Mutex:0x375fc18>, #name="stderr", #level=0, #formatter=#<Log4r::DefaultFormatter:0x375dbd8 #depth=7>, #out=#<IO:<STDERR>>>], #additive=true, #name="vagrant", #path="", #parent=#<Log4r::RootLogger:0x37e6540 #level=0, #outputters=[]>, #level=2, #trace=false>, #level=2, #trace=false>, #machine=#<Vagrant::Machine: default (VagrantPlugins::ProviderVirtualBox::Provider)>, #driver=#<VagrantPlugins::ProviderVirtualBox::Driver::Meta:0x4897560 #logger=#<Log4r::Logger:0x48a4148 #fullname="vagrant::provider::virtualbox::meta", #outputters=[], #additive=true, #name="meta", #path="vagrant::provider::virtualbox", #parent=#<Log4r::Logger:0x487e4c8 #fullname="vagrant::provider::virtualbox", #outputters=[], #additive=true, #name="virtualbox", #path="vagrant::provider", #parent=#<Log4r::Logger:0x37e65e8 #fullname="vagrant", #outputters=[#<Log4r::StderrOutputter:0x375fd50 #mon_owner=nil, #mon_count=0, #mon_mutex=#<Mutex:0x375fc18>, #name="stderr", #level=0, #formatter=#<Log4r::DefaultFormatter:0x375dbd8 #depth=7>, #out=#<IO:<STDERR>>>], #additive=true, #name="vagrant", #path="", #parent=#<Log4r::RootLogger:0x37e6540 #level=0, #outputters=[]>, #level=2, #trace=false>, #level=2, #trace=false>, #level=2, #trace=false>, #interrupted=false, #vboxmanage_path="C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", #uuid="d2575078-1bc6-448b-9c70-04e21249f33b", #version="4.3.22", #driver=#<VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3:0x48d4568 #logger=#<Log4r::Logger:0x48ed108 #fullname="vagrant::provider::virtualbox_4_3", #outputters=[], #additive=true, #name="virtualbox_4_3", #path="vagrant::provider", #parent=#<Log4r::Logger:0x37e65e8 #fullname="vagrant", #outputters=[#<Log4r::StderrOutputter:0x375fd50 #mon_owner=nil, #mon_count=0, #mon_mutex=#<Mutex:0x375fc18>, #name="stderr", #level=0, #formatter=#<Log4r::DefaultFormatter:0x375dbd8 #depth=7>, #out=#<IO:<STDERR>>>], #additive=true, #name="vagrant", #path="", #parent=#<Log4r::RootLogger:0x37e6540 #level=0, #outputters=[]>, #level=2, #trace=false>, #level=2, #trace=false>, #interrupted=false, #vboxmanage_path="C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", #uuid="d2575078-1bc6-448b-9c70-04e21249f33b">>, #cap_logger=#<Log4r::Logger:0x491d600 #fullname="vagrant::capability_host::vagrantplugins::providervirtualbox::provider", #outputters=[], #additive=true, #name="provider", #path="vagrant::capability_host::vagrantplugins::providervirtualbox", #parent=#<Log4r::Logger:0x37e65e8 #fullname="vagrant", #outputters=[#<Log4r::StderrOutputter:0x375fd50 #mon_owner=nil, #mon_count=0, #mon_mutex=#<Mutex:0x375fc18>, #name="stderr", #level=0, #formatter=#<Log4r::DefaultFormatter:0x375dbd8 #depth=7>, #out=#<IO:<STDERR>>>], #additive=true, #name="vagrant", #path="", #parent=#<Log4r::RootLogger:0x37e6540 #level=0, #outputters=[]>, #level=2, #trace=false>, #level=2, #trace=false>, #cap_host_chain=[[:virtualbox, #<#<Class:0x491d8d0>:0x4b76518>]], #cap_args=[#<Vagrant::Machine: default (VagrantPlugins::ProviderVirtualBox::Provider)>], #cap_caps={:docker=>#<Vagrant::Registry:0x491d7f8 #items={:public_address=>#<Proc:0x3806538#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/providers/docker/plugin.rb:54>, :proxy_machine=>#<Proc:0x3806490#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/providers/docker/plugin.rb:59>}, #results_cache={}>, :hyperv=>#<Vagrant::Registry:0x491d780 #items={:public_address=>#<Proc:0x380ed10#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/providers/hyperv/plugin.rb:25>}, #results_cache={}>, :virtualbox=>#<Vagrant::Registry:0x491d708 #items={:forwarded_ports=>#<Proc:0x383fcd0#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/providers/virtualbox/plugin.rb:27>, :nic_mac_addresses=>#<Proc:0x383fc58#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/providers/virtualbox/plugin.rb:32>, :public_address=>#<Proc:0x2a38508#C:/dev/tools/Vagrant/embedded/gems/gems/vagrant-share-1.1.3/lib/vagrant-share.rb:39>}, #results_cache={}>}>)
INFO machine: Calling action: ssh on provider VirtualBox (d2575078-1bc6-448b-9c70-04e21249f33b)
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x460fde8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x4686480>
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "--version"]
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3
INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "list", "hostonlyifs"]
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckCreated:0x4686468>
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckAccessible:0x4686450>
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckRunning:0x4686438>
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SSHExec:0x4686420>
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "d2575078-1bc6-448b-9c70-04e21249f33b", "--machinereadable"]
INFO subprocess: Starting process: ["C:\\Program Files (x86)\\Git\\bin/ssh.EXE"]
INFO ssh: Invoking SSH: ["vagrant#127.0.0.1", "-p", "2222", "-o", "Compression=yes", "-o", "DSAAuthentication=yes", "-o", "LogLevel=FATAL", "-o", "StrictHostKeyChecking=no", "-o", "UserKnownHostsFile=/dev/null", "-o", "IdentitiesOnly=yes", "-i", "C:/Users/vitallan/.vagrant.d/insecure_private_key"]
Does anyone know how can I ssh in my box?
EDIT: i tried openning new forwardding doors (like #user1389596 suggested), but it still doesnt work

Hmm, ssh 127.0.0.1 is the loopback address (the same machine). Shouldn't you use the local LAN IP of your ubuntu server intead?

Not able to start JBoss 5.1 GA on windows 7

I have no clue about what am I wrong in here.
C:\Program Files\JBOSS\jboss-5.1.0.GA\bin>run.bat
Calling C:\Program Files\JBOSS\jboss-5.1.0.GA\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\JBOSS\jboss-5.1.0.GA
JAVA: C:\Program Files\Java\jdk1.6.0_34\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun
.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg
.jboss.resolver.warning=true -server
CLASSPATH: C:\Program Files\JBOSS\jboss-5.1.0.GA\bin\run.jar
===============================================================================
log4j:ERROR Failed to create directory structure: C:\Program Files\JBOSS\jboss-5
.1.0.GA\server\default\log
log4j:ERROR setFile(null,false) call failed.
java.io.FileNotFoundException: C:\Program Files\JBOSS\jboss-5.1.0.GA\server\defa
ult\log\boot.log (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
at java.io.FileOutputStream.<init>(FileOutputStream.java:116)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:2
56)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.j
ava:132)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.j
ava:96)
at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigura
tor.java:654)
at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigura
tor.java:612)
at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyC
onfigurator.java:509)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:415)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:441)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionCon
verter.java:470)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
at org.jboss.logging.log4j.Log4jLoggerPlugin.init(Log4jLoggerPlugin.java
:70)
at org.jboss.logging.Logger.getDelegatePlugin(Logger.java:603)
at org.jboss.logging.Logger.<init>(Logger.java:119)
at org.jboss.logging.Logger.getLogger(Logger.java:567)
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java
:204)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:1
73)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:1
43)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:08,937 INFO [ServerImpl] Starting JBoss (Microcontainer)...
11:42:08,938 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build:
SVNTag=JBoss_5_1_0_GA date=200905221634)
11:42:08,939 INFO [ServerImpl] Bootstrap URL: null
11:42:08,939 INFO [ServerImpl] Home Dir: C:\Program Files\JBOSS\jboss-5.1.0.GA
11:42:08,940 INFO [ServerImpl] Home URL: file:/C:/Program%20Files/JBOSS/jboss-5
.1.0.GA/
11:42:08,940 INFO [ServerImpl] Library URL: file:/C:/Program%20Files/JBOSS/jbos
s-5.1.0.GA/lib/
11:42:08,942 INFO [ServerImpl] Patch URL: null
11:42:08,942 INFO [ServerImpl] Common Base URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/common/
11:42:08,943 INFO [ServerImpl] Common Library URL: file:/C:/Program%20Files/JBO
SS/jboss-5.1.0.GA/common/lib/
11:42:08,944 INFO [ServerImpl] Server Name: default
11:42:08,944 INFO [ServerImpl] Server Base Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server
11:42:08,945 INFO [ServerImpl] Server Base URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/server/
11:42:08,946 INFO [ServerImpl] Server Config URL: file:/C:/Program%20Files/JBOS
S/jboss-5.1.0.GA/server/default/conf/
11:42:08,946 INFO [ServerImpl] Server Home Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default
11:42:08,947 INFO [ServerImpl] Server Home URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/server/default/
11:42:08,947 INFO [ServerImpl] Server Data Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\data
11:42:08,948 INFO [ServerImpl] Server Library URL: file:/C:/Program%20Files/JBO
SS/jboss-5.1.0.GA/server/default/lib/
11:42:08,949 INFO [ServerImpl] Server Log Dir: C:\Program Files\JBOSS\jboss-5.1
.0.GA\server\default\log
11:42:08,949 INFO [ServerImpl] Server Native Dir: C:\Program Files\JBOSS\jboss-
5.1.0.GA\server\default\tmp\native
11:42:08,950 INFO [ServerImpl] Server Temp Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\tmp
11:42:08,951 INFO [ServerImpl] Server Temp Deploy Dir: C:\Program Files\JBOSS\j
boss-5.1.0.GA\server\default\tmp\deploy
11:42:09,548 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/P
rogram%20Files/JBOSS/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
11:42:10,125 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.pl
ugins.cache.CombinedVFSCache]
11:42:10,129 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache
: null]]
11:42:10,409 INFO [CopyMechanism] VFS temp dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\tmp
11:42:10,411 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
11:42:10,667 ERROR [AbstractKernelController] Error installing to Create: name=A
spectManager state=Configured
java.io.FileNotFoundException: Failed to create tmpClassesDir: C:\Program Files\
JBOSS\jboss-5.1.0.GA\server\default\tmp\aopdynclasses
at org.jboss.aop.asintegration.core.AspectManagerServiceDelegate.create(
AspectManagerServiceDelegate.java:237)
at org.jboss.aop.deployers.AbstractAspectManager.create(AbstractAspectMa
nager.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(Reflec
tionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(
ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethod
JoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$Joi
npointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(Executio
nWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInte
rnal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.sim
pleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins
tall(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:540)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
(AbstractKernelDeployer.java:319)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
s(AbstractKernelDeployer.java:297)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(Abs
tractKernelDeployer.java:130)
at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicK
ernelDeployer.java:76)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:91)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:161)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:138)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:11,350 INFO [ServerInfo] Java version: 1.6.0_34,Sun Microsystems Inc.
11:42:11,350 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (b
uild 1.6.0_34-b04)
11:42:11,351 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.9-
b04,Sun Microsystems Inc.
11:42:11,352 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
11:42:11,353 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128M -X
mx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dg
c.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.di
rs=C:\Program Files\JBOSS\jboss-5.1.0.GA\lib\endorsed
11:42:11,384 INFO [JMXKernel] Legacy JMX core initialized
Failed to boot JBoss:
java.lang.IllegalStateException: Incompletely deployed:
DEPLOYMENTS IN ERROR:
Deployment "AspectManager" is in error due to: java.io.FileNotFoundException:
Failed to create tmpClassesDir: C:\Program Files\JBOSS\jboss-5.1.0.GA\server\def
ault\tmp\aopdynclasses
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "JMXStartStopAdvice$AspectBinding" is missing the following depende
ncies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "BeansDeploymentAopMetaDataDeployer" is missing the following depen
dencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", bu
t is actually in state "**ERROR**")
Deployment "AOPDeploymentAopMetaDataDeployer" is missing the following depende
ncies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", bu
t is actually in state "**ERROR**")
Deployment "AOPClassLoaderDeployer" is missing the following dependencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "JMXRegistrationAdvice$AspectBinding" is missing the following depe
ndencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "AspectManagerJMXRegistrar" is missing the following dependencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "JMXCreateDestroyAdvice$AspectBinding" is missing the following dep
endencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalVa
lidate(AbstractKernelDeployer.java:278)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(A
bstractKernelDeployer.java:174)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:142)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:13,576 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
11:42:13,582 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Press any key to continue . . .

Looks like a bug that occurs with certain specific combinations of JRE and OS versions (see https://jira.jboss.org/jira/browse/JBAS-6981). Basically, the JBoss config is relying on reflection to return constructors in a certain order, and in some cases this order is different, causing the exception. Did you change your JRE version when you reinstalled, say from 1.6.0_17 to _18?
Anyway, the workaround is described in the JIRA issue, and also here. You need to change the content of conf/bootstrap/profile.xml. Look for the definition of the AttachmentStore, and change the constructor line so that it starts:
The original version doesn't have the class="java.io.File" attribute.
Pretty sloppy of the JBoss folks, but there you go.
Hope it helps.
(copied from Error starting jboss server)

Resources