Failover interface failed
Hi,
I have 2 ASA 5520 firewall configured with HA(Failover). but some time my primary firewall goes down standby firewall doesnt come active. i found below log from primary firewall..what is the reason & what is the mining of reason code of 4...
Nov 30 2012 14:07:47: %ASA-1-105002: (ASA) Enabling failover.
Nov 30 2012 14:08:43: %ASA-1-105043: (Primary) Failover interface failed
Nov 30 2012 14:08:56: %ASA-1-103001: (Primary) No response from other firewall (reason code = 4).
After i hard reboot my standby firewall below log had been generated..
Nov 30 2012 15:51:57: %ASA-1-105042: (Primary) Failover interface OK
Nov 30 2012 15:52:02: %ASA-1-709003: (Primary) Beginning configuration replication: Send to mate.
Nov 30 2012 15:52:15: %ASA-1-709004: (Primary) End Configuration Replication (ACT)
Please assist....
Regards
Suhas
Hi,
The explanation for that can be found in the ASAs syslog messages document.
Here it is
103001 Error Message %ASA-1-103001: (Primary) No response from other firewall (reason
code = code).
Explanation This is a failover message, which is displayed if the primary unit is unable to communicate with the secondary unit over the failover cable. (Primary) can also be listed as (Secondary). for the secondary unit. Table 1-2 lists the reason codes and the descriptions to determine why the failover occurred.
Table 1-2 Reason Codes
Reason Code
Description
1
The local unit is not receiving the hello packet on the failover LAN interface when LAN failover occurs or on the serial failover cable when serial failover occurs, and declares that the peer is down.
2
An interface did not pass one of the four failover tests, which are as follows: 1) Link Up, 2) Monitor for Network Traffic, 3) ARP, and 4) Broadcast Ping.
3
No proper ACK for 15+ seconds after a command was sent on the serial cable.
4
The local unit is not receiving the hello packet on the failover LAN and other data interfaces and it is declaring that the peer is down.
5
The failover LAN interface is down, and other data interfaces are not responding to additional interface testing. In addition, the local unit is declaring that the peer is down.
Recommended Action Verify that the failover cable is connected correctly and both units have the same hardware, software, and configuration. If the problem persists, contact the Cisco TAC.
Are you saying that the Primary ASA loses all connectivity to the Secondary ASA (looking at the log messages). Judging by the above Cisco description it would mean the Primary ASA isnt getting Failover Hellos through any of the monitored interfaces which again would make it seem like the Secondary Firewall is expriencing some problems.
- Jouni
Similar Messages
-
CSM error message on ASA Failover interface
Hello
We use CSM 4.4 to manage our ASA firewalls.
One of them is a failover pair. CSM now always creates a warning message when approving an activity, stating:
FWSVC Access Rules Warnings -> The following interfaces GigabitEthernet0/3,management, are not bound to any Access Rules and remain wide open for traffic to lower security level interfaces
Is there a way to surpress those messages?
Or is it required to configure an access-list to the lan-based failover interface?
Thanks
PatrickHi Bro
Yes, there is a way to suppress these error messages by issuing the command "no logging message " in that particular context but I wouldn't advise to do so.
Perhaps, this could indicate a legitimate error on your part. If you could paste the show run output here, that would be great. We could advice your accordingly.
Regards,
Ram -
Interfaces fails twice but executes correclty from next time
Hi,
I have interfaces which are coping data from MS Access tables to oracle tables.
NOw here i am facing somewhat strange issue.
I have 3 environments Dev,Test and PROD.
Now when i am moving scenarios from TEST to PROD ,the interfaces fails for first 2 times giving following error
ODI-1227: Task SrcSet0 (Loading) fails on the source MICROSOFT_ACCESS connection MTP_Products.
Caused By: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(JdbcOdbc.java:3907)
at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(JdbcOdbcResultSet.java:5698)
at sun.jdbc.odbc.JdbcOdbcResultSet.getString(JdbcOdbcResultSet.java:354)
and executes correctly next time.
Although i have specified fields data types and its legth more than required.
Let me know if anyone has come across such issues or anyone has idea about something like it.
Help appreciated.
Thanks,
MaheshDownload a new copy of the Firefox program: http://www.mozilla.com/firefox/all.html
Trash the current Firefox application to do a clean reinstall.
Install the new version that you have downloaded.
Your profile data is stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder], so you won't lose your bookmarks and other personal data. -
Does the ASA's failover interface work at 1000/Full Duplex?
I was once told that the speed had to be set to 100Mbs on the Failover link when using LAN based failover on a Gig switchport.
I am running Active/Passive on my ASAs right now, this is the only configuration that I needed on my primary unit for the FO interface, I never had to set the interface link speed.
interface GigabitEthernet0/3
description LAN/STATE Failover Interface
failover
failover lan unit primary
failover lan interface FOLink GigabitEthernet0/3
failover replication http
failover link FOLink GigabitEthernet0/3
failover interface ip FOLink 192.168.100.1 255.255.255.0 standby 192.168.100.2 -
[vmware] Virtual machine communication interface failed
hello,
on a fresh install of archlinux, i have installed vmware workstation 11.0 but when i execute this command :
vmware-modconfig --console --install-all
i have this error
Virtual machine communication interface failed
full log
vmware-modconfig --console --install-all
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/cpuid.o
/tmp/modconfig-sc9HDC/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
^
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/task.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-sc9HDC/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-sc9HDC/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-sc9HDC/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-sc9HDC/vmmon-only/vmmon.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
cp -f vmmon.ko ./../vmmon.o
make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/driver.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/hub.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/userif.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/netif.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/bridge.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/procfs.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/smac.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-sc9HDC/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-sc9HDC/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-sc9HDC/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-sc9HDC/vmnet-only/vmnet.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
cp -f vmnet.ko ./../vmnet.o
make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface failed
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Unable to start services
[root@hulk vmware-root]# ls
vmware-818.log vmware-authdlauncher-2058.log vmware-vmis-1888.log
vmware-apploader-1976.log vmware-vmis-1407.log vmware-vmis-1910.log
vmware-apploader-818.log vmware-vmis-1429.log
[root@hulk vmware-root]# chown gael:users *
[root@hulk vmware-root]# chown -R gael:users ./
[root@hulk vmware-root]# modprobe vmci
modprobe: FATAL: Module vmci not found.
[root@hulk vmware-root]# vmware-modconfig --console --install-all -v
/usr/lib/vmware/bin/vmware-modconfig-console: invalid option -- 'v'
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/cpuid.o
/tmp/modconfig-KdpHql/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
^
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/task.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-KdpHql/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-KdpHql/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-KdpHql/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-KdpHql/vmmon-only/vmmon.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
cp -f vmmon.ko ./../vmmon.o
make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
CC [M] /tmp/modconfig-KdpHql/vmnet-only/driver.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/hub.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/userif.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/netif.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/bridge.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/procfs.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/smac.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-KdpHql/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-KdpHql/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-KdpHql/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-KdpHql/vmnet-only/vmnet.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
cp -f vmnet.ko ./../vmnet.o
make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface failed
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Unable to start services
thanks for your helpAlso having the same problem
dustin ~ $ sudo vmware-modconfig --console --install-all
[sudo] password for dustin:
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
make: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
Using kernel build system.
/sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/task.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-KZzuso/vmmon-only/vmcore/moduleloop.o
/tmp/modconfig-KZzuso/vmmon-only/linux/driver.c:1332:1: warning: always_inline function might not be inlinable [-Wattributes]
LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
^
LD [M] /tmp/modconfig-KZzuso/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-KZzuso/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-KZzuso/vmmon-only/vmmon.ko
make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
make: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
Using kernel build system.
/sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
CC [M] /tmp/modconfig-KZzuso/vmnet-only/driver.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/hub.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/userif.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/netif.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/bridge.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/procfs.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/smac.o
CC [M] /tmp/modconfig-KZzuso/vmnet-only/vnetEvent.o
In file included from include/linux/pci.h:34:0,
from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
from /tmp/modconfig-KZzuso/vmnet-only/netif.c:43:
include/linux/pci_ids.h:2248:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
#define PCI_VENDOR_ID_VMWARE 0x15ad
^
In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
from /tmp/modconfig-KZzuso/vmnet-only/netif.c:42:
/tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
#define PCI_VENDOR_ID_VMWARE 0x15AD
^
CC [M] /tmp/modconfig-KZzuso/vmnet-only/vnetUserListener.o
In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:52:
/tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
#define PCI_VENDOR_ID_VMWARE 0x15AD
^
In file included from include/linux/pci.h:34:0,
from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:51:
include/linux/pci_ids.h:2248:0: note: this is the location of the previous definition
#define PCI_VENDOR_ID_VMWARE 0x15ad
^
LD [M] /tmp/modconfig-KZzuso/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-KZzuso/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-KZzuso/vmnet-only/vmnet.ko
make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
/sbin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface failed
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Unable to start services
Now I have the same failed communication interface also
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface failed
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Unable to start services
PS, I have the vmware-patch 11.0.0-1 installed -
Software installation external audio interface fails Terratec dmx6 fire usb
Software installation external audio interface fails Terratec dmx6 fire usb.
Dear Apple Power User in this forum,
here is a question for some of us experts.
I have a external usb audio interface Terratec, Model: DMX 6 fire USB.
http://www.terratec.net/en/products/technical-data/produktetechnische_daten_en3246.html
0. There should be after install enclosing software an control app in the app folder, but it isnt there. Why?
1. the attached installer protocol seems to be normal. isnt it?
2. the usb audio hardware appears in system profiler.
3. there isnt the audio hardware in audio-midi-setup! Why?
4. one of the installed content is visibil in activity monitor as an extension "35 DMX6FireService root 0,0 1 964,00 KB 18,55 MB 22 Intel 00.01 176,00 KB 184,00 KB 73 72"
5. an other part is in the system-library-extension folder "TTDMX6fire.kext"
6. other files i am not capacity to find....
7. and there is the app missing in apps folder! Whitout that it can not work.
8. Software is for 10.5 and 10.6 32-bit tested from the vendor!?
9. My MacBookPro early 2008 2.4ghz is capabel of 64bit but is default in 32 mode says apple spec, also my osx 10.5.8 newest updates should be 32 bit. Isnt it?
10. installation tested whit disconnected/connected ext. volumes or display or these audio interface, whith repaired permissions, on two different macs (second is iMac), whit reboot,
11. tested on different usb ports, usb port test passed whith other equipment,
12. on windows xp all works.
13. tested on a new admin user, same problem.
14. searched whith terminal command line in applications, nothing.
15. get software from cd and homepage, no effect.
16. asked vendor: "until now never had problems like that"
any ideas? please help!
for testing or showing the installer look here:
http://www.terratec.net/en/driver-and-support/driver_21300.html?selectproduct=DM X%206Fire%20USB
Installation Protocol:
Dec 25 00:08:39 cadas-macbook-pro /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer[400]: vm_allocate: 0, 0x5800000 - 0x25800000
Dec 25 00:08:39 cadas-macbook-pro /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer[400]: vm_protect: 0
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: @(#)PROGRAM:Install PROJECT:Install-388
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: @(#)PROGRAM:Installer PROJECT:Installer-281
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Hardware: MacBookPro4,1 @ 2.40 GHz (x 2), 4096 MB RAM
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Running OS Build: Mac OS X 10.5.8 (9L30)
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: TMPDIR=/var/folders/gC/gCDdYZuFE98Z28wIB40BeE+TI/-Tmp-/
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SHELL=/bin/bash
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: HOME=/Users/cada
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: USER=cada
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: LOGNAME=cada
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: DISPLAY=/tmp/launch-MQSZjG/:0
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SSHAUTHSOCK=/tmp/launch-x3IAC1/Listeners
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: ApplePubSub_SocketRender=/tmp/launch-YalWkk/Render
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: _CF_USER_TEXTENCODING=0x1F5:0:3
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SECURITYSESSIONID=a1b410
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: COMMAND_MODE=unix2003
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: DMX6fireUSB Installation Log
Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Opened from: /Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg
Dec 25 00:08:39 cadas-macbook-pro installdb[402]: started (uid 96)
Dec 25 00:08:39 cadas-macbook-pro installdb[402]: Opened receipt database on '/' with schema 17.
Dec 25 00:08:45 cadas-macbook-pro installdb[402]: done. (0.004u + 0.003s)
Dec 25 00:09:10 cadas-macbook-pro runner[403]: Administrator authorization granted.
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: =============================================================================== =
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: User picked Standard Install
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Choices selected for installation:
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6fireUSB"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6FireUSBCpl"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#dmx6fireusbcpl.pkg : com.terratec.dmx6fireusb.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6fire.pkg : com.terratec.dmx6fireusb1.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "TTDMX_6fire_CUSTOMEXT"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6firecustomext.pkg : com.terratec.dmx6fireusb2.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "TTDMX6fire"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6fire-1.pkg : com.terratec.dmx6fireusb3.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6FireService"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#dmx6fireservice.pkg : com.terratec.dmx6fireservice3.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "LaunchDaemon"
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#comterratecdmx6fire.pkg : com.terratec.dmx6fireusb4.pkg : 1
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: =============================================================================== =
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: It took 0.00 seconds to summarize the package selections.
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: location = file://localhost
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#dmx6fireusbcpl.pkg
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6fire.pkg
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6firecustomext.pk g
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6fire-1.pkg
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#dmx6fireservice.pkg
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#comterratecdmx6fire.pk g
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: _installNextPackage of 1
Dec 25 00:09:15 cadas-macbook-pro installdb[405]: started (uid 96)
Dec 25 00:09:15 cadas-macbook-pro installdb[405]: Opened receipt database on '/' with schema 17.
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Starting installation:
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Preparing volume "250GB_MBPro2" for installation
Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Configuring volume "250GB_MBPro2"
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Preparing disk for local booted install.
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Free space on "250GB_MBPro2": 11,6 GB (12495523840 bytes).
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Create temporary directory "/private/tmp/dmx6fireusb.pkg.400aysS6s"
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Running install actions
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Processing dmx6fireusbcpl:
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: It took 0.06 seconds to create the install plan for dmx6fireusbcpl.
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:16 cadas-macbook-pro Installer[400]: run preupgrade script for dmx6fireusbcpl
Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.pCJk/./preflight[408]: : deleting previous Kernel Extensions
Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.pCJk/./preflight[408]: PID: 43
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: Initializing new flat-package receipt.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: Extracting...
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: 20 of 20 files written in 0.05 seconds.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: 408 kilobytes installed at 7.5 MB/s.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb.pkg.bom"
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6fire:
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.03 seconds to create the install plan for ttdmx6fire.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: Initializing new flat-package receipt.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: Extracting...
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: 9 of 9 files written in 0.01 seconds.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: 92 kilobytes installed at 11.5 MB/s.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb1.pkg.bom"
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6firecustomext:
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for ttdmx6firecustomext.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: Initializing new flat-package receipt.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: Extracting...
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: 9 of 9 files written in 0.01 seconds.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: 80 kilobytes installed at 9.7 MB/s.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb2.pkg.bom"
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6fire-1:
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for ttdmx6fire-1.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: run preupgrade script for ttdmx6fire-1
Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.MEBZ/./preflight[424]: : deleting previous Kernel Extensions
Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.MEBZ/./preflight[424]: PID:
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: Initializing new flat-package receipt.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: Extracting...
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: 9 of 9 files written in 0.03 seconds.
Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: 832 kilobytes installed at 26.2 MB/s.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb3.pkg.bom"
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing dmx6fireservice:
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for dmx6fireservice.
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: Initializing new flat-package receipt.
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: Extracting...
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: 2 of 2 files written in 0.01 seconds.
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: 136 kilobytes installed at 13.4 MB/s.
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:18 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireservice3.pkg.bom"
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Processing comterratecdmx6fire:
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Determining files to install
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for comterratecdmx6fire.
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Configuring deferred files
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Determining obsolete files
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Assembling temporary receipt
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Removing obsoleted files
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Creating destination path
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Validating package payload
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Starting file extraction
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: Initializing new flat-package receipt.
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: Extracting...
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: 2 of 2 files written in 0.01 seconds.
Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: 8 kilobytes installed at 1.0 MB/s.
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing post-extraction actions
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finishing receipt
Dec 25 00:09:18 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb4.pkg.bom"
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Removing temporary directory "/private/tmp/dmx6fireusb.pkg.400aysS6s"
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finalize disk "250GB_MBPro2"
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Notifying system of updated components
Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/System/Library/Extensions'
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: _installNextPackage of 0
Dec 25 00:09:18 cadas-macbook-pro Installer[400]:
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: ** Summary Information **
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Operation Elapsed time
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: -----------------------------
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: script 0.29 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: zero 0.02 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: install 1.42 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: validate 0.01 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: os 0.00 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: extract 0.87 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: receipt 0.05 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: disk 1.01 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: config 0.19 seconds
Dec 25 00:09:18 cadas-macbook-pro Installer[400]:
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Starting installation:
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finalizing installation.
Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Registering applications
Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/Applications/./DMX6FireUSBCpl.app'
Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/Applications/.'
Dec 25 00:09:19 cadas-macbook-pro Installer[400]: IFDInstallController 868C80 state = 5
Dec 25 00:09:19 cadas-macbook-pro Installer[400]: Displaying 'Install Succeeded' UI.
Dec 25 00:09:24 cadas-macbook-pro installdb[405]: done. (0.026u + 0.040s)solved whith the old driver vom archive of vendor: "DMX6Fire_USBMac.1.00c.dmg" thats for 10.5.x for me works.
The newest from the vendor delivered driver 1.22 (marked for 10.5 and 10.6) seems to not work under 10.5. -
ARP collision on failover interface of ASA5510
Seeing a funny problem. Whenver the secondary ASA is rebooted, there is complaint of an ARP conflict on the failover interface:
Received ARP request collision from 169.254.0.1/1cdf.0f2e.e8b6 on interface FAILOVER with existing ARP entry 169.254.0.1/1cdf.0f2e.e0b0
169.254.0.1 is the primary ASA's failover interface, and the physical interface has MAC address 1cdf.0f2e.e0b0
169.254.0.2 is the secondary ASA's failover interface, and the physical interface has MAC address 1cdf.0f2e.e8b6
Failover IPs should remain constant even as roles change, so I'm very puzzled why the secondary would take the primary's IP.
Both are single context running 9.0(3)Hi Johnny,
The Ip addresses that we assign in failover are for active and standby unit, they are not assigned as primary and secondary units.
So as the role of a unit in the failover pair changes the IP addresses and the MAC also changes accrodingly.
So what you are seeing is normal.
further the same is documented as well:
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#acti
Hope this helps,
Cheers,
Naveen -
Webservice interface failed, sapstartsrv stopped
Hi,
in our SRM production (abap+java) system's syslog we get following error -->
webservice interface failed, sapstartsrv stopped
=================
We are not sure what error is this.
Can somebody help in this?
Thanks in Advance,
Akki.Hi
Please see related links ->
Note 1081201 SAP Start Service may crash when fetching a Java callstack
Note 927637 Web service authentication in sapstartsrv as of Release 7.00
Note 936273 sapstartsrv for all platforms
Note 897933 Start and stop sequence for SAP Systems
Note 867892 MMC shows current SAP processes as being stopped
Note 877795 Problems w/ sapstartsrv as of Release 7.00 & 6.40 patch 169
Re: How to stop sapstartsrv and sapstart processes ?
https://forums.sdn.sap.com/click.jspa?searchID=7502269&messageID=3661396
https://forums.sdn.sap.com/click.jspa?searchID=7502269&messageID=9957
Regards
- Atul -
Send an email if interface fails
Hi experts
I am working in CRM 6.0 Service project. Here we are creating service ticket. Once the ticket is created, status and BP details will be sent to 3rd party back office system. If it is successfully posted in the back office system, CRM will get updated with new status and External reference number. Our requirement is if interface fails, we want to send an automated email to 2nd response manager with the ticket details that is failed to send 3rd party back office system.
Can this be achieved by Actions? Or is there any better way? If it is actions, what will be the trigger point we have to use?
Appreciate your expert help in this.
Regards
SuryaYou can have the interface to set a status in your transaction to indicate an error has occurred and your action can be trigger based on that status.
By using status management, besides email, error report can also be generated to monitor errors. -
Failover cluster failed due to mysterious IP conflict ?
I'm having a mysterious problem with my Failover cluster,
Cluster name: PrintCluster01.domain.com
Members: PrintServer01.domain.com andPrintServer02.domain.com
in the Failover Cluster Management – Cluster Event I received the Critical error message 1135 and 1177:
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 15/06/2011 9:07:49 PM
Event ID: 1177
Task Category: None
Level: Critical
Keywords:
User: SYSTEM
Computer: PrintServer01.domain.com
Description:
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is
connected such as hubs, switches, or bridges.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 15/06/2011 9:07:28 PM
Event ID: 1135
Task Category: None
Level: Critical
Keywords:
User: SYSTEM
Computer: PrintServer01.domain.com
Description:
Cluster node 'PrintServer02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run
the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node
is connected such as hubs, switches, or bridges.
After further investigation, I found some interesting error here, from the very first critical error message logged in the Event viewer on PrintServer02:
Log Name: System
Source: Tcpip
Date: 15/06/2011 9:07:29 PM
Event ID: 4199
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PrintServer02-VM.domain.com
Description:
The system detected an address conflict for IP address 192.168.127.142 with the system having network hardware address 00-50-56-AE-29-23. Network operations on this system may be disrupted as a result.
192.168.127.142 --> secondary IP of PrintServer01
how could that be possible it conflict by one of the PrintServer01 node ? the detailed is as below:
**From PrintServer01**
Ethernet adapter Local Area Connection* 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-50-56-AE-29-23
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.1.183(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
I have double check in all of the cluster members that all IP addresses is now unique.
however I'm sure that I the IP is static not by DHCP as from the IPCONFIG results below:
From **PrintServer01** (the Active Node)
Windows IP Configuration
Host Name . . . . . . . . . . . . : PrintServer01
Primary Dns Suffix . . . . . . . : domain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.com
domain.com.au
Ethernet adapter Local Area Connection* 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-50-56-AE-29-23
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.1.183(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster Public Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-29-23
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.127.155(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.127.88(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.127.142(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.127.143(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.127.144(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.127.254
DNS Servers . . . . . . . . . . . : 192.168.127.10
192.168.127.11
Primary WINS Server . . . . . . . : 192.168.127.10
Secondary WINS Server . . . . . . : 192.168.127.11
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster Private Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-43-EC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.184.2.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
From **PrintServer02**
Windows IP Configuration
Host Name . . . . . . . . . . . . : PrintServer02
Primary Dns Suffix . . . . . . . : domain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.com
domain.com.au
Ethernet adapter Local Area Connection* 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-50-56-AE-5F-E5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.2.86(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster Public Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-79-FA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.127.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.127.119(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.127.254
DNS Servers . . . . . . . . . . . : 192.168.127.10
192.168.127.11
Primary WINS Server . . . . . . . : 192.168.127.11
Secondary WINS Server . . . . . . : 192.168.127.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster Private Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-77-8D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.184.2.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Any help would be greatly appreciated.
Thanks,
AWT
/* Server Support Specialist */I
am facing the same scenario as the original poster. This is on Server 2008 R2 SP1.
WIndow event log entries follow the same pattern. The MAC address listed in connection with the duplicate IP belonged to the passive node.
Interestingly, the Cluster.log begins to explode with activity a few milliseconds before the first Windows event is logged.
2012/07/11-15:20:59.517 INFO [CHANNEL fe80::8145:f2b9:898e:784e%37:~3343~] graceful close, status (of previous failure, may not indicate problem) ERROR_IO_PENDING(997)
2012/07/11-15:20:59.517 WARN [PULLER SQLTESTSQLB] ReadObject failed with GracefulClose(1226)' because of 'channel to remote endpoint fe80::8145:f2b9:898e:784e%37:~3343~
is closed'
2012/07/11-15:20:59.517 ERR [NODE] Node 1: Connection to Node 2 is broken. Reason GracefulClose(1226)' because of 'channel to remote endpoint fe80::8145:f2b9:898e:784e%37:~3343~
is closed'
2012/07/11-15:20:59.517 WARN [RGP] Node 1: only local suspects are missing (2). moving to the next stage (shortcut compensation time 05.000)
2012/07/11-15:20:59.548 WARN [NETFTAPI] Failed to query parameters for fe80::5efe:169.254.1.79 (status 80070490)
2012/07/11-15:20:59.548 WARN [NETFTAPI] Failed to query parameters for fe80::5efe:169.254.1.79 (status 80070490)
2012/07/11-15:20:59.579 INFO [CHANNEL 192.168.3.22:~3343~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
2012/07/11-15:20:59.579 WARN cxl::ConnectWorker::operator (): GracefulClose(1226)' because of 'channel to remote endpoint 192.168.3.22:~3343~ is closed'
2012/07/11-15:20:59.829 INFO [GEM] Node 1: EnterRepairStage1: Gem agent for node 1
2012/07/11-15:21:00.141 INFO [GEM] Node 1: EnterRepairStage2: Gem agent for node 1
2012/07/11-15:21:00.499 WARN [RCM] Moving orphaned group Available Storage from downed node SQLTESTSQLB to node SQLTESTSQLA.
2012/07/11-15:21:00.499 WARN [RES] IP Address <Cluster IP Address>: WorkerThread: NetInterface ef150d1a-f4a1-4f4f-a5c7-6e7cb2bfacab changed to state 3.
2012/07/11-15:21:00.499 WARN [RCM] Moving orphaned group MSSTEST from downed node SQLTESTSQLB to node SQLTESTSQLA.
2012/07/11-15:21:00.546 WARN [RES] IP Address <SQL IP Address 1 (DEVSQL)>: Failed to delete IP interface 2003B882, status 87.
2012/07/11-15:21:00.562 WARN [RES] Physical Disk <Cluster Disk 2>: PR reserve failed, status 170
2012/07/11-15:21:00.577 WARN [RES] Physical Disk <Cluster Disk 1>: PR reserve failed, status 170
2012/07/11-15:21:00.593 WARN [RES] Physical Disk <Cluster Disk 3>: PR reserve failed, status 170
2012/07/11-15:21:02.215 WARN [NETFTAPI] Failed to query parameters for 192.168.3.32 (status 80070490)
2012/07/11-15:21:02.215 WARN [NETFTAPI] Failed to query parameters for 192.168.3.32 (status 80070490)
2012/07/11-15:21:05.864 DBG [NETFTAPI] received NsiParameterNotification for fe80::5cd:8cc2:186:f5cb (IpDadStatePreferred )
2012/07/11-15:21:06.565 ERR [RES] Physical Disk <Cluster Disk 2>: Failed to preempt reservation, status 170
2012/07/11-15:21:06.581 ERR [RES] Physical Disk <Cluster Disk 2>: OnlineThread: Unable to arbitrate for the disk. Error: 170.
2012/07/11-15:21:06.581 ERR [RES] Physical Disk <Cluster Disk 2>: OnlineThread: Error 170 bringing resource online.
2012/07/11-15:21:06.581 ERR [RHS] Online for resource Cluster Disk 2 failed.
2012/07/11-15:21:06.581 WARN [RCM] HandleMonitorReply: ONLINERESOURCE for 'Cluster Disk 2', gen(0) result 5018.
2012/07/11-15:21:06.581 ERR [RCM] rcm::RcmResource::HandleFailure: (Cluster Disk 2)
2012/07/11-15:21:06.581 WARN [RES] Physical Disk <Cluster Disk 2>: Terminate: Failed to open device \Device\Harddisk5\Partition1, Error 2
2012/07/11-15:21:06.581 ERR [RES] Physical Disk <Cluster Disk 1>: Failed to preempt reservation, status 170
2012/07/11-15:21:06.581 ERR [RES] Physical Disk <Cluster Disk 1>: OnlineThread: Unable to arbitrate for the disk. Error: 170.
2012/07/11-15:21:06.581 ERR [RES] Physical Disk <Cluster Disk 1>: OnlineThread: Error 170 bringing resource online.
Full cluster log here:
https://skydrive.live.com/redir?resid=A694FDEBF02727CD!133&authkey=!ADQMxHShdeDvXVc -
Payables Open Interface failed-help plz.
All,
Version: 11.5.10.2
The project is about integrating the legacy system with Oracle 11i. i.e we are importing invoices created in 3rd party appln and importing it to Oracle thru Payables Open interface. I'm stuck with 1 use case. i.e invoice against a PO having split accounting.
scenario 1:
1. created a PO in Oracle with 1 line having 2 distributions
2. Against the same PO, invoice is created with for the same line item and imported to Oracle. I populated PO related info in PONumber,POLineNumber and POShipmentNum in the ap_invoice_lines_interface table.
3. Payables OPen interface worked fine
scenario 2:
1. Against the same PO having split, created an invoice for the line item, this time I added a freight on to it.
2. Concurrent failed(i.e it didnt throw any error to the ap rejections table),
3. so i populated po_distribution_num to the ITEM line, and ran the concurrent again. It processed the invoice successfully.
I've following queries:
1. In the 1st scenario, without populating po_dist_num to the lines table, conc. processed the invoice successfully
2. In the 2nd, only after populating the po_dist_num, the conc. processed it successfully
3. In what scenario/test case, does the payables open interface expects po_dist_num?
Please advise.
Rgds,
SenAll,
Version: 11.5.10.2
The project is about integrating the legacy system with Oracle 11i. i.e we are importing invoices created in 3rd party appln and importing it to Oracle thru Payables Open interface. I'm stuck with 1 use case. i.e invoice against a PO having split accounting.
scenario 1:
1. created a PO in Oracle with 1 line having 2 distributions
2. Against the same PO, invoice is created with for the same line item and imported to Oracle. I populated PO related info in PONumber,POLineNumber and POShipmentNum in the ap_invoice_lines_interface table.
3. Payables OPen interface worked fine
scenario 2:
1. Against the same PO having split, created an invoice for the line item, this time I added a freight on to it.
2. Concurrent failed(i.e it didnt throw any error to the ap rejections table),
3. so i populated po_distribution_num to the ITEM line, and ran the concurrent again. It processed the invoice successfully.
I've following queries:
1. In the 1st scenario, without populating po_dist_num to the lines table, conc. processed the invoice successfully
2. In the 2nd, only after populating the po_dist_num, the conc. processed it successfully
3. In what scenario/test case, does the payables open interface expects po_dist_num?
Please advise.
Rgds,
Sen -
Failover cluster fails validation after a single node restart
I had a lab environment setup that works great, passes validation, can do live migrations without issue but as soon as I restarted one of the nodes, the then still live node became the only node able to access the storage backend. What's weird is that the restarted
node can still access the CSV storage and run VMs off of it, but the validation report is unable to list the actual disks.
My Cluster consists of 2 nodes. I have an iSCSI backed shared storage server and I can see that both of my nodes
are connected to the iSCSI targets successfully, but the node I first restarted no longer lists any disks/volumes in disk management and the once available MPIO menus are disabled in the iSCSI control panel. I also tried to restart the second node after the
first node came back but although the first node was up and running and had VMs on it, restarting the second node brought the entire cluster down. I see event IDs 1177, 1573, and 1069 appear in the Cluster Events log. When the second node came back up, the
cluster came back with it, but not the storage. Both nodes seem to display similar behavior in that they cannot access the storage backend. Now the storage is inaccessible by both nodes. I was able to get both nodes connected to the storage backend by
going to the iscsicpl and disconnecting all current connections to the iSCSI backend and adding them back. Doing the test again after bringing the storage back up resulted in the same behavior and this time redoing the iSCSI connections is not helping.
I think the issue here is that the first node I restarted is unable to see any disks/volumes from the storage backend only after joining the cluster and doing a restart. Before joining the cluster I did reboots on both nodes and both were able to connect to
the iSCSI backend without issue. It wasn't until after joining the cluster that node 1 became unable to access the storage backend after reboots. The validation report fails with "No disks were found on which to perform cluster validation tests. To correct
this, review the following possible causes: ..." although none of the suggestions seem applicable and the validation report was successful right before the restart of the node.
Does anyone have suggestions on how to further troubleshoot or resolve this issue?
I am using Hyper-V Server 2012 R2 on both nodes and they are joined to the same domain.Hi,
I don’t found the similar issue, please your storage compatible with server 2012R2, Update Network Card Drivers and firmware on both the Nodes, temporarily disable your AV
soft and firewall install the Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters update.
The Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151/en-us
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Windows 2008 failover clustering fails with Event ID 1205 1069 1558
I have a two nodes Windows 2008 and SQL 2008 cluster running in active\passive. I was restarting
my nodes after applying windows update then I received the following error message below within Failover Cluster Manager. I get errors with Event ID 1205 1069 1558 this happens every month .. Could someone help me on to find the root cause for
this issue how to check if it is an issue with network or Quorum drive ?First, take a look at the 1069 event. This should point out which resource is failing.
Then, open a command prompt and run the command: cluster log /g
This will generate a cluster.log file that you can use to further troubleshoot this issue. The log file will be located in the C:\Windows\Cluster\Reports folder.
The cluster.log will be based on GMT time, so you may need to translate this to the local time zone in order to find the events you are looking for. Look for ERR or WARN messages and these should hopefully give you more insight as to why the resource is
failing.
Hope this helps.
Visit my blog about multi-site clustering -
SQL 2012 installation for Failover Cluster failed
While installation of SQL 2012 on FOC validation fails on "Database Engine configuration" page with following error:
The volume that contains SQL Server data directory g:\MSSQL11.MSSQLSERVER\MSSQL\DATA does not belong to the cluster group.
Want to know how does SQL installation wizard queries volumes configured with Failover Cluster. does it:
- Enumerate "Physical Disk" resources in FOC
- does it enumerate all Storage Class resources in FOC for getting the volume list
- or it depends on WMI (Win32_Volume) to get volumes ?
The wizard correctly discovers volume g:\ in its FOC group on "Cluster Resource Group" and "Cluster Disk Selection" page. but gives the error on Database configuration page.
Any help in this would be appreciated.
Thanks in advance
Rakesh
Rakesh AgrawalCan you please check if there is any disk in the cluster which is not in online state? Please run below script following the steps.
1. Save a script as "Disk.vbs" and use
use CSCRIPT to run it.
2. Syntax: CSCRIPT <Disk.vbs> <Windows Cluster Name>
< Script>
Option Explicit
Public objArgs, objCluster
Public Function Connect()
' Opens a global cluster object. Using Windows Script Host syntax,
' the cluster name or "" must be passed as the first argument.
Set objArgs = WScript.Arguments
if objArgs.Count=0 then
wscript.Echo "Usage Cscript <script file name> <Windows Cluster Name> "
WScript.Quit
end IF
Set objCluster = CreateObject("MSCluster.Cluster")
objCluster.Open objArgs(0)
End Function
Public Function Disconnect()
' Dereferences global objects. Used with Connect.
Set objCluster = Nothing
Set objArgs = Nothing
End Function
Connect
Dim objEnum
For Each objEnum in objCluster.Resources
If objEnum.ClassInfo = 1 Then
WScript.Echo ObjEnum.Name
Dim objDisk
Dim objPartition
On Error Resume Next
Set objDisk = objEnum.Disk
If Err.Number <> 0 Then
WScript.Echo "Unable to retrieve the disk: " & Err
Else
For Each objPartition in objDisk.Partitions
WScript.Echo objPartition.DeviceName
Next
End If
End If
Next
Disconnect
</Script> -
Interface Failing when ever we do maintanace!
Dear All,
We are facing a Big problem everytime in our prduction server please help!
Problem: SENDER SERVER:RFC RECEIVER SERVER: IDOC MIDDLEWARE:+XI 3.0 with latest patch+
Every week when ever we restart our Receiver Server (for maintanace)! the mssges from XI to Reciver comes as "Cancelled with Errors" and no flow occurs.!
What we do when we encounter the problem is that we just AGAIN restart both XI and Receiver Server all the time! and the problem gets rectified by its own! we are ot able to diagnose the problem exactly!
And also we know that this is not a PROPER SOLUTION (Restarting Receiver and XI) when ever this "cancelled with errors" problem occure!
Please Advice how to solve the problem without Restarting XI and Receiver everytime!
This problem occurs all the time when ever we restart Receiver Server! then again we have to restart XI for rectifing the problem!
Please Advice!
Thank's in Advance!
Edited by: senthilprakash selvaraj on Mar 7, 2008 6:36 AM
Edited by: senthilprakash selvaraj on Mar 7, 2008 6:38 AMDear Jai,
this is the error we receive in message Monitoring when ever we restart the Receiver server!
"Returning synchronous error message to calling application: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=HMFSAPPRD SYSNR=00 GWHOST=HMFSAPPRD GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner not reached (host 172.16.18.102, service sapgw00) TIME Fri Mar 07 02:15:36 2008 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8684 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10060 ERRNO TEXT WSAETIMEDOUT: Connection timed out COUNTER 9 ."
for all the interfaces for the scenario are comming as "cancelled with errors"
"we even tried reactivation Communication Channels it didn work"
but when we again restart XI System, the flow resuming successfully! but Restarting a System is not a solution na! please advice!
Maybe you are looking for
-
Cannot assign an empty string to a parameter with JDBC type VARCHAR
Hi, I am seeing the aforementioned error in the logs. I am guessing its happening whenever I am starting an agent instance in PCo. Can somebody explain whats going on? Regards, Chanti. Heres the complete detail from logs - Log Record Details Messa
-
Can I Programmatically Change the Active Group on a Hypertrend in DSC?
I would like to know how to programmatically change the active group of a hypertrend in Labview DSC. I saw a link which said it can be done in Lookout. But in the DSC module, the active group is read only. I know of a hard way to do it. I could sa
-
Hi All, Can you tell me what are the T-codes that i need to use in my P2P cycle if WM is activated. After PO i do GR, do i have to use any other transaction before or after GR if WM is activated, similarly during Goods Issue do i have to use any othe
-
I create a page about a year ago that includes an uploaded video. I now realize I've lost the original file and want to use it elsewhere. Any clues on how I can get access to the file within the wonderful world of iWeb? Thanks
-
After syncing my blackberry to my computer the contacts on my blackberry changed the information. It cut off names and put some in last names and lists by the spontaneously created last name. It looks like it does this when there is a space in the n