Failed:Error disabled - SFP vendor not supported on Fabric Interconnect 6248UP

We are connecting a FC-uplink on a Fabric Interconnect 6248UP to a MDS9124. On the Fabric Interconnect side we use a 8Gbps SFP (DSpSFP-FC8G-SW) on the MDS9124 side there is a 4 Gbps SFP.This should work when speed is at fixed speed 4 Gbps on both sides (I was told). When the SFP's and cabling is connected I get an error in the UCS manager on the FC-uplink port we are using:
Failed:Error disabled - SFP vendor not supported.
I cannot change the speed on the FC-Uplink ( I can only set user-label). The Fabric Interconnect is configured for FC on the last 8 ports and that is where the SFP for the storage is located (port 31).

I have a similar problem.  I'm using port 1/41 and gets this output
show system firmware expand | head lines 10
UCSM:
   Running-Vers: 2.1(3a)
   Package-Vers: 2.1(3a)A
   Activate-Status: Ready
Catalog:
   Running-Vers: 2.1(3a)T
   Package-Vers: 2.1(3a)A
   Activate-Status: Ready
sh interface fc 1/41
fc1/41 is down (Error disabled - SFP vendor not supported)
   Hardware is Fibre Channel, SFP is Unknown(0)
   Port WWN is 20:29:00:2a:6a:7e:7b:00
   Admin port mode is F, trunk mode is off
   snmp link state traps are enabled
   Port vsan is 1
   Receive data field Size is 2112
   Beacon is turned off
   1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
   1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
     0 frames input, 0 bytes
       0 discards, 0 errors
       0 CRC, 0 unknown class
       0 too long, 0 too short
     0 frames output, 0 bytes
       0 discards, 0 errors
     0 input OLS, 0 LRR, 0 NOS, 0 loop inits
     0 output OLS, 0 LRR, 0 NOS, 0 loop inits
   last clearing of "show interface" counters never
show int fc 1/41 transceiver details
fc1/41 sfp is present but not supported
   name is CISCO-FINISAR  
   part number is FTLX8571D3BCL-C2
   revision is A  
   serial number is FNS17401NYG    
   FC Transmitter type is Unknown(0)
   FC Transmitter supports Unknown(0) link length
   Transmission medium is Unknown(0)
   Supported speeds are - Min speed: -1 Mb/s, Max speed: -1 Mb/s
   Nominal bit rate is 10300 MBits/sec
   Link length supported for 50/125mm fiber is 80 m(s)
   Link length supported for 62.5/125mm fiber is 20 m(s)
   No tx fault, no rx loss, no sync exists, diagnostic monitoring type is 0x68
   SFP Diagnostics Information:
                                     Alarms                 Warnings
Is this a firmware problem?

