Attribute modifying not happening

I have one custom attribute in user create page,populating in process form and provisioning in OID
For updating this attribute in process form i have made 2 tasks change attribute and update attribute for that custom attribute.
But when i am editing user form that task is not launching, i am able to see the task in ADD task and when i am manualy adding this task it is showing completed but in task history status is pending.

I created a user in OIM and provisioned that user in OID. Then I updated one of his value say for example company decription. The task is getting triggered and the values are getting updated in process form but not in OID>
No error is getting displayed other than:
INFO,23 Feb 2010 17:04:26,453,[XL_INTG.OID],com.thortech.xl.integration.OID.tcU
ilOIDUserOperations:createUser(S,S,S,S,S) Returning with code: USER_CREATION_SU
CESSFUL
WARN,23 Feb 2010 17:04:31,671,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:31,671,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:31,671,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:31,671,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:31,671,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
unning SETCOMPANYDESCRIPTION
arget Class = CopyAdapterValue
ntered
WARN,23 Feb 2010 17:04:52,015,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:52,015,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:52,015,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:52,015,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.
WARN,23 Feb 2010 17:04:52,015,[XELLERATE.WEBAPP],TimeZone is not set for the br
wser's machine.

Similar Messages

  • VG-204 SIP - PSTN outbound not happening from CUCM

    I have VG204 configured as SIP , SIP trunk is established to CUCM 7.x , Outbound to PSTN calls is not happening but Extension dialing  within CUCM DB is happening. Inbound from PSTN works.
    Call manager is not forwarding the calls initiated from vg204 extn to PSTN gateway .
    Pls assist if i am missing something on vg204 or CUCM for outbound calls to happen .
    , the error log on cucm  is
    SIP/2.0 404 Not Found
    Reason: Q.850;cause=1
    version 15.1
    no service pad
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec localtime show-timezone
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    no service dhcp
    boot-start-marker
    boot system flash:vg20x-advipservicesk9-mz.151-3.T3.bin
    boot system flash:
    boot-end-marker
    aaa session-id common
    clock timezone GMT 0 0
    crypto pki token default removal timeout 0
    no ip source-route
    ip cef
    no ip bootp server
    no ip domain lookup
    no ipv6 cef
    voice call send-alert
    voice rtp send-recv
    voice service voip
    no ip address trusted authenticate
    allow-connections h323 to h323
    allow-connections h323 to sip
    allow-connections sip to h323
    allow-connections sip to sip
    fax protocol pass-through g711alaw
    modem passthrough nse codec g711alaw
    sip
      bind control source-interface FastEthernet0/0
      bind media source-interface FastEthernet0/0
      redirect contact order best-match
    voice class codec 2
    codec preference 4 g711alaw
    codec preference 5 g711ulaw
    voice class sip-profiles 1000
    request ANY sip-header User-Agent modify "User-Agent: Cisco-SIPGateway.*" "User-Agent: Cisco/v11 r1/alg01"
    request ANY sip-header Server modify "Server: Cisco-SIPGateway.*" "Server: Cisco/v11 r1/alg01"
    response ANY sip-header Server modify "Server: Cisco-SIPGateway.*" "Server: Cisco/v11 r1/h2p-vg-alg01"
    response ANY sip-header User-Agent modify "User-Agent: Cisco-SIPGateway.*" "User-Agent: Cisco/v11 r1/alg01"
    response ANY sip-header Remote-Party-ID remove
    request ANY sdp-header Attribute modify "a=rtr" "a=X-nortr"
    response ANY sdp-header Attribute modify "a=rtr" "a=X-nortr"
    voice vad-time 1000
    voice-card 0
    application
    package callfeature
      param long-dur-disc-cause 21
      param long-dur-duration 1440
      param long-dur-action disconnect
      param long-dur-call-mon enable
    service dsapp
      param callWaiting FALSE
      param blind-xfer-wait-time 2
      param callTransfer TRUE
    global
      service default dsapp
    archive
    log config
      hidekeys
    dial-control-mib retain-timer 1440
    dial-control-mib max-size 500
    ip tftp source-interface FastEthernet0/0
    interface FastEthernet0/0
    ip address 10.10.10.13 255.255.255.224
    ip access-group al_trusted_SIP in
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    load-interval 60
    speed 100
    full-duplex
    arp timeout 420
    control-plane
    voice-port 0/0
    no snmp trap link-status
    timeouts interdigit 4
    description h2p/01
    station-id name Analog phone
    station-id number 26999
    caller-id enable
    voice-port 0/1
    no snmp trap link-status
    timeouts interdigit 4
    description h2p/02
    station-id name Analog phone
    station-id number 26998
    caller-id enable
    voice-port 0/2
    no snmp trap link-status
    timeouts interdigit 4
    description h2p/03
    station-id name Analog phone
    station-id number 26997
    caller-id enable
    voice-port 0/3
    no snmp trap link-status
    timeouts interdigit 4
    description h2p/04
    station-id name Analog phone
    station-id number 26996
    caller-id enable
    mgcp profile default
    dial-peer voice 1100 voip
    permission orig
    description Incoming from IP network
    huntstop
    session protocol sipv2
    incoming called-number .
    voice-class codec 2 
    voice-class sip profiles 1000
    dtmf-relay rtp-nte
    dial-peer voice 1210 voip
    description SIP registrar server
    huntstop
    preference 4
    destination-pattern .T
    session protocol sipv2
    session target ipv4:10.10.10.15
    voice-class codec 2 
    voice-class sip profiles 1000
    dtmf-relay sip-notify
    dial-peer voice 99900 pots
    description Analog phone
    huntstop
    preference 4
    destination-pattern 26999
    progress_ind alert strip
    port 0/0
    dial-peer voice 99901 pots
    description Analog phone
    huntstop
    preference 4
    destination-pattern 26998
    progress_ind alert strip
    port 0/1
    dial-peer voice 99902 pots
    description Analog phone
    huntstop
    preference 4
    destination-pattern 26997
    progress_ind alert strip
    port 0/2
    dial-peer voice 99903 pots
    description Analog phone
    huntstop
    preference 4
    destination-pattern 26996
    progress_ind alert strip
    no digit-strip
    port 0/3
    dial-peer hunt 2
    no dial-peer outbound status-check pots
    gateway
    media-inactivity-criteria all
    timer receive-rtcp 5
    timer receive-rtp 1200
    sip-ua
    retry invite 3
    registrar 1 ipv4:10.10.10.15 expires 3600
    g729-annexb override

    Can someone assist me pls.

  • 'dimension attribute was not found' error while refresing the cube in Excel

    Dear All,
    Thanks for all your support and help.
    I need an urgent support from you as I am stuck up here from nearly past 2-3 days and not getting a clue on it.
    I have re-named a dimension attribute 'XX' to 'xx' (Caps to small)in my cube and cleared all dependencies (In Attribute relationship tab as well).
    But while refreshing the data in excel client (of course after processing the full cube) I get an error
    'Query (1, 1911) the [Dimension Name].[Hierarchy Name].[Level Name].[XX] dimension attribute was not found' error.
    Here I am trying to re-fresh an existing report without any changes with the new data.
    Does not it re-fresh automatically if we clear the dependencies or there something that I am missing here (Like order of the dependencies).
    Cube processed completely after modifications and able to create new reports without any issues for same data. What else could be the reason?
    Can some one help me here?
    Thanks in Advance and Regards,

    Thnaks alot Vikram,
    In se11  ,when i was trying to activate the  /BIC/FZBKUPC , it is showing the warnings  like
    Key field KEY_ZBKUPCP has num. type INT4: Buffering not possible, Transport restricted.What it means.
    In PErformance Window it is showing like:
    A numeric type was used for a key field. A table of this sort cannot be buffered.When buffering, the table records for numeric values cannot be stored in plain text.
    Procedure
    You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
    If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
    Please adivice with your valueable suggestyions.
    Thanks Vikram.

  • XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'

    Hello,
    I'm a long-time Siebel developer but novice to BIP, trying to enhance some complex rtf templates that an experienced xdo/bip developer (contractor) designed for us in the past, with a couple of new fields that have been added to the integration object.
    All templates and sub-templates receive 'no errors found' when using add-in tool selection of 'Validate Template'. Unfortunately we cannot utilize the 'preview' capability due to the way the sub-templates are called, so only way to test is to upload into server and attempt to run real-time.
    This results in UI error of SBL-OMS-00203, which when we dig into the xdo log file turns out to be:
    <Line 648, Column 88>: XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'.
    I have exported all templates and sub-templates into XSL-FO Style Sheet and looked at line 648 column 88, and none of them seem to correspond to this line/column combination (in fact most exports do not even go that high in lines).
    Googling 'XML-22009' hasn't proven to be of much help, so reaching out to the xdo experts in this forum.
    How are the line/column #'s determined in the xdo log output?
    I am pretty sure that it must be some issue with my 'Main' template, since none of the sub-templates have been changed (and the current version of the report, without the new fields incorporated, still runs fine from the UI). In the XSL-FO format export of the (modified, with new fields added) 'Main.rtf' file, line 648 places it right in the midst of a bunch of hex which corresponds to an imbedded image (which was also part of the existing template, no change there) and that line only has 65 columns (i.e. doesn't even go up to 88), so I'm questioning how valid the Line/Column information is in the xdo log error message.
    Any hints on troubleshooting this one would be greatly appreciated!
    Thanks & Regards,
    Katrina

    Hi,
    as I wrote in the inital message, we even left out the output method or used "application/pdf". The result is unfortunately always the same. And I still claim this is not a problem with the stylesheet itself, it has to do something with the mobile's environment.
    Something I didn't tell: we have 2 servlets in our application, 1 responsible for output in html and 1 in pdf. The .fo stylesheet passed to the 'html servlet' is parsed correctly (and shows the source code, because it does not know about fo and conversion to pdf), the .xsl stylesheet passed to the 'pdf servlet' raises same exception/same line. You might tell us that there is a problem with the 'pdf servlet', but once again: why in online it is working?
    Greetings and thanx very much for your precious time!

  • When on facebook or sites with pictures, the pctures almost look like a negative except that it's green. this does NOT happen in IE

    while on facebook pictures look like negatives but green. almost as if they were ifrared but bright green. eyes, hair, items most of the picture is this bright green. this does not happen if i go to facebook using Internet Explorer. i have deleted firefox and reinstalled over and over but it keeps reoccurring. very frustrating!!

    That's strange, I haven't heard of that one! A standard diagnostic step is to try Firefox's Safe Mode to see whether it is caused by a custom setting or add-on.
    First, I recommend backing up your Firefox settings in case something goes wrong. See [https://support.mozilla.com/en-US/kb/Backing+up+your+information Backing up your information]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
    Next, restart Firefox in [http://support.mozilla.com/kb/Safe+Mode Safe Mode] using
    Help > Restart with Add-ons Disabled
    In the Safe Mode dialog, do not check any boxes, just click "Continue in Safe Mode."
    If the photos look right, the problem most likely is an add-on or custom setting. Do you have any add-ons that modify or block images, ads, or Flash?

  • JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

    Hi all,
    I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
    error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
    Cheers,
    --Tim West
    Full output (from wscompile Ant task) - added linebreaks for readability
    Buildfile: C:\common\eclipse-projects\thp\build.xml
    wscompile-init:
    ANEW-generate-server-binding:
    [wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
    -features:documentliteral,wsi -g -gen:server -keep -verbose \
    C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
    [wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: userDefinedBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdHeader]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestAckHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyResponseChoiceHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusQueryHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: statusStructure]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseHdr]
    [wscompile] error: generator error: internal error (should not happen): tie.generator.002
    BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
    Total time: 2 seconds

    Hi again,
    The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
    Thanks again,
    -Tim West
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
        name="TentativeHold"
        targetNamespace="http://www.w3.org/2001/08/thp/definitions"
        xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns="http://schemas.xmlsoap.org/wsdl/">
      <types>
        <schema xmlns="http://www.w3.org/2001/XMLSchema"
            xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
            targetNamespace="http://www.w3.org/2001/08/thp/schemas">
          <!-- =================================================================== -->
          <!-- Item - holdHeader -->
          <!-- Note - This information is required in all the Tentative Hold Protocol
                      communications. -->
          <!-- Fields- holdID - UUID. -->
          <!--             customerID - account number or other identifier -->
          <!--             replyTo - could be a unique locator such as a URI or an
                              email address depending on the communication protocol
                              to be used. -->
          <!-- comment - space for trading partner defined info. -->
          <!-- =================================================================== -->
          <complexType name="holdHeader">
            <sequence>
              <element name="holdID" type="int"/>
              <element name="customerID" type="string"/>
              <element name="replyTo" type="string"/>
              <element name="comment" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - userDefinedBody -->
          <!-- Note - This will carry any domain-specific information  (e.g., product
                ID and quantity). An implementation shall probably have many
                different userDefinedBody's (one for holdRequest, holdRequestAck,
                ...). This body is used in all messages. -->
          <!-- Fields - Trading partner to trading partner specific or an agreed
             - standard (e.g., RosettaNet PIP). -->
          <!-- =================================================================== -->
            <!-- TIM: Just junk here for now, must fix later -->
          <complexType name="userDefinedBody">
            <sequence>
              <element name="someRequestField" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestHdr -->
          <!-- Note - Specifies the Tentative Hold Protocol header for messages
             - requesting a tentative hold. -->
          <!-- Fields - Same as holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdRequestHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestAckHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + timeUntilResponse - a indication of the time it
             - will take the resource provider to process the request. -->
          <!-- =================================================================== -->
          <complexType name="holdRequestAckHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="timeUntilResponse" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdGrantHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdDuration" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the
             - denial. The implementation may choose to use reason codes or just
             - textual descriptions. -->
          <!-- =================================================================== -->
          <complexType name="holdDenialHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="reason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdModifyRequestHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdModifyGrantHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the denial.
             - The implementation may choose to use reason codes or just textual
             - descriptions.-->
          <!-- =================================================================== -->
          <complexType name="holdModifyDenialHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyResponseChoiceHdr -->
          <!-- Note - The use of a single type for this response was to facilitate a
             - synchronous request/response for the modify request without preventing
             - asynchronous.-->
          <!-- Fields - Either holdModifyGrantHdr or holdModifyDenialHdr -->
          <!-- =================================================================== -->
          <!-- TIM: JWSDP does not support xsd:choice, so I'm turning this into a sequence.
             -      The implementor is now responsible for ensuring exactly one of these
                    is present.
            -->
          <complexType name="holdModifyResponseChoiceHdr">
            <sequence>
              <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
              <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + customerReason - a description of or a code for
             - the reason why the hold is being cancelled. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationRequestHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="customerReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationResponseHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationNotificationHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + cancellationReason - a description of or a code
             -for the reason the vendor is cancelling the hold. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationNotificationHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="cancellationReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusQueryHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusQueryHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - statusStructure -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdState - a description of the state of the hold.
             - Possible values currently defined are: responding, in process, active,
             - and inactive. The definition is left open (not restricted) for future or
             - user refinement of the useful values. -->
          <!-- =================================================================== -->
          <complexType name="statusStructure">
            <sequence>
              <element name="itemHeader" type="holdSchema:holdHeader"/>
              <element name="holdState" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseBody -->
          <!-- Note - -->
          <!-- Fields - holdItemsCount - the number of holds matching the holdStatusQuery. -->
          <!--             itemList - The header and state of the holds that match the query. -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseBody">
            <sequence>
              <element name="holdItemsCount" type="int"/>
              <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdErrorHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <!-- TIM: Combined old "holdErrorHdr" and "holdErrorBody" as a fault must
             - have only a single part (see WSDL sec 3.6).
            -->
          <complexType name="holdError">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdErrorType" type="int"/>
              <element name="holdErrorDesc" type="string"/>
            </sequence>
          </complexType>
          <!-- TIM: To use doc/lit, we need <element> tags here to reference from WSDL -->
          <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
          <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
          <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
          <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
          <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
          <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
          <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
          <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
          <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
          <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
          <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
          <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
          <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
          <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
          <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
          <element name="holdError" type="holdSchema:holdError"/>
        </schema>
      </types>
      <message name="HoldRequest">
        <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
        <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldRequestAck">
        <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
        <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldGrantResponse">
        <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
        <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldDenialResponse">
        <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
        <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyRequest">
        <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
        <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyResponse">
        <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
        <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationRequest">
        <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
        <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationResponse">
        <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
        <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationNotification">
        <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
        <part name="body" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusQueryRequest">
        <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
        <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusResponse">
        <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
        <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
      </message>
      <message name="HoldErrorResponse">
        <!-- TIM: altered to be consistent with updated schema - the
           - fault body must have only one part
          -->
        <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
      </message>
      <portType name="TentativeHoldServicePortType">
        <operation name="InitiateHold">
          <input message="tns:HoldRequest"/>
          <output message="tns:HoldRequestAck"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldModify">
          <input message="tns:HoldModifyRequest"/>
          <output message="tns:HoldModifyResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldCancellation">
          <input message="tns:HoldCancellationRequest"/>
          <output message="tns:HoldCancellationResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateStatusQuery">
          <input message="tns:HoldStatusQueryRequest"/>
          <output message="tns:HoldStatusResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
      </portType>
      <portType name="TentativeHoldNotificationServicePortType">
        <operation name="NotifyHoldGranted">
          <output message="tns:HoldGrantResponse"/>
        </operation>
        <operation name="NotifyHoldDenied">
          <output message="tns:HoldDenialResponse"/>
        </operation>
        <operation name="NotifyServerHoldCancellation">
          <output message="tns:HoldCancellationNotification"/>
        </operation>
      </portType>
      <binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
          <operation name="InitiateHold">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldModify">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldCancellation">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateStatusQuery">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
      </binding>
      <service name="TentativeHoldService">
        <documentation> Mythical Tentative Hold Web service</documentation>
        <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHold/"/>
        </port>
      </service>
      <service name="TentativeHoldNotificationService">
        <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHoldNotification"/>
        </port>
      </service>
    </definitions>

  • Error RSM006 "Attributes are not yet maintained"

    Hello everyone, I have had a problem with two infopackages,  one of them has the 0COORDER_TEXT datasource and the other 0COORDER_ATTR datasource. When I run the process chain with these infopackages, I have the error RSM006 "Attributes are not yet maintained", if I try to change these infopackages with the RSA1 I have the same error.
    Do you have any suggestion to solve this problem?
    Thank you very much.
    Best Regards
    Maximiliano Valin

    Thank you, I check your recommendation and I found everything ok, the 0COORDER is ok and active, and the tranfer rules are ok and active too, I don't know what other thing could be the problem.
    This is the help message that appear when the error happens.
    Attributes are not yet maintained
    Message no. RSM006
    Diagnosis
    The attributes have either not yet been created or activated.
    The data cannot be taken from the source system without maintained attributes. Therefore, this data request is not possible.
    Procedure
    Maintain the attributes for this master data-InfoSource in the Administrator Workbench and then activate them.
    Thank you for everything.

  • Temporary VO throws JBO-25058: Definition 0 of type Attribute is not found

    Hello,
    I'm working with ADF 11.1.1.5.
    I know that this error message usually indicates a misspelled attribute name.
    But my code ist this:ViewObject tVO = _myApplicationModel.createViewObjectFromQueryStmt(null,
                                "select count(1) as my_count from table where other_attr = ?");
    tVO.setWheresetWhereClauseParam(0, someValue);
    tVO.execureQuery();
    Object countReturned = tVO.first().getAttribute(0); // literal int 0 as indexThis code was working for several years. My SCM shows no differences to the last known working version.
    But today it started throwing oracle.jbo.NoDefException: JBO-25058: Definition 0 of type Attribute is not found in ViewDefImpl_189_190.
         at oracle.jbo.server.ViewRowImpl.getAttribute(ViewRowImpl.java:866)
         at my.package.MyApplicationClass.methodUsingTempVo(MyApplicationClass.java:lastLineInExample)
    ...How can this code fail at all?
    How do I solve this?
    bye
    TPD

    Alejandro Profet wrote:
    My fault, I read too fast :)at least you were quick... ;o)
    I suppose you check this before:Object countReturned = tVO.first().getAttribute("my_count");
    No. I did not expect this to work anyhow while accessing via index fails.
    BTW:
    Currently the error disapeaed.
    The only thing I did was to relaunche the application. I did not change any code. Neither I recompiled.
    I'm not a religious man but look's like I have sacrifice something to any good for this not happening in production. I'm thinking of an Oracle licence... ;o)
    bye
    TPD

  • Copy to Mac file Created Date uses iPhoto Modified not Original Date

    When a photo is edited in iPhoto the 'Extended Photo Info' 'Modified' date field is changed to the now() date and time but the 'Original' date iPhoto remains the same.
    Then when a copy is made of a photo in iPhoto and then 'Paste Item(s)' is made to the Mac desktop all the files dates default to the iPhoto 'Modified' date not the iPhoto 'Original Date'. Then if a sort by the 'Original Date' on the Mac is desired it will not happen unless the Created date file settings is changed for each photo copied to the Mac Desktop.
    How can photos in iPhoto be copied to the Mac Desktop with the 'Original Date' used in the Mac file 'Created' date field?

    when a copy is made of a photo in iPhoto and then 'Paste Item(s)' is made to the Mac desktop all the files dates default to the iPhoto 'Modified' date not the iPhoto 'Original Date'
    Where are you seeing this date?  In the Info window for the file with the Finder?  That's to be expected because those dates are the file dates, not the EXIF photo created and modified dates which can't be view by the Finder.  You will need to use a 3rd party EXIF view like  EXIF Viewer for Mac OS X .
    So don't confuse the EXIF date(s) with the file dates.
    OT

  • Synchronized modifier not allowed in interface

    My understanding of an interface is that it defines a contract. The synchronized modifier can be an important part of the contract. So why doesn't Java allow for declaring some methods of an interface to be synchronized?
    I just came across this again, let me try to illustrate:
    public
    interface IfcX
       void updateConsistently( double a, double b );
    }As Java doesn't let me specify synchronized in the interface, I introduce an abstract class where I can make the method synchronized:
    public
    abstract
    class someXBase
       public
       synchronized
       // Java does not let me make this an abstract method!
       void updateConsistently( double a, double b )
       { /* Java does not let me provide no body! */ }
    }This class still has a problem: I provided an empty body, while actually I did want to keep that method abstract. The empty body produces a potential for bad surprises for naive extenders of someXBase. The empty body violates the principle of "minimum surprise". If I forget to redefine the method in an extension of someXBase, then I'm in trouble. And it will be easy to forget when there are many methods like this.
    public
    class someX
    extends
       someXBase
       /* These attributes must not go into someXBase,
          as they belong to the concrete implementation only,
          not to the contract: */
       protected double _a ;
       protected double _b ;
       public
       synchronized
       void updateConsistently( double a, double b )
          synchronized (this)
             _a = a ;
             _b = b ;
    }someX is how it should be. Only one client can be inside updateConsistently at any time, and the implementation of updateConsistently makes sure that method only updates a and b when nobody else is reading or writing any of them.

    My understanding of an interface is that it defines a
    contract. The synchronized modifier can be an
    important part of the contract.
    So why doesn't Java
    allow for declaring some methods of an interface to be
    synchronized?I disagree. Synchronization is an implementation detail only.
    Thread safety however can be an important part of the contract, but the relevant part of the contract to specify that is in public documentation.
    This class still has a problem: I provided an empty
    body, while actually I did want to keep that method
    abstract. I fail to see why you have done this - anybody can override the method anyway and not declare it synchronized. If you want to make sure somebody overrides the method, then it can help to throw an exception by default (the most appropriate in such a case would be an UnsupportedOperationException),
    If you want client code to ensure thread safety, then document your code properly - If you provide an interface whose JavaDoc says "All methods are thread safe" or something similar, then anybody implementing the interface so that it is not thread safe has violated that contract. This is similar to providing documentation that says the draw method for a Shape, that takes a Canvas as a parameter, should draw the Shape on the Canvas - you have no way of forcing somebody to do that, so you rely on them conforming to the interface's contract (usually just its JavaDoc is enough).
    If you were to force client code to synchronize a particular method, then you would be dictating the implementation. You need to bear in mind somebody may be able to write the code so that it is thread safe without declaring a particular method synchronized (in fact, this will always be the case), and in that situation you may be causing undue contention (and thus slowing down execution) by forcing the method to be synchronized; You might also make it difficult to avoid deadlock if the implementor wants to synchronize on different objects.

  • Recon not happening

    Hi,
    I am new to OIM .I am trying to recon the details from a txt file to the process form field .Below is my code:
    import java.util.Hashtable;
    import java.io.*;
    import Thor.API.Exceptions.tcAPIException;
    import Thor.API.Exceptions.tcObjectNotFoundException;
    import Thor.API.Operations.tcReconciliationOperationsIntf;
    import com.thortech.xl.dataaccess.tcDataProvider;
    import com.thortech.xl.scheduler.tasks.SchedulerBaseTask;
    import com.thortech.xl.util.adapters.tcUtilXellerateOperations;
    public class Detrecon extends SchedulerBaseTask
         private String itResourceName;
         private String trustedSourceRO;
         String recondetails;
         long recKey;
         //Fetches the attributes from the task scheduler
         public void init()
              //itResourceName = getAttribute("Server");
              trustedSourceRO = getAttribute("Resource Object");
         //Performs reconcilliation using the api
         public void execute()     
              tcReconciliationOperationsIntf tcreconciliationoperationsintf = null;
                        String userDetails="";
              String recondetails="";
              try
              File file = new File("D://trial1.txt");
    int ch;
    StringBuffer strContent = new StringBuffer("");
    FileInputStream fin = null;
    fin = new FileInputStream(file);
    while( (ch = fin.read()) != -1)
    strContent.append((char)ch);
    userDetails=strContent.toString();
    fin.close();
    catch(FileNotFoundException e) {  
    System.out.println("File could not be found on filesystem");
    }catch(IOException ioe){ 
    System.out.println("Exception while reading the file" + ioe);
    try{
         tcreconciliationoperationsintf = (tcReconciliationOperationsIntf)getUtility("Thor.API.Operations.tcReconciliationOperationsIntf");
                        Hashtable<String,String> userDet =new Hashtable<String,String> ();
                        userDet.get(userDetails);//(recondetails,userDetails);
                        userDet.put(recondetails, userDetails);
                        recKey=tcreconciliationoperationsintf.createReconciliationEvent(trustedSourceRO, userDet, true);
              } catch (tcAPIException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
              } catch (tcObjectNotFoundException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
    recondetails is the field in the process form.
    I reading the details from the txt file as string buffer and changing into String.then storing the string in hashtable.
    But recon is not happening.please healp me.
    Thanks in advance.
    cats paw.

    hi,
    Sorry for the late reply
    I am getting the below error:
    ERROR,08 Mar 2011 16:15:12,939,[XELLERATE.SCHEDULER.TASK],Class/Method: SchedulerBaseTask/run encounter some problems: {1}
    java.lang.NullPointerException
         at java.util.Hashtable.put(Hashtable.java:595)
         at com.anz.Recon.Detrecon.execute(Detrecon.java:74)
         at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
         at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
         at java.security.AccessController.doPrivileged(AccessController.java:214)
         at javax.security.auth.Subject.doAs(Subject.java:495)
         at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:118)
         at Thor.API.Security.LoginHandler.websphereLoginSession.runAs(Unknown Source)
         at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
         at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
         at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)

  • Navigation Attribute is not getting displayed as in Masterdata Table

    Hi All,
    I have an infoobject "YDOCUMENT" compoundedd with "S_ORD_ITEM". Also i have added few attribute (Reason for rejection and Order Status) for the same. This infoobject is getting updated through data load from Sales Order Item level DSO and it will contain the Reason for rejection and ORder Status for each Sales ORder and item combination.
    After performing the data load i am able to see the attribute successfully getting updated into the master data table as expected, But when i run the Bex report and disply these Attributes as Nivugational Attributes, I am gettign the value as "Unassigned, and i am getting the proper result from the infoobject master data table.
    Can anyone give me any idea why this is happening? How we can i fix this issue?
    Thanks,
    Muruganand.K

    Hello All,
    The issue is due to the SID generation failure for the Attribute, This didnt happen properly because i am inserting the records into the infoobject during the data load to another DSO.
    Now i am doing a Direct data load to the infoobject to update the attribute this is solving the issue.
    Regards,
    Muruganand.K

  • View attributes can not be retrieved. View instance not found or undefined

    Hi,
    I am creating a simple master detail OAF page. For this I have done following steps:
    1. Created ParentEO and ChildEO
    2. Created ParentVO with a transient attribute called "SelectFlag" with default value "Y" .
    3. Created ChildVO
    4. Created a UserViewLink.
    5. Created Application module (UserAM).
    6. New Page UserPG
    7. In the main region I have defined Application Module.
    8. Under the main region, I have created a new advanced table region with following properties:
    View Instance : ParentVO1
    Detail View Attribute : SelectFlag
    View Link Instance: UserViewLink.
    Now when I click to select the "Child View Attribute", it gives a pop up saying "View attributes can not be retrieved. View instance not found or undefined".
    Please help, I am not able to proceed on this.
    Thanks,
    Anupam

    Anupam,
    I do not see in your steps where you associated the VO with the AM. In order to select an attribute, the AM must have an instance of the VO associated with it. Double click the AM in the navigator. Click Data Model and shuttle the VO's you want to be available from the left to the right.
    Hope this helps.
    Kristofer

  • Master Data Attribute is not getting reflected in the Cube?

    Hi All,
    I have loaded the data from ODS to the cubes for customer master and it contains a lot of navigational attributes
    for instance :
    master data for customer in development is
    customer   customer group 5(nav attributes)  Customer pricing group
    1001           HAW                                                         IE
    And hence when i load the customer 1001 from the ods to the cubes i can see the customer contains navigtional attributes for customer pricing group but CUSTOMER GROUP5 doesnt gets displayed in the cube.
    I check the master data it contains the values for customer group. How to Rectify this issue?
    Pls advise me!!
    Thanks
    Pooja

    hi all,
    I have explicity clicked on the navigational attributes in the cube i can see the values for the other navigational attributes being displayed in the cube for customer master but then only one navigational attribute is not getting displayed.
    For instance
    customer, customer gp2, customer grp5
    100, nr, nv
    only customer grp5 is not getting displayed which has values in the master data but then customer grp2 along with customer is getting displayed.
    Thanks
    Pooja

  • When I try and play music on my iPhone downloaded from iTunes it says 'this URL is not found on this server'. This does not happen when I play the same music through my iPad. Can anyone help?

    When I try to play music downloaded from itunes on my iPhone 4S it says 'this URL is not found on the server'. This does not happen when I play the same music on my iPad. The music plays fine. The message also comes up when I try and login to iTunes on my iMac. Can anyone help?

    I too am having the same issue as the OP.
    Your USER AGENT information is Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.3.18 (KHTML, like Gecko) Version/8.0.3 Safari/600.3.18
    Every webserver that receives a request from your browser is able to determine the HTTP USER AGENT information unless it has been removed by some software (e.g. firewall) before the request was trasmitted.

