RS232 Comms Error Indication

Hi all, new to the site so please forgive me for any question that seems obvious or child’s play Basically the problem I have is that sometimes I loose communication between my FieldPoint FP-1000 and LabView. When I say I loose comms, the Network and Access LED on the FP are still flashing away but all the values on the screen go to zero. It is not a set time when it will do this, it is random and ive only had it once where the values came back briefly then went again Ive checked the port using 'Hyperterminal' as described in the NI help section and the port appears OK. Also all Baud rates have been checked  Does anybody know what the FP-1000 does if it has a comms error or does it even have that error code available to display? Its just strange that the port is ok and the network and access LED's appear to still be transmitting and the DAQ on LabView is still receiving messages so to me the FP seems ok?
Ive got a programme called Portmon on Cd which ive been advised to use to check the status of the port when it goes down, unless you have any sugegstions before I try it?  Many thanks in advance, any ideas or suggestions are welcome and greatly appreciated Regards Mitch  

Hi Mitch,
Please can you test the comms connection with some of the example programs shipped with LabVIEW. The ones I am thinking of are located in the LabVIEW Example Finder (Open LabVIEW goto Help >> Find Examples)
From the Example Finder go to Hardware I/O >> FieldPoint >>  Getting Started >> Analog Input.vi
This will let you quickly and easily test the comms on the FieldPoint. It will also show you how to use the FP Read vi.
Regards
JamesC
NIUK and Ireland
It only takes a second to rate an answer

