Error in Importing PAR file in NDWS
HI Gurus,
I am trying to import a PAR file in NWDS, but it is showing an error. below is the screenshot
after pressing ok below is the screenshot for error
here the project is being created but the coding part is not coming.
help me.
Hello,
First Check Error Long. That path is alredy given by Govardan.
at the same time. please reffer these 2 threads
http://scn.sap.com/thread/2024115 and http://scn.sap.com/thread/2069456
Similar Messages
-
Error while importing PAR file from local system.
Hi Experts,
While importing PAR file into my NWDS, I am encountered by some strange error.
Please refer below screenshot for your reference.
After clicking on "OK" button of the above error popup, another popup emerge with different error, please find below the screenshot for this error.
Please let me know the reason and resolution of this error. It will be very helpful for me.
Thanks in advance.
Thanks and Regards,
sarvesh AgarwalHi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks, -
Error while importing par file
dear Experts,
i am facing a problem while importing par.bak file. the error message comes
"indexed store transactions did not commit properly"
Reason
sorry an error occurred creating new project
then once i click ok
i get the error
com.sap.portal.plugins.config-archiver caused exception during the "unpack" operation
any one has the solution for thisHi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks, -
Error after importing PAR file into NWDS
Hi Experts,
I have imported a par file into my NWDS worlspace . While building the project it's giving the following error .
import javax.servlet.http.HttpServletResponse can't be resolved .
While i am organizing the importa , the same import is getting deleted and i am getting a new error as follows .
The project was not built since its classpath is incomplete. Cannot find the class file for javax.servlet.http.HttpServletRequest. Fix the classpath then try rebuilding this project.
jdk1.5 has been configured correctly inside NWDS and i have tested it also .
Can anybody help me out regarding this .
Thanks in advance .Hi Jain,
Just right click on project to properties->java build path-> add external jars add the jar file servlet.jar.
Venkat. -
Error while importing .par file into NWDS
Hi Experts,
For my query I saw a similar thread in sdn forum. the link is given below.
/thread/382306 [original link is broken]
I have unzipped the par file and inside this there is no other par file. So I have to import this par file only.
Can anybody give some alternate way to resolve this.
Thanks a lot in advance.
Edited by: Srini on Nov 22, 2010 10:46 PMHi Experts,
Please reply on this.
Thanks a lot in advance. -
Error occuring during importing .par file
Hi all,
I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from System administration>Support->Portal Runtime->Browse Deployement. I have locally saved this file on C:\temporary. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import-->Par file. But its giving me this error:
error in opening zip file
Reason: Sorry, an error occured creating the new project.
The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
"Unpack" Operation See log for more details.
However, in my package explorer in NWDS I can see a project created and with the structure. But in Portal-INF I cant see seven jsp files and four text files which comprises of basic functionality of the Logon Page.
Can anyone suggest me a solution to this?
Regards,
Priyanka.Hi,
After renaming com.sap.portal.runtime.logon.par.bak to com.sap.portal.runtime.logon.par. Try opening the file with winrar/winzip to see if you have a right par file structure. On some portal versions, when you open com.sap.portal.runtime.logon.par file, you have again a com.sap.portal.runtime.logon.par file inside it.
So if you find com.sap.portal.runtime.logon.par file inside com.sap.portal.runtime.logon.par. Then just extract it again and try importing it into NWDS.
Greetings,
Praveen Gudapati
[Points are always welcome for helpful answers] -
Error While uploading PAR File into NWDS
Hi Experts,
I have been to this location:
Server(D)\usr\sap\P64(SID)\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
I have copied this file com.sap.portal.runtime.logon.par.bak and pasted on my desktop.
Changed the name to com.mycompany.portal.runtime.logon.par
I tried to upload the file to NWDS(File --> Import --> Par file) and I am getting the fallowing error.
http://imageshack.us/photo/my-images/853/error1un.png/
and when i click OK on above Error
i get this errors : http://imageshack.us/photo/my-images/571/error2v.png/
I am unable to upload the Par file did i miss something?
Regards,
SivaDear Siva,
that is indeed strange.
Still don't know if this could be an issue with your NWDS or the PAR itself.
So let's do 2 tests
===============================================
TEST NR. 1
Let's try and check the NWDS first by creating a custom PAR.
Don't worry, it's easy.
Just open your NWDS and go to the top menu
File > New > Project
Inside the popup window that will open please choose
Portal Application (on the left) and Create a Portal Application Project (on the right)
Then give any name you would like (no spaces or dots, etc...)
You now have a Portal project created on NWDS ( you will see a folder on the left side with your project name)
Click on that folder with your LEFT mouse button and choose EXPORT
Choose PAR File
Choose your Project
Choose a path where you want your PAR file to be saved. (uncheck the deploy PAR file, but check the include the source code).
And click Finish.
Now delete the project you have created (by clicking on the folder with your LEFT mouse button again, but chose DELETE project)
Now you're ready to re-import the PAR file.
===============================================
TEST NR. 2
Maybe your standard PAR file that you've downloaded doesn't have the source code included or is corrupted.
Please try to open it with a ZIP program and check what type of structure/files you have there.
Have you also checked your NWDS log ?
You could also share here that log, so that I can better help you.
Kindest Regards
/Ricardo -
Error: An error occurred importing the file. Detail: File does not exist or
Hi,
I am getting the error the below error while importing the file in FDM. I have read and write access to the folder. I tried loading text and excel files, I am getting the same error.
An error occurred importing the file.
Detail: File does not exist or access denied.
Thanks.Hi Tony,
Thanks for the reply.
I have Oracle Database and the version is 11.1.0.7; So even for this version do I need to have SQLLDR.exe on the server where FDM is installed.
Thanks,
Edited by: user10720012 on May 16, 2011 11:42 AM -
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 swf file in to Crystal Xcelsius Designer 4.5
help me...., Error while importing swf file in to Crystal Xcelsius Designer 4.5
I read in the book called "CRYSTAL XCELSIUS for DUMMIES" on page 243 under topic called Nesting a Dashboard within another Dashboard.
sorry i used the wrong word embed, here i am importing the swf using image component.
My requirement is somethis like this parent child dependency menu.
eg: i have to two tabs 1)alphabets 2) Numerics First levet menu
if you click alphabets tab then the following menu A/B/C/D/..... Z i have diff charts.. under each alphabet.
If you click numberic tab then the follwing menu should one/two/three/.......ten here also i have diff charts under number
in over to avoid complexity in dynamic visibility i divided the into 3 dashboards. 1- alphabets 2- number and 3 -importing both swfs.. everything works fine except first tab and last tab under alphabets and numerics.
If some one help me with some alernative ... would be great.
Thanks -
Error while importing zip file for second time to B2B through ant script
[echo] args=import
importstatus:
[echo] Commandline arguments 1: [import]
[echo] Import with overwrite=true
[echo] B2BCommandLineUtility: importRepository: Error messages:
[echo] MDS-00521: error while reading document /soa/b2b/tpa_JOvrtiV-7030143
019445112136.xml from metadata repository
[echo] MDS-00520: failure to read document /soa/b2b/tpa_JOvrtiV-70301430194
45112136.xml because it is not in the metadata repository
[echo] MDS-00911: Document with name "/soa/b2b/tpa_JOvrtiV-7030143019445112
136.xml" and version 16 does not exist in the repository.
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo]
Can anybody plz help???
Thanks in Advance!!!Hi,
Even I am getting the same error while importing the .zip file for the second time through B2B console-->Administration-->Import/export tab.
But again it works for the third time..
Error Message:
Import of file OriginalProject.zip failed. MDS-00521: error while reading document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml from metadata repository MDS-00520: failure to read document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml because it is not in the metadata repository MDS-00911: Document with name "/soa/b2b/tpa_MnjhBHh-70301432125893445241.xml" and version 34 does not exist in the repository. ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1
Please help... -
Error while Importing MDL File
Hi All,
While Importing a MDL File, I am getting the following Error. Can someone help me asap.
mport started at Apr 6, 2010 10:20:09 AM
Project "PUBLIC_PROJECT"
Error occurred importing from file "C:\oracle\product\10.2.0\db_2\owb\bin\admin\ETLDEV-20100405_2210.mdl".
oracle.wh.util.Assert: Repository Connection Error: The connection to the repository was lost, because of the following database error: Closed Connection Exit OWB without committing.
at oracle.wh.util.Assert.owbAssert(Assert.java:51)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:186)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:156)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:152)
at oracle.wh.util.SQLExceptionHandler.handle(SQLExceptionHandler.java:65)
at oracle.wh.repos.pdl.lock.OracleLock.release(OracleLock.java:153)
at oracle.wh.repos.pdl.lock.OracleLockOptimizer.unlock(OracleLockOptimizer.java:138)
at oracle.wh.repos.pdl.lock.LockOperation.execute(LockOperation.java:90)
at oracle.wh.repos.pdl.lock.LockOperationSet.execute(LockOperationSet.java:51)
at oracle.wh.repos.pdl.lock.LockMaster.downgradeToExclude(LockMaster.java:222)
at oracle.wh.repos.pdl.lock.LockMaster.destroyLockHolder(LockMaster.java:199)
at oracle.wh.repos.pdl.lock.RequestToHolderMap.endRequest(RequestToHolderMap.java:83)
at oracle.wh.repos.pdl.lock.RequestToHolderMap.closeFolderForCreate(RequestToHolderMap.java:39)
at oracle.wh.repos.pdl.lock.LockModuleImpl.closeFolderForCreate(LockModuleImpl.java:61)
at oracle.wh.repos.pdl.dispatcher.EventDispatcherImpl.closeFolderForCreate(EventDispatcherImpl.java:174)
at oracle.wh.repos.pdl.metadataloader.Import.MDLLockManager.releaseMDLImportLocks(MDLLockManager.java:456)
at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.releaseImportLocks(MDLImport.java:1531)
at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1981)
at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.internalRunImport(MDLUpgradeImportTransaction.java:218)
at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.run(MDLUpgradeImportTransaction.java:319)
Thanks,
SMDid the instance go down whilst doing this?
Is there more to the log before where you started it?
Cheers
David -
Import .par file into NWDS and Rum it without deploying ?
Hello All,
I'm new to the NWDS and the Portal.
I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
Is this the right forum to place my Query ?
If not then please let me know the right forum .
My Requirement is like this :-
1. I need to create a Portal Application which calls an URL.
2. But before developing this, my Client gave me one 2 options :
a. He gave me a par file and asked me to make changes in it.
b. Create a new Portal Project which calls the URL ( Predefined ).
3. I wanted to check the 1rst option i.e " a ".
4. I tried to Import the .par file into NWDS like this :
* Windows --> Open Perspective --> Enterprise Portal .
* File --> Import --> Par FIle.
* I gave the name of the Project as PortalLogon.
5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
<b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
<b>B. How to test my PortalLogon Project without deploying ?</b>
Is it possible to test this Project without deploying ?
If yes can anyone tell me hoe to do this ?
Regards,
Deepu.KHi Deepu,
Usually Server will be having all the jar files and If you want to deploy your par file using NWDS you need to give a path to your Jar file location.
So better download all the jar files from your server and keep it in your local desktop.
Create a new folder called "JarFiles" in your desktop and keep all of your jar files inside.
Download Jar finder from IBM Site ( search for "Resolving Java Classpath Issues" in SDN ,you will get a pdf and follow it.).Add it as a plugin to your NWDS path.
Restart NWDS.
Now you can resolve the jar file issues.there are many weblogs /articles/forum QAs regarding this.
If u need more clarification,please let me know.
Thank you.
Regards,
Karthick Eswaran -
Import .par file into NWDS and Run without deployment ?
Hello All,
I'm new to the NWDS and the Portal.
I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
My Requirement is like this :-
1. I need to create a Portal Application which calls an URL.
2. But before developing this, my Client gave me one 2 options :
a. He gave me a par file and asked me to make changes in it.
b. Create a new Portal Project which calls the URL ( Predefined ).
3. I wanted to check the 1rst option i.e " a ".
4. I tried to Import the .par file into NWDS like this :
* Windows --> Open Perspective --> Enterprise Portal .
* File --> Import --> Par FIle.
* I gave the name of the Project as PortalLogon.
5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
<b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
<b>B. How to test my PortalLogon Project without deploying ?</b>
Is it possible to test this Project without deploying ?
If yes can anyone tell me hoe to do this ?
Regards,
Deepu.Khi Deepu,
for simply displaying a URL, you can use the commonly available URL iView.
your folder->new->create iView->iView from template->URL iView and then enter your URL
for the other think.......
you can create an iView from PAR file.
your folder->new->create iView->Iview from PAR->then select your PAR and create an iView for that.
and the last one.......to see the effect without deploying it on the portal......refer the link
http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
and the usual libraries to be associated are
<b>htmlb.jar</b> and
<b>com.sap.portal.htmlbbridge.zip</b>
Cheers........ -
An error occured importing the file
Hello,
We are currently experiencing an issue with Importing a file that contains the Japanese Kanji character set.
The error received is "Error - An error occured importing the file"
The Kanji characters are only for the Descriptions within the import file and WILL NOT be stored in the Oracle Database. I have enabled the East Asian lanaguages on the Windows 2k3 server but still get the error. Is there another setting the needs to be enabled or a 3rd party software that must be installed?
Any help would be appreciated.
Thanks
TonyHello,
It appears that you did not tell FDM to accept possible non ASCII characters.
To do this change the option in "Administration" -> "Configuration Settings" -> "File Encoding Type" to Unicode.
Keep in mind this will allow the parsing engine to accomidate additional characters. BUT, if the file is an ANSI type file that contains the characters and not a TRUE Unicode file, the characters will just now be skipped.
Thank you.
Maybe you are looking for
-
Unable to read podcast in a row
Hi, I just receive my ipod 30gb black. My system is windows xp pro SP2 and I use Itunes 7.0.1.8 and ipod software is 1.2. The problem I have is that I cannot read several podcasts in a row. In a list, I put some episode from my favorites podcast, and
-
Does the advanced queue support setting the pay load type as array/table?
Does the advanced queue support setting the pay load type as array/table? if yes, how to write the enqueue script, I tried to write the following the script to enqueue, but failed, pls help to review it . Thanks... ------Create payload type create or
-
Trying to find a way to remotely start mac after overheating
Hi. I'm involved in a school project building a solar powered kiosk for a park, and we're using an Intel Mac Mini for our system. Now, it gets pretty down there, and it's pretty much a guarantee that the Mac will shutdown due to overheating at some p
-
HT1589 is holding down shift not working for anyone else?
is holding down shift not working for anyone else?
-
Unable to access 14 day trial even though I've never had Playstation Plus
I started my account years ago on a ps3. When I signed in on my ps4 for the first time, it would not let me have a 14 day ps+ trial. I have never purchased ps+, and until about a week ago, had never even been a member of it. I was able to get a 2 day