Forté 3.0.M Communication under HP11 &TCP_NODELAY

Hi,
does anyone know if Forté uses sockets with or without TCP_NODELAY set ?
is it something that can be configured ( at installation time ) ?
thanks.
olivier
Nota. Environment is HP11 & Forté 3.0.M
O. Brousseau
Architecture & Performance Team
Sema Group France ( DTS )

All these ports (below) are open on the VPN server but still can't transfer files via drag and drop to client Macs. It gets stuck at 0% while it tries and then fails. But I'm able to observe and control.
5900 tcp/udp
5988 tcp
3283 tcp/udp
Hmm, I found this in the Apple knowledge database:
When using VPN, you may need to set your router to allow a larger MTU and/or to disallow fragmented packets.
Maybe the above is worth a try. Anybody on the same boat?

Similar Messages

  • RE: Forté 3.0.M Communication under HP11 &TCP_NODELAY

    Hi Olivier,
    Good news for you. In Release 3.0.N Forte will allow users to configure
    TCP_NODELAY option for Forte sockets. Please see defect report 52766.
    Regards,
    Zenon Adamek
    Purolator
    -----Original Message-----
    From: Olivier Brousseau [SMTP:Olivier.Brousseausema.fr]
    Sent: Tuesday, April 11, 2000 9:28 AM
    To: kamranaminyahoo.com
    Cc: ZAdamekpurolator.com
    Subject: Forté 3.0.M Communication under HP11 & TCP_NODELAY
    Hi,
    does anyone know if Forté uses sockets with or without TCP_NODELAY set ?
    is it something that can be configured ( at installation time ) ?
    thanks.
    olivier
    Nota. Environment is HP11 & Forté 3.0.M
    O. Brousseau
    Architecture & Performance Team
    Sema Group France ( DTS )

    Did you ever resolve this issue, because I am having exactly the same issue!  Thanks!

  • Problems uninstalling Forte for java 4 community edition

    I just installed Forte for java 4 community edition at work, and when i tried to uninstalled it with add/remove programs from control panel. And the uninstall wizard start but then a Sun window apper and it is written, uninstalling and the uninstall program seems to be frozen.

    i have the same problem, reading the documentation it seems you got to run the installer again and you ll get prompted with the "file deletion confirmation"
    too bad i have a self-installing package and i don't get the prompt...
    guesses anyone?

  • Applet servlet communication under mac os x

    Hi everbody,
    I have an applet that invokes a servlet via url connection and maintain session status using cookies. Everything works fine under linux and windows but I have problems under mac ox 10.2 (with jdk1.4.1):
    I reported an EOFException reading th stream header.
    here is my code
    URLConnection connection = null;
    try{
    connection = getConnection(entity);
    ObjectOutputStream outputToHost = new ObjectOutputStream(connection.getOutputStream());
    outputToHost.writeObject(packet);
    outputToHost.flush();
    outputToHost.close();
    }catch (Exception e) {
    error_tmp = "brokensession";
    e.printStackTrace();
    if (_cookie == null) {
    _cookie = connection.getRequestProperty("set-cookie"); 
    ObjectInputStream inputFromHost = null;
    try {
    inputFromHost = new ObjectInputStream(connection.getInputStream());
    answer = (Hashtable) inputFromHost.readObject();
    if (answer.get("error") != null){
    error_tmp = (String) answer.get("error");
    status.put("nessieStatusApplet" , error_tmp);
    } catch (Exception e) {
    status.put("nessieStatusApplet" , "connection-out");
    e.printStackTrace();
    The first time I execute the servlet call it works ok, the second time the it seems that the headers are lost and I have the excpetion.
    Maybe it is something like sun jdk bug #4325987, now solved in sun jdk.
    Any idea?

    1.4.1 on Mac OS X is under NDA, nobody can discuss this on an open fourm...Some guy was once so much upset by the users' being allowed neither to discuss their experience nor to help each other, that he founded the open source movement. (GCC, Linux are maybe the most prominent fruits.) What is his name?

  • Inclusion of my name in SDN community under the Company

    Hi expert
    I have registered my name under SDN as a individual category. How i will be able to  add my name under the category company where I am presently working.Can anybody please suggest a way out for this.
    Regards.
    Surendra

    Hi Surendra,
    Go to the top right of the screen in the forum, there you have the My Profile/ Update profile, where you can edit your current mail id to company official email Id, name of the company etc., which are related to your company.,
    If, You have SAP Marketplace id, you can login on the same id in the sdn, so that all will accounted to your company account..
    Thanks and regards,
    Sri

  • Communication under a proxy

    Hi, I need to read some specific information (like the temperature) from a web page and I'm in a LAN workstation with internet access provided by proxy. How can i do this using a java program?

    System.getProperties().put( "proxySet", "true" );
    System.getProperties().put( "proxyHost", "myProxyMachineName" );
    System.getProperties().put( "proxyPort", "85" ); You can also do this on the command line to java: java -DproxySet=true -DproxyHost=something.proxy.com -DproxyPort=85 Application

  • RE: (forte-users) Sv: (forte-users) The Death ofForte

    This is what I got today:
    Statement of Direction
    Sun Microsystems, Inc.
    Forté 4GL(tm) Product (formerly the Forté Application Environment)
    Product Context
    · Forté 4GL is an award-winning, proven product with many unique
    advantages for building enterprise business systems that are distributed,
    that involve the integration of existing business systems as well as new
    functionality, and that target heterogeneous runtime environments.
    · Forté 4GL is recognized by Gartner Group as the most successful
    Enterprise Application Development Tool.
    · The Sun Microsystems, Inc. (SMI) development tools group (formerly
    Forté Software, Inc.) has a strong internal commitment to Forté 4GL. Forté
    Fusion is written with, and is currently being enhanced with Forté 4GL.
    · The SMI development tools group intends to actively enhance and
    promote Forté 4GL for the indefinite future. The best opportunity for
    attracting new customers is to leverage the ability of Forté 4GL to easily
    build powerful shared business services (server components) that can be
    accessed by non-Forté clients (e.g., browsers, Java clients) and that can
    easily integrate with new and existing business systems.
    · The product enhancement plan calls for continuing to issue
    incremental releases approximately twice a year. To speed the release of new
    functionality, new features will be included with "preview status." This
    means that the overall release can support production deployments, but that
    the features marked "preview" are certified for development and demos.
    · The planned contents of the next two releases are indicated below.
    Users should not expect any features other than those on the list. The
    contents of subsequent releases will be determined approximately a year in
    advance.
    · SMI has retained the Forté field sales organization as an
    independent unit whose primary product offerings are Forté 4GL and Forté
    Fusion. Continued volume sales of Forté 4GL remain the foundation of our
    business plan.
    Mid-Year Release
    · Tentatively labeled "release 3.5" to be distributed as a free
    product enhancement for customers under maintenance
    · Scheduled for Summer 2000
    · Defining features
    · Introspection (reflection) - the ability for an object to describe
    itself at runtime
    · Improved integration with applications developed using
    Forté-for-Java Community Edition(tm) (formerly NetBeans)
    · Platform support improvements to track important operating system
    and database vendor activity
    · Target features
    · Display system enhancements (e.g., Motif 2 support, line arrowheads,
    window refresh control, editable outline fields)
    · Dynamic library loading
    · Improved CORBA/IIOP support
    · Improved XML and XSLT class support
    · JMQ support
    End-Year Release
    · Tentatively labeled "release 3.6" to be distributed as a free
    product enhancement for customers under maintenance
    · Scheduled for year end 2000
    · Defining features
    · Any Release 3.5 target features that were not included in 3.5
    · Generation of EJB interfaces for R3 service objects
    · Platform support improvements to track important operating system
    and database vendor activity
    · Target features
    · COBOL record handling as part of the OS390 transaction adapter
    · Improved runtime security
    · Interface classes for access to Netscape Server 4.0 and possibly
    other web servers
    Longer Term Product Directions
    1. TOOL code to Java code migration. Neither release 3.5 nor 3.6 will
    contain an automated solution in this area. Technical differences between
    TOOL and Java make a 100% automated conversion all but impossible. A
    workable solution is likely to involve a combination of tools and services.
    2. Common repository between the 4GL and Java products. The recently
    devised Java Tools Strategy has necessitated a change in the technology base
    for our Java products to make them compatible with both the iPlanet
    Application Server and the Forté for Java Community Edition. This, in turn,
    has complicated our original vision of a common repository to the point that
    we will not embark on this project. Instead, we have elevated
    interoperability a short-term priority. In addition, we plan to migrate the
    Fusion process definition tools to Java, thereby enabling Fusion definitions
    to be stored in a common repository with Java code and components.
    3. Other long-term enhancements will be determined by additional
    customer and market feedback. A major criterion for new functionality will
    be enhancing the revenue generating ability of the product, thereby
    fostering its long-term health in the marketplace.
    As our products continue to evolve, the features and specifications
    described in this document are subject to change without notice. Sun
    Microsystems cannot guarantee the completion of any future products or
    product features mentioned in this Statement of Direction. By signing
    below, the receiving Company agrees that it has not relied on, is not
    relying on and will not rely on the potential availability of any future Sun
    product, functionality or feature in making any purchases from Sun.
    Executed by the Receiving Company Executed by Sun
    Microsystems, Inc.
    Signature:________________________
    Signature:________________________
    Name:___________________________
    Name:___________________________
    (Please Print) (Please
    Print)
    Title:____________________________
    Title:____________________________
    Date:____________________________
    Date:____________________________

    This is what I got today:
    Statement of Direction
    Sun Microsystems, Inc.
    Forté 4GL(tm) Product (formerly the Forté Application Environment)
    Product Context
    · Forté 4GL is an award-winning, proven product with many unique
    advantages for building enterprise business systems that are distributed,
    that involve the integration of existing business systems as well as new
    functionality, and that target heterogeneous runtime environments.
    · Forté 4GL is recognized by Gartner Group as the most successful
    Enterprise Application Development Tool.
    · The Sun Microsystems, Inc. (SMI) development tools group (formerly
    Forté Software, Inc.) has a strong internal commitment to Forté 4GL. Forté
    Fusion is written with, and is currently being enhanced with Forté 4GL.
    · The SMI development tools group intends to actively enhance and
    promote Forté 4GL for the indefinite future. The best opportunity for
    attracting new customers is to leverage the ability of Forté 4GL to easily
    build powerful shared business services (server components) that can be
    accessed by non-Forté clients (e.g., browsers, Java clients) and that can
    easily integrate with new and existing business systems.
    · The product enhancement plan calls for continuing to issue
    incremental releases approximately twice a year. To speed the release of new
    functionality, new features will be included with "preview status." This
    means that the overall release can support production deployments, but that
    the features marked "preview" are certified for development and demos.
    · The planned contents of the next two releases are indicated below.
    Users should not expect any features other than those on the list. The
    contents of subsequent releases will be determined approximately a year in
    advance.
    · SMI has retained the Forté field sales organization as an
    independent unit whose primary product offerings are Forté 4GL and Forté
    Fusion. Continued volume sales of Forté 4GL remain the foundation of our
    business plan.
    Mid-Year Release
    · Tentatively labeled "release 3.5" to be distributed as a free
    product enhancement for customers under maintenance
    · Scheduled for Summer 2000
    · Defining features
    · Introspection (reflection) - the ability for an object to describe
    itself at runtime
    · Improved integration with applications developed using
    Forté-for-Java Community Edition(tm) (formerly NetBeans)
    · Platform support improvements to track important operating system
    and database vendor activity
    · Target features
    · Display system enhancements (e.g., Motif 2 support, line arrowheads,
    window refresh control, editable outline fields)
    · Dynamic library loading
    · Improved CORBA/IIOP support
    · Improved XML and XSLT class support
    · JMQ support
    End-Year Release
    · Tentatively labeled "release 3.6" to be distributed as a free
    product enhancement for customers under maintenance
    · Scheduled for year end 2000
    · Defining features
    · Any Release 3.5 target features that were not included in 3.5
    · Generation of EJB interfaces for R3 service objects
    · Platform support improvements to track important operating system
    and database vendor activity
    · Target features
    · COBOL record handling as part of the OS390 transaction adapter
    · Improved runtime security
    · Interface classes for access to Netscape Server 4.0 and possibly
    other web servers
    Longer Term Product Directions
    1. TOOL code to Java code migration. Neither release 3.5 nor 3.6 will
    contain an automated solution in this area. Technical differences between
    TOOL and Java make a 100% automated conversion all but impossible. A
    workable solution is likely to involve a combination of tools and services.
    2. Common repository between the 4GL and Java products. The recently
    devised Java Tools Strategy has necessitated a change in the technology base
    for our Java products to make them compatible with both the iPlanet
    Application Server and the Forté for Java Community Edition. This, in turn,
    has complicated our original vision of a common repository to the point that
    we will not embark on this project. Instead, we have elevated
    interoperability a short-term priority. In addition, we plan to migrate the
    Fusion process definition tools to Java, thereby enabling Fusion definitions
    to be stored in a common repository with Java code and components.
    3. Other long-term enhancements will be determined by additional
    customer and market feedback. A major criterion for new functionality will
    be enhancing the revenue generating ability of the product, thereby
    fostering its long-term health in the marketplace.
    As our products continue to evolve, the features and specifications
    described in this document are subject to change without notice. Sun
    Microsystems cannot guarantee the completion of any future products or
    product features mentioned in this Statement of Direction. By signing
    below, the receiving Company agrees that it has not relied on, is not
    relying on and will not rely on the potential availability of any future Sun
    product, functionality or feature in making any purchases from Sun.
    Executed by the Receiving Company Executed by Sun
    Microsystems, Inc.
    Signature:________________________
    Signature:________________________
    Name:___________________________
    Name:___________________________
    (Please Print) (Please
    Print)
    Title:____________________________
    Title:____________________________
    Date:____________________________
    Date:____________________________

  • RE: (forte-users) Forte ADE

    In addition to this confusion, I'd like to see some statement by Forte to
    indicate
    WHEN the next Forte R4 is scheduled (before the Sun era is was said to be
    Summer 2000) and
    WHAT exactly it will contain (major headings will do).
    With the cancellation of the Forte Forum event doubt and uncertainty are
    spreading in the
    Forte communities that I talk with and no one seems to counterbalance these
    doubts with an
    official statement. How serious does Sun take TOOL Forte for the coming few
    years? Release
    of Fusion V2 seems to say "serious". The deafning silence with regard to R4
    indicates the
    opposite. And the users are divided (as always).
    Theo de Klerk
    Architecture & Application Integration
    Professional Services
    Compaq Computer Corp. - the Netherlands
    -----Original Message-----
    From: Rottier, Pascal [mailto:Rottier.Pascalpmintl.ch]
    Sent: Tuesday, 18 April, 2000 17:49
    To: 'kamranaminyahoo.com'
    Subject: (forte-users) Forte ADE
    A long, long time ago
    In a galaxy far away....
    I saw a demonstration of Forte's new Application Development
    Environment,
    which was more userfriendly than the current one. It also looked more
    similar to the interface of the other development tools out
    there, with a
    tree structure and capabilities to browse through the
    inheritance tree, and
    not opening a new window for every project, class and method that is
    accessed.
    This new interface was supposed to be included in Forte 4, which would
    combine TOOL and Java and would be released soon.
    Since then, we've seen SynerJ and now FJEE, but Forte 4 is still not
    released. And when it will be released, it still won't
    support TOOL and Java
    simultaneously. That's OK. I understand that.
    But now I've heard that this improved ADE won't even be
    included in Forte 4.
    Is this true? And if so, why?
    Pascal
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe,
    send in a new
    email the word: 'Unsubscribe' to:
    forte-users-requestlists.xpedior.com

    You may be interested in the following which comes from a statement of direction
    recently issued by Sun.
    Product Context
    + Forté 4GL is an award-winning, proven product with many unique advantages for
    building
    enterprise business systems that are distributed, that involve the integration
    of existing
    business systems as well as new functionality, and that target heterogeneous
    runtime
    environments.
    + Forté 4GL is recognized by Gartner Group as the most successful Enterprise
    Application
    Development Tool.
    + Forte 4GL has a substantial customer base that has been successful with the
    product and that
    looks forward to using Forté 4GL for new applications.
    + The Sun Microsystems, Inc. (SMI) development tools group (formerly Forté
    Software, Inc.)
    has a strong internal commitment to Forté 4GL. Forté Fusion is written with, and
    is currently
    being enhanced with Forté 4GL.
    + SMI has retained the Forté field sales organization as an independent unit
    whose primary
    product offerings are Forté 4GL and Forté Fusion. Continued volume sales of
    Forté 4GL
    remain the foundation of our business plan.
    Product Future
    + We intend to actively enhance and promote Forté 4GL for the indefinite
    future.
    + We believe Forté 4GL will flourish in the long term, especially if we are
    able to harness the
    considerable selling power of the entire SMI field sales organization. To make
    the product
    more attractive and easier to sell, we will continue to make the product more
    modular and
    easier to integrate with heterogeneous software environments.
    + We believe that the best opportunity for attracting new customers is to
    leverage the ability of
    Forté 4GL to easily build powerful shared business services (server components)
    that can be
    accessed by non-Forté clients (e.g., browsers, Java clients) and that can easily
    integrate with
    new and existing business systems.
    + We believe that Forté 4GL?s continued success is enhanced by continuing to
    issue small and
    frequent product releases. Our target is two such releases per year.
    + There is a great potential for our three product lines (Forté 4GL, Forté
    Fusion, and Forté for
    Java) to complement and reinforce each other. Interoperability among the three
    product lines
    is seen as a critical success factor for Forté 4GL.
    Forte 4GL Statement of Direction Page 2
    Sun Microsystems, Inc Proprietary and Confidential
    Product Priorities
    1. Interoperability with third party software components
    + External (non-4GL) client support (e.g., browsers, Java clients)
    + External server integration (e.g., messaging, component support, data
    exchange)
    2. Enhanced productivity
    + Increased automation (i.e., less coding)
    + Support for platform updates (e.g., new versions of OS, DBMS)
    3. TOOL code to Java code migration
    4. Unified developer look and feel with other Forte development products
    5. Common repository
    Short Term Product Plans
    Mid-year release
    + New features available as ?preview? per the standard Forte maintenance
    release procedures
    + Tentatively labeled ?release 3.5? and distributed as a free product
    enhancement for
    customers under maintenance
    + Scheduled for Summer 2000
    + Defining features
    + Introspection (reflection) ? the ability for an object to describe itself at
    runtime
    + Improved integration with applications developed using Forté-for-Java
    Community
    Edition
    + Platform support improvements to track important operating system and
    database
    vendor activity
    + Target features
    + Display system enhancements (e.g., Motif 2 support, line arrowheads, window
    refresh control, editable outline fields)
    + Dynamic library loading
    + Improved CORBA/IIOP support
    + Improved XML and XSLT class support
    + JMQ support
    New year release
    + New features available as ?preview? per the standard Forte maintenance
    release procedures
    + Tentatively labeled ?release 3.6? and distributed as a free product
    enhancement for
    customers under maintenance
    + Scheduled for year end 2000
    + Defining features
    + Any Release 3.5 target features that were not included in 3.5
    + Generation of EJB interfaces for R3 service objects
    + Platform support improvements to track important operating system and
    database
    vendor activity
    + Target features
    + COBOL record handling as part of the OS390 transaction adaptor
    + Improved runtime security
    + Interface classes for access to Netscape Server 4.0 and possibly other web
    servers
    Long Term Product Plans
    + To be determined by customer and market feedback.
    + A major criterion for new functionality will be enhancing the revenue
    generating ability of
    the product, thereby fostering its long-term health in the marketplace.
    + Substantial emphasis will be placed on creating new capabilities that enhance
    the
    attractiveness of the product for new users.
    + The contents of Release 3.7 (or whatever it will be called) will be
    solidified just after release
    3.5 ships. Subsequent planning visibility will be two forward releases.
    "Klerk, Theo de" <Theo.de.Klerkcompaq.com> on 04/18/2000 12:27:36 PM
    To: "'Rottier, Pascal'" <Rottier.Pascalpmintl.ch>,
    "'kamranaminyahoo.com'" <kamranaminyahoo.com>
    cc: (bcc: Charlie Shell/Bsg/MetLife/US)
    Subject: RE: (forte-users) Forte ADE

  • Forte install hangs when looking for Java2 SDK

    When running the "Forte for Java 4, Community Edition Setup" program under Windows ME, the installation gets as far as "Searching for suitable Java 2 SDK. Please wait .." then hangs.
    I have the Java 2 SDK version 1.3.1 and Java 2 Runtime Environment Standard Edition 1.4.0 installed.
    Any suggestions?
    Thanks,
    John

    Go to the Sun One Studio page here http://forte.sun.com/ffj/index.html and look in the FAQ/Installation for the solution to the hang.

  • No Data displayed in overview tab under Transaction Data in Support Messsag

    Dear All
    In support desk I am raising a message as a message creator from a satellite system
    Then as an administrator i assign the call to the processor
    At this stage when i change from Fast entry mode to Transaction Data i can see the details and communication under Overview tab.
    Now When i log in as a processor or end user and see in my messages and open the message which is raised for solution
    i cannot see any thing under Overview tab.
    Overview tab is coming blank for same message raised.
    Please help is there any component or role to be activated or given to processor and end user for seeing the details under Overview tab.
    Thanks
    Vishrut Shah

    Hi Shah,
    Please check the link below, it may help you for assigning authorizations:
    http://help.sap.com/saphelp_sm32/helpdata/en/45/cb27429d16db2ce10000000a1550b0/content.htm
    Check http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50557bd9-6b6f-2a10-259d-b0cdc6b121c6?quicklink=index&overridelayout=true and search the authorization part .
    Regards,
    Nibu Antony

  • RE: (forte-users) Object Request Brokers.....

    Hi Rajeev,
    I just happen to have the following two technotes on hand that helped me
    answers the very same questions..
    <<forte.zip>>
    Hope it helps... if you need more help... fell free to give me a shout!
    Ciao
    Kim
    -----Original Message-----
    From: Rajeev Talwar [SMTP:rtalshotmail.com]
    Sent: Monday, February 21, 2000 6:34 PM
    To: kamranaminyahoo.com
    Subject: (forte-users) Object Request Brokers.....
    Hi All,
    We are writing a cold fusion application which needs to use some
    services from a Forte application. We also have a Cold Fusion Visi
    Broker(ORB)to communicate with Forte. I was wondering what all we need
    in order to get a handle to all the service objects used by Forte
    application in our Cold Fusion application.
    Also do we need to change our deployment scheme for the Forte
    application. I
    believe we have to make a special deployment
    for Forte application to be available to ORB's. By default,
    Forte uses Unix internal communication mechanism like sockets
    etc. for service objects to be available across different
    partitions.
    Also do we need to run both applications and ORB on the same box
    or can we put them in some kind of network.
    I hope I made myself quite clear what we are looking for. I will be
    more than happy to put some more details in case someone needs
    further clarification.
    Are there any technotes out there whcih we can refer to.
    I will appreciate any thoughts.
    -Rajeev Talwar
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a
    new
    email the word: 'Unsubscribe' to:
    forte-users-requestlists.xpedior.com

    You can also use the HTTP-DC project.... You don't
    need Web Enterprise for this. From what I can tell,
    this is available in L.x on....
    There is api documentation in M.2 (with scant
    examples.)
    There's a special process to put the project in your
    repository (it isn't installed in the repository in
    the standard install,) the documentation in M.2
    (probably in M.0 too, AFAIK) that tells you how to do
    this (look for HTTP-DC in the online help.)
    I haven't done much with it yet, I've just installed
    it. If anybody out there has examples, that'd be
    great. I'll try to contribute more the moment I get a
    chance to explore it....
    Christopher Fury
    BellSouth Communications Systems
    --- Daniel Nguyen <dnguyenclub-internet.fr> wrote:
    Hi,
    If you have Web Enterprise, you can user
    HttpAccess.SendRequest().
    Hope this helps,
    Daniel Nguyen
    Freelance Forte Consultant
    Amin, Kamran a &eacute;crit:
    Is there any way to make a HTTP request from TOOLto another HTTP Service?
    thanks in advance.
    For the archives, go to:
    http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. Tounsubscribe, send in a new
    email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
    For the archives, go to:
    http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To
    unsubscribe, send in a new
    email the word: 'Unsubscribe' to:
    forte-users-requestlists.xpedior.com
    Kick off your party with Yahoo! Invites.
    http://invites.yahoo.com/

  • FieldPointOPC2.exe Driver & Communication Loss

    Background/Environment:
    Currently I have a legacy hardware system utilizing older FieldPoint FP-1600 ethernet modules with a couple of Discrete Input & Output modules.  I run a custom desktop Visual C++ application which connects to the FieldPoint array through Ethernet via OPC server through the FieldPointOPC2.exe driver.  The application doesn't run LabView or any other auxillary NI software to perform its work.  The desktop computer (HP Proliant DL380 G4) was originally running Windows 2000 and Field Point Explorer to handle configuration.  The computer was replaced with a HP Proliant DL380 G7 server running Windows Server 2008 SP1.  FieldPointExplorer was replaced with MAX 4.1, the application updated for Visual Studio 2008, and we currently still use the FieldPointOPC2.exe driver (version 4.0.1.15).  I believe the driver may be configured to run in compatibility mode for Windows XP SP3 but not certain.  I am not certain what firmware level is running on the FP-1600 but is not likely to be the latest.  No NI additional services are running besides NI Configuration Manager.
    Problem/Questions:
    The application seems to have brief periods where a loss of communication to the OPC server occurs.  I suspect this because inputs will seemingly all change state creating warnings/alerts in our application, but very quickly will return to normal operation as if nothing was ever wrong.  The issue occurs very rarely and randomly (maybe once/week) although the system runs almost 24x7 6-days per week.  Network hardware all appears to be ok including cabling.  Is 4.0.1.15 the latest driver version for FieldPointOPC2.exe?  Other forum posts suggest a version 5 may be available but I've had no luck locating it in the online driver packages.
    Outside of the random loss of communication, I also experience an occasional application exception which I believe may also be tied to the FieldPointOPC2 driver:
    Updating the hardware is not readily an option due to funding issues and I'm hesistant to update FP1600 firmware considering their age, availability, and non-supported status from NI.  Any help is greatly appreciated.  

    I found the following additional information regarding intermittent communication loss for FP-1600 modules from http://www.ni.com/white-paper/4368/en
    The referenced links in the white-paper for checking and obtaining firmware are no longer valid however.  I found version 502 available elsewhere on the NI site to try.    The FieldPoint Ethernet Network Module Diagnostic Utility is also unavailable...
    FieldPoint Explorer and Firmware Versions
    Most Common Symptom: Intermittent Loss of Communication
    National Instruments recommends that at a minimum, firmware revision 0200 be used with the FieldPoint Ethernet Network Module, but it is a good idea to always use the latest available firmware. . For instructions on how to check the current firmware revision, please see our KnowledgeBase entry on Determining the Firmware Revision of Network Modules. To update to the most current release of the FieldPoint Ethernet Network Module firmware, please see our KnoweldgeBase entry on How Do I Update the Firmware of an FieldPoint Ethernet Network Module?. Additionally, National Instruments recommends FieldPoint Explorer version 2.0.1 (or higher) for the most robust communication under various network fault conditions. Please visit our Drivers and Updates Library to download the current version of FieldPoint Explorer.
    Operation with Insufficient Power Supply
    Most Common Symptom: Intermittent Loss of Communication
    Under certain brown-out type conditions, the processor goes into a halt state that is not cleared until power is removed and re-applied to the module. This can happen if the power supply voltage drops below 11 V (the minimum specified voltage), but briefly remains in a range of ~0.7-10.9 V. However, because the module is operating outside of the specified power supply range, the exact failure mode cannot be guaranteed. To determine if you are suffering from an insufficient power supply, connect a multimeter or oscilloscope to the V and C terminals of the FieldPoint Ethernet Network Module. Verify that the power supply voltage is above 11 volts at all times and under all operating conditions. For example, if the FieldPoint Ethernet Network Module power supply is also used to drive other devices, test the power supply voltage when those devices are active and pulling maximum current.
    Diagnostic Check
    Most Common Symptom: Intermittent Loss of Communication
    A very small percentage of FP-1600 revision A and B modules had a manufacturing defect that could potentially cause intermittent loss of communication. Additionally, application programs might report errors such as Cannot connect to process and Timeout Period Expired. If this is the problem, power-cycling the module will temporarily clear the problem, but the problem might re-appear later. The revision of a FP-1600 module can be determined by reading the label on the underside of the FP-1600. The label will list an assembly number of the format 185690x-01, wherex is the revision letter. To determine if a revision A or B module is suffering from the defect, please download the FieldPoint Ethernet Network Module Diagnostic Utility. If the test utility determines that the module suffers from the defect, please contact National Instruments Technical Support for a RMA number and upgrade per Engineering Change Order (ECO) 13425.

  • Q: Add Community Assignments - dynamic groups

    Hi all!
    Just wondering why I have the option to add a dynamic group to a
    Community (under Assignments) but when I do, the
    assignment is lost.
    Thanks in advance!
    Adam

    Adam,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
    - Check all of the other support tools and options available at
    http://support.novell.com.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://support.novell.com/forums)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Getting Community in PRC

    Hi All,
    I'm trying to query all communities that a user has access to, using PRC. But i couldn't get that.
    I tried couple of ways.
    1) getting the communities via Object Manager
    IObjectManager objManager = remoteSession.getObjectManager(ObjectClass.Community);
    IObjectQuery objectQuery = objManager.queryObjects(folderId);
    2) via Community Manager and use queryObjects after that.
    But it always returns '0' row count, even though the parent folder has some community. The user that i'm connecting as has access to these communitities. I tried placing a portlet in the communities and the method queryCommunitiesForPortlet() works fine.
    1) I would like to know "how do i get all the communitieis that the logged in user has access to"?
    2) Do we have similar methods which does the functionality of a ptdata:currsubcommunitiesdata tag in PRC?
    Bharat Karthik
    [email protected]
    http://www.eminenttech.com/

    You're probably getting zero count b/c you're looking in a parent folder that doesn't have a community object.
    When you create a community, a folder name of the same community name is created.
    Let's say you have temporaryfolder -> inside you create a community object.
    temporaryCommunity community folder gets created -> page id object. (this is in 6.1).
    You must feed in the temporary community folder id to get the object returned...
    So with ObjectManager, there is no particular call that tells this to search its subfolders, so parent folder you're passing in doesn't contain a community object, it's the community folder that represents your actual community that does.
    Means you just didn't feed the right folder id, you're still 1 level too high. I tested the code out - same code you posted and this only returned a result when I did this.
    Again. Temporary folder = 300
    you create a community under temporary folder.
    this creates:
    communityName community folder object
    -> inside that is a page object.
    communityName communy folder = 321
    feed in 321 and not 300, as ObjectManager will not look in the subfolder 321.
    kinda hard to follow, but tried my best.

  • Printing under WinNT4.0

    When we print with report 2.0 under Windows NT 4.0, report tries to write the temporary printing-files in the system32 directory. we have already set the system variables REP_PATH and REP_TMP to folder "temp", but it did not work.
    Any suggestions?
    null

    My first inclination would be to check to make sure that the serial port
    you are trying to initialize has any errors on the NT machine. Check
    the error number coming out of the Serial Port Initialization VI and see
    if it isn't 0. A number other than zero indicates an error. There may
    be something else using the serial port.
    If you right click on the Serial Port Initialization VI and bring up the
    Online Help, it will tell you what the valid numbers for serial ports
    are for Win 95, 98, and NT. (They're all the same.)
    Mark
    In article <39abb87f$0$[email protected]>,
    "Holger Decker" wrote:
    > My application (including serial communication) works fine under
    Win95, 98
    > but I can't establish an communication under WinNT 4.0 W
    orkstation
    (SP5).
    > What can I do??
    >
    > Thanks
    >
    > Holger Decker
    >
    >
    Sent via Deja.com http://www.deja.com/
    Before you buy.

Maybe you are looking for