Similar Messages

  • "Comm Error" message when connecting to car stereo

    When connecting my 80G IPod to the port in my car, the IPod screen rolls horizontally, then says "OK to disconnect", and the stereo displays the "Comm Error" message. I was able to connect to the stereo before but don't know what happened to cause this. Re-setting the IPod did not resolve the problem. Has anyone else seen this? Please help!
    5th Generation IPod   Windows XP  

    I’ve got a 30gb ipod doing the same thing. I know it’s not the car as my friends nano works fine on it. Have you have any success?

  • Epson Artisan 810 comm error

    When scanning with the 810 from its control panel for "scan to email",as soon as I push on the scan to email via USB on the panel it gives a comm error and says to check if computer is connected.
    This is the second 810 to do the same thing. Unistalled/reinstalled drivers, no luck. The scan from the computer to the scanner works OK without error but want to use the control panel for fast and easy scan to emails.
    Tried different usb cable, same results.
    Really am stumped. Epson tech blames IMAC software, Apple support says its in the all in one pntr/scanner. Epson says they have not heard of this problem before.
    Am using new Snow Leopard on 1 year old computer

    I have the same problem. Everything works fine, except that from the printer console, the only option for scan to Email/PDF/PC only gives the option for USB Connection (which is inconvenient for me to use). My MacBook Pro does not show up in the list like the photos in the instructions.
    I tried installing "Drivers and Utilities Combo Package - Network" dated 1/04/10, from Epson's site, file epson13616.dmg, to no avail.
    The Artisan 810 is connected by ethernet to my Time Capsule (internal network) and the MBP is connected by wireless to the same network. It will scan fine from the application on the Mac, but not from the unit's console. Really disappointing, since instead of putting something on the printer, and punching a couple buttons, you have to put it on there, go to the computer (on the other side of the room for me), pull up the software, scan, then go back to the printer to remove the item (or flip the page!)

  • Comm error using iphone in Scion?

    Hi,
    Recently, my Scion xD stereo displays "comm error" when I attempt to play my iphone through it. I tried a new cord. No luck. I tried another iphone and it worked perfectly. So it looks like my phone is the culprit. Ideas?
    Thanks in advance.

    Hi Bastille521,
    Welcome to the Support Communities!
    The following article will provide some troubleshooting steps for this issue:
    iOS: Troubleshooting car stereo connections
    http://support.apple.com/kb/TS3581
    Some car stereos require a firmware update for AVRCP 1.4 Bluetooth compatibility
    http://support.apple.com/kb/TS4483
    I hope this information helps ....
    Have a great day!
    - Judy

  • Fax test shows passed but fax doesn't work comm error

    new machine . fax test passed but when fax is trying to be sent comes back as comm error. help

    Hi @farmerj15 ,
    I see by your post that when you try to send a fax you are getting a comm error, the fax test all passed. I will do my best to help you.
    Make sure the printer is connected directly to a wall outlet. (don't use a power hub or a surge protector) This ensures the printer is receiving full power and may help this situation.
    I have provided a document to go through the steps to see if that will resolve the issue.
    Cannot Send or Receive Faxes.
    Sorry for all the questions, but it will help to resolve this issue quicker if you are still having issues.
    Please let me know the following:
    Can you receive a fax?
    What kind of line do you have? (Analogue, DSL, Cable Modem)
    Where is the fax cable connected to? (modem, wall jack)
    Are you using a filter?
    Are you using the 2 wire fax cable?
    Do you have distinctive ring set up on the line?
    Is there any voice mail set up?
    Do you have a answering machine? (Where is it connected to)
    Is there a phone also connected the printer?
    Have a nice day!
    Thank You.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • Cannot Receive faxes "result: comm error 232"

    Device:   LaserJet Pro 200color MFP  M276mw
    Product # CF145A
    This fax is not connected to a computer. Just stands alone to its own dedicated fax line.
    Will send faxes out, but cannot receive them.  Error Message is always "Comm error 232"
    I have tried turning off ECM to correct this problem, but error persists.
    Have sent faxes out with no problem however, no luck in receiving from two different sources.  

    Hi @Vibe2J ,
    I see that you are having issues receiving faxes and you are using a dedicated fax line. I would like to help you out today.
    Run a fax test.
    From the Home screen, touch the wrench button.
    Touch the service button.
    Touch the Fax service button.
    Touch run fax test.
    You should get 4 passes.
    Check these settings for the fax:
    Go to the wrench icon/fax setup menu/advanced setup/private receive/turn it off.
    Go to the wrench icon/service /fax service/error correction/turn it off.
    Go to the wrench icon/fax setup /advanced setup/fax speed/change it to medium.
    Go to wrench icon/service menu/fax service/clear saved faxes.
    If you are still having issues, then follow this document.
    Cannot Send or Receive Faxes.
    Sorry for all the questions, but it will help to resolve this issue quicker.
    Did the fax test pass?
    What type of connection do you have? (Analogue, DSL, Cable Modem)
    Are you using a filter?
    Are you using the 2 wire fax cable?
    Do you have distinctive ring set up on the line?
    Is there any voice mail set up?
    Do you have a answering machine? (Where is it connected to)
    Where is the fax cable connected to? (modem, wall jack)
    Is there a phone also connected the printer?
    Have a nice day!
    Thank You.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • %NHRP-3-PAKERROR: Receive Error Indication from NHS IP , code: administratively prohibited(4), offset: 0, data:

    Hi,
    I am continuously getting the following error on my DMVPN spoke:
     %NHRP-3-PAKERROR: Receive Error Indication from <NHS tunnel IP>, code: administratively prohibited(4), offset: 0, data: 
    Here are debugs:
    054486: Aug 30 00:01:13 DXB: NHRP: Attempting to send packet via DEST <NHS tunnel IP>
    054487: Aug 30 00:01:13 DXB: NHRP: Receive Error Indication via Tunnel1 vrf 0, packet size: 128
    054488: Aug 30 00:01:13 DXB:  (F) afn: AF_IP(1), type: IP(800), hop: 255, ver: 1
    054489: Aug 30 00:01:13 DXB:      shtl: 4(NSAP), sstl: 0(NSAP)
    054490: Aug 30 00:01:13 DXB:      pktsz: 128 extoff: 0
    054491: Aug 30 00:01:13 DXB:  (M) error code: administratively prohibited(4), offset: 0 
    054492: Aug 30 00:01:13 DXB:      src NBMA: <NHS public IP>
    054493: Aug 30 00:01:13 DXB:      src protocol: <NHS tunnel IP>, dst protocol: <spoke tunnel IP>
    054494: Aug 30 00:01:13 DXB:      Contents of error packet:
    054495: Aug 30 00:01:13 DXB:         00 01 08 00 00 00 00 00 00 FF 00 58 74 68 00 34 
    054496: Aug 30 00:01:13 DXB:         01 01 04 00 04 04 C8 02 00 00 1B 29 3E A7 F3 52 
    054497: Aug 30 00:01:13 DXB:         AC 12 14 A7 0A 14 5A 13 
    Any clue as to why these are logs are appearing?

    All,
    Here's a quick blurb from a document I've been working on which helps to explain this specific error message:
    An error code of 7 will be returned by the NHS when an error occurs when processing the packet which is not associated with any of the other NHRP error codes. According to RFC2332, triggers for the error code include invalid version numbers, invalid protocol types, and failed checksums. This error is commonly seen if the NHS receives a Resolution Request for an IP address which it does not have an entry for in its NHRP cache. For example, if a DMVPN spoke tries to send traffic to a spoke IP address which is not registered with the hub, the hub will return an NHRP Error Indication with the Protocol Generic Error specified.
    To troubleshoot this condition, you should collect the following on both the hub and spoke routers:
    show ip nhrp
    debug nhrp
    debug nhrp packet
    Collecting the debugs will show you the exact NHRP packets which are being sent and received, which may give you an indicate as to what is prompted these errors to be return. Keep in mind that the debugs can be quite chatty and significant NHRP traffic may cause the debugs to impact the router performance.
    HTH,
    Frank

  • Comm. error while checking accnt assignment for invoice 8000338378 in syste

    Hi all,
    Comm. error while checking accnt assignment for invoice (8000338378) in system   .
    But every thing is good.but we are geting error list above error
    Reagrds,
    Srikanth

    Hi Praveen and all,
    Thanks for your replies.
    I tried doing setting with VKOA and checked with
    VF02, Environment-Account determination analysis.
    --> it says account determination is found.
    Then i clicked the Flag button(Release to accounting) in VF02.
    It gives below error in status bar
    <b>"only output tax is allowed for account 175000 JTC1, E0 is not allowed"</b>
    How to go ahead or solve this error.
    suggest me please.
    regards
    Ambichan

  • DMVPN NHRP error indication logs

    I am seeing a ton of these entries one of my spoke routers.. the hub router IP is 10.1.2.1 and all the dst IP's are not in use so I can't figure out why the spoke router is sending packets to 10.1.2.3, 10.1.2.44, 10.1.2.47 and so-o and those IP's are not in use in my environment. 
    Its dropping packets across the tunnel constantly and I can't figure out why. Does anyone have an idea of what is happening? 
    Oct 29 20:05:13.544 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma:28.28.45.45) dst: 10.1.2.3), offset: 0, data: 00 01 08 00 00 00 00 00 00 FF 00 58 F3 2C 00 34
    Oct 29 20:05:18.572 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma:28.28.45.45) dst: 10.1.2.44), offset: 0, data: 00 01 08 00 00 00 00 00 00 FF 00 58 F2 F2 00 34
    Oct 29 20:05:23.777 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma:28.28.45.45) dst: 10.1.2.47), offset: 0, data: 00 01 08 00 00 00 00 00 00 FF 00 58 F2 ED 00 34
    Oct 29 20:05:30.181 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma:28.28.45.45) dst: 10.1.2.46), offset: 0, data: 00 01 08 00 00 00 00 00 00 FF 00 58 F2 EC 00 34
    Oct 29 20:05:36.638 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma:28.28.45.45) dst: 10.1.2.7), offset: 0, data: 00 01 08 00 00 00 00 00 00 FF 00 58 F3 26 00 34
    Oct 29 20:05:42.842 IST: %NHRP-3-PAKERROR: Received Error Indication from 10.1.2.1, code: protocol generic error(7), (trigger src: 10.1.2.192 (nbma: 28.28.45.45) dst: 10.1.2.34),
    This is the tunnel config on the spoke itself, granted I have another tunnel (different ISP) on this spoke going to another hub and I do not see these error messages on that tunnel.

    All,
    Here's a quick blurb from a document I've been working on which helps to explain this specific error message:
    An error code of 7 will be returned by the NHS when an error occurs when processing the packet which is not associated with any of the other NHRP error codes. According to RFC2332, triggers for the error code include invalid version numbers, invalid protocol types, and failed checksums. This error is commonly seen if the NHS receives a Resolution Request for an IP address which it does not have an entry for in its NHRP cache. For example, if a DMVPN spoke tries to send traffic to a spoke IP address which is not registered with the hub, the hub will return an NHRP Error Indication with the Protocol Generic Error specified.
    To troubleshoot this condition, you should collect the following on both the hub and spoke routers:
    show ip nhrp
    debug nhrp
    debug nhrp packet
    Collecting the debugs will show you the exact NHRP packets which are being sent and received, which may give you an indicate as to what is prompted these errors to be return. Keep in mind that the debugs can be quite chatty and significant NHRP traffic may cause the debugs to impact the router performance.
    HTH,
    Frank

  • Nested perform on commit error

    hi all,happy new year 2006
    in my custom transaction upon save,
    iam calling a Func module in update task passing all the internal tables which contain the update data.
    inside this FM iam doing table updates without commit and also calling change document funcs ( open,single/multiple case/close) to update the CDHDR and CDPOS tables.
    iam also calling BAPI_SALESORDER_CHANGE inside this update task FM. after the call iam calling BAPI_TRANSACTION_COMMIT.
    Iam getting an update task termination message saying that there are nested perform on commit statements happenening in some some SAP prog call and therefore it causes a dump. i have seen that the fm 'CHANGEDOCUMENT_CLOSE' calls a 'perform on commit'.
    but not able to figure out where exactly is the problem.
    any suggestions.
    thanks a lot.

    Hi KP!
    I'm sure you can't call BAPI_TRANSACTION_COMMIT in an update task - there a commit is a forbidden statement.
    I had a short look at CHANGEDOCUMENT_CLOSE:
    *    don't call this form on COMMIT when you are already in a form on
    *    commit
        IF sy-oncom = 'P'.
          PERFORM swe_event_create_changedocumnt.
        ELSE.
          PERFORM swe_event_create_changedocumnt ON COMMIT.
        ENDIF.
    At least here (and on release 640, ERP 5.0) a different coding for update tasks is executed.
    Do you have a shortdump, where you can check exact place of the nested call? Or is this a generation error -> again try to check exact place.
    Regards,
    Christian

  • ADF commit error

    Hi,
    oracle.jbo.JboException: JBO-28201: Post threshold limit reached.
    Some entities yet to be posted.
    I get this error sometimes when I delete a row from a view and then commit the transaction.
    view.removeCurrentRow();
    AppModule.getTransaction ().commit ();
    I have optimistic locking

    This error is reached when the post cycle could not complete. Are you 'adding' an entity into the transaction to post during the post cycle of entities during transaction commit?

  • Oracle post failover transaction commit error

    I have a problem on trasaction after database failover.
    Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary and
    another is standby), JDK 1.3.1
    We found this problem in Oracle (Net 8 connection time) failover test.
    Here is what we did.
    During the load, we shut down the primary Oracle server (box).
    All in-flight transactions were wrong, this is ok.
    When new requests came in, WebLogic begin to refresh the connections.
    Because the primary Oracle server was down, it took about 70 seconds to
    refresh a connection (due to the socket timeout value) and redirect to the
    standby Oracle. This is fine.
    After a while, all connections were refreshed and all connected to the
    standby serever.
    When I opened WebLogic console to monitor the in-flight transaction, I found
    some transactions are doing committing and never finished.
    At this time most of the transaction can go through but few of them through
    an exception (attached at the end). This error could never gone although the
    frequency was not high. The strange thing is I checked the database, the
    data was committed.
    I've tried Oracle OCI driver and thin driver, both had this problem. Is
    there anyone can help me on that?
    Thanks,
    Wenji
    <Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
    transaction Name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
    1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
    onds since begin=122,seconds
    left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
    ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
    gic.transaction.name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],
    weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
    erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
    esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
    javax.transaction.SystemException: Timeout during commit processing
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:243)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:189)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
    at

    Wenji Tong wrote:
    Thanks, Joe!
    Things could be more complicate. I did some tests to find the details of the
    problem. Here are the results.Hi,
    This is developing into a bigger problem than I can solve informally in newsgroups,
    so I suggest that you open an official support case with this information.
    Joe
    >
    >
    1. I've done a test. In this test, I shut down the Oracle and also stop the
    load. After all threads and connection returned to the pool and all
    transactions done (roll back or abandoned), I started load again. I still
    could find this error. That means this error is not related to any in-flight
    transactions.
    2. After all connectioin failed over, this error was still not gone. The
    frequency was not high, but it was always there.
    3. In WebLogic console, monitor in-flight transaction, I saw some
    transactions were doing committing, but never finished if there was no load.
    When I saw an error printed in log, one of the committing transaction gone
    but there came out another transaction doing the commit and can't be
    finished. I'm not sure if it was related to WebLogic console's bug.
    4. Increase the transaction timeout can fix this problem. Unfortunately, we
    can't increase the transaction timeout anymore due to our business
    requirements.
    I hope those information will be helpful.
    Thanks,
    Wenji
    "Joseph Weinstein" <[email protected]> wrote in message
    news:[email protected]...
    Wenji Tong wrote:
    I have a problem on trasaction after database failover.
    Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary
    and
    another is standby), JDK 1.3.1
    We found this problem in Oracle (Net 8 connection time) failover test.
    Here is what we did.
    During the load, we shut down the primary Oracle server (box).
    All in-flight transactions were wrong, this is ok.
    When new requests came in, WebLogic begin to refresh the connections.
    Because the primary Oracle server was down, it took about 70 seconds to
    refresh a connection (due to the socket timeout value) and redirect tothe
    standby Oracle. This is fine.
    After a while, all connections were refreshed and all connected to the
    standby serever.
    When I opened WebLogic console to monitor the in-flight transaction, Ifound
    some transactions are doing committing and never finished.
    At this time most of the transaction can go through but few of themthrough
    an exception (attached at the end). This error could never gone althoughthe
    frequency was not high. The strange thing is I checked the database, the
    data was committed.
    I've tried Oracle OCI driver and thin driver, both had this problem. Is
    there anyone can help me on that?
    Thanks,
    WenjiHi. It seems that Oracle failover is not perfect. Our transactioncoordinator
    is supposed to have control of the transaction. If a failover occurs while
    a transaction is pending, the coordinator should still have the ability toroll
    back the tx. Apparently there are cases where the failover causes an open
    transaction to be committed, in such a way that even if the coordinatorhas
    decided to roll it back, it can't. These may be when the failover occurswhile
    we are waiting for the commit call to return. We either get an exceptionor
    we get no return from the commit() call so we try to roll back and fail.The
    actual commit succeeded, but we never knew.
    Joe
    <Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
    transaction Name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    >nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
    >1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
    onds since begin=122,seconds
    left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
    >ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
    gic.transaction.name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],
    weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
    >erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
    esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
    javax.transaction.SystemException: Timeout during commit processing
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:243)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:189)
    atweblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
    at

  • DB Adapter connecting to DB2 Database is giving Transaction Commit Error

    Hi All,
    I have a simple BPEL process in 11g which executes a select query through the DB adapter in the DB2 database
    The below is the query
    select column1,column2,column3 from table1 where column1='123456'
    During the invoke of the DBAdapter I am getting the following Error in SOAP UI testing tool
    ++<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">++
    ++<env:Header/>++
    ++<env:Body>++
    ++<env:Fault>++
    ++<faultcode>env:Server</faultcode>++
    ++<faultstring>Exception occured when binding was invoked.++
    ++Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DB2Test' failed due to: DBWriteInteractionSpec Execute Failed Exception.++
    *++unknown failed. Descriptor name: [unknown].++*
    ++Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..++
    ++".++
    ++The invoked JCA adapter raised a resource exception.++
    ++Please examine the above error message carefully to determine a resolution.</faultstring>++
    ++<faultactor/>++
    ++<detail>++
    ++<exception>Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed.</exception>++
    ++</detail>++
    ++</env:Fault>++
    ++</env:Body>++
    ++</env:Envelope>++
    The Datasource configured has "Support Global Transactions" option Checked and One Phase Commit selected.
    Any help or pointers in this regard will be greatly appreciated.
    Thanks in advance
    Regards
    Nithya Subramanian

    Hi Anuj,
    I tried the Option 2 given in the thread which you have mentioned.
    Our DataSource is targeted to the managed server so we just restarted the managed server.
    I am still getting the same error of
    "Cannot call Connection.commit in distributed transaction. Transaction Manager will commit the resource manager when the distributed transaction is committed."
    Are there any other alternative approach to fix this issue?
    Regards
    Nithya

  • Network DR test causes Exchange DAG network to fail (Failover Cluster Manager reports comms errors)

    We have a DAG configured between 2 mailbox servers, one in each of our main data centres. Our comms team recently performed a DR test between our 2 data centres, switiching from the main production link to the backup link. During this outage the Failover
    Cluster Manager reported errors, with each mailbox server reporting the other as uncontactable. The Events that were logged include the following:
    Isatap interface isatap.{02ADE20A-D5D4-437F-AD00-E6601F7E7A9D} is no longer active. (EventID 4201)
    Cluster node 'MAILBOX_SERVER' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the
    Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is
    connected such as hubs, switches, or bridges. (EventID 1135)
    File share witness resource 'File Share Witness (\\WITNESS_SERVER\SHARE_NAME)' failed to arbitrate for the file share '\\WITNESS_SERVER\SHARE_NAME'. Please ensure that file share '\\WITNESS_SERVER\SHARE_NAME' exists and is accessible by the cluster. (EventID
    1564)
    Cluster resource 'File Share Witness (\\\WITNESS_SERVER\SHARE_NAME)' in clustered service or application 'Cluster Group' failed. (EventID 1069)
    The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network
    configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. (EventID 1177)
    The Cluster Service service terminated with service-specific error A quorum of cluster nodes was not present to form a cluster. (EventID 7024)
    The Microsoft Exchange Information Store service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service. (EventID 7031)
    Looking at the Cluster Events in the Failover Cluster Manager Snap-In i see a heap of Event ID 47 (cannot activate the DAG databases as the server is not up according to Windows Failover Cluster Service) and:
    Node status could not be recorded. This could prevent some network failure logic from functioning correctly. NodeStatus:IsHealthy=True,HasADAccess=True,ClusterErrorOverrideFalse,LastUpdate=5/2/2011 8:25:42 AMUTC Failure:An Active Manager operation failed.
    Error: An error occurred while attempting a cluster operation. Error: Cluster API '"ClusterRegSetValue() failed with 0x6be. Error: The remote procedure call failed"' failed.. (EventID 184)
    Forcefully dismounting all the locally mounted databases on server 'BACKUP_MAILBOX_SERVER. (EventID 307).
    Our Comms team doesn't believe it is a comms issue as they did not log any network communication errors between the servers in the two sites (using icmp). So if it is not a comms issue, how can I configure the Failover Cluster Manager to be resilient to
    this type of network failover event.
    Thanks
    Dan

    Isn't it also true that in a stretched DAG with even numbered nodes, the PAM needs to be in the same site as the active DAG node?  If the connection between both nodes goes down, and the PAM is in the "passive" site, the primary node will
    dismount the databases since it can't check with the PAM to make sure its safe for it to be up.  
    In a even-numbered node stretched DAG, the PAM changes to the DR/passive site everytime a failover occurs, but doesn't automatically switch back when you reactivate the primary node.

  • LCDS commit error from arraycollection

    Hi all,
    I am attempting to hook Flex up to the LCDS engine installed
    with CF8. I can get the ds.fill() method to populate an
    ArrayCollection just fine, pump the data out in a DataGrid and
    shows perfectly. However, when I update a record in the datagrid I
    get an error indicating that "Error during update: The OLDBEAN
    argument passed to the update function is not of type" and then it
    says my CFC type.
    I changed to code to set autoCommit to false and update one
    entrry via code then manually call commit, and this works fine,
    although I did have to cast the single record to my data type (it
    was a generic Object). Setting it back and debugging shows that all
    of the records in my ArrayCollection are typed as generic Object's
    not as my defined data type.
    My question is: how do I get the ds.fill() method to return
    the correctly typed objects (I am using the CF8 wizard-generated
    CRUD arguments)
    OR
    How can I programatically convert the contents of the
    ArrayCollection to the required type "on-the-fly" before calling
    ds.commit()?
    Hoping somebody can help, this is driving me nuts!
    Just as a final thought, does this indicate a bug in the CF
    CRUD generation wizard or am I just doing it wrong?
    Cheers,
    Owen West
    HNE Health
    [email protected]

    Which the information provide it's hard to troubleshoot because there's no Oracle related information.
    What's your Oracle version? do you have enough space on rollback segment tablespace or undo tablespace (9i and above)
    Any error in your database's alert log file?

Maybe you are looking for