`failed parsing crontab` error
Hi!
I made a script that downloads an image, and added it to crontab -e -u skazhy
like this:
* /10 * * * * /home/skazhy/script
But it does not complete and I get this error ir crond.log:
Mar 1 14:38:01 myhost crond[3077]: failed parsing crontab for user skazhy: /10 * * * * /home/skazhy/script
The script has no errors. I haven't used cron before, what's wrong here?
there is a typo in the crontab entry, a space between first asterisk and "/10"
it shuld be
*/10 * * * * <script>
Last edited by vik_k (2010-03-01 14:11:06)
Similar Messages
-
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing
Hi,
I am trying to update an already existing Sales Order through PO Change Inbound 860. When i am performing changes in the line quantity and scheduled ship date with operation code as "Update" then it is successfully updating the Order and also we are able to generate the POAck for the updated sales order lines. But when i am rejecting one of the PO change lines by checking rejected flag, then order is getting imported successfully(I mean sales order is getting updated successfully) but during the POAck Generation i.e. 865 its raising "*ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00103: Warning: document structure does not match DTD Error at line 1*" at XML Gateway. we are using XML Gateway to process the orders, can somebody help me to get rid of this issue. Thanks in advance.
Thanks,
Sunil ChauhanHi Kishan
Thanks for the reply.
Because this is an outbound transaction so i can not provide you the XML file as we are facing issue to generate the same. Also we are using oracle seeded PO outbound Ack map.
In addition i can provide you the DTD file.
<!-- ==================================================== -->
<!ENTITY % RESOURCES SYSTEM "oagis_resources.dtd">
%RESOURCES;
<!-- ==================================================== -->
<!ELEMENT ACKNOWLEDGE_PO_008 (CNTROLAREA, DATAAREA+)>
<!ATTLIST VERB
value CDATA #FIXED "ACKNOWLEDGE"
>
<!ATTLIST NOUN
value CDATA #FIXED "PO"
>
<!ATTLIST REVISION
value CDATA #FIXED "008"
>
<!ELEMENT DATAAREA (ACKNOWLEDGE_PO)
>
<!ELEMENT ACKNOWLEDGE_PO (POORDERHDR, POORDERLIN*)
>
<!ELEMENT POORDERHDR ((%DATETIME.DOCUMENT;)?, (%OPERAMT.EXTENDED.T;)?, POID, POTYPE, ACKREQUEST?, CONTRACTB?, CONTRACTS?, DESCRIPTN?, NOTES*, OPRAMTAUTH?, PORELEASE?, TAXWHEXMPT?, USERAREA?, ACKHEADER, ATTCHREF*, CHARGE*, PARTNER*, POTERM*)
>
<!ELEMENT ACKHEADER (SENDER, (%DATETIME.PROMDELV;)?, (%DATETIME.PROMSHIP;)?, ACKCODE, DESCRIPTN?, NOTES*, SALESORDID?, USERAREA?)
>
<!ELEMENT POTERM (DESCRIPTN?, TERMID?, ((DAYOFMONTH, PROXMONTH) | DAYSNUM), ((%OPERAMT.EXTENDED.T;) | (%QUANTITY.PERCENT;)), USERAREA?)
>
<!ELEMENT POORDERLIN ((%QUANTITY.ORDERED;), (%DATETIME.NEEDDELV;)?, (%OPERAMT.UNIT.T;)?, POLINENUM, DRAWING?, HAZRDMATL?, ITEMRV?, ITEMRVX?, NOTES*, PACKING?, POLNSTATUS?, TAXWHEXMPT?, ((DESCRIPTN, ITEM?, ITEMX?, UPC?) | (ITEM, ITEMX?, UPC?) | (ITEMX, UPC?) | (UPC)), USERAREA?, ACKLINE*, ATTCHREF*, CHARGE*, DISTRIBUTN*, PARTNER*, POTERM*, POSUBLINE*, POLINESCHD*)
>
<!ELEMENT ACKLINE ((%DATETIME.PROMDELV;)?, (%DATETIME.PROMSHIP;)?, (%QUANTITY.ORDERED;)?, ACKCODE, NOTES*, SALESORDID?, USERAREA?)
>
<!ELEMENT POSUBLINE ((%QUANTITY.ITEM;), DRAWING?, ITEMRV?, ITEMRVX?, PSBLINENUM?, ((DESCRIPTN, ITEM?, ITEMX?, UPC?) | (ITEM, ITEMX?, UPC?) | (ITEMX, UPC?) | (UPC)), USERAREA?)>
<!ELEMENT POLINESCHD ((%DATETIME.NEEDDELV;), (%QUANTITY.ORDERED;), DESCRIPTN?, PSCLINENUM?, USERAREA?)
>
Thanks,S
--Sunil -
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing L
Hi There,
I am trying to load XML data [Given Below] into a table using "Load XML Data" option.
<?xml version="1.0"?>
<ROWSET>
<ROW>
<ID>13</ID>
<TYPE_SEQ>8</TYPE_SEQ>
<TYPE>B749</TYPE>
<TYPE_DESC>B758</_TYPE_DESC>
<EFFECTIVE_FROM>2099-01-01</EFFECTIVE_FROM>
<EFFECTIVE_TO>2099-01-01</EFFECTIVE_TO>
<CREATED_BY>958344</CREATED_BY>
<CREATED_ON>2099-01-01</CREATED_ON>
<UPDATED_BY>172283</UPDATED_BY>
<UPDATED_ON>2099-01-01</UPDATED_ON>
</ROW>
</ROWSET>
It throws the following error.
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00222: error received from SAX callback function
Can any one advice the solution please.
-Sudheer.Hi Sudheer,
This is caused by the date format you are using. Probably it is not matching with your NLS settings. Check your NLS settings, what the date format is, and use that in the XML.
Check it with this code:
SELECT XMLELEMENT("date", sysdate) FROM dual;Make sure, you have your NLS_DATE settings in the same format.
Check it with:
SELECT * FROM v$nls_parameters WHERE parameter = 'NLS_DATE_FORMAT'And then make sure it is the same by setting for example:
ALTER SESSION SET NLS_DATE_FORMAT = 'YYYY-MM-DD';Greetings,
Rutger -
B2B-51566 Description: Parse stream error with RosettaNet 1.1
Hi
Need help with the following error message
B2B-51566 Parse stream error
We have a trading partner set up to use RosettaNet 1.1 protocol and we are getting 51566 error. We are NOT experiencing this error with a trading partner who is in RosettaNet 2.0
we are currently patched up to 11.1.1.5
One thing I notice is when i go to the message and open the packed message i get this "Cannot display Packed Message in binary format."
Here is the payload
XMessage-ID: <[email protected]d.e2open.com>
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_176_29725195.1331307008851";
type="Application/x-RosettaNet"
Content-Description: This is the RosettaNet Business Message
Content-ID: "-15059242:135f6ea5e3c:-62b9"
------=_Part_176_29725195.1331307008851
Content-Type: Application/xml; rnsubtype=preamble-header; name=Preamble
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename=Preamble
Content-ID: <[email protected]>
Content-Description: This is the Preamble Header part of the Business Message
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">
<Preamble>
<DateTimeStamp>20120309T153008.852Z</DateTimeStamp>
<GlobalAdministeringAuthorityCode>RosettaNet</GlobalAdministeringAuthorityCode>
<GlobalUsageCode>Production</GlobalUsageCode>
<VersionIdentifier>1.1</VersionIdentifier>
</Preamble>
------=_Part_176_29725195.1331307008851
Content-Type: Application/xml; rnsubtype=service-header; name=ServiceHeader
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename=ServiceHeader
Content-ID: <[email protected]>
Content-Description: This is the Service Header part of the Business Message
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ServiceHeader SYSTEM "ServiceHeaderPartMessageGuideline.dtd">
<ServiceHeader>
<ProcessControl>
<ProcessIdentity>
<description>
<FreeFormText>NotNull</FreeFormText>
</description>
<GlobalProcessCode>Request Purchase Order</GlobalProcessCode>
<GlobalProcessIndicatorCode>3A4</GlobalProcessIndicatorCode>
<initiatingPartner>
<GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
</initiatingPartner>
<InstanceIdentifier>PIPC0A85CB8135F814CB4200000EAFE56F0</InstanceIdentifier>
<VersionIdentifier>V02.00</VersionIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Seller Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</fromService>
<toService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Buyer Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</toService>
</ServiceRoute>
<TransactionControl>
<AttemptCount>1</AttemptCount>
<PartnerRoleRoute>
<fromRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</fromRole>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</toRole>
</PartnerRoleRoute>
<TransactionIdentity>
<GlobalTransactionCode>Request Purchase Order</GlobalTransactionCode>
<InstanceIdentifier>TIC0A85CB8135F814CB4200000EAFE5700</InstanceIdentifier>
</TransactionIdentity>
<SignalControl>
<inResponseTo>
<ActionIdentity>
<GlobalBusinessActionCode>Purchase Order Request Action</GlobalBusinessActionCode>
<InstanceIdentifier>C0A85CB8135F814C33C00000EAFE5670</InstanceIdentifier>
</ActionIdentity>
</inResponseTo>
<InstanceIdentifier>20120309T153008.882Z</InstanceIdentifier>
<PartnerRoute>
<fromPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>364132837</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
</PartnerDescription>
</fromPartner>
<toPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
</PartnerDescription>
</toPartner>
</PartnerRoute>
<SignalIdentity>
<GlobalBusinessSignalCode>Receipt Acknowledge</GlobalBusinessSignalCode>
<VersionIdentifier>1.1</VersionIdentifier>
</SignalIdentity>
</SignalControl>
</TransactionControl>
</ProcessControl>
</ServiceHeader>
------=_Part_176_29725195.1331307008851
Content-Type: Application/xml; rnsubtype=service-content;
name=ReceiptAcknowledgement
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename=ReceiptAcknowledgement
Content-ID: <[email protected]>
Content-Description: This is the Service Content part of the Business Message
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ReceiptAcknowledgement SYSTEM "ReceiptAcknowledgementMessageGuideline.dtd">
<ReceiptAcknowledgement>
<fromRole>
<PartnerRoleDescription>
<ContactInformation>
<contactName>
<FreeFormText>E2open Support</FreeFormText>
</contactName>
<EmailAddress>[email protected]</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>650-381-6000</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>364132837</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</fromRole>
<receivedDocumentDateTime>
<DateTimeStamp>20120309T153008.907Z</DateTimeStamp>
</receivedDocumentDateTime>
<receivedDocumentIdentifier>
<ProprietaryDocumentIdentifier>337719</ProprietaryDocumentIdentifier>
</receivedDocumentIdentifier>
<thisMessageDateTime>
<DateTimeStamp>20120309T153008.904Z</DateTimeStamp>
</thisMessageDateTime>
<thisMessageIdentifier>
<ProprietaryMessageIdentifier>20120309T153008.905Z</ProprietaryMessageIdentifier>
</thisMessageIdentifier>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</toRole>
</ReceiptAcknowledgement>
------=_Part_176_29725195.1331307008851--I do have SR but hoping i can get quicker answer hereYou may always escalate the SR if you are not getting response timely. Anyways, give the reference of this thread in the SR and ask service engineer to file a bug.
I will email you the wire messageI saw the wire message you mailed across. There are some junk characters in the starting of the payload and that's why parsing is failing. Most probably it is a BOM (Byte Order Mark). Ask your TP to send messages in UTF-8 encoding without BOM or any other junk character in the starting of the message. You may open the wire message payload you mailed across in notepad or textpad and you will able to see those junk characters in the starting of the payload.
Regards,
Anuj -
SCCM 2012 Export Task Sequence fails with generic error message
We have a complex task sequence comprising of more than 50 applications\packages, 1975 drivers, 18 driver packages etc etc. Its long, it's big and it will not export with it's content.
We have several environments for development test and live. I am attempting to export the primary task sequence with all it's dependencies from live so that I can port it over to a new development environment.
I can export the zip file without content and it comes to 92Mb in size. The entire task sequence software set is 50Gb+. When I attempt to export with all dependencies and content the process gets about 60% of the way through and fails with the error
"Error: The filename, directory name, or volume label syntax is incorrect"
Googling the error roughly defines the problem as 'the export process cannot access the defined source path for one of the dependant items'
I wrote a PowerShell script that looks as every application, package, driver, driver package, boot image, os image and software update package in the entire SCCM software library and verifies that each and every package has a valid UNC source directory
that can be reached using test-path.
I also wrote another tool that parsed the entire source software library on the server looking for permissions errors (permissions on the structure set at a directory level rather than inherited), directories that were too long, inaccessible or otherwise
blocked, nothing was found.
It will take a very long time to go through and check each and every dependency by hand - time I do not have at present.
I looked in the TaskSequenceProvider.log as that is supposed to contain messages from the export process and found the messages in there far too high a level to use
=======================
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:00:41.161-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.339-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
<![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:01:36.036-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="5592" file="wmiprovider.cpp:399">
<![LOG[[1AFF658 PID:3500] Initializing provider for namespace root\sms\site_P01]LOG]!><time="13:02:36.550-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068"
file="wmiprovider.cpp:90">
<![LOG[[1AFF658 PID:3500] Initialization of provider for namespace root\sms\site_P01 succeeded]LOG]!><time="13:02:36.551-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1"
thread="7068" file="wmiprovider.cpp:107">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.554-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.558-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:02:36.559-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.428-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
<![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:03:36.369-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:399">
====================
Is there any way of increasing the log verbosity? I need to see what item is causing the export to fail.
Is there another log containing the information about the export & what it is doing?
All out builds that use the task sequence complete successfully, we can edit the sequence fine, make changes etc. so no internal corruption we can find.
Any ideas?Torsten, smsprov.log did indeed prove useful, I could see every package as it was validated. Unfortunately the log was wrapping about every 4 minutes and it takes 3+ hours for the task sequence to reach the fail point so I still cannot see the offending
package as it wraps before I can get to the log.
I will increase the size of the log and see if I can maintain some details to investigate.
There was nothing of note in the event logs, certainly nothing leading me to suspect that WMI might be reaching its limits.
I will keep looking for the cause and will post here when I find it <= positive thinking :) -
Dreamweaver (CS5) stopped working. The error message says - XML parsing fatal error: Invalid document structure, line: 1, I tried to reload DW. No change. I also tried to reset the computer to an earlier date before I reloaded. Also didn't work. Can anybody shed some light?
The first thing to try is Deleting Corrupted Cache. Be sure to turn on Hidden Files & Folders in your file manager (Win Explorer or Mac Finder).
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
If all else fails, use the CC Cleaner Tools below to wipe DW from your system, followed by a software re-install.
http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
Keep us posted on your results.
Nancy O. -
DB 7.8 Restart fails with SQL error -9407, unexpected error 3
Hello,
MaxDB Instance (7.8.01.18) fails to restart with the error
"SQL error -9407 System error: unexpected error 3
Internal errorcode 6433 "system_error" 20017, Restart Filesystem failed with
'System error unexpected error'
9, File directory restart failed; error '3'
31, Error linking entry to parent; file no '000000004066',
parent file no '000000000000000000033D',
file type 'IndexFile', error '11'
We had the problem "[-8]: Execution failed, parse again" with one table,
then we tried to restart the database. Now it doesn't come up any more.
Is there another possibility instead of a recovery?
Greetings
UlrichYour problem description sounds very similar to the following error:
PTS1237652:
"Appearance:
Restart fails with file directory corruption:
31,Error linking entry to parent; file no 'xxx', parent file no 'yyy', file type 'IndexFile', error '11'
Preconditions and circumstances:
During a recreate index operation the index was dropped and recreated manually.
Workaround:
None. The system must be recovered to the time just before the index was recreated."
Please note that this is one of those issues that has only been fixed with 7.8.02. 7.8.02 is currently in customer testing, if anyone wants to join, just open a CSS message and test this version before we make it generally available for download.
Best regards,
Thorsten -
BUILD FAILED java.lang.Error: unable to load schema-for-schema for W3C XML
I am new to JAXB, I am trying to run the sample applciations on Win 98,
I have set up the environment values as per the UserGuide specs.
I am getting the following error:
BUILD FAILED java.lang.Error: unable to load schema-for-schema for W3C XML Schema at com.sun.msv.reader.xmlschema.XMLSchemaReader.getXmlSchemaForXmlSchema (XMLSchemaReader.java:190)
Could someone please suggest a solution.
Thank you.Hi
I am using Windows 2000 and I am repeatedly getting the same error too (See below). Would appreciate any help ..
parsing a schema...
org.iso_relax.verifier.VerifierConfigurationException
at com.sun.msv.verifier.jarv.FactoryImpl.compileSchema(FactoryImpl.java:104)
at org.iso_relax.verifier.VerifierFactory.compileSchema(Unknown Source)
at org.iso_relax.verifier.VerifierFactory.compileSchema(Unknown Source)
at com.sun.msv.reader.xmlschema.XMLSchemaReader.getXmlSchemaForXmlSchema(XMLSchemaReader.java:186)
at com.sun.tools.xjc.Driver$1.<init>(Driver.java:477)
at com.sun.tools.xjc.Driver.loadXMLSchemaGrammar(Driver.java:476)
at com.sun.tools.xjc.Driver.loadGrammar(Driver.java:404)
at com.sun.tools.xjc.Driver.run(Driver.java:268)
at com.sun.tools.xjc.Driver.main(Driver.java:88)
at sample1.Binder.main(Binder.java:18)
StackTrace of Original Exception:
java.lang.NullPointerException
at com.sun.msv.datatype.xsd.TypeIncubator.addFacet(TypeIncubator.java:64)
at com.sun.msv.reader.datatype.xsd.XSDatatypeExp$1.addFacet(XSDatatypeExp.java:87)
at com.sun.msv.reader.datatype.xsd.FacetState.startSelf(FacetState.java:56)
at com.sun.msv.reader.State.init(State.java:154)
at com.sun.msv.reader.GrammarReader.pushState(GrammarReader.java:579)
at com.sun.msv.reader.datatype.xsd.TypeState.startElement(TypeState.java:101)
at org.xml.sax.helpers.XMLFilterImpl.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:459)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221)
at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:874)
at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:591)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:747)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at com.sun.msv.reader.GrammarReader._parse(GrammarReader.java:459)
at com.sun.msv.reader.GrammarReader.switchSource(GrammarReader.java:434)
at com.sun.msv.reader.GrammarReader.switchSource(GrammarReader.java:407)
at com.sun.msv.reader.xmlschema.XMLSchemaReader.switchSource(XMLSchemaReader.java:683)
at com.sun.msv.reader.xmlschema.ImportState.startSelf(ImportState.java:41)
at com.sun.msv.reader.State.init(State.java:154)
at com.sun.msv.reader.GrammarReader.pushState(GrammarReader.java:579)
at com.sun.msv.reader.SimpleState.startElement(SimpleState.java:72)
at org.xml.sax.helpers.XMLFilterImpl.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:459)
at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:877)
at org.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:569)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:759)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at com.sun.msv.reader.GrammarReader._parse(GrammarReader.java:459)
at com.sun.msv.reader.GrammarReader.parse(GrammarReader.java:449)
at com.sun.msv.reader.xmlschema.XMLSchemaReader.parse(XMLSchemaReader.java:89)
at com.sun.msv.verifier.jarv.XSFactoryImpl.parse(XSFactoryImpl.java:26)
at com.sun.msv.verifier.jarv.FactoryImpl.compileSchema(FactoryImpl.java:95)
at org.iso_relax.verifier.VerifierFactory.compileSchema(Unknown Source)
at org.iso_relax.verifier.VerifierFactory.compileSchema(Unknown Source)
at com.sun.msv.reader.xmlschema.XMLSchemaReader.getXmlSchemaForXmlSchema(XMLSchemaReader.java:186)
at com.sun.tools.xjc.Driver$1.<init>(Driver.java:477)
at com.sun.tools.xjc.Driver.loadXMLSchemaGrammar(Driver.java:476)
at com.sun.tools.xjc.Driver.loadGrammar(Driver.java:404)
at com.sun.tools.xjc.Driver.run(Driver.java:268)
at com.sun.tools.xjc.Driver.main(Driver.java:88)
at sample1.Binder.main(Binder.java:18)
java.lang.Error: unable to load schema-for-schema for W3C XML Schema
at com.sun.msv.reader.xmlschema.XMLSchemaReader.getXmlSchemaForXmlSchema(XMLSchemaReader.java:190)
at com.sun.tools.xjc.Driver$1.<init>(Driver.java:477)
at com.sun.tools.xjc.Driver.loadXMLSchemaGrammar(Driver.java:476)
at com.sun.tools.xjc.Driver.loadGrammar(Driver.java:404)
at com.sun.tools.xjc.Driver.run(Driver.java:268)
at com.sun.tools.xjc.Driver.main(Driver.java:88)
at sample1.Binder.main(Binder.java:18)
Exception in thread "main"
-Thanks
Guna -
7.3.0 -8 Execution failed, parse again
Hello,
We have a customer still using an old 7.3.0 SAPDB installation.
We modified the schema a couple of days ago to handle some new functionality.
Now we try to use the newly created tables we get.
432.488.0 16:41:00.265 (DS) Exception in commit (E_DATABASE Error executing "INSERT INTO C_PinRecord SET oid = ?,type = ?,acl = ?,version = ?,chipType = ?,cardNumber = ?,pin1 = ?,pin2 = ?,puk = ?": [SAP AG][SQLOD32 DLL][SAP DB] General error;-8 POS(1) Execution failed, parse again.)
The error is repeatable for every try.
My conclusion is that the catalog data is left in a bad state somehow. The customer is of course in another country
and I need to send some kind of procedure to try to recover.
Does anyone have any hints of the best procedure to follow to try to fix the error?
We have tried doing a database check without finding any problems.
Best Regards,
Stefan GustafssonThank you for your help.
The database version reports:
Kernel 7.3.0 Build 025-000-085-923
Runtime environment 7.3.0 Build 025-000-085-923
I know this is an old version, but all our customers is using the exact same version. We are now working on the
next version of our software there we use 7.7.06.09 instead.
In our system we use an ODMG mapping that creates tables and view for all classes we use. The problems started then
we added a new class in an update a couple of days ago.
During this update one new table and one new view was created in the database as:
CREATE TABLE T_PinRecord (
oid FIXED(10) KEY NOT NULL,
chipType VARCHAR(64),
cardNumber VARCHAR(64),
pin1 VARCHAR(32),
pin2 VARCHAR(32),
puk VARCHAR(32),
FOREIGN KEY (oid) REFERENCES T_Object (oid) ON DELETE CASCADE
CREATE VIEW C_PinRecord AS SELECT T_Object.oid,T_Object.type,T_Object.acl,T_Object.version,T_PinRecord.chipType,T_PinRecord.cardNumber,T_PinRecord.pin1,T_PinRecord.pin2,T_PinRecord.puk FROM T_Object,T_PinRecord WHERE T_Object.oid = T_PinRecord.oid AND T_PinRecord.oid = T_Object.oid WITH CHECK OPTION
The T_Object table is one of the main tables of the OR mapping and has been there since the installation.
CREATE TABLE T_Object (
oid FIXED (10,0) KEY NOT NULL,
type FIXED (21,11),
acl FIXED (21,11),
version FIXED (10,0),
FOREIGN KEY oid REFERENCES T_Oid (oid) ON DELETE CASCADE
CREATE TABLE T_Oid (
oid FIXED (10,0) KEY NOT NULL
We don't use dbprocedures and no other triggers except the ON DELETE CASCADE stuff.
I asked the customer to run two commands:
check table so.t_object catalog
check table so.t_pinrecord catalog
The first command failed with the -9404 error but the second one succeeded.
This was somewhat unexpected since the T_Object table is part of all views and I have no reports
that the system fails for normal use.
My plan was to drop the T_PinRecord table and view and recreate them, but now I'm not sure this will help.
Dropping the T_Object table is not possible since it will delete all objects in database.
I have asked the customer to take a complete data backup and send to us, hopefully we can export out
the data and reload it into a working instance.
Best Regards,
Stefan Gustafsson -
Sign in failed - Unknown server error (-2) when trying to sign in to new playbook
I get the message "Sign in failed - Unknown server error (-2)" when I try to login to the Blackberry ID page of a new playbook during initial setup. This prevents me from continuing and using my device. A similar error message appears when I tap "Forgot password?" which is An unknown error has occured. Please try again (-2)
I have tried what others have done when they have unknown error (-6) which is turn off playbook and plug into desktop manager then update to reflash, but I continue to get the same error.
I know my BB ID username and password are correct because I can login to the web with them. Not sure what to do next.Just to test the simple things first, did you try to sign in using another credential?
If only yours fails, then is a RIM issue, otherwise is indeed your Playbook failure.
--- Catalonia, next state in Europe ----
Use the "solved" or "Like" icons if my answer helped you.
BES10 administrator for several customers.
"SMPTE Calculator" timecode APP developer for BB10 -
The system failed to merge, error code : General Access denied
The system failed to merge, error code : General Access denied. Could anyone help me on this
Hi,
It could be several things, I think it could be a good start with the following page:
https://blogs.technet.com/b/chrad/archive/2009/10/02/differencing-disks-merging-80070005-error-just-one-persons-lesson-learned.aspx
If that doesn't help you could check out the following technet page to see if it is a permission problem. (it is not exactly the same problem but one of our customers once had the same problem and we solved it with the follwing KB:http://support.microsoft.com/kb/2249906/en-us
Hope this helps you out. -
Executable build failing with no error message with smtp email VIs
I have a VI which I want to build into a .exe which will be used as an HMI for a real-time system. I am using the SMTP VIs to text/email me various notifications about the system state. The main VI works fine if run but will not build into an .exe. The error message comes back blank so no help there (LabView 2010). If I just simply disable the portion of the code in the HMI.VI which contains the email VI code, the application builds. I searched for anwers and was unable to resolve the problem. Any ideas? Do I need to include anything in the build that is specific to the LabView SMTP VIs? I'm new to building .exe's so I appologize for any rookie mistakes I may have made.
Thanks.mikeporter wrote:
You said you searched for answers (on the forum?).
Yes.
What did you find?
I found a bunch of topics on email send errors after the application was built but nothing related to .exe building failures (related to the SMTP/email VIs). I also found topics dicussing the bug that fails to report an (any) error during the .exe build (for 2011). The solution was to install the service pack. if that's my problem then I will have to go through the motions to get that done (corporate computers / lack of persmissons and such).
What have you tried? This question has been answered many, many, many times.
I tried what I stated in the OP. If I disable the portion of the code which contains the email SMTP VIs, the application builds, otherwise, the build fails and no error code or description is given.
PS: probably has nothing to do with the SMTP drivers, per se.
If the answer has been given many, many times, then I appologize for not being able to find it before posting. Trust me, the last thing I want to is waste my time fishing for answers on the forum, especially when I get a response from forum members who would rather point out that my mis-identified problem has been answered many, many times, rather then just helping me out. -
Payables Open Interface Pgm fails without any error(Very urgent)
All,
I'm into an integration project where in I'm pushing Invoice doc from a third party appln to Oracle apps (11.5.10.2) thru payables open interface. The integration is smooth till today. We pushed a record today, but the concurrent neither picks up the data but failed with 'completed error' status. When I delete the same record from the interface, the concurrent runs fine. So we are sure there is some issue with the data in my record. Since concurrent is failed without any reason, from where I can get the log to know what is the actual problem with that record? Pls help me with your inputs.
Thanks,
SenSen,
To enable trace, please refer to this document (skip the part about generating TKPROF, just check the concurrent request output file if more details about the error are logged after enabling trace and setting the profile option).
Note: 453527.1 - How To Trace a Concurrent Request And Generate TKPROF File
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=453527.1
The database log file can be usually found under $ORACLE_HOME/admin/<SID>_<hostname>/bdump directory (or from SQL*Plus, issue "show parameter background_dump_dest").
Regards,
Hussein -
CMS import for SAP ESS component(SP 15) fails with fatal error.
Hi,
We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
20090610145206 Info :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
20090610145206 Info :Component:sap.com/SAP_ESS
20090610145206 Info :Version :MAIN_ERP05PAT_C.20090427083436
20090610145206 Info :1. propagation request is of type TCSSoftwareComponent
20090610145206 Info :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
20090610145232 Fatal :VcmFailure received
20090610145232 Fatal :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090610145232 Fatal :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090610145232 Info :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked with only the last sentence changed to:
Step Repository-check ended with result 'fatal error'
Can anyone help me on this.... ?
Thanks,
Sonali.
Edited by: Sonali M S on Jun 10, 2009 1:16 PMHi Bala,
The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
Can there be any other reason for this?
Thanks,
Sonali. -
Rendering of Proxies in AE fails with generic error messages.
*sigh* working with AVC in CS4 on my quad core has been an exercise in pain.
I've followed the optimization guides linked to in the different forum posts and that lets me zip along until I actually start adding effects. Then I am right back to a crawl. I recently discovered proxies in AE and learned that I can use "replace" in premeire to leverage those same proxies... Sweet... When I works I am back to editing in both in real time!
The problem is AE is regularly failing to generate proxies for me and I cannot figure out why. All my video is shot the same 24mbps, 60fps, 1080p (true 60i). All shot from my Canon HF S10.
The error is always "Error reading frame from file" and it always occurs just before the render is about to complete. Sometimes I get lucky and a working .mov was generated in spite of the error. Bu most times the file isn't there.
So my 2.4ghz quad core with 8gb ram can't edit the originals and I can't create proxies... I'm effectively dead in the water.
I tried using Media Encoder to generate my proxies with no success either. It fails with "Unspecified Error".
Both times I am trying to encode to Quicktime, Jpeg, Draft Settings. For the heck of it I tried different codecs, etc. Nothing seems to help. Even worse is sometimes if I just queue the same file multiple times it eventually works.
Is there anything at all I can do to make successful proxy generation less like winning the lottery?Yeah I updated to that right away. Premiere itself seems to behave most of the time. To be honest I've hardly had any problems with Premiere even before the 4.2 update.
But AVC (mts files) seem to be very problematic in AE in general. I also experience the issue mentioned here:
http://forums.adobe.com/message/2404464
Sounds like re-encoding to another format is the only way I'll be able to work in AE reliably. So I have to figure out a way to get Media Encoder to finish it's jobs.
Maybe you are looking for
-
Hi, I hv 2 plants say 1000 & 2000 In both plants products are define with 2 different catergories say Residential and Industrial. Now if m define order type as per above two category say Z001 and Z002 in both plants. so can it possible to give diffe
-
Sony - IC Recorder (ICD - PX312F)
Hello, I recently bought an audio recorder, model: DCI - PX312F to record an important meeting at work. Unfortunately when I looked for the audio file on my computer, i don't find it. I checked the recorder and the file disappeared. Probably it was d
-
HT4623 how do I restore a water damaged iphone?
I recently dropped my iphone 5 in water and did my best to dry it out. how do i restore it after that? now what?
-
It says my passcode is not valid and so my phone is disabled. How do I found out my pass code?
How do I found out my passcode if it says it is wrong?
-
Configuration Messaging 6 2005Q1 Error
Hi all, 1. I istalled Sun java messaging server 6. 2. I edit amsamplesilent to prepare amsamplesilent.my: # cd /opt/SUNWam/bin #mv amsamplesilent amsamplesilent.my 3. I configure Access Manager: #./amconfig -s amsamplesilent.my but get the following