id summary reporter owner description type status component version resolution keywords cc guest host 3671 After installing VirtualBox 2.2.0 IBM DB2 Warehouse Center product stops working - it gets error timeout grof "Hi, I have installed VirtualBox 2.2.0 on Windows XP SP3 and after installation I tried to use ""IBM DB2 Warehouse Center"" client product on host that connects to Warehouse server on another Windows machine. After 1 minute I get error from warehouse product: ""DWC09117E VWERR_Q_TIMEOUT Message queue timeout occurred before message received. RC = 9117 RC2 = 0"". This error means warehouse client tries to connect to warehouse server but is not able to get connection working, so it gets timeout error. I am sure this is not warehouse server problem, because I can connect to that product from other machine. Detailed info from warehouse: ""DWC09117E VWERR_Q_TIMEOUT Message queue timeout occurred before message received. Explanation: A Data Warehouse Center internal error occurred. User Response: 1. If importing table names, restrict the list to fewer tables. Some ways to do this are: - Request tables but not views. - Use a table qualifier. - Request a table qualifier and table name. 2. Increase the agent start/stop timeout in the configuration. 3. If this is not successful, record all details of this error message and contact IBM Software Support with the information."" I am 100% sure this bug is related to VirtualBox 2.2.0. Why? Because I have had installed VirtualBox 2.1.4 and warehouse client worked OK. I have created backup of whole windows primary partition. I installed VirtualBox 2.2.0 beta2 and got this error. I restored Windows host partition back to 2.1.4 and warehouse client was working fine. Now I have installed 2.2.0 final and got the same error. Now I have to revent back to 2.1.4. It looks like 2.2.0 corrupts some network settings or something like that. I have attached Vbox.log file at another issue I have: http://www.virtualbox.org/ticket/3668 By the way, I have also reported bug: http://www.virtualbox.org/ticket/3670 which is network related, but I am not sure this is the same bug. Regards" defect closed network VirtualBox 2.2.0 fixed other Windows