Maybe you are looking for

  • Follow up doc in R/3 using action profile

    Hi   1)How to create a follow up doc i.e billing doc in r/3 for sales order created in crm?    2) How to create a New Tab Using EEWB for Marketing campaign? its showing only basic data,channels... Regards, sanjana

  • Flat File Destination: Broken Rows

    I am exporting data to a csv file. One of the columns has values with so mixed characters which end up confusing the system and breaking the rows before the real end of the row. What I mean is; on the flat file a resultant single row can be broken do

  • Converting visio to pdf, bullet points disappear

    I'm having issues converting a MS Visio document into a pdf.  In my document I have text boxes that use the standard bullets in MS Visio.  When I convert the file to pdf using the distiller or the converter icon, the bullets will 'disappear' from the

  • NAC Framework with 802.1x authentication

    I am having trouble getting support and information on NAC framework. According to the cisco web NAC framework is in Phase 2 and is useable. According to Cisco representitives it is not supported yet. I have ACS 4.1, CTA 2.0, Symantec 10.1.4, and CSA

  • Sky (UK) Hub and Time Capsule

    I have been using a Time Capsule for a couple of years, with wired ADSL and a wired connection to my iMac, with Wifi for iPhones in the home. No prospect of getting Fibre anytime soon, so switched ISP to Sky which is the only LLU provider locally and