Linux Integration Services (LIS) version 4.0 available!

We are pleased to announce the release of Linux Integration Services (LIS) version 4.0. As part of this release we have expanded the access to Hyper-V features and performance to the latest Red Hat Enterprise
Linux, CentOS, and Oracle Linux version.
Full Announcement on the Virtualization Blog here:
http://blogs.technet.com/b/virtualization/archive/2015/05/01/linux-integration-services-4-0-announcement.aspx
Download from Microsoft Downloads Center here:
http://www.microsoft.com/en-us/download/details.aspx?id=46842
We look forward to hearing about your experiences with LIS.
Michael Kelley, Lead Program Manager, Open Source Technology Center

Ubuntu may have moved those three button as well to that control bar.

Similar Messages

  • [Forum FAQ] How to upgrade the Linux Integration Service

    Symptom
    When you move a Linux guest virtual machine from the legacy system to Windows Server 2012 R2 Hyper-V host, you may face the incompatibility issues. The most common problems are that the mouse pointer maybe a little inaccuracies, the guest VM cannot use the
    dynamic memory.
    Cause
    The cause may be that the integration service not compatible with the Windows Server 2012 R2 Hyper-V host.
    Solution
    We need to upgrade the integration service to at least version 3.5.
    In this demo, we use the CentOS 5.8_x86_x64.
    You can refer to the following steps to perform the upgrading.
    1. Before install the Integration service you can use the following command to check the version of the installed Integration service. (Figure 1)
    #su root
    #/sbin/modinfo hv_vmbus
    Figure 1: check the version of the installed Integration service
    2. Download the Integration Service 3.5 image from here.
    http://www.microsoft.com/en-us/download/details.aspx?id=41554
    3. Insert the Integration Service 3.5 image.
    a. Open Hyper-V Linux guest VM console.
    b. Click-> Media->DVD Drive-> Specific the Integration service image location, insert Disk.
    4. Mount the image.
    If automount is enable, the Integration service image will be mounted automatically. If not, please use the following command to mount the image. (Figure 2)
    #mount /dev/cdrom /media
    Figure 2: Mount the image
    After that, we can see the image content. (Figure 3)
    Figure 3: Imange content
    5. Upgrade the integration service.
    Use the following command locate to the current Linux Distribution Directory. In this example, we select the RHEL58. (Figure 4)
    #cd RHEL58
    #./upgraee.sh
    Figure 4: Locate the Linux Distribution Directory
    When you see the message, "Linux Integration Service for Hyper-V has been upgraded. Please reboot your system", it means the upgrading is finished.
    6. Reboot your Linux system. (Figure 5)
    Figure 5: Reboot the system
    7. Confirm the upgrading.
    After Linux boots up, use the following command to check if the upgrading is succeed. (Figure 6)
    #/sbin/modinfo hv_vmbus
    Figure 6: Verify the upgrading.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    May be you should write a WIKI article on same.

  • Linux Integration Service Version 3.5 installed and it shows "Network Degraded"

    In my Windows 2012 R2 , all my Linux virtual machines show "network degraded" in the Hyper-V manager.
    I installed the 3.5 version although the Fedora 20 kernel already comes with some hyper-v modules, looking to get rid of the message. I did not succeed, in fact, I am not shore if my new 3.5 modules are bring used or not.
    I type
    modinfo hv_vmbus
    filename:       /lib/modules/3.13.7-200.fc20.x86_64/kernel/drivers/hv/hv_vmbus.ko
    license:        GPL
    alias:          acpi*:VMBus:*
    alias:          acpi*:VMBUS:*
    depends:
    intree:         Y
    vermagic:       3.13.7-200.fc20.x86_64 SMP mod_unload
    signer:         Fedora kernel signing key
    sig_key:        C3:83:0B:47:32:E7:AE:9D:9E:43:FC:FB:76:F1:35:CC:8F:FF:60:9E
    sig_hashalgo:   sha256
    Can anybody tell me if I am using the latest modules, and if not, how can I make sure they do load?
    Federico
    ff

    I tried to compile Integration Services on RHEl 6.5, the latest of the 2.6 line, and compilation fails
    ./rhel6-hv-driver-install
    Building Modules
    make: Entering directory `/usr/src/kernels/2.6.32-431.11.2.el6.x86_64'
    make: Leaving directory `/usr/src/kernels/2.6.32-431.11.2.el6.x86_64'
    make: Entering directory `/usr/src/kernels/2.6.32-431.11.2.el6.x86_64'
      CC [M]  /usr/src/LIS3.5/hv-rhel6.x/hv/netvsc_drv.o
      CC [M]  /usr/src/LIS3.5/hv-rhel6.x/hv/netvsc.o
      CC [M]  /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.o
    /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.c: In function ‘rndis_filter_set_device_mac’:
    /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.c:579: error: incompatible type for argument 3 of ‘utf8s_to_utf16s’
    include/linux/nls.h:55: note: expected ‘enum utf16_endian’ but argument is of type ‘wchar_t *’
    /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.c:579: error: too few arguments to function ‘utf8s_to_utf16s’
    /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.c:584: error: incompatible type for argument 3 of ‘utf8s_to_utf16s’
    include/linux/nls.h:55: note: expected ‘enum utf16_endian’ but argument is of type ‘wchar_t *’
    /usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.c:584: error: too few arguments to function ‘utf8s_to_utf16s’
    make[1]: *** [/usr/src/LIS3.5/hv-rhel6.x/hv/rndis_filter.o] Error 1
    make: *** [_module_/usr/src/LIS3.5/hv-rhel6.x/hv] Error 2
    make: Leaving directory `/usr/src/kernels/2.6.32-431.11.2.el6.x86_64'
    Installing Modules
    cp: cannot stat `./*.ko': No such file or directory
    Can somebody help?
    ff

  • How to set up Bonding on CentOS 6.2 with Linux Integration Services 3.4

    Having a hard time setting up bonding to work on a vm running CentOS 6.2. LinuxICv34.iso is installed.  Using three network adapters.
    Prior to os install I configured the three Network Adapters with the following settings:
    ***Via Virtual Switch Manager:
    Connection Type: External Network, Allow management os to share network adapter
    VLAN ID: Unchecked
    SR-IOV: Unchecked (Unsupported on host)
    Extensions: MS NDIS Capture = Unchecked | MS Windows Filtering Platform = Checked
    ***Via VM Settings:
    For all adapters:
    VLAN ID and Bandwidth Management is unchecked.
    In Hardware Acceleration, Enable virtual machine queue is checked, Enable IPsec task offloading is checked, and maximum number is 4096. Additionally, Enable SR-IOV is unchecked.
    In Advanced Features, a Static Mac address is assigned and Enable Mac address spoofing is checked, DHCP Guard is unchecked, Router guard is unchecked, Port mirroring is None, and NIC Teaming is checked.
    Mac Address for each Adapter:
    Network Adapter 1: 00:25:0D:20:20:1A
    Network Adapter 2: 00:25:0D:20:20:1B
    Network Adapter 3: 00:25:0D:20:20:1C
    After the os and LinuxICv34.iso was installed, I set up networking access on eth0 by making the following changes:
    vi /etc/sysconfig/network-scripts/ifcfg-eth0
    DEVICE="eth0"
    HWADDR="00:25:0D:20:20:1A"
    NM_CONTROLLED="no"
    ONBOOT="yes"
    BOOTPROTO="static"
    IPADDR="10.1.1.110"
    NETMASK="255.255.255.0"
    GATEWAY="10.1.1.100"
    DNS1="10.1.1.105"
    DNS2="10.1.1.106"
    Then:
    vi /etc/sysconfig/network
    NETWORKING=yes
    HOSTNAME=MyCentOS6.MyActiveDirectoryDomain
    GATEWAY=10.1.1.100
    and finally:
    vi /etc/resolv.conf
    nameserver 10.1.1.105
    nameserver 10.1.1.106
    I entered service network restart and was able to ping google.com so I then moved on to setting up eth1, eth2, and bond0.
    DEVICE="eth1"
    HWADDR="00:25:0D:20:20:1B"
    NM_CONTROLLED="no"
    ONBOOT="yes"
    MASTER="bond0"
    SLAVE="yes"
    USERCTL="no"
    DEVICE="eth2"
    HWADDR="00:25:0D:20:20:1C"
    NM_CONTROLLED="no"
    ONBOOT="yes"
    MASTER="bond0"
    SLAVE="yes"
    USERCTL="no"
    DEVICE="bond0"
    USERCTL="no"
    BOOTPROTO="none"
    ONBOOT="yes"
    IPADDR="10.1.1.110"
    NETMASK="255.255.255.0"
    BONDING_OPTS="miimon=100 mode=balance-alb"
    TYPE="Bonding"
    I then went back into eth0 and changed it to:
    DEVICE="eth0"
    HWADDR="00:25:0D:20:20:1A"
    NM_CONTROLLED="no"
    ONBOOT="yes"
    #BOOTPROTO="static"
    #IPADDR="10.1.1.110"
    #NETMASK="255.255.255.0"
    #GATEWAY="10.1.1.100"
    #DNS1="10.1.1.105"
    #DNS2="10.1.1.106"
    MASTER="bond0"
    SLAVE="yes"
    USERCTL="no"
    Next I added file /etc/modprobe.d/bonding.conf per CentOS 6 instructions, and wrote the following line on the file:
    alias bond0 bonding
    I then entered service network restart and expected everything to work, but instead received these error messages:
    ADDRCONF(NETDEV_UP): bond0: link is not ready
    bonding: bond0: Error: dev_set_mac_address of dev eth0 failed! ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
    bonding: bond0: Error: dev_set_mac_address of dev eth1 failed! ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
    bonding: bond0: Error: dev_set_mac_address of dev eth2 failed! ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
    I have tried commenting out the mac addresses, USERCTL=no and NM_CONTROLLED=no in the ifcfg files but that hasn't helped.
    I'm running out of ideas... Can anyone give me some tips?
    Much appreciated~

    Hello ECase,
    i known my answer is probably too late but maybe it can help others who are having the same difficulties. My setup looks almost like yours and I did the same steps as you did. Unfortunately with exactly the same results.
    What helped in my case was to change the teaming mode.
    These are the modes available in CentOS:
    mode=0 (Balance-rr) –
    This mode provides load balancing and fault tolerance.
    mode=1 (active-backup) –
    This mode provides fault tolerance.
    mode=2 (balance-xor) –
    This mode provides load balancing and fault tolerance.
    mode=3 (broadcast) –
    This mode provides fault tolerance.
    mode=4 (802.3ad) –
    This mode provides load balancing and fault tolerance.
    mode=5 (balance-tlb) –
    Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.
    mode=6 (balance-alb) –
    Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.
    Mode 0 -4 worked great while mode 5 and 6 don't work at all. So if you try bonding on a CentOS guest in Hyper-V keep mode between 0 and 4
    Regards

  • Hyper-V & Linux Integeration Services

    I've been hacking for the majority of the day at getting LIS working on Arch, and any tips would be helpful.
    I'm not fantastic at working with the under belly of linux, and usually I'm dependent on forums/guides.  This one has me stumped.
    From what I can gather, LIS drivers has been included into the Linux Kernel around 2.6.35.  Arch being on 36, should then have these drivers. 
    For the most part, it seems to, as the Integrated Shutdown feature works.  However, I can't seem to get the mouse in X to work with remote desktop.  This appears to be because the system doesn't know how to recognize "Enlightened" drivers.  Therefore, I've attempted to install the LIS drivers using the package available on Microsoft's website. 
    http://www.microsoft.com/downloads/en/d … b5b9b64551
    When I go to make the drivers, a series of errors pop up  in reference to osd.c & osd.o
    So I attempted a different approach, I tried installing Xen's Satori drivers. 
    http://www.xen.org/download/satori.html
    When I go to do this, I get the error vmbus driver not installed.
    Thus, my question is two part...
    1) has anyone successfully installed LIS for Arch and gotten the "Enlightened" drivers to work
    2) (now this is where my poor understanding of linux shows) Would it be possible for me to 'inject' vmbus.ko into the kernel drivers?  If so, how would I go about doing this.
    Thanks in advance.

    I have brought this problem as far as I can, but for reference's sake, I want to document what I've done for anyone else looking to do this. 
    First I updated all of the make files and the setup script to reflect changes in the linux kernel from when Satori was originally released.  Microsoft's Linux Integrated Services placed the hyperv drivers in /kernel/drivers/vmbus/ whereas once these drivers were integrated into the kernel they are now located in /kernel/drivers/staging/hv/.  Also, the modules were named differently, for instance vmbus.ko in Satori is now hv_vmbus.ko
    ./setup.pl
        Changed line 57 to reflect the proper name of the hyperv drivers in the linux kernel. 
        From
            if (!CheckModule("vmbus.ko")) {
        To
            if (!CheckModule("hv_vmbus.ko")) {
        Changed line 67 to reflect the proper location of the hyperv drivers in the linux kernel.
        From
            my $modulepath = "/lib/modules/" . $kernel_rel . "/kernel/drivers/vmbus/" . $module;
        To
            my $modulepath = "/lib/modules/" . $kernel_rel . "/kernel/drivers/staging/hv/" . $module;
    ./dist/Makefile
        Changed line 25 to reflect the proper location of the hyperv drivers
        From
            INSTALL_DIR := /lib/modules/$(shell uname -r)/kernel/drivers/vmbus
        To
            INSTALL_DIR := /lib/modules/$(shell uname -r)/kernel/drivers/staging/hv
    ./dist/inputvsc/Makefile
        Changed line 12 to reflect the proper location of the hyperv drivers
        From
            VMBUSDIR := /lib/modules/$(shell uname -r)/kernel/drivers/vmbus
        To
            VMBUSDIR := /lib/modules/$(shell uname -r)/kernel/drivers/staging/hv
    Once these references were changed, this allowed the setup script to properly detect that the hyperv drivers were installed correctly.  The first thing the script attempts to do is build the HID driver.  With the hid drivers included with the Satori cd, this has compile errors with hid-input.c.  On a whim, I replaced hid-input.c with the file included in kernel version 2.6.36.3 which is the kernel version running on my arch VM. 
    By doing this the HID driver builds successfully, but a new error occurs.
        cp: cannot stat '/lib/modules/2.6.36-ARCH/kernel/drivers/staging/hv/Module*.symvers' No such file or directory
    To clear this warning I commented out the following lines
    ./dist/inputvsc/Makefile
    Line 40 & 41
        #cp -f $(VMBUSDIR)/Module*.symvers $(PWD)/vmbus.symvers
        #cat $(PWD)/hid.symvers $(PWD)/vmbus.symvers > $(PWD)/Modules.symvers   
    This allows the setup script to progress to installing inputvsc driver, however a new compile error occurs This new error yells about osd.c
    Like the last compile error, I attempted to fix the error by replacing the old file with the new one out of the kernel I replaced  ./dist/vmbus/osd.c with osd.c out of 2.6.36.3. This unfortunately did not fix the issue.
    At this point I am not a good enough coder to debug why the file compiling is failing.  As a side note I did all of these steps with OpenSUSE, and I was able to progress a little farther (replacing files with 2.6.34.7 rather than 2.6.34.7)  and I started to get errors involving VmbusApi.H in reference to inputvsc_drv.c
    Since inputvsc_drv.c is not apart of the kernel and was written by Citrix, there was no newer file to replace it with, and once again I gave up due to being unable to troubleshoot complex compiling issues.
    I did some googling to see if the inputvsc driver is going to get included with the kernel at any point but couldn't find any information.  I guess at this point I'll just run arch on virtualbox and be happy with it.

  • SQL Server Integration Services 11.0 not showing

    To whom it may concern,
    I have been using SSIS 2008 R2 without a problem.  I then installed VS 2012 and migrated my SSIS packages from VS 2010 to VS 2012.  I also installed the BI Components (SSDTBI_VS2012_x86_ENU) in VS 2012,
    All the SSIS packages runs fine within VS 2012.  As soon as I run the packages from the command line (i.e. "C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe") the packages referencing any lookup objects provides the following
    error: 
    Error: 2014-04-21 13:20:15.85
    Code: 0xC000F427
    Source: Update Category SSIS.Pipeline
    Description: To run a SSIS package outside of SQL Server Data Tools you must install Derived Column of Integration Services or higher.
    End Error
    Error: 2014-04-21 13:20:15.85
    Code: 0xC000F427
    Source: Update Category SSIS.Pipeline
    Description: To run a SSIS package outside of SQL Server Data Tools you must install Lookup [Table Name] of Integration Services or higher.
    End Error
    I checked my services on my Local machine and the following integration service is the only one available:
    SQL Server Integration Service 10.0 (i.e. SQL Server Integration Service 11.0 is missing)
    I presume this is the problem.  
    I will appreciate it if someone can assist with this problem.  I have also tried to repair MS-SQL 2012 (Express Version) to no avail (Shared Features).
    Kind Regards,

    Hi, I am running SSIS on a Local Dev Machine and I am trying to execute the packages via the "C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe" Command Line It look as though I need to remove my previous version of SSIS and then install the
    2012 SSIS.
    I have also downloaded the extend MS SQL 2012 Express Version (1.9 GB), but still no no avail.  It therefore seems to be related to the previous version of SSIS that I possibly need to remove and then try to reinstall SSIS for 2012.
    I will revert back as soon as I have done these tests.
    As I said before, the Express version doesn't have SSIS.
    MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

  • Integrations services error 4000 - integration services does not match the expected version

    I have a 2 node high availability cluster built on 2012r2 DataCentre. One VM continually fails to backup and gives the event log error
    "Hyper-V Volume Shadow Copy Requestor failed to connect to virtual machine 'QuadPro' because the version does not match the version expected by Hyper-V (Virtual machine ID 094B6B22-BBED-4D0B-8E47-D8D4D0D3F986). Framework version: Negotiated (0.0) -
    Expected (3.0); Message version: Negotiated (0.0) - Expected (5.0). To fix this problem, you must upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu."
    When I do the suggested action I get a message stating
    "The computer is already running the current version of integration services (version 6.3.9600.16384)".
    This VM was built through the failover management console under 2012r2. The VM in question is a 2008r2 standard server running a single database application.
    Please advise.
    Matt

    Hi,
    I have run the command using both nodes and get the following error:
    PS C:\Users\*******> Get-VMIntegrationService -ComputerName node01 -VMName quadpro
    Get-VMIntegrationService : A parameter is invalid. Hyper-V was unable to find a virtual machine with name quadpro.
    At line:1 char:1
    + Get-VMIntegrationService -ComputerName node01 -VMName quadpro
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (quadpro:String) [Get-VMIntegrationService], VirtualizationInvalidArgum
       entException
        + FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.GetVMIntegrationServiceCommand
    However I tried one of the other VMs for testing purposes (and to check syntax etc) and got the following success message.
    PS C:\Users\******> Get-VMIntegrationService -ComputerName node02 -VMName appserver01
    VMName      Name                    Enabled PrimaryStatusDescription SecondaryStatusDescription
    Appserver01 Time Synchronization    True    OK
    Appserver01 Heartbeat               True    OK                      
    OK
    Appserver01 Key-Value Pair Exchange True    OK
    Appserver01 Shutdown                True    OK
    Appserver01 VSS                     True    OK
    Appserver01 Guest Service Interface False   OK

  • Current version of integration services on Hyper V host and ugrading versions on VM's

    Greetings!
    I am looking for where the latest version number of integration services is posted, so I may verify what it should be. I am able to query using powershell the vm's on the hosts and get a return of the current version installed. However, I seem to be
    unable to find out the current version of IS on the hosts themselves. How do I get this information?

    With all current releases of Hyper-V:
    When you patch your Hyper-V Server and reboot, the vmguest.iso is generated dynamically to match the release of the Hyper-V Server.
    This is historic and was designed to ensure compatibility of the ICs in the VM with the Services of the host.
    That said, only Hyper-V 2012 R2 can give you the 'latest' integration components, but they might not function well if VMs are moved to older versions of Hyper-V.  That is why 2012 R2 in a VM is 'not supported' on Hyper-V 2008 R2 or 2008 (for example).
    In the future Integration Components will be through Windows Update (if your Hyper-V Server is 'Windows 10" or later):
    http://blogs.technet.com/b/virtualization/archive/2014/11/11/hyper-v-integration-components-are-available-through-windows-update.aspx
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • SSIS 2012 Error - The SQL Server specified in Integration Services service configuration is not present or is not available..

    hi Guys,
     working on below error if anyone has work around. 
    It is on SQL Server 2012 cluster. 
    The SQL Server specified in Integration Services service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring
    the Integration Services Service" in SQL Server 2012 Books Online.
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

    Hi Logicinisde,
    This issue might be caused that we install named instance on the machine, or the default instance listening a different port rather than the default one.
    To solve this issue, please refer to the following article for detail information:
    http://blog.sql-assistance.com/index.php/there-is-no-default-instance
    Regards,
    Elvis Long
    TechNet Community Support

  • ASR (Auto Service Request) version 3.1 now available

    ASR (Auto Service Request) version 3.1 has been released to production.
    You can access the ASR 3.1 download and documentation via the link at the bottom of http://oracle.com/asr.
    Changes in ASR 3.1:
    ASR Manager installable on any Solaris 10 or OEL (Oracle Enterprise Linux) operating environment
    Supports the ability to install the ASR Manager on a non-qualified, non-entitled server. This means the ASR Manager can be installed in a Solaris local zone or LDOM, in virtual environments such as VirtualBox and VMWare, and on M-Series domains and Blade servers.
    Changes in the customer email notifications.
    The updated user documentation includes examples of the new email messages.
    Our customers and Partners are advised to use My Oracle Support to manage their ASR assets, as well as the ASR Manager "list_asset" command.
    The "asr report" command is now disabled.
    See the "What's new" section of Installation and Operations guide for more info on ASR 3.1 changes.
    Note that the ASR download is now hosted by My Oracle Support and is no longer on the Sun Download Center.
    Best Regards,
    Wayne Seltzer
    ASR Product Manager
    Oracle Global Customer Services

    Hi
    I have wls 10.3.1 installed on my local machine. I installed it as part of configuring FMW 11g. I am trying to add
    OSB component to it by running : osb1031_wls103_win32.exe.
    But I am receiving the following error message:
    The product maintenance level of the current installer ( wls 10.3.0.0) is not compatible with the maintenace
    level of the product installed on your system (wls 10.3.1.0). Please obtain a compatibile installer or perform
    maintenance on your current system to achieve the desired level.
    So my guess from the above message is that "osb1031_wls103_win32.exe" is for wls 10.3 and not for wls 10.3.1.
    Where can I get the OSB installer for wls 10.3.1? or how can I fix the above error?

  • SQL Server 2005 Dev Integration Services Fail

    I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box.  I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box.  So far I've
    not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
    Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box?  Worked great on my XP box.
    I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
    TIA
    Harry

    Thanks Alberto
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Professional Service Pack 1 (Build 7601)
    Time            : Mon Aug 25 09:31:30 2014
    DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features.  Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
    install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
    Server in Books Online.
    DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
    Machine         : DT0315
    Product         : Microsoft VSS Writer for SQL Server 2012
    Product Version : 11.0.2100.60
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
    Machine         : DT0315
    Product         : Integration Services
    Error           : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
    Error message: Unknown error 0x80131501
    Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
    32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Integration Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Failed
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
    Last Action     : InstallFinalize
    Error String    : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
    Error message: Unknown error 0x80131501
    Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
    32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
    Error Number    : 29549
    Machine         : DT0315
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
    Machine         : DT0315
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Analysis Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Notification Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Tools (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
     SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

  • CentOS based linux VM running on Hyper-v : Checking root filesystem fails when kernel switches having old PV(para virtualised driver based on 2.6.32 linux kernel) to new PV(which is equivalent to linux integration component 3.4)

    hi all,
    I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support
    Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i
    am hitting following filesystem check error messages :
    Setting hostname hostname:
    Checking root filesystem
    fsck.ext3/dev/hda2:
    The superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2
    filesystem(and not swap or ufs or something else),then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    : No such file or directory while trying to open /dev/hda2
    *** An error occurred during the filesystem check.
    *** Dropping you to a shell; the system will reboot
    *** When you leave the shell.
    Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :
    (Repair filesytem) 1 # mount
    /dev/hda2 on / type ext3 (rw)
    proc on /proc type proc (rw)
    (Repair filesystem) 1# cat /etc/mtab
    /dev/hda2 /ext3 rw 0 0
    proc /proc proc rw 0 0
    (Repair filesystem) 1# df
    Filesystem 1K-blocks used Available Use% Mountedon
    /dev/hda2 4%
    I think for all above command there should be /dev/sda2 instead of /dev/hda2.
    Also my fstab , and fdisk -l looks like ok for me.
    (Repair filesystem) 1# cat /etc/fstab
    LABEL=/ / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    LABEL=swap-xvda3 swap swap defults 0 0
    (Repair filesystem) 1# fdisk -l
    Device Boot Start End Block Id System
    /dev/sda1 * 1 49 98535 83 Linux
    Partition 1 does not end with cylinder boundary.
    /dev/sda2 49 19197 39062500 83 Linux
    Partition 2 does not end with cylinder boundary.
    /dev/sda3 ......
    Partition 3 does not ......
    /dev/sda4 ......
    Partition 4 does not end ....
    (Repair filesystem) 1# e2label /dev/sda1
    /boot
    (Repair filesystem) 1# e2label /dev/sda2
    (Repair fielsystem) 1# ls /dev/sd*
    /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
    (Repair filesyatem) 1# ls /dev/hd*
    ls: /dev/hd*: No such file or directory
    Kindly suggest any configuration of windows server or kernel configs missing or how to resolve this issues
    Many many thanks for your reply.
    thanks & Regards,
    Ujjwal

    i am not able to understand duplicate UUID and from where it is picking /dev/hda* ?
    ~
    VVM:>>
    VVM:>> Output of dmesg | grep ata contain substring "Hyper-V" ?
    VVM:>>
    it doesn't contain "Hyper-V" or ata related message and the output doesn't change with boot parameter reserve=0x1f0, 0x8
    ~~
    ~~~~
    ==
     output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8)
    ==
     see later ( in "good situation" example  )
    ~~
    ===
    Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst:
    reserve=0x1f0, 0x8
    . (This option reserves this I/O region and prevents ata_piix from loading).
    ==
     See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8) :
    ~~
    [ 0.176027] 
    libata version 3.00 loaded.
    [ 0.713319] 
    ata_piix 0000:00:07.1: version 2.13
    [ 0.713397] 
    ata_piix 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
    [ 0.713404] 
    ata_piix: probe of 0000:00:07.1 failed with error -22
    [ 0.713474] 
    pata_acpi 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
    [ 0.713479] 
    pata_acpi: probe of 0000:00:07.1 failed with error -22
    ~~
      As result: 1) IDE disk handled by hv_storvsc , but 2) no CD-ROM device
    ==
    ~ # blkid
    /dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
    ==
    ~~
    VVM>>
    VVM>>Q1: Output of blkid contain duplicate UUID ?
    VVM>>
    -> blkid contains duplicate UUID, below are the output.
    ~~
     This situation is classic problem "
    use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the DVD-ROM / CD-ROM device handling)
    ~~
     For compare, see example "good situation": 
     See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( without boot parameter reserve=0x1f0, 0x8) :
    ~~~~
    ~ # dmesg |grep ata
    [ 0.167224] libata version 3.00 loaded.
    [ 0.703109] ata_piix 0000:00:07.1: version 2.13
    [ 0.703267] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
    [ 0.703339] ata_piix 0000:00:07.1: setting latency timer to 64
    [ 0.704968] scsi0 : ata_piix
    [ 0.705713] scsi1 : ata_piix
    [ 0.706191] atal: PATA max UDMA/33 cmd 0xlf0 ctl 0x3f6 bmdma 0xffa0 irq 14
    [ 0.706194] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
    [ 0.868844] atal.00: host indicates ignore ATA devices, ignored
    [ 0.869142] ata2.00: ATAPI: Virtual CD, , max MWDMA2
    [ 0.871736] ata2.00: configured for MWDMA2
    ~~~~
    ===
    ~ # uname -a
    Linux ubuntu 3.7.0-7-generic #15-Ubuntu SUP Sat Dec 15 14:13:08 UTC 2012 x86_64 GNU/Linux
    ~ # lsmod
    hv_netvsc 22769 0
    hv_storvsc 17496 3
    hv_utils 13569 0
    hv_vmbus 34432 3 hv_netvsc,hv_storvsc,hv_utils
    ~ # blkid
    /dev/sr0: LABEL=”CDROM" TYPE="iso9660”
    /dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
    ===
     ( only CD-ROM and 1( one) IDE disk connected to ATA)
    ~~
    regarding ata_piix.c patch . . .
    As far as i understand this patch , it ignore ATA devices on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
    ~~
     Yes:
    ignore ATA-HDD ( but not ignore ATA CD-ROM )  on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
    ~
     this patches need be backported:
      cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
    and its prerequisite
      db63a4c8115a libata: add a host flag to ignore detected ATA devices
    ~
    ~~
    P.S.
     Are You do this:
    ==
    As temporary solution, increase on 1-2 Gb size all .vhd connected to IDE bus
    ( but not increase size of partitions inside disks)
    ==
    ? fsck write message a-la: "no error in file system" ?
    2013-01-24 Answer by Ujjwal Kumar: As a temporary solution looks ok for me, but [ VVM: need true solution ]
    P.P.S.
    To Ujjwal Kumar :
     My e-mail:
    ZZZZZZZZZZZZZZZ
    please send e-mail to me,  in reply I send to You patches to ata_piix ( and *.c before and after patches) , etc.
    } on 2013-01-14 -- DoNe

  • ETL Failure - Integration Service Error

    Hi all,
    Wondering if anyone has seen this error before.
    ETL failed with this error message:
    ERROR: Workflow custom workflow  has not run on this Integration
    Service before.
    Nothing has changed with this workflow which has been running without error.  We only have one integration service.
    Thanks for reading.

    2013-07-12 04:10:06.14 INFORMATICA TASK:ABC_Custom_SIL:ABC_SIL_Special_Programs:(Source
    : FULL Target : FULL) has started.
    ANOMALY INFO::: Error while executing : INFORMATICA TASK:ABC_Custom_SIL:ABC_SIL_Special_Programs:(Source
    : FULL Target : FULL)
    MESSAGE:::
    Irrecoverable Error
    Error while contacting Informatica server for getting workflow status for ABC_SIL_Special_Programs
    Error Code = 3:An error occurred in starting or running or stopping the
    workflow or task.
    Pmcmd output :
    =====================================
    STD OUTPUT
    =====================================
    Informatica(r) PMCMD, version [9.1.0 HotFix2], build [357.0902], LINUX 64-bit
    Copyright (c) Informatica Corporation 1994 - 2011
    All Rights Reserved.
    Invoked at Fri Jul 12 04:10:28 2013
    Connected to Integration Service: [INT_PROD].
    ERROR: Workflow [ABC_SIL_Special_Programs] has not run on this Integration
    Service before.
    Disconnecting from Integration Service
    Completed at Fri Jul 12 04:10:29 2013
    =====================================
    ERROR OUTPUT
    =====================================
    Re-Queue to attempt to run again or attach to running workflow
    if Execution Plan is still running or re-submit Execution Plan to execute the
    workflow.
    EXCEPTION CLASS::: com.siebel.analytics.etl.etltask.IrrecoverableException
    com.siebel.analytics.etl.etltask.InformaticaTask.doExecute(InformaticaTask.java:183)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.doExecuteWithRetries(GenericTaskImpl.java:411)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.execute(GenericTaskImpl.java:307)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.execute(GenericTaskImpl.java:214)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.run(GenericTaskImpl.java:586)
    com.siebel.analytics.etl.taskmanager.XCallable.call(XCallable.java:63)
    java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    java.util.concurrent.FutureTask.run(FutureTask.java:138)
    java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    java.util.concurrent.FutureTask.run(FutureTask.java:138)
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    java.lang.Thread.run(Thread.java:662)
    (Number of retries : 1)
    pmcmd startworkflow -sv INT_PROD -d Domain_lx-xxxxx-p02p -u Administrator -p
    **** -f ABC_Custom_SIL -paramfile
    /opt/hrinfo/informatica/powercenter9.1/server/infa_shared/SrcFiles//DataWarehouse.DataWarehouse.ABC_Custom_SIL.ABC_SIL_Special_Programs.txt
    ABC_SIL_Special_Programs
    2013-07-12 04:10:29.207 INFORMATICA TASK:ABC_Custom_SIL:ABC_SIL_Special_Programs:(Source
    : FULL Target : FULL) has finished execution with Failed status.

  • Integration Services Fails to Update - Error Code: 1783

    Hi All,
      I moved a 2008R2 VM guest from a 2008R2 host to a 2012R2 host.  Two other VM guests that I moved went without an issue.
       When attempting to install the updated Integration Services for the third it errors...
    Upgrade Hyper-V Integrations Services
    A previous installation of Hyper-V integration services has been detected (version 6.1.7601.17514).  Click Ok to upgrade this installation.
    [I press OK]
    During the process it makes it to: Installing Guest Components....then
    An error has occured:  One of the update processes returned error code: 1783
    Any ideas how to resolve?

    Hi Kisner,
    "The KB 3004394 update that was dated December 10, 2014 can cause additional problems on computers that are running Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1. This includes the inability to install future updates. This new update
    is available to remove KB 3004394 from your computer."
    http://support.microsoft.com/kb/3024777
    I would like to check the current state of this issue .
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .
    Thanks for the direct link Elton - that resolved the issue and I could install Integration Services without issue.
    Thanks to you too Mark.

  • Register Integration service in DAC.

    Hi all,
    I am getting this message while trying to register the Informatica Integration Service in DAC. On the other hand the repository server registration is succcesful in DAC. I have the INFA_DOMAINS_FILE,INFA_HOME environmnet variables set already and the INTEGRATION and REPOSITORY services are up and running. I have added the Informatica/server/bin path to the PATH variables too.
    I have entered the relational connection in workflow manager and assigned the integration services to workflows also. I have checked the port, Integration service seems t to be running on 4006 port. Can any one help please..
    Failure connecting to "INFORMATICA_DW_SERVER"!
    =====================================
    STD OUTPUT
    =====================================
    Informatica(r) PMCMD, version [8.6.1 HotFix6], build [319.0622], LINUX 64-bit
    Copyright (c) Informatica Corporation 1994 - 2009
    All Rights Reserved.
    Invoked at Thu Dec 17 18:12:44 2009
    The command: [pingserver] is deprecated. Please use the command [pingservice] in the future.
    WARNING: Lost server connection.
    ERROR: Cannot connect to Integration Service [Integration:4006].
    Completed at Thu Dec 17 18:12:44 2009
    =====================================
    ERROR OUTPUT
    =====================================

    hello any news about the solution to this issue?? I would appreciate sharing the solution just in case it has been resolved.
    Regards to you all..

Maybe you are looking for