This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SAPHR driver for 4.5


getting this error when trying to run the JCO3Test. Notice that this
comes from the documentation.

I am not able to find the sapshim.jar file anywhere. I don't see it on
the 4.5 ISO or in a patch. I only find the saphrshim.jar


8.3.1 com/sap/conn/jco/ext/DestinationDataProvider Exception
This error occurs when the SAP Java Connector sapjco3.jar file or the
JCO native support libraries are not present or are improperly located.
Ensure the proper platform version of sapjco3.jar is located in the same
directory as SAPShim.jar. Also check the JCO native support libraries to
ensure they are present and properly configured. Use the JCO3
installation instructions for the appropriate platform.

thanks,
Fred


--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.netiq.com/member.php?userid=9869
View this thread: https://forums.netiq.com/showthread.php?t=53921

Parents
  • 0  
    On 7/23/2015 8:14 PM, fp IDMWORKS wrote:
    >
    > getting this error when trying to run the JCO3Test. Notice that this
    > comes from the documentation.
    >
    > I am not able to find the sapshim.jar file anywhere. I don't see it on
    > the 4.5 ISO or in a patch. I only find the saphrshim.jar
    >
    >
    > 8.3.1 com/sap/conn/jco/ext/DestinationDataProvider Exception
    > This error occurs when the SAP Java Connector sapjco3.jar file or the
    > JCO native support libraries are not present or are improperly located.
    > Ensure the proper platform version of sapjco3.jar is located in the same
    > directory as SAPShim.jar. Also check the JCO native support libraries to
    > ensure they are present and properly configured. Use the JCO3
    > installation instructions for the appropriate platform.


    I think saphrshim is correct.

    Error is when JCO is not correct on RL server.

    There is a native library and the sapjco.jar. If you execute the
    sapjco.jar the default class is a JCO tester.

  • 0   in reply to   
    On 7/24/15 5:35 AM, Geoffrey Carman wrote:
    > On 7/23/2015 8:14 PM, fp IDMWORKS wrote:
    >>
    >> getting this error when trying to run the JCO3Test. Notice that this
    >> comes from the documentation.
    >>
    >> I am not able to find the sapshim.jar file anywhere. I don't see it on
    >> the 4.5 ISO or in a patch. I only find the saphrshim.jar
    >>
    >>
    >> 8.3.1 com/sap/conn/jco/ext/DestinationDataProvider Exception
    >> This error occurs when the SAP Java Connector sapjco3.jar file or the
    >> JCO native support libraries are not present or are improperly located.
    >> Ensure the proper platform version of sapjco3.jar is located in the same
    >> directory as SAPShim.jar. Also check the JCO native support libraries to
    >> ensure they are present and properly configured. Use the JCO3
    >> installation instructions for the appropriate platform.

    >
    > I think saphrshim is correct.
    >
    > Error is when JCO is not correct on RL server.
    >
    > There is a native library and the sapjco.jar. If you execute the
    > sapjco.jar the default class is a JCO tester.
    >


    You are correct, the JCO3 libraries are not supplied with the driver
    they are supplied by SAP, and should be installed and configured separately.

    Casper
Reply
  • 0   in reply to   
    On 7/24/15 5:35 AM, Geoffrey Carman wrote:
    > On 7/23/2015 8:14 PM, fp IDMWORKS wrote:
    >>
    >> getting this error when trying to run the JCO3Test. Notice that this
    >> comes from the documentation.
    >>
    >> I am not able to find the sapshim.jar file anywhere. I don't see it on
    >> the 4.5 ISO or in a patch. I only find the saphrshim.jar
    >>
    >>
    >> 8.3.1 com/sap/conn/jco/ext/DestinationDataProvider Exception
    >> This error occurs when the SAP Java Connector sapjco3.jar file or the
    >> JCO native support libraries are not present or are improperly located.
    >> Ensure the proper platform version of sapjco3.jar is located in the same
    >> directory as SAPShim.jar. Also check the JCO native support libraries to
    >> ensure they are present and properly configured. Use the JCO3
    >> installation instructions for the appropriate platform.

    >
    > I think saphrshim is correct.
    >
    > Error is when JCO is not correct on RL server.
    >
    > There is a native library and the sapjco.jar. If you execute the
    > sapjco.jar the default class is a JCO tester.
    >


    You are correct, the JCO3 libraries are not supplied with the driver
    they are supplied by SAP, and should be installed and configured separately.

    Casper
Children
  • 0   in reply to   
    On 7/24/2015 7:38 AM, Casper Pedersen wrote:
    > On 7/24/15 5:35 AM, Geoffrey Carman wrote:
    >> On 7/23/2015 8:14 PM, fp IDMWORKS wrote:
    >>>
    >>> getting this error when trying to run the JCO3Test. Notice that this
    >>> comes from the documentation.
    >>>
    >>> I am not able to find the sapshim.jar file anywhere. I don't see it on
    >>> the 4.5 ISO or in a patch. I only find the saphrshim.jar
    >>>
    >>>
    >>> 8.3.1 com/sap/conn/jco/ext/DestinationDataProvider Exception
    >>> This error occurs when the SAP Java Connector sapjco3.jar file or the
    >>> JCO native support libraries are not present or are improperly located.
    >>> Ensure the proper platform version of sapjco3.jar is located in the same
    >>> directory as SAPShim.jar. Also check the JCO native support libraries to
    >>> ensure they are present and properly configured. Use the JCO3
    >>> installation instructions for the appropriate platform.

    >>
    >> I think saphrshim is correct.
    >>
    >> Error is when JCO is not correct on RL server.
    >>
    >> There is a native library and the sapjco.jar. If you execute the
    >> sapjco.jar the default class is a JCO tester.
    >>

    >
    > You are correct, the JCO3 libraries are not supplied with the driver
    > they are supplied by SAP, and should be installed and configured
    > separately.


    We had a guy at an AT