Failed to connect Company (-222)

Trying to connect DI from UI API.
private SAPbobsCOM.Company oCompany;
        private SAPbouiCOM.Application SBO_Application;
        //  Connect to SBO '
        private void SetApplication() {
            SAPbouiCOM.SboGuiApi SboGuiApi = null;
            string sConnectionString = null;
            SboGuiApi = new SAPbouiCOM.SboGuiApi();
            sConnectionString = System.Convert.ToString( Environment.GetCommandLineArgs().GetValue( 1 ) );
            SboGuiApi.Connect( sConnectionString );
            SBO_Application = SboGuiApi.GetApplication( -1 );
        //  Connect with connection string '
        private int SetConnectionContext() {
            int setConnectionContextReturn = 0;
            string sCookie = null;
            string sConnectionContext = null;
            int lRetCode = 0;
            oCompany = new SAPbobsCOM.Company();
            sCookie = oCompany.GetContextCookie();
            sConnectionContext = SBO_Application.Company.GetConnectionContext( sCookie );
            if ( oCompany.Connected == true ) {
                oCompany.Disconnect();
            setConnectionContextReturn = oCompany.SetSboLoginContext( sConnectionContext );
            return setConnectionContextReturn;
        //  Connect to SBO '
        private int ConnectToCompany() {
            int connectToCompanyReturn = 0;
            // Establish the connection to the company database.
            connectToCompanyReturn = oCompany.Connect();
            return connectToCompanyReturn;
        //  Init the Class '
        public Test() : base() {
            SetApplication();
            if ( !( SetConnectionContext() == 0 ) ) {
                SBO_Application.MessageBox( "Failed setting a connection to DI API", 1, "Ok", "", "" );
                System.Environment.Exit( 0 ); //  Terminating the Add-On Application
            if ( !( ConnectToCompany() == 0 ) ) {
                SBO_Application.MessageBox( "Failed connecting to the company's Data Base", 1, "Ok", "", "" );
                Application.Exit(); //  Terminating the Add-On Application
            SBO_Application.MessageBox( "DI Connected To: " + oCompany.CompanyName, 1, "Ok", "", "" );
            // events handled by SBO_Application_ItemEvent
               bool tmpB = false;
               SBO_Application.ItemEvent += new SAPbouiCOM._IApplicationEvents_ItemEventEventHandler( SBO_Application_ItemEvent );
      But Getting error "Failed to connect company" . Why??

Hello...
I´m with the same problem, but the return code is -131
I try to find in the SDK Help Center, but i´m not found the errors list.
Can same one help me, please?
Tks

Similar Messages

  • Wicd fails to connect/inconsistently connects, manual connect works.

    Hi all, wicd is failing to connect after an update today. I've tried both my wired and wireless networks; it fails to connect to both for the majority of the time. I've been able to connect 1 or twice to both without failure, however. Manually running "sudo dhcpcd eth0" connects without issue. The issue seems to be with dhcpcd 5.5.4-1, as a downgrade to the [core] version (5.2.12-4) fixes the issue. Any ideas?
    /var/log/errors.log:
    Feb 8 23:37:53 localhost dhcpcd[5808]: dhcpcd not running
    Feb 8 23:37:54 localhost dhcpcd[5814]: dhcpcd not running
    Feb 8 23:37:54 localhost dhcpcd[5820]: dhcpcd not running
    Feb 8 23:37:57 localhost dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
    Feb 8 23:38:00 localhost dhcpcd[5856]: dhcpcd not running
    Feb 8 23:39:50 localhost dhcpcd[6067]: dhcpcd not running
    Feb 8 23:39:50 localhost dhcpcd[6074]: dhcpcd not running
    Feb 8 23:39:51 localhost dhcpcd[6082]: dhcpcd not running
    Feb 8 23:40:08 localhost dhcpcd[6216]: dhcpcd not running
    Feb 8 23:40:09 localhost dhcpcd[6238]: dhcpcd not running
    /var/log/wicd/wicd.log:
    2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: checking for 192.168.1.7
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: dhcpcd[3603]: forked to background, child pid 3626
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 ::
    2012/02/08 23:26:04 :: DHCP connection successful
    2012/02/08 23:26:04 :: Connecting thread exiting.
    2012/02/08 23:26:05 :: Sending connection attempt result success
    2012/02/08 23:27:23 :: Connecting to wireless network s_wifi
    2012/02/08 23:27:24 :: Putting interface down
    2012/02/08 23:27:24 :: Releasing DHCP leases...
    2012/02/08 23:27:24 :: Setting false IP...
    2012/02/08 23:27:24 :: Stopping wpa_supplicant
    2012/02/08 23:27:24 :: Flushing the routing table...
    2012/02/08 23:27:24 :: Putting interface up...
    2012/02/08 23:27:26 :: Running DHCP with hostname carbon
    2012/02/08 23:27:26 :: dhcpcd[3760]: version 5.5.4 starting
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: waiting for carrier
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: carrier acquired
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sending IPv6 Router Solicitation
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sendmsg: Cannot assign requested address
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: broadcasting for a lease
    2012/02/08 23:27:26 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: received RA for unexpected interface from fe80::222:75ff:fed5:73d4
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: dhcpcd[3760]: forked to background, child pid 3784
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 ::
    2012/02/08 23:27:27 :: DHCP connection successful
    2012/02/08 23:27:27 :: not verifying
    2012/02/08 23:27:27 :: Connecting thread exiting.
    2012/02/08 23:27:30 :: Sending connection attempt result success
    2012/02/08 23:28:04 :: Putting interface down
    2012/02/08 23:28:04 :: Error checking link using /sys/class/net/eth0/carrier
    2012/02/08 23:28:04 :: Releasing DHCP leases...
    2012/02/08 23:28:04 :: Setting false IP...
    2012/02/08 23:28:04 :: Stopping wpa_supplicant
    2012/02/08 23:28:04 :: Flushing the routing table...
    2012/02/08 23:28:04 :: Putting interface up...
    2012/02/08 23:28:06 :: Running DHCP with hostname carbon
    2012/02/08 23:28:06 :: dhcpcd[3899]: version 5.5.4 starting
    2012/02/08 23:28:06 ::
    2012/02/08 23:28:06 :: dhcpcd[3899]: eth0: waiting for carrier
    2012/02/08 23:28:06 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: carrier acquired
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sending IPv6 Router Solicitation
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sendmsg: Cannot assign requested address
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: broadcasting for a lease
    2012/02/08 23:28:07 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: checking for 192.168.1.7
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: dhcpcd[3899]: forked to background, child pid 3922
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 ::
    2012/02/08 23:28:08 :: DHCP connection successful
    2012/02/08 23:28:08 :: Connecting thread exiting.
    2012/02/08 23:28:09 :: Sending connection attempt result success
    2012/02/08 23:35:31 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:35:31 :: Removing PID file...
    2012/02/08 23:35:31 :: Shutting down...
    2012/02/08 23:35:31 :: Exception KeyError: KeyError(139867792365312,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:35:33 :: ---------------------------
    2012/02/08 23:35:33 :: wicd initializing...
    2012/02/08 23:35:33 :: ---------------------------
    2012/02/08 23:35:33 :: wicd is version 1.7.1 717
    2012/02/08 23:35:33 :: setting backend to external
    2012/02/08 23:35:33 :: trying to load backend external
    2012/02/08 23:35:33 :: successfully loaded backend external
    2012/02/08 23:35:33 :: trying to load backend external
    2012/02/08 23:35:33 :: successfully loaded backend external
    2012/02/08 23:35:33 :: Automatically detected wireless interface wlan0
    2012/02/08 23:35:33 :: setting wireless interface wlan0
    2012/02/08 23:35:33 :: automatically detected wired interface eth0
    2012/02/08 23:35:33 :: setting wired interface eth0
    2012/02/08 23:35:33 :: setting wpa driver wext
    2012/02/08 23:35:33 :: setting use global dns to False
    2012/02/08 23:35:33 :: setting global dns
    2012/02/08 23:35:33 :: global dns servers are None None None
    2012/02/08 23:35:33 :: domain is None
    2012/02/08 23:35:33 :: search domain is None
    2012/02/08 23:35:33 :: setting automatically reconnect when connection drops True
    2012/02/08 23:35:33 :: Setting dhcp client to 0
    2012/02/08 23:35:33 :: Wireless configuration file found...
    2012/02/08 23:35:33 :: Wired configuration file found...
    2012/02/08 23:35:33 :: chmoding configuration files 0600...
    2012/02/08 23:35:33 :: chowning configuration files root:root...
    2012/02/08 23:35:33 :: Using wireless interface...wlan0
    2012/02/08 23:35:33 :: Using wired interface...eth0
    2012/02/08 23:35:47 :: Connecting to wireless network s_wifi
    2012/02/08 23:35:47 :: Putting interface down
    2012/02/08 23:35:48 :: Releasing DHCP leases...
    2012/02/08 23:35:48 :: Setting false IP...
    2012/02/08 23:35:48 :: Stopping wpa_supplicant
    2012/02/08 23:35:48 :: Flushing the routing table...
    2012/02/08 23:35:48 :: Putting interface up...
    2012/02/08 23:35:50 :: Running DHCP with hostname carbon
    2012/02/08 23:35:50 :: dhcpcd[5483]: version 5.2.12 starting
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: waiting for carrier
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: carrier acquired
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: broadcasting for a lease
    2012/02/08 23:35:50 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: offered 192.168.1.3 from 192.168.1.1
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: checking for 192.168.1.3
    2012/02/08 23:35:51 ::
    2012/02/08 23:35:55 :: dhcpcd[5483]: wlan0: leased 192.168.1.3 for 283824000 seconds
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 :: dhcpcd[5483]: forked to background, child pid 5514
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 ::
    2012/02/08 23:35:55 :: DHCP connection successful
    2012/02/08 23:35:55 :: not verifying
    2012/02/08 23:35:55 :: Connecting thread exiting.
    2012/02/08 23:35:58 :: Sending connection attempt result success
    2012/02/08 23:37:39 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:37:39 :: Removing PID file...
    2012/02/08 23:37:39 :: Shutting down...
    2012/02/08 23:37:39 :: Exception KeyError: KeyError(139889612089088,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:37:40 :: ---------------------------
    2012/02/08 23:37:40 :: wicd initializing...
    2012/02/08 23:37:40 :: ---------------------------
    2012/02/08 23:37:40 :: wicd is version 1.7.1 717
    2012/02/08 23:37:40 :: setting backend to external
    2012/02/08 23:37:40 :: trying to load backend external
    2012/02/08 23:37:40 :: successfully loaded backend external
    2012/02/08 23:37:40 :: trying to load backend external
    2012/02/08 23:37:40 :: successfully loaded backend external
    2012/02/08 23:37:40 :: Automatically detected wireless interface wlan0
    2012/02/08 23:37:40 :: setting wireless interface wlan0
    2012/02/08 23:37:40 :: automatically detected wired interface eth0
    2012/02/08 23:37:40 :: setting wired interface eth0
    2012/02/08 23:37:40 :: setting wpa driver wext
    2012/02/08 23:37:40 :: setting use global dns to False
    2012/02/08 23:37:40 :: setting global dns
    2012/02/08 23:37:40 :: global dns servers are None None None
    2012/02/08 23:37:40 :: domain is None
    2012/02/08 23:37:40 :: search domain is None
    2012/02/08 23:37:40 :: setting automatically reconnect when connection drops True
    2012/02/08 23:37:40 :: Setting dhcp client to 0
    2012/02/08 23:37:41 :: Wireless configuration file found...
    2012/02/08 23:37:41 :: Wired configuration file found...
    2012/02/08 23:37:41 :: chmoding configuration files 0600...
    2012/02/08 23:37:41 :: chowning configuration files root:root...
    2012/02/08 23:37:41 :: Using wireless interface...wlan0
    2012/02/08 23:37:41 :: Using wired interface...eth0
    2012/02/08 23:37:46 :: Connecting to wireless network s_wifi
    2012/02/08 23:37:46 :: Putting interface down
    2012/02/08 23:37:46 :: Releasing DHCP leases...
    2012/02/08 23:37:46 :: Setting false IP...
    2012/02/08 23:37:47 :: Stopping wpa_supplicant
    2012/02/08 23:37:47 :: Flushing the routing table...
    2012/02/08 23:37:47 :: Putting interface up...
    2012/02/08 23:37:49 :: Running DHCP with hostname carbon
    2012/02/08 23:37:49 :: dhcpcd[5759]: version 5.5.4 starting
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sending IPv6 Router Solicitation
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sendmsg: Cannot assign requested address
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: broadcasting for a lease
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: dhcpcd[5759]: forked to background, child pid 5777
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 ::
    2012/02/08 23:37:49 :: DHCP connection successful
    2012/02/08 23:37:49 :: not verifying
    2012/02/08 23:37:49 :: Connecting thread exiting.
    2012/02/08 23:37:52 :: Sending connection attempt result success
    2012/02/08 23:37:52 :: Autoconnecting...
    2012/02/08 23:37:53 :: Putting interface downAttempting to autoconnect with wired interface...
    2012/02/08 23:37:53 ::
    2012/02/08 23:37:53 :: Releasing DHCP leases...
    2012/02/08 23:37:53 :: Setting false IP...
    2012/02/08 23:37:53 :: Stopping wpa_supplicant
    2012/02/08 23:37:53 :: Flushing the routing table...
    2012/02/08 23:37:53 :: Putting interface up...
    2012/02/08 23:37:55 :: Running DHCP with hostname carbon
    2012/02/08 23:37:55 :: dhcpcd[5828]: version 5.5.4 starting
    2012/02/08 23:37:55 ::
    2012/02/08 23:37:55 :: dhcpcd[5828]: eth0: waiting for carrier
    2012/02/08 23:37:55 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: carrier acquired
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sending IPv6 Router Solicitation
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: broadcasting for a lease
    2012/02/08 23:37:57 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: checking for 192.168.1.7
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: dhcpcd[5828]: forked to background, child pid 5851
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 ::
    2012/02/08 23:37:58 :: DHCP connection successful
    2012/02/08 23:37:58 :: Connecting thread exiting.
    2012/02/08 23:38:00 :: Sending connection attempt result success
    2012/02/08 23:38:01 :: No wired connection present, attempting to autoconnect to wireless network
    2012/02/08 23:38:04 :: Unable to autoconnect, you'll have to manually connect
    2012/02/08 23:39:43 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:39:43 :: Removing PID file...
    2012/02/08 23:39:43 :: Shutting down...
    2012/02/08 23:39:43 :: Exception KeyError: KeyError(140388630619904,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:39:45 :: ---------------------------
    2012/02/08 23:39:45 :: wicd initializing...
    2012/02/08 23:39:45 :: ---------------------------
    2012/02/08 23:39:45 :: wicd is version 1.7.1 717
    2012/02/08 23:39:45 :: setting backend to external
    2012/02/08 23:39:45 :: trying to load backend external
    2012/02/08 23:39:45 :: successfully loaded backend external
    2012/02/08 23:39:45 :: trying to load backend external
    2012/02/08 23:39:45 :: successfully loaded backend external
    2012/02/08 23:39:45 :: Automatically detected wireless interface wlan0
    2012/02/08 23:39:45 :: setting wireless interface wlan0
    2012/02/08 23:39:45 :: automatically detected wired interface eth0
    2012/02/08 23:39:45 :: setting wired interface eth0
    2012/02/08 23:39:45 :: setting wpa driver wext
    2012/02/08 23:39:45 :: setting use global dns to False
    2012/02/08 23:39:45 :: setting global dns
    2012/02/08 23:39:45 :: global dns servers are None None None
    2012/02/08 23:39:45 :: domain is None
    2012/02/08 23:39:45 :: search domain is None
    2012/02/08 23:39:45 :: setting automatically reconnect when connection drops True
    2012/02/08 23:39:45 :: Setting dhcp client to 0
    2012/02/08 23:39:45 :: Wireless configuration file found...
    2012/02/08 23:39:45 :: Wired configuration file found...
    2012/02/08 23:39:45 :: chmoding configuration files 0600...
    2012/02/08 23:39:45 :: chowning configuration files root:root...
    2012/02/08 23:39:45 :: Using wireless interface...wlan0
    2012/02/08 23:39:45 :: Using wired interface...eth0
    2012/02/08 23:39:50 :: Autoconnecting...
    2012/02/08 23:39:50 :: Attempting to autoconnect with wired interface...
    2012/02/08 23:39:50 :: Putting interface down
    2012/02/08 23:39:51 :: Releasing DHCP leases...
    2012/02/08 23:39:51 :: Setting false IP...
    2012/02/08 23:39:51 :: Stopping wpa_supplicant
    2012/02/08 23:39:51 :: Flushing the routing table...
    2012/02/08 23:39:51 :: Putting interface up...
    2012/02/08 23:39:53 :: Running DHCP with hostname carbon
    2012/02/08 23:39:53 :: dhcpcd[6087]: version 5.2.12 starting
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: waiting for carrier
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: carrier acquired
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: broadcasting for a lease
    2012/02/08 23:39:53 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: checking for 192.168.1.7
    2012/02/08 23:39:54 ::
    2012/02/08 23:39:58 :: Daemon going down, killing wicd-monitor...
    2012/02/08 23:39:58 :: Removing PID file...
    2012/02/08 23:39:58 :: Shutting down...
    2012/02/08 23:39:58 :: Exception KeyError: KeyError(140583090784000,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
    2012/02/08 23:40:00 :: ---------------------------
    2012/02/08 23:40:00 :: wicd initializing...
    2012/02/08 23:40:00 :: ---------------------------
    2012/02/08 23:40:00 :: wicd is version 1.7.1 717
    2012/02/08 23:40:00 :: setting backend to external
    2012/02/08 23:40:00 :: trying to load backend external
    2012/02/08 23:40:00 :: successfully loaded backend external
    2012/02/08 23:40:00 :: trying to load backend external
    2012/02/08 23:40:00 :: successfully loaded backend external
    2012/02/08 23:40:00 :: Automatically detected wireless interface wlan0
    2012/02/08 23:40:00 :: setting wireless interface wlan0
    2012/02/08 23:40:00 :: automatically detected wired interface eth0
    2012/02/08 23:40:00 :: setting wired interface eth0
    2012/02/08 23:40:00 :: setting wpa driver wext
    2012/02/08 23:40:00 :: setting use global dns to False
    2012/02/08 23:40:00 :: setting global dns
    2012/02/08 23:40:00 :: global dns servers are None None None
    2012/02/08 23:40:00 :: domain is None
    2012/02/08 23:40:00 :: search domain is None
    2012/02/08 23:40:00 :: setting automatically reconnect when connection drops True
    2012/02/08 23:40:00 :: Setting dhcp client to 0
    2012/02/08 23:40:00 :: Wireless configuration file found...
    2012/02/08 23:40:00 :: Wired configuration file found...
    2012/02/08 23:40:00 :: chmoding configuration files 0600...
    2012/02/08 23:40:00 :: chowning configuration files root:root...
    2012/02/08 23:40:00 :: Using wireless interface...wlan0
    2012/02/08 23:40:00 :: Using wired interface...eth0
    2012/02/08 23:40:09 :: Putting interface down
    2012/02/08 23:40:09 :: Releasing DHCP leases...
    2012/02/08 23:40:09 :: Setting false IP...
    2012/02/08 23:40:09 :: Stopping wpa_supplicant
    2012/02/08 23:40:09 :: Flushing the routing table...
    2012/02/08 23:40:09 :: Putting interface up...
    2012/02/08 23:40:11 :: Running DHCP with hostname carbon
    2012/02/08 23:40:11 :: dhcpcd[6245]: version 5.2.12 starting
    2012/02/08 23:40:11 ::
    2012/02/08 23:40:11 :: dhcpcd[6245]: eth0: waiting for carrier
    2012/02/08 23:40:11 ::
    2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: carrier acquired
    2012/02/08 23:40:12 ::
    2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: broadcasting for a lease
    2012/02/08 23:40:12 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: offered 192.168.1.7 from 192.168.1.1
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: checking for 192.168.1.7
    2012/02/08 23:40:13 ::
    2012/02/08 23:40:18 :: dhcpcd[6245]: eth0: leased 192.168.1.7 for 283824000 seconds
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 :: dhcpcd[6245]: forked to background, child pid 6272
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 ::
    2012/02/08 23:40:18 :: DHCP connection successful
    2012/02/08 23:40:18 :: Connecting thread exiting.
    2012/02/08 23:40:19 :: Sending connection attempt result success
    excerpt from dmesg:
    [ 220.232167] iwlwifi 0000:03:00.0: PCI INT A disabled
    [ 235.617077] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [ 235.617084] Copyright(c) 2003-2011 Intel Corporation
    [ 235.617227] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [ 235.617297] iwlwifi 0000:03:00.0: setting latency timer to 64
    [ 235.617467] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [ 235.617472] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900117e4000
    [ 235.617477] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [ 235.618087] iwlwifi 0000:03:00.0: irq 56 for MSI/MSI-X
    [ 235.618299] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [ 235.618699] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 235.647477] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [ 235.647483] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
    [ 235.647488] iwlwifi 0000:03:00.0: Valid Tx ant: 0X7, Valid Rx ant: 0X7
    [ 235.647519] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [ 235.650620] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [ 235.650965] Registered led device: phy1-led
    [ 235.651159] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
    [ 246.254967] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 246.261863] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 246.530405] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 246.537210] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 246.685081] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 251.545715] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 251.552573] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 251.752912] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 252.006076] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.058081] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.060295] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 252.305685] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.357970] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 252.359622] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 253.667466] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 253.674333] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 253.880956] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 254.137065] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 254.189437] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 254.191042] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 254.282074] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 254.288879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 254.493939] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 256.572737] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.627057] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 256.634142] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.636012] wlan0: authenticated
    [ 256.737360] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 256.786082] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 256.826726] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 256.828337] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 256.881172] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 256.884801] wlan0: authenticated
    [ 256.986051] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 256.991611] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 256.991618] wlan0: associated
    [ 257.006311] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 541.311145] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 541.368832] cfg80211: Calling CRDA to update world regulatory domain
    [ 541.453885] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 541.460755] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 541.683356] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 542.134773] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 542.187993] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 542.189715] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 545.110702] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 545.111269] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 546.693999] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 546.700730] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 546.936168] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 547.190401] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 547.243068] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 547.244623] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 547.340217] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 547.347099] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 547.560981] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 549.644554] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 549.647565] wlan0: authenticated
    [ 549.647945] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 549.651558] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 549.651564] wlan0: associated
    [ 549.664372] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 551.461505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 551.463148] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 552.308069] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 552.361536] cfg80211: Calling CRDA to update world regulatory domain
    [ 552.462798] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 552.469740] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 552.690035] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 552.942343] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 552.994174] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 552.995790] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 555.897119] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 555.898730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 579.349813] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 579.356589] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 579.591802] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 579.846307] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 579.898914] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 579.900576] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 580.152275] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 580.205302] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 580.206916] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 582.895184] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 582.896930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 585.270436] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 585.277198] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 585.499201] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 585.854505] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 585.906564] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 585.908183] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 588.995907] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 588.997528] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 663.872912] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 663.879693] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 664.081192] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 664.334184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 664.385981] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 664.387425] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 664.487889] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 664.494654] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 664.717618] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 666.791284] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 666.793798] wlan0: authenticated
    [ 666.794109] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 666.797735] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 666.797743] wlan0: associated
    [ 666.813158] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 667.322243] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 667.323899] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 670.192203] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 670.263747] cfg80211: Calling CRDA to update world regulatory domain
    [ 670.358193] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 670.365031] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 670.589231] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 670.840405] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 670.893001] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 670.894626] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 675.344581] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 675.346128] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 703.509218] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 703.515992] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 703.736371] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 703.985977] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.038426] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.040078] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 704.292262] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.344831] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 704.346446] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 706.924844] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 706.926454] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 709.146741] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 709.153635] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 709.380526] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 709.727666] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 709.779778] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 709.781421] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 712.682663] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 712.683237] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1163.099577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1163.106361] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1163.334124] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1163.785622] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1163.838170] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1163.839786] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1164.088913] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1164.141284] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1164.142888] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1166.755012] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1166.761833] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1166.791221] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1167.001157] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1167.002730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1167.256207] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1167.308293] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1167.309927] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1167.433323] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1167.440189] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1167.683916] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1169.766437] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 1169.769518] wlan0: authenticated
    [ 1169.769895] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 1169.773508] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 1169.773514] wlan0: associated
    [ 1169.788727] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1170.264529] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1170.266191] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1250.157515] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 1250.213474] cfg80211: Calling CRDA to update world regulatory domain
    [ 1250.304748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1250.311548] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1250.531278] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1250.786838] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1250.839522] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1250.841153] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1253.742306] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1253.743948] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1285.564500] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1285.571291] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1285.799384] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1286.050860] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1286.102984] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1286.104632] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1286.225143] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1286.231901] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1286.434212] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1288.467235] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
    [ 1288.469740] wlan0: authenticated
    [ 1288.470052] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
    [ 1288.473730] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
    [ 1288.473738] wlan0: associated
    [ 1288.485867] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1289.075695] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1289.077339] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1291.610215] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
    [ 1291.654374] cfg80211: Calling CRDA to update world regulatory domain
    [ 1291.749248] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1291.755994] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1291.979161] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1292.230432] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.283644] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.285268] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1292.534611] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.586642] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1292.588281] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1293.916374] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1293.923205] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1294.158126] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1294.410095] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1294.461555] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1294.463149] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1296.861675] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1296.863283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1299.572965] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1299.579879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1299.802442] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1300.160999] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1300.212812] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1300.214548] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1303.095815] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1303.097470] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1409.502302] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1409.509094] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1409.732008] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1409.987074] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.039305] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.040915] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1410.289187] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.342358] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1410.344038] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1413.025445] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1413.027081] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 1427.879453] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 1427.886240] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [ 1428.101077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1428.452191] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.505126] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.506718] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1428.756124] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.808184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
    [ 1428.809809] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 1431.511433] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 1431.513072] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    roobie wrote:
    I had a similar problem yesterday (especially reffering to the error "Exception KeyError: KeyError(-1219500352,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored"
    And after reading https://bbs.archlinux.org/viewtopic.php?id=121589 i synced my system time with my hwclock and it worked after that. The command I used:
    hwclock -u -systohc
    It may be the cause of your problem as well...
    My hardware clock and system time are in sync and there's no change of time in my logs like is mentioned in the thread. I don't think this is the issue.
    EDIT: This seems to be limited to my home network, possibly an IPv6 problem. Maybe the IPv6 address is not being assigned properly somewhere?
    Last edited by soupcan (2012-02-10 00:23:03)

  • Add-On connection for Journal Entry - Failed to Connect to SBO Common

    We have a customer (SAPBO 2005A SP01 PL29) with some specific requirements that required an add-on running in the background to monitor the addition of Goods Receipt PO's to the system. When the GRPO is successfully added, the Add-On will (behind the scenes) create an appropriate Journal Entry through the SAP DI. One of the issues that we encountered during the development of this functionality was that when it was tested by users, they weren't authorized to access the Financials module or the Journal Entry screen. What we ended up doing was creating a secondary connection (vCompany) in the DL pulling the information from the encrypted user information from SAP the Add-On used to connect, but utilizing a management level user ID and password. Once that connection has been made, the Journal Entry is added through the DI and that secondary connection is disconnected.
    The problem that we're encountering is this. When the users are logged into SAP Client with an regular user, and the GRPO adds, the secondary connection fails and returns a message of "Failed to Connect to SBO-Common". However, if the user is logged into SAP as an adminitrative level user and the GRPO is added, the secondary connection is successful and the Journal Entry is created. The secondary connection is strictly used for the JE. Here's the code (VS.Net 2005) for the secondary connection:
    vCompany = New SAPbobsCOM.Company
    vCompany.UseTrusted = True
    vCompany.language = SAPbobsCOM.BoSuppLangs.ln_English
    vCompany.CompanyDB = oCompany.CompanyDB
    vCompany.UserName = "XXXXX"
    vCompany.Password = "YYYYY"           
    vCompany.Server = oCompany.Server
    vCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
    lRetConnect = vCompany.Connect()
    Where "XXXXX" would be the appropriate management level SAP User Name and "YYYYY" would be that users password.
    Has anyone else had this kind of issue where you needed a secondary connection with management level access behind the scenes to accomplish something in SAP and had problems getting it to connect? Any thoughts or ideas would be greatly appreciated.

    Hi Dennis,
    what you can try is to make a untrusted connection
    oCompany.UseTrusted = False
    and set the DBUser and Pwd
    oCompany.DbUserName = "sa"
    oCompany.DbPassword = "insertpwd"
    lg David

  • Failed to Connect to SBOCommon

    Hello,
    I created a simple program to get the Session ID from the di server using the VB6.0, I supplied all the valid entries but i still can't get the session id. Here is the SBODI_Server.log response given to me.
    <?xml version="1.0"?><env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Body><env:Fault><env:Code><env:Value>env:Receiver</env:Value><env:Subcode><env:Value>-111</env:Value></env:Subcode></env:Code><env:Reason><env:Text xml:lang="en">Failed to Connect to SBOCommon</env:Text></env:Reason><env:Detail><Command>Login</Command></env:Detail></env:Fault></env:Body></env:Envelope>

    Have a look at this thread
    Can't connect to Company Database w/ SOAP

  • Hyperion Financial Reporting Studio "Failed to Connect to Server"

    One of my report developers recently got a new laptop. Since then, she hasn't been able to open an existing report or create a new one. She can log into Financial Reporting Studio, but when trying to open an existing report or create a new report, she gets the error message "Failed to Connect to Server".
    We've tested using her laptop and using mine. We are both fine on my laptop. We both have same issue on her laptop. Therefore, we don't think it's a security/credentials issue.
    We've searched help documentation and other threads in this forum but haven't been able to find what we need.
    We suspect that file(s) are missing or something wasn't configured properly during the new install. Maybe the Planning ADM Driver?? Our company's tech support hasn't been able to help. This is a new implementation, the consultants are gone, and our IT staff isn't up to speed yet.
    Can anyone offer help as to what file/configuration could be the cause and exactly how to correct?
    Thanks.

    We had the same issue after installing the Financial Reporting Studio client.
    If you run the batch script HRRunAnt.cmd in the directory C:\Hyperion\products\biplus\install\bin after installation this fixes the problem.

  • Fail to connect DB via DI-API on SAP Business One 9.0 for HANA

    Hi,experts.
    I am coding a sample program using VB.net on SAP Business One 9.0 for HANA.
    But this problem fail to connect DB.
    The code relevant to connect DB is below.
    ============================================-
    SAPbobsCOM.Company.DbServerType = 6
    SAPbobsCOM.Company.Server = ServerName:30015
    SAPbobsCOM.Company.UseTrusted = False
    SAPbobsCOM.Company.DbUserName = SYSTEM
    SAPbobsCOM.Company.DbPassword = ********
    SAPbobsCOM.Company.CompanyDB = CompanyDBName
    SAPbobsCOM.Company.UserName = manager
    SAPbobsCOM.Company.Password = ********
    ' Connecting to a company DB
    RetCode = SAPbobsCOM.Company.Connect
    ============================================
    (Result)  RetCode = False
    (Expected result) RetCode = True
    I think this is a commonly difinition on SAP Business One for HANA.,
    but I can not find any useful information...
    Could you give me advice about this problem?
    Best regards,
    Yuka Masuda

    Thank you for your reply, Maik.
    I changed DbServerType from 6 to 9,
    and the program works!!
    I appreciate your useful information.
    Thank you.
    Best regards,
    Yuka Masuda

  • -111 Failed to Connect to SBOCommon

    I am getting an occational error when I am trying to connect to one of our test databases with the DI API.
    This is what the code looks like:
      oCompany = New SAPbobsCOM.Company
            oCompany.Server = "192.168.123.76"
            oCompany.CompanyDB = "Feb19_ForAuditors"
            oCompany.UseTrusted = True
            oCompany.UserName = "maanger"
            oCompany.Password = "manager"
            '** Disconnect from DB if connection present
            If (oCompany.Connected = True) Then
                oCompany.Disconnect()
            End If
            Try
                '** Attempt connection to DB
                lRetCode = oCompany.Connect
            Catch ex As Exception
                MessageBox.Show("Error upon connecting to " & oCompany.CompanyDB & Environment.NewLine & _
                            ex.Message, "SAPbobCOM Error", MessageBoxButtons.OK, MessageBoxIcon.Error)
                Close()
            End Try
            If lRetCode <> 0 Then
                '** If there was a code other than 0 (connected) state why
                oCompany.GetLastError(lErrCode, sErrMsg)
                MessageBox.Show(sErrMsg)
            End If
    Now normally my SAP B1 setup for the application itself is set to Used Trusted.  I started off using .UseTrusted = True but it would never let me connect until it supplied .Username and .Password
    Now it seems it seems to fail more often now with both the username and password as well as being a trusted connection.
    I can use SAP fine, but when I try to run my little app it says Failed to Connect to SBOCommon
    Is there anything wrong in the above code? I would like to use the trusted connection because I don't want to have people type in their username/password each time they run this little middleware app nor do I want to store it on each machine.
    Could it possible be an issue if my program crashes and the connection to the SAP database was not closed properly and it has to wait to timeout??
    Just looking to figure this out

    Tyler,
    You state that you get the error "occasionally".  Does that mean that you do not get it all of the time?   If you do not get it all of the time, what is the difference/what has happened between the time that you do not see the error and the time that you do?  What version of Business One and patch level are you using?
    Here is a note from the SAP Notes database that may help, but it has to do with db ownership and also may not pertain to your issue ...
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0000979081
    Eddy

  • Facetime Calls Fail to connect-need Network update help

    Since we got a new desktop computer (PC) facetime calls come in but fail on connecting on all of our devices. Wifi access otherwise works fine. We have 2 iphone 4s-1 on IOS 6 and one on IOS 7 and two ipads-one on each IOS and the problem is universal so I know I don't need to update IOS as all help says you have to as a first step (it's the apple version of reboot). Anyway, all devices work fine on my office network so it's clearly our home network is somehow blocking facetime. Looking at the network settings on the ipad vs PC Network properties, the last digit of the IP address is different but it's not editable. I tried forgetting the network and going to settings>general>reset>reset network settings and nothing seems to have changed. Our router is cable company supplied and I don't know anything about setting up or changing network settings, there's nothing immediately obvious to change on that screen. Found some help stuff on AirPort utility but it's way above my head-I have no idea if it even applies to a PC...any help/ideas? I'm barely computer literate (obviously) so beyone poking around in the control panel, I'm stuck.

    Since all your devices have the same problem, the cause must be something in your router or at your ISP. Something is blocking the required traffic.
    Well known TCP and UDP ports used by Apple software products

  • Failed to connect Error - Need Help, Please

    I installed , created the simple "Hello" program and it ran fine on the simulator.
    Then, I click the run OTA and now I'm in deep yogurt!
    I get the message:
    *** Error ***
    Failed to connect to device 0!
    Reason:
    Emulator 0 terminated while waiting for it to register!
    BUILD SUCCESSFUL (total time: 4 seconds)
    I just want to restore things to what they were before I selected Run OTA. I've been reading for the past 3 hours and haven't found out to restore. I even deleted and re-installed but, still get the same meassge (probably some saved java pref file...). Anyway, HOW TO RESTORE to a virgin setup????
    Thanks

    ... I read somewhere I need to reboot - I did and it took care of it.

  • Remote app on ipod fails to connect to itunes 10

    After upgrading to iTunes 10, my remote app on the ipod touch 4G fails to connect. I've reauthorized, which times out most times, but eventually when it works, it only continues to connect to iTunes until I close and restart the program. I've disabled all firewalls and still have the issue. iTunes 10/iPod Touch 4G/iOS 4.1/ancient remote.app do not play well together.
    Anyone else unable to get the remote app working reliably with this combination?

    Hello all,
    I would like to get more details from people who are still having trouble getting Remote 2.0.1 to connect. If you are unable to connect, please email me <[email protected]> with the following information:
    - A detailed description of the specific issue you are seeing.
    - What OS is on the host computer? (the one with iTunes on it)
    - What OS is on the affected iOS device(s)?
    - A description of your network topology. Please be as detailed as you can, including hardware and firmware versions, if possible. Also please explain how everything is connected.
    - Is the base station running default settings, or do you have any non-standard settings enabled? If so, please elaborate.
    - Do you have the built-in firewall enabled on the host computer?
    - Do you have any other firewall or Internet protection (anti-virus, etc) installed on the host computer?
    - Were you able to connect with versions of Remote prior to 2.0?
    - If you have multiple computers, can you get Remote to connect to any of them?
    - Does Home Sharing work between computers on your network?
    - Do you see any messages in Console (in Applications/Utilities) on the host computer that seem to coincide with the connection failures?
    Thanks,
    Roy
    <[email protected]>

  • My iphone 5 won't make a call when i fail to connect to the internet via 3g

    My iphone 5 won't call when i fail to connect to the internet via 3g.
    At work i dont have wifi i have 3g, if i launch say the sky go app,or the iplayer, sometimes they work and everything is fine...sometimes they wont load as 3g for whatever reason cant get a connection at that particular time........ if i then try and make a call the call will fail. I've experimented 25 + times and this is definately the cause.
    (note: when the 3g connection does work, the phone has absolutely no problem calling people)
    Anyone had this problem?
    Even better has anyone got a solution?
    Thanks,
    Nick.

    Are you sure that the carrier's signal is strong where you are having this problem? Certain building structures and locations have poor cellular signal strength and this often results in the "No Service" indication. Are other users able to get service in the same locations where you have problems?

  • On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

    I have a new install of Windows 2012.  I have two physical servers.  One is a W2012 std Domain Controller ("DC").  The Second is configured as W2012 HyperV  ("HV").  Under HV I have
    two VMs.  One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS").  All systems are behind a firewall appliance.  Exchange is working via Outlook and OWA internally and externally.  The self
    created SSL must be installed manually on external machines since it comes up as an untrusted certificate.  Once installed remote outlook works and OWA works.  I have configured the terminal server and I am able
    to login remotely as various users under my "TS group".  The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
    on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
    for alias@ domain, then fails the logging on to the mail server)  The error reads:  "Outlook cannot log on.  Verify you are connected to the network and are using the proper server and mailbox name.  The
    connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC.  I have
    tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command.  I have also tried to use the guid via "Get-Mailbox
    ALIAS | fl name, exchangeguid.  Keep in mind all desktop users on the network are connecting to Outlook without issue.
    I would appreciate any thoughts on solving this issue.

    Hi,
    According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
    Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
    open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
    Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
    autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
    Regards,
    Winnie Liang
    TechNet Community Support

  • My new i phone 5 wont sync with my laptop, keeps saying failed to connect to sync services. any help?

    I just purchased a new i phone 5. when i go to connect with my laptop it says 'failed to connect to sync services, try again later' it shows my phone, and i can see my app screens, however it wont let me sync, back up or make changes. this is my first apple product, any help would be greatly appreciated.

    Hello there, load dogg.
    The following Knowledge Base article provides some in-depth steps to help troubleshoot the issue you are descibing:
    iTunes for Windows: "Unable to load data class" or "Unable to load provider data" sync services alert
    http://support.apple.com/kb/ts2690
    Thanks for reaching out to Apple Support Communities for answers to your question.
    Cheers,
    Pedro D.

  • OBIEE 11g agents are failed to connect to Essbase

    OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase.
    User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Essbase variables in RPD are upto date.
    Only agents are failing and error says invalid credentials, but dashboard pages are running without any issue.
    OBIEE: 11.1.1.5 (BP4)
    Essbase: 11.1.2.1
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
    Essbase and OBIEE services are up and running.
    Any help will be appreciated.

    We finally implemented CSS Token option and ended up with this error. We are unable to connect to essbase with CSS Token option.
    We followed the Oracle document to implement this.
    [nQSError: 43119] Query Failed: EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials. (HY000)
    We did update this property:
    JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} -Didstore.identityAttribute=objectguid"
    Any help will be appreciated!

  • Fingerprint reader not working in IE and saying failed to connect to sensor

    Hi all,
    I bought a Qosmio x500 10t a couple of months back. For the first couple of weeks i had no probs using the fingerprint reader to log in to windows and to log in to websites in Internet exploer.
    All of a sudden it would not work on any website stored. The green banner showed accross the top of site and asked to swipe finger but nothing happened when I swiped. I rebooted and it worked again but not for long before failing. This time a reboot didnt work so i deleted my finger prints and websites and started from scratch. That worked for a couple of attempts before probs started again. And on trying to get into Fingerprint utility it says failure to connect to sensor. So, I did a system restore. It worked for a couple of times again and then same probs. So I found the updated utility software, uninstalled the old and put on the new. Same again, worked for a couple of times then failed.
    I could not find anything stuck in the registry but to be on the safe side i did a full system clean back to factory setup using backup discs. Hey presto i thought it had worked. Everything going ok for first 24hrs and then same problems start to occur. Only this time it is also prompting me to enroll fingerprints even though i already have. And when i try to get into the utilioty it says failed to read sensor again.
    The fingerprint log on to windows always works as long as i dont close the fingerprint utility down before shutting down. If i do exit the utilty i cant reopen it as it just says failed to connect to sensor. And then i have to unistall and reinstall the utility software. Aty the moment it occasionally works on websites stored but most of the time it doesnt do anything.
    Please help. Do I need to send laptop back to Toshiba??

    Hi,
    *I got a solution* for the problem that the fingerprint sensor "suddenly" does not work any more.
    When starting the Toshiba Fingerprint Utility, it says "failed to connect to fingerprint sensor".
    Is it possible that just before it stopped working there was a new firewall installed, or firewall settings had been changed?
    *In my case, the problem was solved by changing my firewall settings* (Windows 7 Firewall Control) to ALLOW all traffic for
    the Authentec Fingerprint Sensor Service (AFSS). It is the file "AtService.exe" in C:\Program files
    The reason is simple:
    The Toshiba Fingerprint utility communicates with the fingerprint sensor service via TCP/IP.
    Therefore, any firewall that blocks traffic on the local computer will block the communication.
    *After changing my firewall settings, fingerprint sensor works* on my R700 flawlessly now.

Maybe you are looking for