Error while importing RFC schema
Hello Friends,
I am getting the following error while importing the RFC schema in Integration repository from SAP which is on ECC version.
The error I am getting is:
Unable to establish connection to R/3 system 10.238.52.79 (system=03, client=250) Troubleshooting tips:
Is the target system online?
Check the connection data (note that server names and groups are case-sensitive)
Tips for administrators (see the configuration guide for more details):
Does the user have the required authorizations in the target system?
Is the target system configured correctly in "etc/services"?
I checked the target system configuraion as well as user authorization. All the connection parameters are also correct.
Does anybody have idea about the solution to this problem?
Regards,
Nitin.
I had this problem before. I had to make an entry with SAPGW03 in my services file on the XI server. the entry should look like
sapgw03 3303
That resolved my problem. If you are working with a XI server on Windowns the file is located in <WINDOWS_DIR>\system32\driver\etc\ directory.
Thanks,
Kalyan Musunuri
OBT Global Inc.
Message was edited by: Kalyan Tej Musunuri
Similar Messages
-
Error while impoting XML schema format
Hi Experts,
I have successfully generated XSD schema from XML file by using third party tool but I was getting the below mentioned error while importing XML schema.Kindly suggest your ideas.
Error:Cannot Import metadata.
XML Parser failed:<invalid element name'xs:scehmaxmlns'> at line <2>,
char<>in file <\\sapbobjbi40\DS Files\Charan\ ZWY_SVCLAIMS_TO_WTYWAREHOUSE.xsd>. (BODI-1112338)
Regards,
RamCan you please share the XSD file ?
-
Error while importing an RFC from R/3
Hello,
I am getting the following error while importing an RFC from an R/3 system in the Repository:
***Ready for import***
Import started...
/XXX/YYY_CREATE_NOTIFICATION:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: PERMISSION_ERROR
Import failed with 1 error
Does any one know what is required? Is it missign authorizations on the R/3 side or on the XI side?
Thank you,
Sumant.Hi,
please check your User (used for importing RFC) authorizations,
it should have RFC authorization .
Thanks,
Madhav
Note: Points If Useful. -
Regd internal error while importing IDOCs and RFC's
Hi All,
Any idea, why i am getting internal error while importing RFX from ECC system to Dev system of PI.
It takes lots of time to import and many times it shows internal error.
I am able to login and select the RFC ... but all of sudden after selection ..the window gets freezed and i have to End task the IR part.
Is this a system error which only basis can fix?, have anyone faced similar issue.If yes please reply ..
Regards
SriniHi Srinivas
sevral times i faced this issue , ask your basis person , to increase the heap size a little more at XI server ,
and most of the time it happens due to Network down / connectivity .
take the help of your network team and basis team .
Regards
Abhishek -
Hi All,
I am getting the below error while importing an 10g dump on an 11g Database.
The command which i am executing is
C:\Users>impdp directory=TEST_DIR parallel=4 dumpfile=TEST_%U.dmp logfile=TEST.log schemas=TEST
The Error is :
ORA-39002: invalid operation
ORA-31694: master table "SYS"."SYS_IMPORT_SCHEMA_01" failed to load/unload
ORA-02354: error in exporting/importing data
ORA-02368: the following file is not valid for this load operation
ORA-02369: internal number in header in file H:\TEST\TEST_03.dmp is not valid
Which means TEST_03.dmp is not valid but when i am executing the same Import by using the below command
C:\Users>impdp directory=TEST_DIR parallel=4 dumpfile=TEST_01.dmp,TEST_02.dmp,TEST_03.dmp,TEST_04.dmp logfile=TEST.log schemas=TEST
Is Throwing an error as
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31619: invalid dump file "H:\TEST\TEST_04.dmp"
So i am confused that in previous command it was stating TEST_03.dmp is not valid and in above command it throwing error as TEST_04.dmp is valid.
Can anyone help me why there is such discrepencies in it while i am running the same commands.
Thanks
Snehasis.Hi,
I would think that all the files are 'bad' in some way but the command is just accessing the files in a different order when run in the two different ways. All the files have to be read at the initial phase of the import.
I think you'll likely find that if you change the order of the files in your second command the bad file will be reported as a different file - oracle often validates things from right to left.
The % option is probably ordering the files in some random sequence and it just so happened that TEST03.dmp was checked first.
The most likely cause of the error is that the files were transferred to the server in the correct ftp mode.
Cheers,
Harry -
Error while importing data into Oracle 11gr2 with arcsde 9.3.1
I am getting error while importing the data into oracle 11g r2. We are using arcsde 9.3.1
It seems to be having some problem with spatial index creation.
kindly help
IMP-00017: following statement failed with ORACLE error 29855:
"CREATE INDEX "A3032_IX1" ON "DGN_POLYLINE_2D" ("SHAPE" ) INDEXTYPE IS "MDS"
"YS"."SPATIAL_INDEX""
IMP-00003: ORACLE error 29855 encountered
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-13200: internal error [ROWID:AAAT5pAA9AACIy5AAQ] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
ORA-06512: at "MDSYSGuys,
I am also getting the same error and also my issue is like I am not even to analyze for which indexes I am getting error. It does not hve any indx name before error.
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX
ORA-39083: Object type INDEX failed to create with error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfer]
ORA-29400: data cartridge error
ORA-12801: error signaled in parallel query server P000
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-13200: internal error [ROWID:AA
ORA-39083: Object type INDEX failed to create with error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfer]
ORA-29400: data cartridge error
ORA-12801: error signaled in parallel query server P002
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-13200: internal error [ROWID:AA
ORA-39083: Object type INDEX failed to create with error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfer]
ORA-29400: data cartridge error
stack cnt....
How can I find for which indexes it is failing?
Thank you,
Myra -
Error while importing WSDL file created in JDeveloper inside BS
Hi All,
I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
The error in OSB is 'The Resource Mapped Does not exist'Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
Regards,
Anuj -
Error while importing .xml file in Datatype
Hi SDN,
I am getting this error while importing .xml file in Datatype.
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
Actually I have created datatype in my development box..
but my client doesn't want to develop in development box.
so i have exported that datatype as xsd from datatype editor.
and while importing into sandbox datatype editor i am getting this error..
Any help please......Hi Rajeev,
now i have an .xml file its not importing into datatype...
error is
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="DT_PLANNINGSCHEDULE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PlanningSchedule_Output">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PlanningScheduleHeader">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleIssueDate" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SchedulePurpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Purpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PurposeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SellerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipToParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Language">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LanguageCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationGroupedPlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Location">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BasePlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LineItemNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerLineItemNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemIdentifiers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNumbers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StandardPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProductIdentifier" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemDescription" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfItemReferences">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrimaryReference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Reference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RefNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForecastFrequencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CommitmentLevelCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleDates">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfDateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DateQualifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleQuantities">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfQuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityValue" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="UnitOfMeasurement">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UOMCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> -
Error while importing MS project into cProject
Hi
I am getting the below error while importing MS project client file or XML file into cProjects.
dpr_shared087
Logon language becomes original language
Message no. DPR_SHARED087
Diagnosis
The logon language is defined as a possible text language in Customizing for Collaboration Projects under Specify Text Languages. Therefore, it is valid.
System Response
The logon language becomes the original language of the new object that was created.
Kindly suggest what configuration data if any is missing.
Regards
SrikrishnaHi
I am getting the below error while importing MS project into cProject.
Error occurred when importing from Microsoft Project
Message no. DPR_UI_BSP116
Diagnosis
When a project is imported from Microsoft Project, the system generates an XML string during internal processing. A project is then created in cProjects from this string.
The XML string contains errors because the values from Microsoft Project were transferred without verification.
Procedure for System Administration
Notify SAP or call the cProjects application with the "DebugMode=X" query string and carry out the import again.
The XML string that was generated temporarily is then validated against the cProjects XML schema. The error message from the XML parser is then displayed in the popup.
Kindly suggest, if the below steps for importing MS project is ok or not?
step 1: Create project in MS project with tasks.
step 2: Maintain maping fields of MSP in cProject configurat
step 3: Import MPP file into cProject using "Import" button.
step 4: I am getting the above error while importing the MPP file.
Regards
Srikrishna -
Hi Team,
Getting below errors while import Please suggest.
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema ASID is needed to import this object, but is unaccessible
ORA-28031: maximum of 148 enabled roles exceeded
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'PAC', inst_scn=>'21502808296');COMMIT; END;
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-01031: insufficient privileges
ORA-06512: at "SYS.KUPW$WORKER", line 13249
ORA-06512: at "SYS.KUPW$WORKER", line 14900
ORA-06512: at "SYS.KUPW$WORKER", line 6293
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling KUPP$PROC.CHANGE_USER [PROCACT_SCHEMA:"ASI"]
ORA-06512: at "SYS.KUPW$WORKER", line 12280
ORA-01031: insufficient privileges
ORA-06512: at "SYS.KUPW$WORKER", line 5288
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema ASIF is needed to import this object, but is unaccessible
ORA-28031: maximum of 148 enabled roles exceeded
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'PAC', inst_scn=>'21502808296');COMMIT; END;
ORA-06512: at "SYS.KUPW$WORKER", line 1342
ORA-06512: at line 2
Job "SYS"."SYS_IMPORT_FULL_01" stopped due to fatal error at 17:13:38
Thanks In advance.ORA-28031: maximum of 148 enabled roles exceeded28031, 00000, "maximum of %s enabled roles exceeded"
// *Cause: The user attempted to enable too many roles.
// *Action: Enable fewer roles. -
Hi,
I am getting following error while importing a WSDL file to siebel tool. It seems that
WSDL wizard is treating the XSD schema namespsace declaration as a schema import, and is trying to connect to the w3.org URL.
(Also this problem seems to be WindowsXp specific..as I am able to import the same WSDL file to other machine (having WindowsNT)
Can somebody help me on this.
===============Error Message=================================
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'FormsServiceService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'FormsService' can not be imported. PortType 'FormsService' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'renderHTMLForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderHTMLForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
The http://schemas.xmlsoap.org/wsdl/:operation 'renderPDFForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderPDFForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
The http://schemas.xmlsoap.org/wsdl/:operation 'renderForm' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderForm' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
The http://schemas.xmlsoap.org/wsdl/:operation 'renderPDFFormWithUsageRights' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderPDFFormWithUsageRightsResponse' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
The http://schemas.xmlsoap.org/wsdl/:operation 'processFormSubmission' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'processFormSubmission' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)
The http://schemas.xmlsoap.org/wsdl/:operation 'renderFormGuide' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'renderFormGuideResponse' in 'http://adobe.com/idp/services'.(SBL-EAI-08009)
XML schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-EAI-00247)Hi,
I think, This is a late answer but I want to reply to help other persons who can get this error. I copied from metalink.
The reason for the error is using of a proxy server (check Explorer > Tools > Internet Options > Connections, and click LAN Setting). One suggestion was to configure the settings to bypass the proxy server for the www.w3.org urls. r Instead used a dial up connection to avoid the proxy server, and was able to import the wsdl ok.
Regards. -
Errors while importing support
hello all,
I am getting following errors while importing support
packages Queue SPAMu2026
- Error in phase: CHECK_REQUIREMENTS
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code: 0232
- Error message: connect failed
I have checked the TPPRAM file, RFC connection and
it's normalu2026
I even changed the directory to /usr/sap/trans/bin and
executed command "tp connect <SID>" and same erroru2026
Return code: 0232
Also I tested the connectivity from STMS
RFC Link tp was started successfully
tp Version 340.15.02
DB Connect Link to database failed
Offline Call connect failed
any ideas? any suggestions? I really need help.
Jack LeeDear All:
the error still the same~
I excuted the R3trans -d and came out like below:
C:\Documents and Settings\dbsadm>R3trans -d
This is R3trans version 6.13 (release 640 - 24.04.09 - 13:43:00).
2EETW169 no connect possible: "DBMS = MSSQL --- SERV
ER = 'PRDTEST' DBNAME = 'DBS'"
R3trans finished (0012).
and here is the trans.log:
4 ETW000 R3trans version 6.13 (release 640 - 24.04.09 - 13:43:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 02.07.2005 - 15:36:52
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Sat Jul 02 15:36:55 2005 6991 0.006991
4 ETW000 [dev trc ,00000] db_con_init called 65 0.007056
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 183 0.007239
4 ETW000 [dev trc ,00000] Loading DB library 'dbmssslib.dll' ... 51 0.007290
4 ETW000 [dev trc ,00000] load shared library (dbmssslib.dll), hdl 0 1550 0.008840
4 ETW000 [dev trc ,00000] using "C:\usr\sap\DBS\SYS\exe\run\dbmssslib.dll"
4 ETW000 14 0.008854
4 ETW000 [dev trc ,00000] Library 'dbmssslib.dll' loaded 7 0.008861
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library dbmssslib.dll
4 ETW000 11 0.008872
4 ETW000 [dev trc ,00000] Version of 'dbmssslib.dll' is "640.00", patchlevel (0.266)
4 ETW000 492 0.009364
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library dbmssslib.dll
4 ETW000 9 0.009373
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library dbmssslib.dll
4 ETW000 19 0.009392
4 ETW000 [dev trc ,00000] New connection 0 created 75 0.009467
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 40 0.009507
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 36 0.009543
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse:
4 ETW000 10 0.009553
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 14 0.009567
4 ETW000 [dev trc ,00000] Thread ID:2320 3431 0.012998
4 ETW000 [dev trc ,00000] Thank You for using the SLOLEDB-interface 51 0.013049
4 ETW000 [dev trc ,00000] Using dynamic link library 'C:\usr\sap\DBS\SYS\exe\run\dbmssslib.dll'
4 ETW000 37 0.013086
4 ETW000 [dev trc ,00000] dbmssslib.dll patch info 117 0.013203
4 ETW000 [dev trc ,00000] patchlevel 0 112 0.013315
4 ETW000 [dev trc ,00000] patchno 266 8 0.013323
4 ETW000 [dev trc ,00000] patchcomment Batch jobs stay in Ready status (1291921)
4 ETW000 10 0.013333
4 ETW000 [dev trc ,00000] np:(local) connection used on PRDTEST 84 0.013417
4 ETW000 [dev trc ,00000] CopyLocalParameters: dbuser is 'dbo' 9 0.013426
4 ETW000 [dev trc ,00000] Using Provider SQLNCLI 12800 0.026226
4 ETW000 [dev trc ,00000] OpenOledbConnection: MARS property was set successfully.
4 ETW000 570 0.026796
4 ETW000 [dev trc ,00000] Provider Release:9.00.4035.00 54486 0.081282
4 ETW000 [dev trc ,00000] Using Provider SQLNCLI 3456 0.084738
4 ETW000 [dev trc ,00000] OpenOledbConnection: MARS property was set successfully.
4 ETW000 311 0.085049
4 ETW000 [dev trc ,00000] i'm dbo but there exists 1 users <> dbo with tables SVERS ==> connect terminated
4 ETW000 8298 0.093347
2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = 'PRDTEST' DBNAME = 'DBS'"
Regards
Jack Lee -
Error while importing music in iMovie 11 From itunes 10
Error while importing music in iMovie 11
I have the same error explained in a other post which was still left unanswered
I have this sound problem after reorganising folders by itunes, i tried to delete al files in itunes and also
deleted the xml file in the itunes dir, created new playlists, but still i have no music sound in imovie timeline
after dragging a mp3 into it. When i preview the file in imovie it souds ok.
Also i see the red dot with the number 1 in the itunes logo while dragging the mp3.
Is there a solution for this problem?
Former post;
Re: Error while importing music in iMovie 09 from iTunes 09
Posted: Jul 24, 2010 8:08 AM in response to: vincentplaces
I'm having the exact same issue, but still haven't figured out what it is. I note that at the top of this thread it indicates that there are two "helpful" entries and one "solved" entry, but I can't find the solved one, so maybe someone will repost it here or kindly link to it.
There is one icon missing though.
As I read through the excellent tutorial at http://www.kenstone.net/fcphomepage/imovie_09stone.html I scroll down to the point where he talks about dragging music in from iTunes, which is what I'm trying to do. I can see, in his screen shot, the extra little icon that is a red oval and a white "1" in it. I don't get that icon when I am trying to drag my music into the video. I do get the green and white plus icon when I try to drag my music in. Also I DO get BOTH the red 1 and the green plus when I try dragging in a sound effect, which I can do with no problem. But why not the music?
I've been able to drag in music with no problem in other productions, so I can't figure out what is going on with this one. I'm sure there is a setting somewhere that got flipped, but I can't figure out where.
In desperation I also tried adding an extra title slide at the end of my video just to make sure there is more video time than music time in the production, but that didn't help at all.
Any help guys?
iMac 27" Mac OS X (10.6.4)Hi
Due to some kind of copy protection in iTunes - I don't copy directly from this in iMovie
to my projects. (Most often the result of doing it in iMovie is a DVD without any sound)
I do
• In iTunes - collect needed audio into a new Playlist
• then burn this out as an Audio-CD .aiff (NOT .mp3)
• This CD I copy into a folder on my Mac (often containing other material that's connected to the project)
• And then I drag and drop these .aiff files into my movie project in iMovie.
This works Greatly and even more so when I do my DVD.
Yours Bengt W -
Error while importing a new CERT in oracle 10G B2B
Hi All,
I am trying to upload a new certificate in 10 G B2B server, its not updating a certificate, I am facing the below error while importing
Error
An error occurred when updating the certificate.
Error -: AIP-16001: The model validation engine failed due to an internal system error.
Error -: AIP-11052: Writing following objects: Certificate failed due to following constraint violation: CERTIFICATE. CAN NOT UPDATE UNVERSIONABLE OBJECT IN A VALIDATED CONFIGURATION.
Note: Please help me in resolving this ASAP.
Regards
SaiHi Sai,
It seems you are updating certificate in a delivery channel which is being used in a validated (or may be deployed) agreement. Please retire/purge any deployed configuration which is using that delivery channel and also make sure no such agreement is in valid state(which is using this delivery channel).
Regards,
Anuj -
Error while importing a table index.
Hi,
We are facing a problem while importing an index to the production region. Below are the details.
1. A secondary index was created on standard SAP table ILOA in DEV region.
2. The Index was successfully moved to the Quality system, without any glitches.
3. Due to some issue (releated to testing, for which we had to revert back the changes), we had to delete the index on ILOA in the DEV region. The transports were moved to the PPD region and hence, the index on ILOA was deleted in PPD also.
4. Once the issue related to testing was resolved, we again created an index on the table ILOA and moved it to PPD.
All these 4 mentioned steps happened successfully and in PPD there was no error while importing the transports.
But, while moving the above transports to the Production region, there was an error :
"Index ILOA~Y could not be activated
(E - No index ILOA~Y found with status M)"
Please note that Y is the name of the index that was created on the table ILOA.
The error code that we have got is "8".
Can anyone please shed any light on what the issue is?? WE cannot re-import the transports in to Production without analysing this issue,because our client doesnt permit that.
Thanks and eagerly awaiting a kind reply.
Regards,
Raghavendra.You've three transports - one to create the index, one to delete, and one to recreate. It could be that the the third one tried to run before the database had finished with the second?
Have you looked on SE14 for the actual status on production of the index?
matt
Maybe you are looking for
-
There are no readers registered for the txt type - Issue importing txt file
Hello guys, I am working on SQL developer 3.2. and Oracle database 11g. I am trying to import a txt file with only two columns and 100 rows separated with a pipe. I can import the same file if its in *.CSV or *.xls format. I right click on the table
-
In itunes it says i have 904 items but when i check setting in the ipod it says 883 songs 24 videos and 173 photos. I know the photos aren't included in the items, but im wpondering y the numbers don't match up no matter how much i update??
-
Music app is STILL a BETA. It's a joke! What is it doing in ios5?
Playlists frozen. Music frozen. Audiobooks not recognized. Where are the controls for audiobook playback speed ??? Didja forget that one guys ?? Buttons too small and not customizable ? Come on ! Lousy interface design. Is this supposed to be an im
-
CS6 Mac - cannot Save As tiff file
OS X 10.7.3 CS 6 Beta Open a raw file (CR2), not as smart object Edit Save (psd format is the default) Save As: same name, but choose tiff format Result: Save As dialogue adds "mpo" as an extension, and the next dialogue is one for JPGs. 1) loading
-
Multiple Images - is it supported - HELP SEEMS UNHELPFUL
Hi, I've got a content item that's supposed to hold 5 properties that happen to be images MyNode Mycontent image1 something,gif image2 somethingelse.gif image5 lastone.gif How do I display these images ? showBinary will only display one of these imag