Similar Messages

  • Extend volume - Storage Pools - iSCSI - "Extend failed" // "Error extending volume: Size Not Supported"

    Hi,
    I've created a storage pools of 44x 1TB SAS, my storage pool name is "DAS" with 39.1TB (35.8 TB Free Space)
    I have a virtual disk named "iSCSI_DFS", Simple, Thin, 20TB with 3.05 TB Allocated
    I've created volumes on that disk, NTFS, Thin, Different size.
    I create iSCSI VIRTUAL DISKS on those Volumes, same size (my volumes are full)
    I want to "extend" my volumes size... I click on my volume, Extend Volume, enter a new size (current is 162GB so I enter 200 and select GB) and click OK
    The Volume status turn to "Extend failed" with "Error extending volume: Size Not Supported"
    Can you help? I need to change my volumes size...
    Thx

    I also could not get my partition to extend using the new Windows Server 2012 interface.  Did you try to extend volume from the "computer management", "disk management" console?  Get there from Administrator Tools - Computer Management.  I
    was able to extend my partition only from there.  You need to first make sure you have available space on the disk.  I had to delete an empty volume first before I was able to extend the partition.  Hope this helps.   Anthony :)
    Thx !! 
    While in the Computer Management, I realised that my Disk was "Basic" and not "Dynamics", Extending using the Disk Management suggest to switch to Dynamics, and it's now working.
    The error in the Server Manager should be "Unable to Extend : Your disk is Basic" or something like.
    The Disk is a virtual disk on my Storage Pools.!!!

  • Failed to Save Document. and Not Supported. Error Message

    Post Author: dscoiho
    CA Forum: General
    I am using Crystal 10 and SQL Server. I have ran into instances when I try to save a report with data or save as I get Failed to Save Document. and Not Supported. error messages. Does anyone have a clue on why this would be happening and is there a work around.

    Post Author: rhartness
    CA Forum: General
    Has anyone found the answer to this problem?  I am experiencing the exact same issue today.  This is quite frustrating!  If anyone has a clue on how to fix this or how to prevent it from happening again please post a reply.
    I'd hate to lose all of my work over the past hour (I couldn't imagine of loosing a days worth of work like the original poster stated) but if there is no fix, I understand.  However, is there something that I could have done to cause this?  If so, I want to avoid doing it in the future.
    Thanks guys.

  • JVM Vendor not supported error in NWDS.

    I installed the NWDS 7.3 for customizing my portal 7.3 logon page. I am following an interesting blog for the same: Getting started with Netweaver 7.3 portal Part 2 - NWDS and Logon Page
    However I am yet to complete this task successfully due to a JVM vendor not supported error. I have a JAVA_HOME entry to the javaw.exe path. Also, i have vm entry of the same path in the NWDS shortcut- properties- target value. C:Program Files (x86)Javajdk1.7.0_02 in
    I chose program files (x86) for this installation bcos during my previous java error i read in my log that JVM 64 bit could not be run.
    Initially i use to get JVM error during startup itself bcos of which i was not able to get to the home page of developer studio. I solved that error now by installing right version and making necessary entries as mentioned above. Now i get a pop up stating that oracle vendor is not supported (it says that i should have either a Sun or SAP provided java). Is it really the problem? If so, can some 1 get me the link to download it.
    I am creating a new thread since the old ones posted by others on the same topic does not give me the solution.
    Thanks in advance

    Hi,
    I also come to this warning. I did a little research, and found solution that worked for me by solving source of problem, without need of trying different JDK versions.
    My current configuration:
    SAP NWDS:
         - v7.30 EHP1 (7.31) SP10 PAT0001 (8.31.100001.140103092401 SP10 PAT0001)
         - file: "nwds-extsoa-7.3-EHP1-SP10-PAT0001-win32.zip"
         - Download location: https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/731/doc/auto_latest_distributions.html
    JDK:
         - v7 Update 51 - both x86 and x64 versions. As NWDS is x86 version, that platfotm is enought if you don't need native support for x64 applications.
         - Latest version download location: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
         - Older versions download location: http://www.oracle.com/technetwork/java/javase/archive-139210.html
         - I'm not suggesting that you need to install last version. I tested it on this version and it worked for me, but I use NWDS only for few specific tasks. So I did't test all functions for JVM compatibility. But my solution should work for solving cause of vendor specific problem. Not other JVM problems. And installing newer Java may be source of other problems, like is every release. But with correct backup there shouldn't be a problem.
    Problem:
    Problem is in older code of initial JVM check, where are specified allowed vendors. Oracle is not included in configuration, so warning is shown. Module is located in plugins folder:
         "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
    Version number (orange) can differs based on NWDS distribution. In jar file is configuration stored in file "config.xml". There is this part, that specifies allowed vendors:
    <supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
          <vendor name="SAP AG">
              <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
          </vendor>
          <vendor name="Sun Microsystems Inc.">
              <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
          </vendor>
      </supportedRuntimes
    Here you can see that only "SAP AG" and "Sun Microsystems Inc." from older Java releases are included. And that's the problem, as new versions are released by Oracle. So vendor differs and warning is here.
    Solution:
    Before we begin it's best to backup whole NWDS directory and also workspace(s)!
    1) Locate file with JVM checking module:
         "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
        As mentioned before, version number can be different in your release.
    2) Create backup copy of current file. Call it for example "com.sap.ide.jvm.check_1.0.0.140103091951.jar.BAK".
    3) Copy original file to temporary location. I used "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
    4) Extract files from JAR. JAR files are basically ZIP files. I used 7-zip program to extract source to folder based on file name:
    "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\".
    5) Locate and edit configuration file "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\config.xml". Add vendor node "Oracle Corporation" (part in green color). Just copy existing node and replace vendor name.
    <supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
        <vendor name="SAP AG">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
        <vendor name="Sun Microsystems Inc.">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
        <vendor name="Oracle Corporation">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
    </supportedRuntimes>
    6) Pack directory. Pack whole content of directory from step 5) back to ZIP format. Change extension to .JAR in your favorite compression program, or rename new file from ".zip" to ".jar" after compression is done. Now we have our new corrected file for checking JVM version in NWDS - "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar".
    7) Replace original file. Copy file over original one:
    "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar" -->
    "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar". Overwrite if asked.
    8) Done.

  • "error: thread-local storage not supported for this target"

    I have a program that uses the __thread specifier, to be run on a Solaris 9/UltraSprac.
    I am not able to compile it using gcc 3.4.4 or 4.0.4, it emits the msg "error: thread-local storage not supported for this target".
    xz@gamera% gcc -v -Wall -D_REENTRANT -c -o func_stack.o func_stack.c
    Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
    Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
    Thread model: posix
    gcc version 3.4.4
    /opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v7 -auxbase-strip func_stack.o -Wall -version -o /var/tmp//cc0poHSN.s
    ignoring nonexistent directory "/usr/local/include"
    ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
    #include "..." search starts here:
    #include <...> search starts here:
    /opt/gcc/3.4.4/include
    /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
    /usr/include
    End of search list.
    GNU C version 3.4.4 (sparc-sun-solaris2.8)
            compiled by GNU C version 3.4.4.
    GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
    func_stack.c:16: error: thread-local storage not supported for this target
    func_stack.c:17: error: thread-local storage not supported for this target
    func_stack.c:19: error: thread-local storage not supported for this target
    xs@gamera% gcc -v -D_REENTRANT  -c -o func_stack.o func_stack.c
    Using built-in specs.
    Target: sparc-sun-solaris2.9
    Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
    Thread model: posix
    gcc version 4.0.4 (gccfss)
    /pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -I. -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v9 -auxbase-strip func_stack.o -version -m32 -o /tmp/ccjsdswh.s -r /tmp/cc2w4ZRo.ir
    ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
    ignoring nonexistent directory "/usr/local/include"
    ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
    ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
    #include "..." search starts here:
    #include <...> search starts here:
    /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
    /usr/sfw/include
    /usr/include
    End of search list.
    GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
            compiled by GNU C version 4.0.4 (gccfss).
    GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
    func_stack.c:16: error: thread-local storage not supported for this target
    func_stack.c:17: error: thread-local storage not supported for this target
    func_stack.c:19: error: thread-local storage not supported for this targetJust as comparison, the corresponding output of compiling another file which does not have __thread declaration is as follows:
    xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
    Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
    Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
    Thread model: posix
    gcc version 3.4.4
    /opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v7 -auxbase-strip common.o -Wall -version -o /var/tmp//cc4VxrLz.s
    ignoring nonexistent directory "/usr/local/include"
    ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
    #include "..." search starts here:
    #include <...> search starts here:
    /opt/gcc/3.4.4/include
    /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
    /usr/include
    End of search list.
    GNU C version 3.4.4 (sparc-sun-solaris2.8)
            compiled by GNU C version 3.4.4.
    GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
    /usr/ccs/bin/as -V -Qy -s -xarch=v8 -o common.o /var/tmp//cc4VxrLz.s
    /usr/ccs/bin/as: Sun WorkShop 6 update 2 Compiler Common 6.2 Solaris_9_CBE 2001/04/02Note that the last 2 lines seem to suggest that a Sun assembler is used as the back-end of gcc. I am not sure whether the failure to compile the first file (with __thread) was due to the incompatibility of this Sun assembler. In the first case, the error msg was emitted before these 2 lines are printed.
    I further read a post about gcc 3.3.3's inability to compile code that has __thread in it, on a HP-UX 11.11: http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1216595175060+28353475&threadId=1148976 The conclusion seems to suggest that "the 2.17 GNU assembler did not support thread local storage" and gcc sees that and thus disallows TLS.
    If the assembler is the culprit, then does anyone know whether this "Sun WorkShop 6 update 2" assembler in my installation can work with TLS? And how come a Sun assembler becomes the back-end of gcc? I read that gas (the GNU assembler) is the default backend of gcc. (How) can one specify the assembler to be used for gcc?
    As an aside, I am able to compile my file on this same Solaris 9/UltraSparc platform using the Sun Studio 12 C Compiler:
    xz@gamera% cc -V -# -D_REENTRANT  -c -o func_stack.o func_stack.c
    cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12
    ### Note: NLSPATH = /pkg/SUNWspro/12/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/pkg/SUNWspro/12/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
    ###     command line files and options (expanded):
    ### -c -D_REENTRANT  -V func_stack.c -o func_stack.o
    /pkg/SUNWspro/12/prod/bin/acomp -xldscope=global -i func_stack.c -y-fbe -y/pkg/SUNWspro/12/prod/bin/fbe -y-xarch=generic -y-xmemalign=8i -y-o -yfunc_stack.o -y-verbose -y-xthreadvar=no%dynamic -y-comdat -xdbggen=no%stabs+dwarf2+usedonly -V -D_REENTRANT  -m32 -fparam_ir -Qy -D__SunOS_5_9 -D__SUNPRO_C=0x590 -D__SVR4 -D__sun -D__SunOS -D__unix -D__sparc -D__BUILTIN_VA_ARG_INCR -D__C99FEATURES__ -Xa -D__PRAGMA_REDEFINE_EXTNAME -Dunix -Dsun -Dsparc -D__RESTRICT -xc99=%all,no%lib -D__FLT_EVAL_METHOD__=0 -I/pkg/SUNWspro/12/prod/include/cc "-g/pkg/SUNWspro/12/prod/bin/cc -V -D_REENTRANT  -c -o func_stack.o " -fsimple=0 -D__SUN_PREFETCH -destination_ir=yabe
    acomp: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12Interestingly, the output no longer mentions the "/usr/ccs/bin/as: Sun WorkShop 6 update 2" assembler.

    Just as another comparison, I compiled a file without __thread on the Solaris 9/UltraSparc platform using gcc 4.0.4. Not surprisingly it worked. But I no longer see the mention of the Sun assembler as in the case of gcc 3.4.4. Nor did I see the mention of "GNU assembler" as in the case of gcc 4.0.4/Solaris 10/x86. Instead, I saw something called "iropt" and "cg". Does anyone know what they are?
    xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
    Using built-in specs.
    Target: sparc-sun-solaris2.9
    Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
    Thread model: posix
    gcc version 4.0.4 (gccfss)
    /pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v9 -auxbase-strip common.o -Wall -version -m32 -o /tmp/ccSGJIDD.s -r /tmp/ccKuJz76.ir
    ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
    ignoring nonexistent directory "/usr/local/include"
    ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
    ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
    #include "..." search starts here:
    #include <...> search starts here:
    /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
    /usr/sfw/include
    /usr/include
    End of search list.
    GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
            compiled by GNU C version 4.0.4 (gccfss).
    GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
    /pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/iropt -F -xarch=v8plus -xchip=generic -O1 -xvector=no -xbuiltin=%none -xcache=generic -Qy -h_gcc -o /tmp/ccUl4mVM.ircg /tmp/ccKuJz76.ir -N/dev/null -is /tmp/ccSGJIDD.s
    /pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/cg -Qy -xarch=v8plus -xchip=generic -OO0 -T3 -Qiselect-C0 -Qrm:newregman:coalescing=0 -xcode=abs32 -xcache=generic -xmemalign=8i -il /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4//gccbuiltins.il -xvector=no -xthreadvar=no%dynamic -xbuiltin=%none -Qassembler-ounrefsym=0 -Qiselect-T0 -Qassembler-I -Qassembler-U -comdat -h_gcc -is /tmp/ccSGJIDD.s -ir /tmp/ccUl4mVM.ircg -oo common.o

  • Failed. Format conversion is not supported

    Hello again, this error happened when I was playing around with Creative Audio Converter
    Failed. Format conversion is not supported
    This error happened when I was converting a song from WMA Pro, 128 Kbps, 44khz, 2 Channel 24-Bit to WMA Pro, 128 Kbps, 44khz, 5.1 Channel 24-Bit
    Why is this error happening? And if the conversion is not supported, then why did Creative bother to put this format on their sound cards? Or is this another of Microsoft's problem?
    Thank You.

    Thank you very much for answering my query about that, at this moment i am very interested on 5.1 channel conversion. I have written to other ppl on other forums about 5.1 channel conversion. One person told me that there are a lot of ways to do it, depending on what kind of 5.1 upmixing do you want to perform. What kinds of upmixing do you use for 5.1 channel conversion? What do you recomend?
    Thank You very much

  • HT1476 when i plug my phone into the usb port with the apple charger that came with my phone i get an error msg say charging not supported by this device.   But when i use a gigaware (radioshack brand) usb charger, no error msg.  Why?

    when i plug my phone into the usb port with the apple charger that came with my phone i get an error msg say charging not supported by this device.   But when i use a gigaware (radioshack brand) usb charger, no error msg.  Why?

    - Try restoring the iPod, first from backup and then try to factory settings/new iPod to rule out a software problem.
    - Look at the dock connector on the iPod. Look for abnormalities like bent or corroded contacts, foreign material and broken or cracked plastic.
    - Could you have damaged something when you took the iPod apart and replaced the Home button?

  • What does the Error Message: "File format not supported" mean?

    When I first open an existing project, I get an Error Message: "File format not supported".   After a few seconds all the windows open up and I can continue to edit.  My question is will this "File format not supported" haunt me later or shall I continue to edit as I am doing? Why does this error message come up?  All the current footage is shot on same camera, the Canon 5D Mark III at 23.98 time code rate,  1920 x 1080.

    More information might help someone help you - Information FAQ http://forums.adobe.com/message/4200840
    Also, are your files on an external drive?

  • Error: "Function or method not supported." when using RF List Mode on NI 5673E

    Hi,
    I am trying to use the RF List Mode in NI RFSG 5673E. I tried running the sample code "RFSG Configuration List Frequency and Power Sweep.vi" but an error would show up:
    "Error: niRFSGCreateConfigurationList.VI <ERR> The LO reported the following error: Function or method not supported." with the error code: BFFA4239. 
    I also tried running other sample codes that contain the Configuration List VI's but the same error appeared. I am using NI RFSG 1.8.5.
    I would really appreciate any help on this. Thanks!

    Hello jdlabrador,
    I setup a 5673E here and tried to run the same example.  I did not encounter an error.
    Other reports I've found pertaining to this error usually involved a large number of steps - there was not enough space on the hardware to accommodate them.  The error text you're seeing is a little different in that it states that the Create Configuration List method isn't supported for the LO.
    Do each of the modules in your 5673E (5450, 5611, 5652) pass a self-test in MAX?  
    Have you associated the 5450 and 5652 with the 5611?
    Could you post a screenshot of the fully-expanded Devices and Interfaces tree from MAX?
    Since RFSG 1.9.5 is available, it may be a good first-step to upgrade to it.  
    Best regards,
    Matthew H.
    Applications Engineer
    National Instruments

  • SapEHP Installer - ERROR: Release '701' is not supported by this tool!

    Hi gurus, I am trying to do a EHP4 upgrade using the EHPI. I am using the latest EHPI 710. The moment i enter the KEYword and Download directory it go through and then come up with an error message "701 is not supported by this tool". Please help me solve this issue.

    Hi Ram,
    1) You are using wrong EHPI , you need to use SAP EHPI 700 version . The EHPI 710 to upgrade SAP NW 710 system to EHP1 i.e to 711
               My Company's Application Components" SAP EHP INSTALLER" SAP EHP INSTALLER 7.00
    2)  You need to generate .xml file from SAP Solution Manager by seleting required ECC usagae types. SAP EHPI will ask for .xml file in future steps.
    Regards,
    Preethish

  • ERROR: Release '640' is not supported by this tool!

    Hi,
    i'm trying to upgrade system SAP ERP 5.0 to SAP ERP 6.0 EHP 4 and i got problem with EHP installer,
    1. I readed and made all the steps as described in Upgrade guide
    2. Downloaded EHP installer version 7.00 (but when it starts shows me on screen version 7.10)
    3. Via MOPZ i took the list and XML file for the SAR files
    4. Downloaded corrections for EHP installer
    when i start EHP installer, it asks me for the code and for the download directory, i put all required and after that EHP installer works for 5-10 minutes and stops with error:
    ERROR: Release '640' is not supported by this tool!
    in VERSSTAMP file wroten:
    EHPIVersion = 2.005.001
    SAPJup = NWSL702_00
    SAPehpi = 710-1
    ostype = hp_64
    release = 702_REL
    toolrelease = 710
    date = 2010-2-4
    time = 7:35:22
    packversion = 24
    crpkversion = 1.020
    Please anyone give solution!

    i think i didn't start the master dvd ))

  • Error message airport utility not supported on this architecture

    I'm using a macbook pro with OS X v10.5.8 and trying to set up a new Time Capsule network, however I'm getting the error message "airport utility not supported on this architecture". How do I fix this so I can set up my network?

    Hmmm, that message would imply that Airport Utility is from a PPC Mac, or an older version of the OS?
    Might download & install this...
    http://support.apple.com/downloads/AirPort_Utility_5_3_2_for_Leopard
    Also see...
    http://support.apple.com/kb/HT1998

  • When trying to change ringtone I keep getting the error message file type not supported.

    I have downloaded some ringtones fro VZ Tones and when I go to make them the default it gives me the error message file type not supported.  If I go to my storage and try to look at pictures, it tells me the same thing.

        That's definitely odd CrystiDawn, and I understand it can be quite frustrating. Let's get to the bottomof this. What device make and model phone do you have? Did you receive a text message with a link to download the ringtones? If so, once downloaded, please go to all your Apps, locate "Files" and play the ringtone using the media player. You will have the option to set it as ringtone while playing and pressing the menu icon. Were the pictures taken from the phone or transferred using the USB cable?
    AdaS_VZW
    Follow us on Twitter at @VZWSupport 

  • Error "This class does not support SAAJ 1.3" in oim 11g

    hai all,
    i have error "This class does not support SAAJ 1.3" when i running create user.
    i already tried added in startWeblogic.cmd and in setDomainEnv.cmd :
    -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl and -Djavax.xml.soap.MessageFactory=com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl
    step like this site (http://blog.xebia.com/2009/07/14/jax-ws-cxf-and-saaj-on-oracle-weblogic-103/)
    i already too set path for = saaj-impl-1.3.jar but the error still same "This class does not support SAAJ 1.3"
    i used weblogic 10.3.5, i'm generate soap message used rt.jar (import javax.xml.namespace.QName; etc)
    any idea to solving this error ?
    thank's
    darvesth
    Edited by: darvesth on Mar 19, 2013 4:08 AM

    thank you darvest, i follow your step before.
    but i added any steps after that.
    1. include saaj-impl-1.13.jar and saaj-api.jar in project adapter
    2. add parameter "SOAPConstants.SOAP_1_2_PROTOCOL" in line code, MessageFactory mf= MessageFactory.newInstance()
    -> MessageFactory mf= MessageFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL);
    so, my problem already resolve..
    i hope this solution usefull to resolve our problem, darvest.
    thanks,
    Tim BENGA

  • Error -11040 Driver does not support this function- Informix SE db

    Hello,
      Weu2019re getting an error -11040 "Driver does not support this function" when trying to connect to an ODBC data source to an InformixSE database. This is with Crystal 2010 and 2008 on a Windows XP sp2 box. Weu2019re trying to use the ODBC(RDO) choice for a new connection.
      The Informix ODBC driver has been loaded. We tried 3 versions, the 2.40 and 3.70(latest) ones from IBM, and one that I believe came with Crystal (CR xxxx). I tried turning on the ODBC trace file, but it didnu2019t write anything to the log. We are supplying the same log in credentials as with Excel.
       The Informix database we use is Informix SE (Standard Engine) v5.10 on separate machine running Unix (Aix) with the Informix-Net daemon running to handle odbc connectivity. We are able to connect from Excel to the Informix database.
      I donu2019t know what ODBC function Crystal may be expecting from the driver that it doesnu2019t seem to support and how to tell Crystal to not need it.
    Thanks,
    Mike

    Hi Mike,
    According to the Platforms for DB support we only support these Informix data sources:
    IDS (Informix Dynamic Server)     11.50       32 bit       64 bit        Linux               AIX                   Solaris
    IDS          IDS Client 11.5                                     Direct     Direct     Not Supported     Not Supported     Not Supported
    ODBC      IBM Informix ODBC SDK 3.50             Direct     Direct     Direct             Direct             Direct
    ODBC      DataDirect ODBC 6.0 SP2 (10)      Direct     Direct     Direct             Direct             Direct
    You may want to try the Data Direct 6.x drivers as a test.
    CR in the .NET IDE is running under 32 bit mode so make sure you are using the 32 bit Client.
    Don

Maybe you are looking for